Another option you might want to consider (which doesnt involve RQL)

If your project is relatively small (say less than 50-100 pages) then
perhaps you could use keywords. If you are able to preassign a new
keyword (say 'recent updates'') to all pages in your project (there is
a plugin you can download and install from the community site which
can do this for you) as well as the content classes whereby new pages
will be created from.

This will enable you to target any specific (foundation) pages in your
site that you want to be listed in the top 5 updated pages list.

All you need to do then is create a new page for the top 5 list, apply
the keyword to the list placeholder on the page (which will then
automatically pull in all the pages in your project) Then apply a sort
filter on the list to only show the top 5 pages, sorted by last update
date.

Another advantage of this keyword method, is that whenever the
'Publish Related Pages Checkbox' is selected - your top 5 list page
will automatically be published by the CMS. (so you dont need to worry
about any fancy publishing jobs to republish this page.)



On Dec 16, 3:58 am, AnthonyFusepoint <[email protected]>
wrote:
> Hi Simon,
>
> here i am, needing a tool like yours!! :)
> We would like to display the ID of the current page in Smart Edit mode
> in order customers to know which page they are really going to
> publish.
> Problem is almost the same as yours, finding the page which is really
> going to be published!
> I'm going to open a RedDot ticket for that because a manual script
> seems way too complicated!! There are so many ways to implement pages
> in RedDot solution!
> It seems to me that RedDot should be able to give us this tool..!
> Hope Brett finally got her solution!
> Best regards
>
> Anthony
>
> On 25 nov, 04:33, "Simon Lewis, UK" <[email protected]>
> wrote:
>
>
>
> > Hi Anthony,
>
> > Fair enough -- I suppose it depends what your spec said.  Mine was for
> > a "What's New?" section on the front page of the intranet site, so
> > that people could see what new pages had been added, and click the
> > links to go direct to the new page.  Obviously if it wasn't a 'real'
> > page that had been added, the user would get a 404 so that was no good
> > in my case.  Hopefully Brett doesn't need to go to the same lengths
> > that I did :o)
>
> > All the best,
>
> > Simon.
>
> > On Nov 24, 3:53 pm, AnthonyFusepoint <[email protected]>
> > wrote:
>
> > > Hi,
>
> > > I didn't see this request so complicated!
> > > Simon, in 2), you explain that you want to find the main page for each
> > > "so called page" in RedDot. You may have needed what you developed,
> > > but i think the real interest in developing such a tool is to know
> > > which page was modified in redDot, I mean the page as RedDot calls it,
> > > an instance from a template. As you just said you had to look for
> > > every instances of your page if It's not linked only once,
> > > keywords...that's a huge and useless job in my opinion even if I see
> > > what you wanted, and i understand better that performances can be
> > > affected. I think the "RedDot Page" 's principle must be kept in mind
> > > the most you can in order not to be overstressed with developing a
> > > tool as Simon did. When I think about the "real" (HTML/ASP/PHP) page
> > > with RedDot is just when i publish any page, I have to know exactly
> > > what will be really published (not always so easy!!).
>
> > > Well, Brett you have two different solutions! ;) Mine is of course way
> > > easier but depending on what you really need Simon's one can be
> > > needed.
>
> > > Anthony- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to