When protecting the uBlogsy node (the root node of my site) then publishing the entire uBlogsy node tags completely break.
Tags will no longer be listed by Show/Hide all tags in the editor. Newly added tags in the editor are no longer saved.
Examine throws an exception:
ERROR System.Exception - [Thread 9] During indexing luceneFieldName:uBlogsySearchableTags, propertyAlias:uBlogsyPostTags, aliasInNode:uTagsyTagName.
System.NullReferenceException: Object reference not set to an instance of an object.
I've tried:
Deleting indices, deleting umbraco.config and republishing
Adding supportProtected="true" to ExamineSettings
Temporary fix:
In order to get this working I have to unprotect the site, publish all nodes, then reprotect. I'm not sure it's a permanent fix, later if something kicks off a full re-index it will probably break. Also, future admins may try to republish, breaking the back office.
It seems that the umbraco back office is seeing my login token for the front end and getting my access goofed up. I found that logging out of the front end fixes any issues I have in the back office.
I need to find the proper channel to report the bug and see what can be done.
Protected site creates broken tags
When protecting the uBlogsy node (the root node of my site) then publishing the entire uBlogsy node tags completely break.
Tags will no longer be listed by Show/Hide all tags in the editor. Newly added tags in the editor are no longer saved.
Examine throws an exception: ERROR System.Exception - [Thread 9] During indexing luceneFieldName:uBlogsySearchableTags, propertyAlias:uBlogsyPostTags, aliasInNode:uTagsyTagName. System.NullReferenceException: Object reference not set to an instance of an object.
I've tried:
supportProtected="true"to ExamineSettingsTemporary fix:
In order to get this working I have to unprotect the site, publish all nodes, then reprotect. I'm not sure it's a permanent fix, later if something kicks off a full re-index it will probably break. Also, future admins may try to republish, breaking the back office.
Please help, thank you.
This looks like an umbraco or examine bug. You might have to log an issue with them.
Anthony,
First, thanks for the quick reply.
Second, thanks for the great blog package.
Finally, I figured out what the problem is.
It seems that the umbraco back office is seeing my login token for the front end and getting my access goofed up. I found that logging out of the front end fixes any issues I have in the back office.
I need to find the proper channel to report the bug and see what can be done.
Regards, Ed
Wow that's a crazy bug!
You can log the bug here:
issues.umbraco.org
is working on a reply...