[wp-trac] [WordPress Trac] #16379: Better UI for doing "Page on Front"
WordPress Trac
wp-trac at lists.automattic.com
Wed Oct 10 19:17:37 UTC 2012
#16379: Better UI for doing "Page on Front"
----------------------------------+------------------
Reporter: markjaquith | Owner:
Type: task (blessed) | Status: new
Priority: normal | Milestone: 3.5
Component: Administration | Version: 3.1
Severity: normal | Resolution:
Keywords: jane-likes has-patch |
----------------------------------+------------------
Comment (by nacin):
Replying to [comment:75 lessbloat]:
> For page_for_posts, I think we need to use the existing blog page if one
exists.
>
> Rationale:
>
> - First, doing this shouldn't pose a problem for new users.
> - For existing users with pages, there would be no way to select an
existing page otherwise.
>
> Thoughts?
So, that makes sense. But the @todo brings up a few other questions:
* What if the existing page we find isn't published? Even if the user
*can* publish pages (and they might not be able to), we probably shouldn't
publish a non-published item. (3.4 only allows published pages to be
selected.) At that point, we might need to settle for `blog-2`. We *could*
show a conflict note if we detect one.
* What if the existing page can't be edited by the user? That means they
can't change the title or slug. If for some reason, the user can't
*create* pages, I've already coded it so a dropdown shows of existing
pages. We might need to do the same for when the user can't edit pages
either.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/16379#comment:76>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list