I've not had much luck in the past with Blog4Umbraco, however I'm keen to give it another try.
I created a fresh 4.7 install, then installed Blog4Umbraco from the repository and I get the error below when trying to publish a blog post, after I try again, it publishes fine but can't give this to my client like this.
Probably should start a separate post but I'd be keen to get some feedback from anyone using B4U in production, how they find it, is it stable etc. Understand that there might be a few quirks/ bugs to fix first.
Many thanks
Rich
Server Error in '/' Application.
Couldn't find any page with the nodeId = 1072. This is most likely caused by the page isn't published! Parameter name: nodeId
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: Couldn't find any page with the nodeId = 1072. This is most likely caused by the page isn't published! Parameter name: nodeId
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:
[ArgumentException: Couldn't find any page with the nodeId = 1072. This is most likely caused by the page isn't published!
Parameter name: nodeId]
umbraco.library.niceUrlJuno(Int32 nodeId, Int32 startNodeDepth, String currentDomain) +1292
umbraco.library.niceUrlDo(Int32 nodeID, Int32 startNodeDepth) +271
Umlaut.Umb.Blog.EventHandlers.Autoping.Document_AfterPublish(Document sender, PublishEventArgs e) +565
umbraco.cms.businesslogic.web.Document.PublishWithResult(User u) +1578
umbraco.cms.presentation.editContent.Publish(Object sender, EventArgs e) +414
System.EventHandler.Invoke(Object sender, EventArgs e) +0
System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) +134
System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument) +165
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3691
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.225
Same problem. I'm still looking for the cause, but for now, there's a workaround:
After clicking Save & Publish (and getting the error), refresh the node list from the blog root. Navigate down to the blog entry in the appropriate date folder and click to edit the content. If you look at the general Properties tab, you should see the link to document listed as just a hash.
Click Save & Publish again (should ALSO get an error). Once you do this, though, and reload the content by clicking it again from the tree, the properties will show the correct url, and it will now appear in the blog lists on the site.
Annoying, since I can't train users around this (well, I can, but it makes Umbraco look unpolished).
Is there a move to port blog4umbraco over entirely to razor? I've found the razor syntax much easier to work with than xslt (which is the only reason I've returned to umbraco after trying it 2 years ago). It would be great to see the project tidied up (especially w.r.t. metawebblog api access!)
I had the same problem. Someone has already fixed this in codeplex...I just downloaded the latest source and compiled and deployed the DLL and it works fine.
i see the project structure has changed mostly after v2.026 release.
By the way, is there anyone who downloaded the latest source code ( with changeset 67452 by codegecko on Feb 6) and mannually installed b4u with new features?
Has anyone either got a proper compiled version that doesn't have this error or can someone describe the steps needed to compile the project and which files i'd need to copy across please?
Couldn't find any page with the nodeId
Hey,
I've not had much luck in the past with Blog4Umbraco, however I'm keen to give it another try.
I created a fresh 4.7 install, then installed Blog4Umbraco from the repository and I get the error below when trying to publish a blog post, after I try again, it publishes fine but can't give this to my client like this.
Probably should start a separate post but I'd be keen to get some feedback from anyone using B4U in production, how they find it, is it stable etc. Understand that there might be a few quirks/ bugs to fix first.
Many thanks
Rich
Server Error in '/' Application.
Couldn't find any page with the nodeId = 1072. This is most likely caused by the page isn't published!
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: nodeId
Exception Details: System.ArgumentException: Couldn't find any page with the nodeId = 1072. This is most likely caused by the page isn't published!
Parameter name: nodeId
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.225
I'm having the exact same problem!
I'm using Umbraco 4.7 as well. Exact same error apart from different Node ID
Same here, having the same problem. I backed up my production data and restored it to a localDB in order to test 4.7 before upgrade.
Same problem. I'm still looking for the cause, but for now, there's a workaround:
After clicking Save & Publish (and getting the error), refresh the node list from the blog root. Navigate down to the blog entry in the appropriate date folder and click to edit the content. If you look at the general Properties tab, you should see the link to document listed as just a hash.
Click Save & Publish again (should ALSO get an error). Once you do this, though, and reload the content by clicking it again from the tree, the properties will show the correct url, and it will now appear in the blog lists on the site.
Annoying, since I can't train users around this (well, I can, but it makes Umbraco look unpolished).
Is there a move to port blog4umbraco over entirely to razor? I've found the razor syntax much easier to work with than xslt (which is the only reason I've returned to umbraco after trying it 2 years ago). It would be great to see the project tidied up (especially w.r.t. metawebblog api access!)
I had the same problem. Someone has already fixed this in codeplex...I just downloaded the latest source and compiled and deployed the DLL and it works fine.
Get source from here http://blog4umbraco.codeplex.com/SourceControl/list/changesets
Hello Trevor!
I have downloaded the newest source code as you described. But i am having trouble compiling some of the solutions.
Could you please explain exactly what solution i need to compile? And also which DLL's i need to deploy and where i need to deploy them to?
I had the same problem, and downloaded the latest source code. Compiled and replaced the dll's, and now its finally works :)
hi Trevor Loader, which changeset you downloaded?
i see the project structure has changed mostly after v2.026 release.
By the way, is there anyone who downloaded the latest source code ( with changeset 67452 by codegecko on Feb 6) and mannually installed b4u with new features?
hi again, i downloaded changeset 51174, it is the one before codegecko branch that has many major difference than v2.026.
i debuged the code and exception is thrown while executing the bold statement below.
Document_AfterPublish method is of Umlaut.Umb.Blog.EventHandlers. Autoping class.
void Document_AfterPublish(Document sender, umbraco.cms.businesslogic.PublishEventArgs e) {
if (sender.ContentType.Alias == "BlogPost") {
string urls = GetValueRecursively("pingServices", sender.Id);
if (!string.IsNullOrEmpty(urls)) {
XmlDocument xd = new XmlDocument();
try { xd.LoadXml(urls); }
catch { }
string blogName = GetValueRecursively("blogName", sender.Id);
string blogUrl = umbraco.library.NiceUrlFullPath(sender.Id);
string currentDomain = HttpContext.Current.Request.ServerVariables["SERVER_NAME"].ToLower();
if (!UmbracoSettings.UseDomainPrefixes)
blogUrl = "http://" + currentDomain + blogUrl;
foreach (XmlNode link in xd.SelectNodes("//link [@type = 'external']")) {
string ping = link.Attributes["link"].Value;
//Log.Add(LogTypes.Debug, sender.Id, ping + " n:" + blogName + " u:" + blogUrl);
PingService(ping, blogName, blogUrl);
}
}
}
if you are not using ping services in your blog, you can easily comment the all method code
or just the bold statement, so you can temporarily fix the issue.
i could handle it like that at the moment, hope it helps you too.
is there anyone have an exact solution about that? let me know about it.
I'm working on it :)
I refactored the method code like below (i added the bold ones), this is also a solution, but not an exact one.
Because library.NiceUrlFullPath(sender.Id); returns "yoursite.com/#" url and it goes to ping services with wrong one.
So if you publish your post twice, the second time right url willl be generated.
void Document_AfterPublish(Document sender, umbraco.cms.businesslogic.PublishEventArgs e) {
if (sender.ContentType.Alias == "BlogPost") {
string urls = GetValueRecursively("pingServices", sender.Id);
if (!string.IsNullOrEmpty(urls)) {
XmlDocument xd = new XmlDocument();
try { xd.LoadXml(urls); }
catch { }
string blogName = GetValueRecursively("blogName", sender.Id);
string currentDomain = HttpContext.Current.Request.ServerVariables["SERVER_NAME"].ToLower();
string blogUrl;
try
{
blogUrl = library.NiceUrlFullPath(sender.Id);
if (!UmbracoSettings.UseDomainPrefixes) blogUrl = "http://" + currentDomain + blogUrl;
}
catch (Exception)
{
Log.Add(LogTypes.Debug, sender.Id, "Cound not get 'NiceUrlFullPath' from current application");
blogUrl = "http://" + currentDomain + "/" + library.NiceUrl(sender.Id);
}
foreach (XmlNode link in xd.SelectNodes("//link [@type = 'external']"))
{
string ping = link.Attributes["link"].Value;
//Log.Add(LogTypes.Debug, sender.Id, ping + " n:" + blogName + " u:" + blogUrl);
PingService(ping, blogName, blogUrl);
}
}
}
}
Note: I got that solution from source code in one of the changesets in codeplex project page.
Has anyone either got a proper compiled version that doesn't have this error or can someone describe the steps needed to compile the project and which files i'd need to copy across please?
Thanks
Chris
Hey Chris,
As the starter of this post thought I might as well comment. To be honest I gave up with Blog4Umbraco but prehaps you could try a later version from here http://blog4umbraco.codeplex.com/SourceControl/list/changesets ?
You might also want to check out http://our.umbraco.org/projects/starter-kits/ublogsy
Rich
Thanks Rich,
I have seen the ublogsy but i need to do some custom development and i have no experience of Razor to do what i need to do...
Cheers
Chris
Rich, uBlogsy v1.xx is not razor based...only v2Beta is...so it might be worth a look.
Whoops - I meant Chris!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.