Ed, That's what I thought was happening, and now it's clear. Thank you so much for the link, which was very insightfull. My douplication days are over!
-galactic On Nov 3, 9:51 am, "[email protected]" <[email protected]> wrote: > I had a similar problem years ago. > > I named the site index page "index" and have the rest of the subfolder > indexes being published as "default.asp". > > I then told the web server to serve index over default. > > Of course, this doesn't mean that one default can't be published over > another though, in which case, you may want to take a look at > this:http://www.reddotcmsblog.com/duplicate-content-publishing-seo-and-ope... > > Ed > > On Nov 3, 9:21 am, galactic <[email protected]> wrote: > > > > > Thanks for your input. Yes I am using multiple publication packages > > allready. Some users mistakenly have been connecting existing instead > > of referencing sub pages. When publishing related pages, It's like Red > > Dot can't find the folder of the publication package and just dumps it > > into the root directory. > > > I do think you answered my question though, Connect Existing should be > > only used for new pages, not pages somewhere else in the structure > > right? Unfortunately I don't see a way to keep people from using this > > instead of referencing a page, there doesn't seem to be a way with > > authorization packages. If you know of a way, please pass it on. > > > Thanks! > > > -galactic > > > On Nov 2, 1:41 pm, Tiffany <[email protected]> wrote: > > > > Arsalan is right, use multiple publication packages, and the index > > > will become the index of each new folder in your structure. > > > Connect Existing will publish NEW pages. > > > If you want the page to publish to one spot, and then link to that > > > original page, then you need to reference the page not connect > > > existing. > > > > On Nov 2, 12:03 pm, Arsalan <[email protected]> wrote: > > > > > Someone correct me if I'm wrong but from my limited Reddot experience, > > > > my guess is that you'll need to create separate publication packages > > > > for each directory. That way all the pages along with respective > > > > index.html pages will be published inside their own folder and won't > > > > overwrite other files. > > > > > ________________________________ > > > > From: galactic <[email protected]> > > > > To: RedDot CMS Users <[email protected]> > > > > Sent: Mon, November 2, 2009 10:44:52 AM > > > > Subject: Referencing vrs Connecting a page. Red Dot 7.5 > > > > > Any comments would be appreciated. > > > > > I am working on a site with lots of folders in it. all of the folders > > > > have index.html pages in them. When red dot users "connect an existing > > > > page" (that is named index) on a related link, at publishing it > > > > produces an error that reads something like "can't find the ___ > > > > directory, publishing to the root directory". Then it overwrites the > > > > home index page!! I started recommending the users use "Reference a > > > > Page" instead. > > > > > My question is : Can I stop Red Dot from publishing to the root > > > > directory if there is such an error? Is what's happening the fact the > > > > connecting an existing page is altering the structure somehow, and > > > > referencing a page does not? What are the major differences between > > > > the two? > > > > > I tried using authorization packages to stop the ability to connect to > > > > existing pages from the module, but it takes out referencing a page as > > > > well. > > > > > Thank you for any insight. > > > > > -galactic- Hide quoted text - > > > > - Show quoted text -- 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 -~----------~----~----~----~------~----~------~--~---
