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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
