oh my what a pain, thanks for sharing. On Jun 2, 12:03 pm, Kelly <[email protected]> wrote: > Realize this is an old post but I had exact same problem today using > RedDot 7.5 and this is how I solved it. Posting here b/c I could not > find answers anywhere and this may help someone else who's "tearing > their hair out" like I was :) > > My page 6331 was ignoring its publication package and overwriting our > main corporate homepage at the Root level. NOT GOOD! > > ERROR message found in Publishing Log: “Page 6331 is not linked in > HTML/ENU” (HTML/ENU is name of our Project Variant). > > Weirder still, this page 6331 was like a "ghost page" - if I did a > Search for the page ID, I could get to it easily and see it connected > as a page beneath an anchor reference, which was referenced to the > same page. But if I then expanded and contracted the anchor link, the > page 6331 completely DISAPPEARED from the tree. Only way to see it > again was to pull it up from the clipboard. > > Reasons were: > 1) The bad page 6331 had the SAME header name and the SAME > filename as > its twin, the “good homepage” > 2) The bad page was not actually linked anywhere in the project > tree > but kept showing up. > 3) We tried again and again to delete it from everywhere it was > referenced. But b/c it had same header & filename as a good page, we > could not delete the reference that we NEEDED to get rid of. > 4) Finally, we renamed the headline of the "bad" page and gave it > a > different filename. THEN we were able to delete it, no problem. > 5) When we did a search for Page ID 6331 then and did "Display > reference in tree", we saw it was now in the Recycle Box, which is > where it should have been from the start. > 5) We could now go to our "good" homepage and publish it. No > longer > did our good or bad homepage overwrite our Root homepage. > > My advice: > 1) Do a search in your project for any page where [headline=(your bad > page headline here)] and check EACH of those pages that come up. Esp > do the > "Display reference in tree" for each of them so you can see where they > 'live' > in your project. > > 2) Find out the filename you have set for this 'bad' page. While on > the Project node, select "Display all filenames" and scroll down to > that filename. This shows you all pages in tree that have THAT > filename assigned and doubtless you have more than 1 such filename in > there. > > One or both of the above will confuse RedDot - or at least this was > the case for us. > > Hope this helps someone. > > Best, > ~Kelly
-- 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.
