[wp-trac] [WordPress Trac] #16379: Better UI for doing "Page on Front"
WordPress Trac
wp-trac at lists.automattic.com
Thu Oct 11 15:29:19 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 lessbloat):
Replying to [comment:76 nacin]:
> 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.
Right, I don't think we should publish an existing non-published page
without them knowing. My gut says that throwing an error would be the
best approach. Something along the lines of "You'll need to __publish
your "blog" page__ before you can use it for your latest posts page.".
Mostly because personally I'd never want my blog directory to be blog-2.
> * 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.
Seems odd to me that a user could manage options, but not have access to
edit pages. Regardless, should a user have access to settings, and not
have access to edit pages, I'd just treat it the same as we're treating
users who can't create pages (just don't show the "Add new page" drop down
option). It seems like such an edge case, that I'd hate to see us add any
more code than that to handle it.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/16379#comment:81>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list