I've two installation of uBlogsy. One is a test site running 2.1.0 and the other is a site I'm working on properly running 2.1.1.
I've just discovered that both sites are failing to send comment notifications with similar errors:
No node exists with id '2388' at umbraco.cms.businesslogic.CMSNode.setupNode() at umbraco.cms.businesslogic.member.Member.setupNode() at umbraco.cms.businesslogic.member.Member..ctor(Int32 id) at uBlogsy.BusinessLogic.EmailService.SendNotificationEmails(String postUrl, Int32 pageId, Int32 commentId) in D:\_PROJECTS\Personal\uBlogsy - Blog\Branches\2.1.0.0\uBlogsy\uBlogsy.BusinessLogic\EmailService.cs:line 83 at uBlogsy.BusinessLogic.EventHandlers.UmbracoExtensions.Document_AfterPublish(Document sender, PublishEventArgs e) in D:\_PROJECTS\Personal\uBlogsy - Blog\Branches\2.1.0.0\uBlogsy\uBlogsy.BusinessLogic\EventHandlers\UmbracoEventHandlers.cs:line 31
No node exists with id '2388' at umbraco.cms.businesslogic.CMSNode.setupNode() at umbraco.cms.businesslogic.member.Member.setupNode() at umbraco.cms.businesslogic.member.Member..ctor(Int32 id) at uBlogsy.BusinessLogic.EmailService.SendNotificationEmails(String postUrl, Int32 pageId, Int32 commentId) in D:\_PROJECTS\Personal\uBlogsy\Branches\2.1.1.0\uBlogsy\uBlogsy.BusinessLogic\EmailService.cs:line 83 at uBlogsy.BusinessLogic.EventHandlers.UmbracoExtensions.Document_AfterPublish(Document sender, PublishEventArgs e) in D:\_PROJECTS\Personal\uBlogsy\Branches\2.1.1.0\uBlogsy\uBlogsy.BusinessLogic\EventHandlers\UmbracoEventHandlers.cs:line 46
Funny that the separate sites are both looking for the same node ID?
I dug around in the source to see what was going on.
I'd deleted the members that were installed with the starter kit. The pointers to those members were still in the Subscription Meta Data field though.
I guess this may or may not happen in real life if you were to purge the members without then finding out which posts they'd subscribed to and delete those subscriptions too. If it did the email notifications would stop working.
No node exists with id '2388' error when sending notification emails
Hi Anthony,
I've two installation of uBlogsy.
One is a test site running 2.1.0 and the other is a site I'm working on properly running 2.1.1.
I've just discovered that both sites are failing to send comment notifications with similar errors:
No node exists with id '2388' at umbraco.cms.businesslogic.CMSNode.setupNode() at umbraco.cms.businesslogic.member.Member.setupNode() at umbraco.cms.businesslogic.member.Member..ctor(Int32 id) at uBlogsy.BusinessLogic.EmailService.SendNotificationEmails(String postUrl, Int32 pageId, Int32 commentId) in D:\_PROJECTS\Personal\uBlogsy - Blog\Branches\2.1.0.0\uBlogsy\uBlogsy.BusinessLogic\EmailService.cs:line 83 at uBlogsy.BusinessLogic.EventHandlers.UmbracoExtensions.Document_AfterPublish(Document sender, PublishEventArgs e) in D:\_PROJECTS\Personal\uBlogsy - Blog\Branches\2.1.0.0\uBlogsy\uBlogsy.BusinessLogic\EventHandlers\UmbracoEventHandlers.cs:line 31
No node exists with id '2388' at umbraco.cms.businesslogic.CMSNode.setupNode() at umbraco.cms.businesslogic.member.Member.setupNode() at umbraco.cms.businesslogic.member.Member..ctor(Int32 id) at uBlogsy.BusinessLogic.EmailService.SendNotificationEmails(String postUrl, Int32 pageId, Int32 commentId) in D:\_PROJECTS\Personal\uBlogsy\Branches\2.1.1.0\uBlogsy\uBlogsy.BusinessLogic\EmailService.cs:line 83 at uBlogsy.BusinessLogic.EventHandlers.UmbracoExtensions.Document_AfterPublish(Document sender, PublishEventArgs e) in D:\_PROJECTS\Personal\uBlogsy\Branches\2.1.1.0\uBlogsy\uBlogsy.BusinessLogic\EventHandlers\UmbracoEventHandlers.cs:line 46
Funny that the separate sites are both looking for the same node ID?
Regards,
Matt
I dug around in the source to see what was going on.
I'd deleted the members that were installed with the starter kit.
The pointers to those members were still in the Subscription Meta Data field though.
I guess this may or may not happen in real life if you were to purge the members without then finding out which posts they'd subscribed to and delete those subscriptions too.
If it did the email notifications would stop working.
Might be an idea to put a catch in there.
Cheers,
Matt
Thanks for the bug report.
2.1.1.1 does a check for non-exsiting members in the meta data.
is working on a reply...