Skip to content

Ensure page for posts and page on front are not set to the same page#22

Merged
westonruter merged 3 commits intodevelopfrom
feature/ensure-distinct-pages-for-front-and-posts
Sep 11, 2016
Merged

Ensure page for posts and page on front are not set to the same page#22
westonruter merged 3 commits intodevelopfrom
feature/ensure-distinct-pages-for-front-and-posts

Conversation

@westonruter
Copy link
Copy Markdown
Contributor

@westonruter westonruter commented Sep 11, 2016

Improves the UX by eliminating the possibility an error scenario:

reading_settings_ _wordpress_develops_ _wordpress

Without object selector, a notification should be displayed when these are selected to be the same. Either that, or the option element should be disabled in one or the other if they are regular dropdown-pages controls. In any case, the object selector control short-circuits this from even being an issue:

browsing for home

searching for home

In both these cases, the page “Home” is not listed in the selector for Page for Posts because it has already been selected as the Page on Front.

Short demo video: https://youtu.be/lDYN2cWczT8

This is to ensure that Customize Posts will have ensured the existence of the static front page section
This ensures that the params can continue to be edited from the control level, without having to wait for the component to be initialized
@westonruter westonruter merged commit 47bdc68 into develop Sep 11, 2016
@westonruter westonruter deleted the feature/ensure-distinct-pages-for-front-and-posts branch September 11, 2016 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant