You could use the DateFolders package: http://our.umbraco.org/projects/developer-tools/datefolders

It doesn't support folders for the 'Day' yet, but you could easily add it to the source...

Thanks for the suggestions - we are moving from the first release of blog for umbeaco to ublogsy and will just be moving all our old blog post nodes underneath the new ublogsy node so we have just decided to forgo day folders for new posts and maintain them for the old blog nodes.

I have installed 1.4 and have found what appears to be a bug. I would post this in the bug forum for the ublogsy package but unfortunatly the our.umbraco.org/forum package posting facility is broken at the moment so I will post it here. This is what my post would have said:

========================================

<%@ Master Language="C#" MasterPageFile="~/masterpages/uBlogsyBaseSite.master" AutoEventWireup="true" %>

<%@ Register TagPrefix="uBlogsy" TagName="Contact" Src="~/usercontrols/uBlogsy/Contact.ascx" %>

  
  
  
  
<asp:Content ContentPlaceHolderId="LeftCol" runat="server">
  <umbraco:Item field="uBlogsyContentBody" runat="server" disable-output-escaping="true"></umbraco:Item>
  
  <hr />
  
  <umbraco:Macro ID="Macro3" runat="server" Alias="uBlogsyListComments" ItemCount="-1" />
  
  <hr />
  
  <uBlogsy:Contact ID="Contact" runat="server" />
</asp:Content>

[InvalidOperationException: Sequence contains no elements]
   System.Linq.Enumerable.Single(IEnumerable`1 source) +2718166
   uBlogsy.BusinessLogic.DataService.GetValueFromLanding(Int32 pageId, String propertyName) in C:\_Projects\_Anthony\Branches\1.4_comment_subscription\uBlogsy\uBlogsy.BusinessLogic\DataService.cs:68
   uBlogsy.Web.usercontrols.uBlogsy.Contact.OnLoad(EventArgs e) in C:\_Projects\_Anthony\Branches\1.4_comment_subscription\uBlogsy\uBlogsy\usercontrols\uBlogsy\Contact.ascx.cs:65
   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.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207

  <uBlogsy:Contact ID="Contact" runat="server" />

Hey Max

Is this happening on load of the page, or on submit of a comment?

Can you show me your content tree?

Basically, it's because a certain property has not been found. It is uBlogsySpamDisableComments. Can you check if that property belongs to the uBlogsyLanding doc type.

ps. uBlogsyLanding is required for the blog to work.

Hi thanks for your reply.

This happens on loading of the page.

I had moved the blog container from underneath the landing node and deleted the landing node - the landing doctype was still there however and still the parent of the other ublogsy doctypes.

as far as I remember the uBlogsySpamDisableComments property was still there; it has however since been removed.

I needed to remove the ublogsy landing page in order to maintain the path structure to our old blog pages to avoid 404 links when people come in from google. This is vital.

Is there any way to modify the installation (if possible not the source code), by, i.e. moving document properties, to make comments work without needing the landing page? 

I have currently implemented a doc2form comments system with umbraco email notifications for publish requests but the dashboard control ublogsy offers would be more ideal.

Thanks

Max

As far as the 404's; you can use my 301 URL Tracker package to route old url's to new url's :-)

Hey Max

The landing content node is required. It has all the settings for the blog to work. There is no easy way to get around this. Hacking the source may cause some issues and is not worth it.

kipusoep's 301 url tracker will do the job for your 404 concerns though.

Thanks for the suggestions. We have around 200 old blog posts and the time it would take to map all the 404's to the right pages would not really be worth it just for slightly better comments page functionality; at the moment any way.

Thanks for the help :) I may well look into the 301 tracker for ongoing site consistency anyway.

Max

You could create one rewrite rule (urlrewriting) to rewrite, for example, '/blog/2011/07/11/some-blog-post/' to '/2011/07/11/some-blog-post/'...

That would still mean reinstalling the package and re-doing a whole load of changes I have already made. I am happy to proceed with the existing doc2form solution. Thanks again for the help.

is working on a reply...