Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Special Characters in pagenamesSpecial Characters in pagenames
Previous
 
Next
New Post
8/28/2012 5:31 PM
 

Hi

I have problems with specials characters (German's Umlaute: ä, ö) in the pagenames. Access and showing the pages is fine. But when i want to edit the text in the html-module an error occoures instead of the WYSIWYG-Standard Editor. (DNN 6.2.2 an 6.2.1)

Any ideas?

Daniel

 
New Post
8/29/2012 7:06 AM
 
Daniel, would you mind to post the details of the error (from DNN eventlog): Did you try using CkEditor provider (http://dnnckeditor.codeplex.com) instead?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/29/2012 4:35 PM
 

In the Event-Log is no entry for this error.

a Popup windows is opening and instead of the editor ist following message:

==========
Server Error in '/cms' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
==========

I changed so the web.config with <customErrors mode="Off"/>. But then I can't reach the dnn (Server Error). So I changed it back to the original and the side works (with the error in the edit window)

Daniel

 
New Post
8/29/2012 5:51 PM
 
custom errors value should not affect accessibility of the site. This seem to be an issue caught be IIS, which might be logged in Windows Eventlog of the web server.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/31/2012 8:54 AM
 

Hi Sebastian

I found some strange behavior of DNN 6.2.2 an 6.2.1 : I can reproduce the error with the special characters in the pagenames. I can change any pagename to a name with  ä/ö/ü, then the editor window for the html-modul no longer work.

BUT, if I change in the page settings the skin (seitenlayout) and container (seiten-modulrahmen) field from <none> (nicht angegeben) to any entry in the list (host: darknight ....), then the editor window works.

I had the idea to set the skin setting of the page to <none>, so when I change the parent-side or website, the child pages will change the skin automatic. Is this wrong?

Grettings from Switzerland
Daniel

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Special Characters in pagenamesSpecial Characters in pagenames


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out