Please do address this issue -- it makes saving / sending blog links a lot easier, particularly in terms of the permalinks etc.

Thank you, Tom

To show this problem in action check out this page of results on Google (this is a search for the word 'blogs' on dotnetnuke.com, which is running the latest problematic version version of the blog module):

• Top 100 results for a search for 'blogs' on Dotnetnuke.com

The vast majority of those search results are pointing to blog entries on dotnetnuke.com (the non-blog entries presented in these search results include blog project pages or forum threads about the blog module). Each result has its main link highlgithed in blue font. This blue hyperlinked text, as is the convention for presenting search engine results, is what is found in each web page's title tag. However, since version 3.04.00 of the blog module was installed on dotnetnuke.com the title tag of every single blog entries (old and new) has exactly the same text ("DotNetNuke > Community > Blogs"). This means that in search engine result pages there will be little (if not zero) information about what a specific blog entry was about. This means less of an incentive for a user to decide to click, in the search results, on a blog entry created using v3.04.00 of the blog module, and that's if the page gets ranked at all because Google now has, in the case of dotnetnuke.com, 100s of blog entries all appearing with the precisely the same title, hence it will be more difficult - but not impossible - for the search engine to differentiate between the blog entires. In a nutsehll: one of the strongest semanitc indicators that a search engine uses to establsih what a web page about has been now been lost for all blog entries!

Compare the situation to the following search engine results (seaching for the word 'blog' on mydnn.org, which is still running (update 20 Feb: mydnn.org has since - unfortunately for their search engines rankings - upgraded to the latest versiuon of the blog module) the previous version of the blog module):

• Top 100 results for a search for 'blog' on mydnn.org

The site MyDnn.org is still running the previous version of the Blog module and its blog entries have - as a consequence - more meaningful and unique titles visible in the search engine results page that better reflect the content of each blog entry. The same thing is (thankfully) still happening for the blogs on my site, which is why I cannot afford to upgrade to version 3.04.00.

I would advise all sites running the DNN blog module who depend on traffic from search engines to very carefully consider the above before they decide to upgrade to v3.04.00. There is a strong risk that upgrading will compromise the ability of blog entries to subsequently rank well for relevant keywords.

I know the project team is as keen as I to improve this module so I hope, based on this feedback, this oversight can be corrected shortly!

eoghano

I don't know with certainty if this is possible. Maybe someone from the project team can advise?

I am pretty sure it is compatible with DNN 4.7 & DNN 4.8. 

You lose the features indicated on the change log here. But with a 'step backwards' to v3.03.01 you 'gain' two features that  were removed in v3.04.00, namely:

• The ability for each blog entry to have a unique title tag.
• The ability for files to be uploaded by a blog user without having to use the FCK editor (discussed here). This feature also means there not just a more intuitive work flow for someone publishing a blog but also greater 'binding' between a blog entry and images uploaded to the blog.

Eoghano