Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Sync page changes to Static Front Page section controls; prevent same page from being used as both page for posts and page on front #270

Conversation

westonruter
Copy link
Contributor

Continuation of #190.

Fixes #153.

…e_on_front & page_for_posts

* Ensure that the settings associated with the dropdown-pages controls get cleared if trashed pages are selected.
* Show "(no title)" in option if no page title is supplied.
* Use jQuery selectors instead of iteration.
* Show (Trashed) with pages in dropdown-pages options that are disabled ].
pageOption.text( optionText );
}

// @todo In the case of page_on_front and page_for_posts, this should only be done if it wouldn't mean that they can be set to the same. See https://github.com/xwp/wp-customize-object-selector/pull/22
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be handled with a new integration specific for these two settings, at the component level itself.

@westonruter westonruter changed the title Fix: Sync page changes to Static Front Page section controls Sync page changes to Static Front Page section controls; prevent same page from being used as both page for posts and page on front Sep 17, 2016
@westonruter westonruter merged commit f523e8b into develop Sep 17, 2016
@westonruter westonruter deleted the feature/sync-page-changes-to-static-front-page-section-controls branch September 17, 2016 01:44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant