0

I have created an enterprise wiki site collection inside SharePoint server 2013, and I have defined managed navigation inside the Global Navigation as follow:-

enter image description here

Then I created a new wiki page named Test , where the physical url will be:-

http://***/sites/testf/Pages/test.aspx

And the friendly url will be :-

http://***/sites/testf/test 

After that I edit the wiki page name & title to be TestUpdated instead of test, but now I will get the page physical url as :-

http://***/sites/testf/Pages/testupdated.aspx

But the problem is that its friendly url will not get updated accordingly, and it will still referencing the old name:-

http://***/sites/testf/test

So why the friendly url did not get the new name and title , is there a reason for this? Can anyone advice on this please?

  • 1
    Because the friendly URL is based on terms, and the name of the terms (not the page). So you also need to rename the term if you rename a page – Robert Lindgren Jun 26 '15 at 11:24
  • @RobertLindgren but seems this is a long process for end users to do , they will expect renaming a wiki page will do all of these. For example when i first deploy the site we realize that when updating the wiki page name its title will NOT get updated,, , so i wrote a workflow that will update the wiki page title when its name is changed.... but now there is also the friendly urls ,,, – john Gu Jun 26 '15 at 11:43
  • 1
    I think you need to think about what you are trying to achive. When we work with friendly URLS (managed navigation) we do this because there also is a term structure that is used for tagging documents or something that should be visible based on the current pages friendly url (term). Otherwise, it is a bit more tricky to work with. Also note that using a termset gives you the possiblity to create a "virtual" hierarchy of tha pages wihout subsites – Robert Lindgren Jun 26 '15 at 11:51
  • 1
    We do that in another way – Robert Lindgren Jun 26 '15 at 12:11
  • 1
    Nope, then you do not used managed navigation, but activates the (enterprise only) managed metadata navigation in the actual pages library – Robert Lindgren Jun 26 '15 at 13:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.