Seems a bit of an overkill to create a whole new package for it, why not incorporate any ideas people come up with into uBlogsy?  Make it an uber scalable blog package ;)

I did consider that.

However, all the features that were suggested when I first made the package ended up meaning almost a complete rebuild for uBlogsy 2.0...which is why it's taken so long to get it released. Bugs!

A separate package means that any new features on either package will not imact the other. It's more about my own time and faster delivery :)

We're using uBlogsy for a motorsports news site (no link to share just yet), and have had to adapt a little bit from uBlogsy's (v. 1.3.6.1) blog format.

• The biggest change of thought is having 10-20 new articles published every day. For example, currently in uBlogsy by default when you click on a tag to see other aricles with same tag, the entire articles themselves appear, rather than just their titles with links pointing to them. (This was easily remedied with the small="1" parameter in uBlogsyListPosts.cshtml.) It would be nice to have a couple of other options like this for the landing page, but it's still pretty easy to work with.
• Content Tree: The default arrangement here is based on date. I think you have to create the folders manually, like 2011, then November. While it may be helpful for the blogger, this isn't the best way to get good search results which is really important for news organizations. Here's some best practices on URL Structure for SEO that we're working with.
• SEO: in order to get high SEO rankings, we wanted to have each article appear under one category, and for that category to appear in the URL. This wasn't going to work with the built-in categories, and we ended up solutioning it by adding folders to the content tree and naming them after the categories (see image below). This works great for the URL, but now the articles are segregated and harder to work with in some ways (although having the built-in Umbraco search function and the ability to move articles around makes it doable). Each of these categories will have hundreds of articles in a short matter of time.
• Once we made the content tree as desrcibed above, the order of posts pulled up by uBlogsyListPosts.cshtml was based on the content tree and not the actual creation or publication date of the article, which we discussed and fixed here. Again, not a big problem but still something to figure out (with Anthony's help!) A fix also needs to be applied to the Previous and Next buttons if you're using those as a way to navigate between articles.
• Comment creation: The people we're making this for don't want anything to do with comments anywhere on their site, which is fine. However, upon creating each new article a comment page appeared automatically. Anthony said this was to become an option in uBlogsy 2.0, so he's already thought of it.
• Performance: We have 30K+ articles that we're considering importing to this uBlogsy (but might just leave them where they are). We haven't yet tested for this high of volume use case, but it would be good to keep that in mind for an organization pumping out articles in the double digits everyday.

Thank you Anthony for making uBlogsy and starting this topic. I'll add to this if I come up with any thing else later.

Hi Anthon;

Could you help me on this. It's fine when i publish it on IE8, It's error when i publish it on IE7

Details:

[NullReferenceException: Object reference not set to an instance of an object.]
uTagsy.Web.usercontrols.uTagsy.datatypes.uTagsy.SaveSettings() in D:\_PROJECTS\uBlogsy - Blog\Branches\1.3.6.1\uBlogsy\uBlogsy\usercontrols\uTagsy\uTagsy.ascx.cs:103
uTagsy.Web.usercontrols.uTagsy.datatypes.uTagsy.OnLoad(EventArgs e) in D:\_PROJECTS\uBlogsy - Blog\Branches\1.3.6.1\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

Hi Kevin

It could be something funky with some javascript on the page. Do you have any other third party datatypes?

Just out of curiosity, try replacing your json text with this:

{"documents":[{"documentType":"uBlogsyPost","tags":[]}]}

Hit save again.

If it works then try adding a tag on the content node.

Hey Frost

Thanks for the feedback.

Regarding tree structure. Date folders are very important for content organisation.

To add categories to the mix would you prefer this?

- Landing

- Category

- Year

- Month

- Day

- The article title

And then perhaps an arbitrary number of sub categories like this?

- Landing

- Category

- SubCategory

- Year

- Month

- Day

- The article title

As far as performance is concerned, I've tested on 2,000+ nodes. I would be interested to find out how it performs with 30k.

is working on a reply...