Tiffany-- You are on the right track. The deciding point in your case is the "about" folder on the publication target, not the temp folder hierarchy.
As long as you do not clean out the folder on your Web server, the publication should go through. But if you wipe out that folder on the target, you would have to make sure the folder is created either manually or by publication first before you use the file name trick. Henry On Tue, May 4, 2010 at 4:34 PM, Tiffany <[email protected]> wrote: > Henry - If the RedDottemp folder is cleared out, will a double > publication catch the index? > What I mean is that if the list on the page defines the folder name > about, the first publication will likely try to publish index to about > without about existing yet. So there will be an error. But if I run > the publication again, maybe it will pick up on the second round? This > seems kind of messy, but perhaps an option. > > Let me know if I understand that incorrectly. > > On May 4, 4:09 pm, "Henry Lu a.k.a. Javahand" <[email protected]> > wrote: > > Tiffany-- > > > > If the folder exists in the target, you can simply prepend "about/" to > > index.html's filename and get it done. > > > > Henry Lu > > > > > > > > On Tue, May 4, 2010 at 3:07 PM, Tiffany <[email protected]> wrote: > > > I think this question has been asked, maybe even by me, but I am still > > > without a comfortable solution for publishing directory indexes. > > > > > For instance, a page named About should be published as about/ > > > index.html. But the publication package is attached to a list on that > > > page and therefore the homepage for About is one level too high to be > > > published in the correct directory. > > > > > Does anyone have any helpful hints on how to do this on the backend > > > (without editing reddottemp folder on the server or making users > > > attach the page twice)? > > > > > -- > > > 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]<reddot-cms-users%[email protected]> > <reddot-cms-users%[email protected]<reddot-cms-users%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/reddot-cms-users?hl=en. > > > > -- > > 646-807-8683 > > > > -- > > 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]<reddot-cms-users%[email protected]> > . > > For more options, visit this group athttp:// > 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]<reddot-cms-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/reddot-cms-users?hl=en. > > -- 646-807-8683 -- 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.
