Fresh 4.8.1 install results in 'Value cannot be null' on publish
Hi all,
Just installed v. 4.8.1 and created the doctypes needed for the sites structure. Now, when I'm publishing a node in the content tree, I get an ArgumentNullException:
The umbraco.config is empty (which makes sense since it never reaches the code in UpdateDocumentCache()) and I have checked that the node is indexed, which it is.
Anyone experienced this and got a hot-fix for it? :-) Got this odd feeling that I have missed something simple 'n easy. I've checked permissions and they seem to be just fine.
Hmm, guess I was a bit too fast posting here :-) A complete re-install fixed the issue. *something* must have gone wrong along the line when installing it the first time.
I found the reason of the error on my second install. I named some of my doctypes "1 - Bla bla" and "2 - Bla bla" which made their aliases start with a "-" Deleting that "-" in the alias fixed the problem.
I guess that deserves a bug report? The autogenerated aliases shouldn't contain dashes. Or as a minimum, they should not start with dashes, since that is not valid for an xml element name.
Fresh 4.8.1 install results in 'Value cannot be null' on publish
Hi all,
Just installed v. 4.8.1 and created the doctypes needed for the sites structure. Now, when I'm publishing a node in the content tree, I get an ArgumentNullException:
The umbraco.config is empty (which makes sense since it never reaches the code in UpdateDocumentCache()) and I have checked that the node is indexed, which it is.
Anyone experienced this and got a hot-fix for it? :-) Got this odd feeling that I have missed something simple 'n easy. I've checked permissions and they seem to be just fine.
Thanks in advance!
All the best,
Bo
Hmm, guess I was a bit too fast posting here :-) A complete re-install fixed the issue. *something* must have gone wrong along the line when installing it the first time.
I found the reason of the error on my second install. I named some of my doctypes "1 - Bla bla" and "2 - Bla bla" which made their aliases start with a "-" Deleting that "-" in the alias fixed the problem.
I guess that deserves a bug report? The autogenerated aliases shouldn't contain dashes. Or as a minimum, they should not start with dashes, since that is not valid for an xml element name.
Oh, absolutely :-) I'll report it. Thanks for reminding me!
is working on a reply...