The state keywords idea did occur to me but there is one snag there: a way to apply keywords to pages en masse. That is, there are a few hundred pages already in the system and they should all default to "Needs review". Is there a quick way to apply that keyword to all of them or does it need to be assigned individually?
I like the nav manager suggestion and will pursue that for now, though it does leave open the question of how to handle pages that aren't in nav manager, such as news lists. I take the silence to mean that there is no way to search on the contents of a particular placeholder within the CMS or to add it to the index. On Sun, Sep 30, 2012 at 5:54 PM, Tony Gayter <[email protected]> wrote: > A quick way to do this would be to have state keywords and pull these into > lists on pages outside of the site (eg onto admin pages). > > Or you could use nav manager to go through all the pages and depending on > the selected state add it to the output. > > The second suggestion would probably be a much cleaner way to do it > On Sep 30, 2012 9:41 PM, "NP" <[email protected]> wrote: > >> I've set up an option list field for all pages in a project that can be >> used to identify the "state" of a page. That is, you can select options >> like "Needs Revisions", "Candidate for removal", etc. Content authors need >> to be able to get at a list of all pages matching a particular status so >> that they can run down the list and make revisions to the pages that need >> them. At first I thought that we might be able to do this with Management >> Server's built-in search functionality by giving the option list values >> that are highly unlikely to show up in web content. So I created a custom >> search using "content" as the search criteria, but it seems that option >> list values aren't searched by this. Is there a way that authors can easily >> search for option list values? Or maybe someone can recommend another way >> to implement this? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "RedDot CMS Users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/reddot-cms-users/-/mJSC6BHUC0oJ. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/reddot-cms-users?hl=en. >> > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/reddot-cms-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
