[wp-trac] [WordPress Trac] #21665: Allow non-editable pages to be classified & organized as "System Pages"
WordPress Trac
wp-trac at lists.automattic.com
Thu Aug 23 09:08:26 UTC 2012
#21665: Allow non-editable pages to be classified & organized as "System Pages"
--------------------------------------+------------------------------
Reporter: bootsz | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: UI | Version:
Severity: normal | Resolution:
Keywords: dev-feedback ui-feedback |
--------------------------------------+------------------------------
Description changed by SergeyBiryukov:
Old description:
> We currently have no means of distinguishing regular “content” pages
> (pages that users can edit) and pages that are used as placeholders for
> custom templates / dynamic content.
>
> As alexking mentions in [http://core.trac.wordpress.org/ticket/17470
> #17470], users are often confused when they attempt to edit these
> "placeholder" or "dummy" pages only to find that the pages appear empty
> from within the page editor.
>
> While his ticket concerned the "page_for_posts" page specifically, this
> issue is equally relevant to custom page templates that do not make use
> of user-generated content via the page editor.
>
> isaackeyet proposed a solution
> [http://core.trac.wordpress.org/ticket/17470#comment:4 in that ticket]
> which introduces the idea of classifying such pages as "System Pages",
> which would offer a more limited set of options for how they can be
> changed:
>
> >Idea to solve this permanently as brought up in the UI chat July 10
> 2012:
> >
> >* Pages have a new, hidden meta field to indicate "System Page" or
> >something that better describes it. Pages are marked System Page when
> >WP is using it as a placeholder for a custom blog set up, or a plugin
> >can use it to indicate a page is used for a contact form (for >example).
> >* Pages are highlighted with a meta description in the pages list,
> >indicating why it's there (created by? reason?)
> >* Most importantly, these System Pages are grouped in the pages >filter
> to be excluded from the regular list, so the list may read >"All |
> Published | System Pages", which should be a better long term >solution
> for this ticket specifically (user confusion).
New description:
We currently have no means of distinguishing regular “content” pages
(pages that users can edit) and pages that are used as placeholders for
custom templates / dynamic content.
As alexking mentions in #17470, users are often confused when they attempt
to edit these "placeholder" or "dummy" pages only to find that the pages
appear empty from within the page editor.
While his ticket concerned the "page_for_posts" page specifically, this
issue is equally relevant to custom page templates that do not make use of
user-generated content via the page editor.
isaackeyet proposed a solution
[http://core.trac.wordpress.org/ticket/17470#comment:4 in that ticket]
which introduces the idea of classifying such pages as "System Pages",
which would offer a more limited set of options for how they can be
changed:
>Idea to solve this permanently as brought up in the UI chat July 10 2012:
>
>* Pages have a new, hidden meta field to indicate "System Page" or
>something that better describes it. Pages are marked System Page when >WP
is using it as a placeholder for a custom blog set up, or a plugin >can
use it to indicate a page is used for a contact form (for >example).
>* Pages are highlighted with a meta description in the pages list,
>indicating why it's there (created by? reason?)
>* Most importantly, these System Pages are grouped in the pages >filter
to be excluded from the regular list, so the list may read >"All |
Published | System Pages", which should be a better long term >solution
for this ticket specifically (user confusion).
--
--
Ticket URL: <http://core.trac.wordpress.org/ticket/21665#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list