After upgrading a 6.0.3 site to 6.1.2.2 and republishing, I now have two nodes (home & settings) showing "(1)" after them. Even if I change the Name value in the Properties tab, it still says "Home (1)" or "Settings (1)". Is there anyway to sort this out?
Thanks kipusoep. Sorry but I don't know what to do with the information? I only upgraded from NuGet yesterday so wouldn't that have included the fix? If not, what do I do now?
Thanks kipusoep. Sorry but I don't know what to do with the information? I only upgraded from NuGet yesterday so wouldn't that have included the fix? If not, what do I do now?
Sorry.
Craig
P.S. Got round the immediate issue by renaming my two nodes "Home Page" and "Site Settings". That way they weren't the same as the nodeTypeAliases of "Home" and "Settings".
Great, Thanks. Couldn't work it out from the info on the left, it was kind of contradictory to the uninitiated (no affected versions, no fix submitted, due in V6.1.3) ;)
Home (1) ?
After upgrading a 6.0.3 site to 6.1.2.2 and republishing, I now have two nodes (home & settings) showing "(1)" after them. Even if I change the Name value in the Properties tab, it still says "Home (1)" or "Settings (1)". Is there anyway to sort this out?
Thanks,
Craig
http://issues.umbraco.org/issue/U4-2458
Thanks kipusoep. Sorry but I don't know what to do with the information? I only upgraded from NuGet yesterday so wouldn't that have included the fix? If not, what do I do now?
Sorry.
Craig
Thanks kipusoep. Sorry but I don't know what to do with the information? I only upgraded from NuGet yesterday so wouldn't that have included the fix? If not, what do I do now?
Sorry.
Craig
P.S. Got round the immediate issue by renaming my two nodes "Home Page" and "Site Settings". That way they weren't the same as the nodeTypeAliases of "Home" and "Settings".
It means it's a known bug in v6.1.2 and is fixed in v6.1.3, which should be released Thursday the 25th: http://our.umbraco.org/contribute/releases/613
Great, Thanks. Couldn't work it out from the info on the left, it was kind of contradictory to the uninitiated (no affected versions, no fix submitted, due in V6.1.3) ;)
Cheers,
Craig
is working on a reply...