{"action":"created","issue":{"url":"https://api.github.com/repos/backdrop/backdrop-issues/issues/1615","repository_url":"https://api.github.com/repos/backdrop/backdrop-issues","labels_url":"https://api.github.com/repos/backdrop/backdrop-issues/issues/1615/labels{/name}","comments_url":"https://api.github.com/repos/backdrop/backdrop-issues/issues/1615/comments","events_url":"https://api.github.com/repos/backdrop/backdrop-issues/issues/1615/events","html_url":"https://github.com/backdrop/backdrop-issues/issues/1615","id":133544836,"number":1615,"title":"[UX] Provide a UI for selecting regions for any blocks that are orphaned during layout design change.","user":{"login":"klonos","id":2423362,"avatar_url":"https://avatars.githubusercontent.com/u/2423362?v=3","gravatar_id":"","url":"https://api.github.com/users/klonos","html_url":"https://github.com/klonos","followers_url":"https://api.github.com/users/klonos/followers","following_url":"https://api.github.com/users/klonos/following{/other_user}","gists_url":"https://api.github.com/users/klonos/gists{/gist_id}","starred_url":"https://api.github.com/users/klonos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/klonos/subscriptions","organizations_url":"https://api.github.com/users/klonos/orgs","repos_url":"https://api.github.com/users/klonos/repos","events_url":"https://api.github.com/users/klonos/events{/privacy}","received_events_url":"https://api.github.com/users/klonos/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-14T14:33:53Z","updated_at":"2016-02-16T20:33:35Z","closed_at":null,"body":"In the default layout, if you switch from the default \"2 columns\" template/design to the \"2 columns flipped\", the user login block that resides in the sidebar is preserved, but if you switch to the \"1 column\" design, the block disappears. If you now switch back to any of the \"2 columns\" or \"2 columns flipped\" design, the sidebar region is empty and the user login block gone.\r\n\r\nWe should warn users about the blocks that are going to be removed/lost from the action of changing a layout design with different regions. I think a confirmation page is in order here with a list of block names with the respective region in parenthesis.\r\n\r\nIdeally though, we should also give the chance for users to place the blocks to the available regions in the new design instead of simply removing them. So, next to each block to be removed in the confirmation page list, we should also have drop-downs with all the available regions in the new design to be selected.\r\n\r\nEven more ideally, instead of drop-downs and a separate confirmation page, we would have the new design displayed with its regions and the blocks that were preserved, plus an additional area on the side (a \"pseudo-region\" if you like, like the one that @quicksketch suggested for the page title in #952, marked with a red border perhaps) that holds all the blocks to be removed with a help text along the lines of:\r\n\r\n\"The new design that you have selected for the [layout_name] layout has different regions than the previous design. As a result, the blocks listed below are left without a region. Please select any of them that you wish to keep in the new design and drag it to the new available regions.\"\r\n\r\nUX++"},"comment":{"url":"https://api.github.com/repos/backdrop/backdrop-issues/issues/comments/184864682","html_url":"https://github.com/backdrop/backdrop-issues/issues/1615#issuecomment-184864682","issue_url":"https://api.github.com/repos/backdrop/backdrop-issues/issues/1615","id":184864682,"user":{"login":"klonos","id":2423362,"avatar_url":"https://avatars.githubusercontent.com/u/2423362?v=3","gravatar_id":"","url":"https://api.github.com/users/klonos","html_url":"https://github.com/klonos","followers_url":"https://api.github.com/users/klonos/followers","following_url":"https://api.github.com/users/klonos/following{/other_user}","gists_url":"https://api.github.com/users/klonos/gists{/gist_id}","starred_url":"https://api.github.com/users/klonos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/klonos/subscriptions","organizations_url":"https://api.github.com/users/klonos/orgs","repos_url":"https://api.github.com/users/klonos/repos","events_url":"https://api.github.com/users/klonos/events{/privacy}","received_events_url":"https://api.github.com/users/klonos/received_events","type":"User","site_admin":false},"created_at":"2016-02-16T20:33:35Z","updated_at":"2016-02-16T20:33:35Z","body":"> For simplicity though, couldnt we just pile all 'leftover' blocks that have lost their region into the main, or some other region? The user can then just drag and drop them to an appropriate region or delete them.\r\n\r\nWe could implement this as a quick intermediate solution. Although moving orphaned blocks to a random/arbitrary region without any other indication of this action is an improvement over removing them completely, it still is not perfect.\r\n\r\nWe could for starters go on with the simple, intermediate solution of having orphaned blocks moved to the main content area (or any other existing region we decide), but if we stop there I see this as solving a buggy behavior by replacing it with another bug (blocks lost/data loss vs. blocks moved to random region).\r\n\r\nI guess it won't be much of an issue with simple cases where the only block that was in the content region was the \"Main content\" block, but it might get worse with more elaborate designs. So lets then do either of these:\r\n\r\na) warn the user with a list of blocks that will be left orphans by changing the layout design and more importantly, tell them in which region we will be moving them to.\r\n\r\nb) move these blocks into a temporary pseudo-region and visually indicate it (emphasis with a red border?).\r\n\r\nOut of the two choices above, of course I prefer the second because we do not make the user remember which blocks were left orphans and we don't mix them with other blocks in the main content area. We clearly move them in a separate place. But I understand if implementing such a solution (the pseudo-region thing) is hard. Just thought that if we do implement such a region for #952, then we could reuse it for this case too."}}