I'm getting an exception when publishing a post for the first time (similar to this thead). I've tried following the steps mentioned in that thread but it hasn't solved the problem. The comments folder is getting created but the publish isn't finishing as the page is not available on the site.
Version of umbraco is 4.7 and it happens on both my localhost (Win 7, IIS 7.5) and our dev server which I think is IIS 6.
Value cannot be null. Parameter name: attribute
Description: An unhandled exception occurred during
the execution of the current web request. Please review the stack trace
for more information about the error and where it originated in the
code.
Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: attribute Stack Trace:
What appears to happen in the Document_AfterPublish event handler is :-
UmbracoAPIHelper.CreateContentNode gets called to create the comments folder
This has a call to UpdateDocumentCache (to add the comments folder) however at this point the comments folder parent (the blog post) hasn't been added to the document cache so this fails. The umbraco api logs ''Couldn't find any page with the nodeId = 0. This is most likely caused by the page isn't published! Parameter name: nodeId' in the database.
The new Examine IndexSet causes an event handler to subscribe to the AfterUpdateDocumentCache event. This tries to access properties that should be in the cache but aren't due to the above error - this crashes and causes the ysod
It appears that the simple solution is just to move the UpdateDocumentCache command for the blog post above UmbracoAPIHelper.CreateContentNode and rebuild the dll.
Has this been fixed in v2.0 of uBlogsy? Reason I ask is that I'm getting a different, but seemingly similar error in uBlogsy 2.0 and also nForum - in both cases, I get an issue when moving media items in the media section.
In case this was down to a conflict with another package (I have quite a few installed), I installed a fresh instance of Umbraco 4.7 and then installed uBlogsy 2.0 beta and NO other packages at all. I thought this would be easier than eliminating all the other packages one by one.
I added 2 folders to the media section (Photos and Images) and uploaded a picture (right click Photos, Create, Image). I then moved the image to the Images folder (right click on the photo in the tree, Move, select Images folder) and got the error below:
Server Error in '/' Application.
No Document exists with Version '7faa9414-be6e-4192-89d5-46032605f388'
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: No Document exists with Version '7faa9414-be6e-4192-89d5-46032605f388'
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
After reloading nodes in the media section, the photo had been moved to the correct destination.
I then uninstalled uBlogsy (deleting all the child document types first - which is a pain!!). Then went back to media and repeated the move process, and the photo moved successfully with no error message.
So it's definitely something to do with the uBlogsy installation - and to me, it seems most likely to relate to:
uBlogsy.BusinessLogic.EventHandlers.UmbracoExtensions.Document_AfterMove(Object sender, MoveEventArgs e) in D:\_PROJECTS\uBlogsy - Blog\Branches\2.0_comment_subscription\uBlogsy\uBlogsy.BusinessLogic\EventHandlers\UmbracoEventHandlers.cs:125
I wonder if the same logic as Suzy and Doug were discussing earlier in this post re the Document_AfterPublish event handler also applies to Document_AfterMove?
Experiencing this issue after copying uBlogsy - Landing content node and child content nodes to new area of site. Can still publish original uBlogsy nodes without any issues.
I'm getting the same error. Using Umbraco 4.7.1 and uBlogsy 2.0 (beta2).
Value cannot be null. Parameter name: attribute
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: attribute
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Hi all, I'm not sure if the problems we're experiencing is related to all this or not. We've set up a special blog editors role that only has privledges to "send to publish." When those users try to send a blog to publish, they get this .NET error:
[NullReferenceException: Object reference not set to an instance of an object.] uTagsy.Web.usercontrols.uTagsy.datatypes.uTagsy.SaveSettings() in D:\_PROJECTS\uBlogsy\Branches\1.32_bugs_search\uBlogsy\uBlogsy\usercontrols\uTagsy\uTagsy.ascx.cs:103 uTagsy.Web.usercontrols.uTagsy.datatypes.uTagsy.OnLoad(EventArgs e) in D:\_PROJECTS\uBlogsy\Branches\1.32_bugs_search\uBlogsy\uBlogsy\usercontrols\uTagsy\uTagsy.ascx.cs:39 System.Web.UI.Control.LoadRecursive() +74 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Control.LoadRecursive() +146 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207
The administrative role can publish blog posts with no error.
Still having issues with ublogsy publishing when having the CWS (creative website starter package) installed. Trying to see if ublogsy is stable enough to be incorporated into an existing website and am testing by adding it to the CWS package.
Umbraco 4.7.1.1, uBlogsy 2.0.0.1
I've read the solution posted by suzyb, but have looked at the source code for 2.0.0.1 and the change was made to the uBlogsy.BusinessLogic EnsureCommentsFolder method and is not working.
Any information would be appreciated. Thanks in advanced.
********UPDATE 2011-03-11 ******************
Was able to remove the CWS examine index and rebuild it. publishing worked.
Error when publishing posts
I'm getting an exception when publishing a post for the first time (similar to this thead). I've tried following the steps mentioned in that thread but it hasn't solved the problem. The comments folder is getting created but the publish isn't finishing as the page is not available on the site.
Version of umbraco is 4.7 and it happens on both my localhost (Win 7, IIS 7.5) and our dev server which I think is IIS 6.
Value cannot be null.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Parameter name: attribute
Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: attribute
Stack Trace:
A colleague managed to fix the bug. I'll post the solution here for anyone having this problem in the future.
He changed this code in the Document_AfterPublish event handler in uBlogsy.Web.Extensions.UmbracoExtensions
to this
umbraco.library.UpdateDocumentCache(sender.Id);
commentsFolder = UmbracoAPIHelper.CreateContentNode("Comments", "uBlogsyFolderComment", properties, sender.Id, true);
umbraco.library.UpdateDocumentCache(commentsFolder.Id);
Just to expand on what suzyb has posted.
This bug only appears when you're using Examine and have set-up another IndexSet (see http://www.farmcode.org/post/2011/03/15/Searching-Umbraco-using-Razor-and-Examine.aspx for the minimum config to set-up a new Examine index).
What appears to happen in the Document_AfterPublish event handler is :-
It appears that the simple solution is just to move the UpdateDocumentCache command for the blog post above UmbracoAPIHelper.CreateContentNode and rebuild the dll.
That sounds insteresting.
Good find.
I would also log the issue with examine.
Cheers.
Has this been fixed in v2.0 of uBlogsy? Reason I ask is that I'm getting a different, but seemingly similar error in uBlogsy 2.0 and also nForum - in both cases, I get an issue when moving media items in the media section.
See http://our.umbraco.org/projects/website-utilities/nforum/bugs/23610-Error-in-media-section for the error I get when I do this with nForum installed. When I uninstall nForum, then the nForum error goes away and the new error refers to uBlogsy. And when I uninstall uBlogsy, the error goes away completely.
Thanks
Allan
Yes I did implement this in 2.0
Strange error.
What packages are installed?
Hi Anthony
In case this was down to a conflict with another package (I have quite a few installed), I installed a fresh instance of Umbraco 4.7 and then installed uBlogsy 2.0 beta and NO other packages at all. I thought this would be easier than eliminating all the other packages one by one.
I added 2 folders to the media section (Photos and Images) and uploaded a picture (right click Photos, Create, Image). I then moved the image to the Images folder (right click on the photo in the tree, Move, select Images folder) and got the error below:
Server Error in '/' Application.
No Document exists with Version '7faa9414-be6e-4192-89d5-46032605f388'
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: No Document exists with Version '7faa9414-be6e-4192-89d5-46032605f388'
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
After reloading nodes in the media section, the photo had been moved to the correct destination.
I then uninstalled uBlogsy (deleting all the child document types first - which is a pain!!). Then went back to media and repeated the move process, and the photo moved successfully with no error message.
So it's definitely something to do with the uBlogsy installation - and to me, it seems most likely to relate to:
I wonder if the same logic as Suzy and Doug were discussing earlier in this post re the Document_AfterPublish event handler also applies to Document_AfterMove?
Ah!
Nice find!
Your crash is due to this:
void Document_AfterMove(object sender, MoveEventArgs e) { Document doc = new Document(((CMSNode)sender).Id); if (doc.ContentType.Alias == "uBlogsyPost") {
I'll fix it in the next release.
Thanks.
Experiencing this issue after copying uBlogsy - Landing content node and child content nodes to new area of site. Can still publish original uBlogsy nodes without any issues.
Using uBlogsy 1.36
Is there a fix without creating a site package?
Hi,
I'm getting the same error. Using Umbraco 4.7.1 and uBlogsy 2.0 (beta2).
Value cannot be null.
Parameter name: attribute
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: attribute
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
I have another examine index. Which if I remove it, stops this error. But I need any solutions available?
Hi Suzy
The same bug was in 2.0 beta 2. Fixed and will be released soon.
Oh that was the stack trace when I create a post... this is the stack trace when I try and publish a post
Oh cheers thanks.. I don't suppose I could get a pre-release of the fix
Sure
What's your email?
[email protected] thanks :)
Hi all, I'm not sure if the problems we're experiencing is related to all this or not. We've set up a special blog editors role that only has privledges to "send to publish." When those users try to send a blog to publish, they get this .NET error:
The administrative role can publish blog posts with no error.
Any ideas?
Have you tried it with another role?
A work around is to replace the datatype with the standard Umbraco tags datatype. You may loose tags for existing posts though.
Still having issues with ublogsy publishing when having the CWS (creative website starter package) installed. Trying to see if ublogsy is stable enough to be incorporated into an existing website and am testing by adding it to the CWS package.
Umbraco 4.7.1.1, uBlogsy 2.0.0.1
I've read the solution posted by suzyb, but have looked at the source code for 2.0.0.1 and the change was made to the uBlogsy.BusinessLogic EnsureCommentsFolder method and is not working.
Any information would be appreciated. Thanks in advanced.
********UPDATE 2011-03-11 ******************
Was able to remove the CWS examine index and rebuild it. publishing worked.
Ah I wasnt aware that cws had a custom examine index.
So that was the solution?
I think someone told me that if you upgrade to the newest examine it would have fixed it.
is working on a reply...