Archive
Monthly
Go
|
|
DNN Blog
Dec
19
Posted by:
Néstor Sánchez
Friday, December 19, 2008
A productive bug-chasing meeting with Don Worthley of the Blog team ended up in a long winded conversation about children, losing money, life priorities and GTD. I don't want to bore anyone with details about these, but rather let you know that after reviewing some code from the Blog module, the bug that I talked about in a previous email has been fixed. The bug was introduced with a feature that allowed 301 redirects to avoid losing page rank and maintaining SEO now that the module creates unique page names for each post. I've tested the fix in my personal Blog (which is in Spanish), Don should be doing further testing in the coming days and I assume it will find its way to the next Blog release.
5 comment(s) so far...
Re: DotNetNuke Blog encoding bug… SOLVED
Hello, this is good news, however following the link to your personal blog seems to be showing the symptoms of encryption error (server error)...
By Fabrice on
Friday, December 19, 2008
|
Re: DotNetNuke Blog encoding bug… SOLVED
Fixed. thx Fabrice
By Hooligannes on
Friday, December 19, 2008
|
Re: DotNetNuke Blog encoding bug… SOLVED
Hi Nestor, you still need to prefix the link to your blog with "http://"
By Sebastian Leupold on
Friday, December 19, 2008
|
Re: DotNetNuke Blog encoding bug… SOLVED
Thanks again, I had left the editing file in OneNote open without clicking "Publish". Tsk, tsk. :P
By Hooligannes on
Friday, December 19, 2008
|
Re: DotNetNuke Blog encoding bug… SOLVED
Thanks Nestor. I was really encouraged last night (this morning) to actually put GTD into practice. Thanks for the Nudge.
Here's a link to a blog post I wrote about a workaround that may work for some. It's not as effective as the fix which I've also described in the comments in case anyone wants to download the source and create a fixed version.
www.itcrossing.com/blog/entryid/291/unicode-characters-in-the-dotnetnuke-blog-module/
By Don Worthley on
Friday, December 19, 2008
|
|