Archive
Monthly
Go
|
|
DNN Blog
Dec
7
Posted by:
Néstor Sánchez
Sunday, December 07, 2008
When you use the Blog module in a site that is in a language other than English, be aware of a small problem with pages that use non-ASCII characters like á, é, ü, etc in the page name. If the Blog module is placed on a page that uses such characters or one that has any predecessors that use them, DotnetNuke will choke on the generated links for individual post showing a 404 error (Page Not Found). For a temporary workaround, simply make sure the page names do not use any of the mentioned characters.
That's what I had to do on my personal site, after upgrading to version 3.5. I have two blogs in that site, one in Spanish and another in English. The one in Spanish was under a root page with the name "Español". I know it's a shame that I had to use "Espanol", but it's the only possible way I found to have the nice unique page names in the URL that are generated by the Blog module. I have already contacted Don to work with him on solving the issue, which of course was not present in earlier versions.
6 comment(s) so far...
Re: Heads up for a Blog module problem with non-traditional characters
I believe that RFC 2396 (the modern uri syntax specification) forbids the use of non-ASCII characters (such as the "ñ" in "Español") in a URL. I am not sure this is a blog module issue, but I will dig a bit deeper to see. Maybe when a DNN page's name has 1 or more non-ASCII characters the DNN core should convert them to ASCII characters when it is building that page's URL?
By Eoghan O'Neill on
Sunday, December 07, 2008
|
Re: Heads up for a Blog module problem with non-traditional characters
DNN correctly encodes the characters (although technically that's not needed since he tabid is enough to find the correct page). I had been using the site with the previous version of the Blog module without any issues. The problem appeared when I upgraded to the latest and this is the only way it works (so far, may be there's another way).
By Hooligannes on
Sunday, December 07, 2008
|
Re: Heads up for a Dotnetnuke Blog module problem with non-ASCII characters
did you log the issue in the public issue tracker at support.dotnetnuke.com?
By Sebastian Leupold on
Monday, December 08, 2008
|
Re: Heads up for a Dotnetnuke Blog module problem with non-ASCII characters
Issue logged as: support.dotnetnuke.com/issue/ViewIssue.aspx?id=8890&PROJID=23
By Hooligannes on
Monday, December 08, 2008
|
Re: Heads up for a Dotnetnuke Blog module problem with non-ASCII characters
Thanks for logging the issue. We're looking into it.
By Antonio Chagoury on
Monday, December 08, 2008
|
Re: Heads up for a Dotnetnuke Blog module problem with non-ASCII characters
Thanks for creating the issue in Gemini. I left a comment with a proposed fix for the issue and I've written a blog entry summarizing a few ways to work around this problem until the final fix is released. You can read the details here:
www.itcrossing.com/blog/entryid/291/unicode-characters-in-the-dotnetnuke-blog-module/
By Don Worthley on
Friday, December 12, 2008
|
|