Hello from the other side of the pond. Many things are happening here.
First thing you want to do is disable that do not publish with leading /. You do want relative pathing from the root of your domain. I have that product page isn't connected to multiple locations. Multiple connections with multiple publication package equals the same page get published to multiple locations. Link generated by navigation manage always go by the mainlink location. You may then asked, "fine, why is the page still missing from root then?" You are missing <!-- <iorangelist><%lst_navigation%></iorangelist> --> In all your foundations, that may possibly (though unlikely) links to page generated, but page builder was never able to crawl the list that page is connected to (because it is not in the code) and publish that page. Dumping all the info via iPhone and 2 thumbs. Let us know of any of that info helped fix the issue Sent from my iPhone On Mar 20, 2013, at 8:37 PM, redDolt <[email protected]> wrote: > Hello all, > > Decloaking to see if anyone can offer some advice on resolving linking issues > on sub pages within a delivery server publication folder structure. I looked > here and on the solution exchange but didnt see anything that quite matched > up to what we are experiencing. > > We are publishing pages from CMS into delivery server and assets into our web > server. Currently, our site structure is essentially all .htm pages being > dumped into a "root" folder. For SEO reasons, we want to change it so that > our stucture resemples our product structure more accurately. > > ex: we would like > http://www.multiquip.co.uk/mikasa-MTX60-rammer.htm to become > http://www.multiquip.co.uk/construction-solutions/rammers/mikasa-MTX60-rammer.htm > > I have figured out how to accomplish this using publication packages applied > at different levels of the site and inherited down and got everything to > appear in the proper place within delivery server and on the web server. > > Unfortunately, this appears to break some of our hrefs. > > We have a set of button pages within a container element that are common to > all product pages linking people to our main solution lines, which are are > referenced back to the home page where they first appear. > > With the sub-directory publishing enabled, the deeper down the site you get > (like on the mikasa-MTX70-rammers.htm page) the browser ends up translating > the construction solutions button link as > www.multiquip.co.uk/construction-solutions/rammers/construction-solutions.htm > instead of just www.multiquip.co.uk/construction-solutions.htm (the actual > valid link), which is an error and produces a file not found screen. The same > thing is occurring with our navigation manager produced site navigation at > the top and some of the media elements. I have “do not publish leading /” > unchecked so I assume CMS should be taking into account when a back link > should be appropriate and indeed, it is working correctly for image assets > and even pdfs pulled from content server, just not hrefs. > > I'm not sure right now what other information would be useful so please let > me know what else i can provide that would be helpful. Seeing as the page is > publishing out to the right locations and is mostly correct, lve got to > assume i'm just missing something stupid. > > Thank you! > > DP > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
