I've just noticed that some of our content has somehow changed to using the page id as the url and not friendly urls. I do know that some of the content was inadvertantly deleted by one of our editors (I know, lesson learn there!) and after restoring it id's appeared instead of the usually friendly url, strangely other content that has been deleted and since resurrected the friendly url was retained.
Any pointers anyone?
We're using Umbraco v
4.0.4.2 (Assembly version: 1.0.3811.17115)
1) Right click the root node of the homepage and select "publish" 2) Go to the "Content" node (the first node in the tree that is always there) and republish the entire site
After doing this does the error still persist?
And it's not because you're previewing the nodes that the id is being displayed?
Thanks Jan, I'll give that ago. Might have to do it out hours though since our site currently has well over 20,000 pieces of content, so quite a large site to republish.
Previous friendly urls now turned to page id's
Hello,
I've just noticed that some of our content has somehow changed to using the page id as the url and not friendly urls. I do know that some of the content was inadvertantly deleted by one of our editors (I know, lesson learn there!) and after restoring it id's appeared instead of the usually friendly url, strangely other content that has been deleted and since resurrected the friendly url was retained.
Any pointers anyone?
We're using Umbraco v 4.0.4.2 (Assembly version: 1.0.3811.17115)
Cheers
Pete
Hi Pete
Have you tried doing the following
1) Right click the root node of the homepage and select "publish"
2) Go to the "Content" node (the first node in the tree that is always there) and republish the entire site
After doing this does the error still persist?
And it's not because you're previewing the nodes that the id is being displayed?
/Jan
Thanks Jan, I'll give that ago. Might have to do it out hours though since our site currently has well over 20,000 pieces of content, so quite a large site to republish.
Cheers
Pete
is working on a reply...