While playing with the new UTF-8 support I tried the following:   
- enable support on the author but not on the public.  
- create a page that contains weird char in the name and activate it.  
   
The result:  
- activation went fine  
- the page name is correct in the public site  
- The url is rendered properly and page is accessible.  
   
So as far as I can tell everything is fine, but I suspect that is just platform 
specific. We have that flag for a reason so I would be more comfortable to get 
a warning in the log when such page is accessed rather then letting it slip 
completely silently and having to hunt for it later.  
Opinions?  
   
Jan
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to