Jian, the plugin option is very attractive very, very close to what I'm looking for. I installed the plugin and tested it out. It seems to only give search results for items with an option list value that has been explicitly selected by a content author. That is to say, it doesn't pick up default values. Since this field has just been introduced, just about every page on the site has a default value assigned and the problem is similar to the retroactive keyword problem.
Is there a way to make this plugin see default values? I would prefer to use the plugin method as it integrates very nicely with the structure we've already got. Otherwise it sounds like keyword + retroactive keyword plugin will do the trick with minimal changes. On Mon, Oct 1, 2012 at 12:46 PM, Jian Huang <jhuangsoftw...@gmail.com>wrote: > Hi, > > First solution: you can preassign keywords to content classes, so when a > page is created, it automatically inherits the keywords. What about > existing pages? Well, there is a plugin that retro active applies back the > keywords. > > Second solution: I was going to say, what about pages that are not in > navigation manager? What if i have 3000+ pages in navigation manager and I > started the search, any way to cancel it? There isn't any way to cancel > manager, then the server perform just goes down until that is done. Also, > using the navigation manager method would need to use Elements.GetElement() > rendertag, which causes enormous memory consumption, known to introduce > other project performance issues. > > Third option: Please find attached a plugin I wrote that is 7.x to 10.x > compatible that find page instances with specific option list value. > Import plugin, activate it, assign to project. Go to the content class you > want to search, expand content elements, select the option list, find > plugin link at bottom of action menu. > > Best, > > -Jian > > > On Monday, October 1, 2012 11:39:45 AM UTC-4, NP wrote: > >> 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 <tonyg...@gmail.com> 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" <napa...@gmail.com> 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<https://groups.google.com/d/msg/reddot-cms-users/-/mJSC6BHUC0oJ> >>>> . >>>> To post to this group, send email to reddot-c...@googlegroups.**com. >>>> To unsubscribe from this group, send email to reddot-cms-use...@** >>>> googlegroups.com. >>>> >>>> For more options, visit this group at http://groups.google.com/** >>>> group/reddot-cms-users?hl=en<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 reddot-c...@googlegroups.**com. >>> To unsubscribe from this group, send email to reddot-cms-use...@** >>> googlegroups.com. >>> >>> For more options, visit this group at http://groups.google.com/** >>> group/reddot-cms-users?hl=en<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 view this discussion on the web visit > https://groups.google.com/d/msg/reddot-cms-users/-/Vf7VzQ0SGU4J. > > To post to this group, send email to reddot-cms-users@googlegroups.com. > To unsubscribe from this group, send email to > reddot-cms-users+unsubscr...@googlegroups.com. > 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 reddot-cms-users@googlegroups.com. To unsubscribe from this group, send email to reddot-cms-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
