Unable to save or update pages(documents) when nodealias > 50 chars - after upgrading to K8.2

Olivier Cozette asked on January 26, 2015 14:47

After upgrading to 8.2, I'm not able to save or update documents when the nodealias is greater than 50 chars. ---- I was able to do so in 7...

I have tried the following procedure, but it is only for K7... there are errors when applying it on 8.x (http://devnet.kentico.com/articles/increasing-the-length-of-the-nodealias)

Recent Answers

Olivier Cozette answered on January 29, 2015 00:57

No answers to this one ? I have found answers to K7, but the SP used on those answers, don't exist anymore on 8..

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on January 29, 2015 08:34

Hi,

Regrettably is is a known bug which should be fixed in one of the upcoming hotfixes.

0 votesVote for this answer Mark as a Correct answer

Olivier Cozette answered on January 31, 2015 04:17

Hello, I downloaded 8.2.4, but the problem still remain. I also try the procedure for K7, as stated by one of your team members, but there were errors and then nothing worked anymore. Have to restore back.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on February 5, 2015 12:21

What is the full error including stack trace you are getting? Unfortunately, there was another case discovered that was not covered by the fix in the #4 hotfix. It should be fixed in tomorrow's hotfix #5.

0 votesVote for this answer Mark as a Correct answer

Olivier Cozette answered on February 10, 2015 01:24

I'm sorry I did not keep a copy of the error: I started a fresh installation of K8.2, and then I've copied all my contents. Everything is OK now.

0 votesVote for this answer Mark as a Correct answer

Simon Lukell answered on March 5, 2015 06:42

Hi Juraj,

I'm planning to upgrade from K7 to K8. I have in the site documents that exceed 50 char on NodeAlias. What hotfix is safe regarding this issue?

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on March 5, 2015 13:36

Hi,

As you can see in my previous post, this issue was fixed in 8.2.5 hotfix

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.