I've installed uBlogsy in my site and it works well enough but I've just looked at the sitemap that is automatically updated with new content and it shows links for the top three levels of the blog Blog > Posts > 2012 as it would with any other section. However the problem is that Posts and 2012 are just folders not pages so I my guess is that this is why these links in the sitemap give the error page. The stack trace is here;
Trace Information
Category
Message
From First(s)
From Last(s)
aspx.page
Begin PreInit
umbracoInit
handling request
7.66906541962622E-05
0.000077
request handler
current url '/blog/posts.aspx'
0.000327651433085458
0.000251
umbracoRequestHandler
Just before xPath query (True, '1295')
0.000377468610112094
0.000050
umbracoRequestHandler
After xPath query
0.000411536679588157
0.000034
umbracoRequestHandler
Access checking started
0.000464413683224617
0.000053
umbracoRequestHandler
Page protected
0.000507721229130349
0.000043
umbracoRequestHandler
Access checking ended
0.0351762216807714
0.034669
umbracoInit
Done handling request
0.0352426929140682
0.000066
umbracoPage
Element loaded: uBlogsyContentTitle
0.0356070022698714
0.000364
umbracoPage
Element loaded: uBlogsySeoDescription
0.0356641740301383
0.000057
umbracoPage
Element loaded: uBlogsyContentSummary
0.0357114413516567
0.000047
umbracoPage
Element loaded: uBlogsyContentBody
0.0357578837199225
0.000046
umbracoPage
Element loaded: umbracoNaviHide
0.0358043710856385
0.000046
umbracoPage
Pagedata loaded for Posts (ID: 1295)
0.0358392091114837
0.000035
umbracoPage
Looking up skin information
0.0359048903895446
0.000066
Unhandled Execution Error
Cannot find ContentPlaceHolder 'ContentPlaceHolderDefault' in the master page '/masterpages/uBlogsyBaseSite.master', verify content control's ContentPlaceHolderID attribute in the content page. at System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection) at System.Web.UI.MasterPage.get_Master() at System.Web.UI.MasterPage.ApplyMasterRecursive(MasterPage master, IList appliedMasterFilePaths) at System.Web.UI.MasterPage.ApplyMasterRecursive(MasterPage master, IList appliedMasterFilePaths) at System.Web.UI.Page.ApplyMasterPage() at System.Web.UI.Page.PerformPreInit() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Ah, I've just found an unsophisticated workaround, Go to the highest page in the tree you want to not show in the Content editor and use the hide in Navigation property. This may give other issues but it works for me for now.
No solution was found save hiding all the posts from the sitemap. If the folders are unhidden the posts themselves don't show in the sitemap. The folders do but crash when selected.
Post folder links in auto sitemap give error
I've installed uBlogsy in my site and it works well enough but I've just looked at the sitemap that is automatically updated with new content and it shows links for the top three levels of the blog Blog > Posts > 2012 as it would with any other section. However the problem is that Posts and 2012 are just folders not pages so I my guess is that this is why these links in the sitemap give the error page. The stack trace is here;
Trace Information
Cannot find ContentPlaceHolder 'ContentPlaceHolderDefault' in the master page '/masterpages/uBlogsyBaseSite.master', verify content control's ContentPlaceHolderID attribute in the content page.
at System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection)
at System.Web.UI.MasterPage.get_Master()
at System.Web.UI.MasterPage.ApplyMasterRecursive(MasterPage master, IList appliedMasterFilePaths)
at System.Web.UI.MasterPage.ApplyMasterRecursive(MasterPage master, IList appliedMasterFilePaths)
at System.Web.UI.Page.ApplyMasterPage()
at System.Web.UI.Page.PerformPreInit()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Ah, I've just found an unsophisticated workaround, Go to the highest page in the tree you want to not show in the Content editor and use the hide in Navigation property. This may give other issues but it works for me for now.
Yes they are not pages, just folders.
They should redirect to the first post. Strange.
No solution was found save hiding all the posts from the sitemap. If the folders are unhidden the posts themselves don't show in the sitemap. The folders do but crash when selected.
Cheers
Gus
is working on a reply...