U6 : New Bug - Rename Content and Sort uses old name
On acompletely fresh install of Final Release of V6, if you rename a content node and then right click the parent node (in my case "home") and select sort, the sort window displays the old content title. Leaving screen to go to Media/Settings and coming back and issue still persists. Went into site running 4.11.3 and issue is not present so it's something newly introduced in version 6.
On a related note, the forums would be much easier to navigate and be more useful if they were broken down by version at a higher level. It's very hard to see if an issue has been reported before for a new version like 6 when the only place to post bugs is the same place that hundreds/thousands of v4 bugs have been reported.
U6 : New Bug - Rename Content and Sort uses old name
On acompletely fresh install of Final Release of V6, if you rename a content node and then right click the parent node (in my case "home") and select sort, the sort window displays the old content title. Leaving screen to go to Media/Settings and coming back and issue still persists. Went into site running 4.11.3 and issue is not present so it's something newly introduced in version 6.
On a related note, the forums would be much easier to navigate and be more useful if they were broken down by version at a higher level. It's very hard to see if an issue has been reported before for a new version like 6 when the only place to post bugs is the same place that hundreds/thousands of v4 bugs have been reported.
Regards,
Phill
Update: clearning browser cache did not resolve issue either, incorrect name still displayed.
Forum Bug: Not able to edit a forum post, get following error: Error parsing XSLT file: \xslt\forum-commentsList.xslt
We have the same problem.
It seems like the rename-method only change the text-property in dbo.cmsDocument, but Sort uses the Text-property in dbo.umbracoNode.
This can fix your problem until a real fix comes.
update dbo.umbracoNode set text = (SELECT text from cmsDocument C Where nodeid= 1179 AND published != 0) WHERE id= 1179
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.