if you restarted the instance on which you changed the settings then no, it 
should not be a problem.

Just double check that you have normalization filter in the filter chain and 
that it is enabled.

If that doesn't help, comment on the issue i mentioned and myself or someone 
else will try to re-test it.



On Dec 16, 2010, at 2:59 PM, frank rittinger wrote:

> Hi Jan,
>  
> thanks for the info. I’m running a very fresh 4.4.1.
>  
> I changed this setting after installation. Could that be a problem?
>  
> Regards,
>  
> Frank
>  
> Von: user-list-ow...@magnolia-cms.com 
> [mailto:user-list-ow...@magnolia-cms.com] Im Auftrag von Jan Haderka
> Gesendet: Donnerstag, 16. Dezember 2010 14:32
> An: Magnolia User-List
> Betreff: Re: AW: [magnolia-user] Activation failed
>  
> What you ran into is http://jira.magnolia-cms.com/browse/MAGNOLIA-3327
> I had that issue before, but for me it worked fine when both were enabled (or 
> disabled). What is your Magnolia version?
>  
> Jan
>  
> On Dec 16, 2010, at 2:00 PM, frank rittinger wrote:
> 
> 
> Hi Jan,
>  
> I just checked: Both set to „true“.  I think the problem is with the path 
> “[%2F]”. I just changed both magnolia.utf8.enabled to false and now it works. 
> It seems like the UTF8 switch mangles the URL. We are running Ubuntu 10.04 
> LTS.
>  
> Any ideas how we can still use the UTF8 support?
>  
> Regards,
> 
> Frank
>  
>  
> Von: user-list-ow...@magnolia-cms.com 
> [mailto:user-list-ow...@magnolia-cms.com] Im Auftrag von Jan Haderka
> Gesendet: Donnerstag, 16. Dezember 2010 11:11
> An: Magnolia User-List
> Betreff: Re: [magnolia-user] Activation failed
>  
> Not 100% sure, but can you please double check that you have same settings 
> for UTF-8 normalization (the magnolia.utf8.enabled property in your 
> magnolia.properties file) on both author and public instances?
>  
> HTH,
> Jan
>  
> On Dec 16, 2010, at 10:52 AM, frank rittinger wrote:
> 
> 
> 
> Hello list,
>  
> I have a problem with the workflow process: Activation always fails for all 
> users (including superuser) with the follow errors on the authoring and 
> (below) the public instance:
>  
> Can't activate: : info.magnolia.cms.exchange.ExchangeException: 1 error 
> detected: Message received from subscriber: Activation failed | User not 
> allowed to (Add, Set, Read) path [%2Fde] on magnoliaPublic8080
>  
> 2010-12-16 09:54:55,473 ERROR 
> info.magnolia.module.exchangesimple.ReceiveFilter : Exception caught
> info.magnolia.cms.security.AccessDeniedException: User not allowed to (Add, 
> Set, Read) path [%2F]
>  
> They reside in different tomcats and the public instance is a copy of the 
> authoring instance. I’m using magnolia Enterprise 4.4.1 and changed the 
> superuser’s password on both instances to the same value.
>  
> From the errors I assume that the subscribers are setup properly, but the 
> users do not have the rights, although they should be identical with 
> superuser rights.
>  
> Any ideas?
>  
> Best regards,
>  
> Frank
> Frank Rittinger
> Senior Software Developer
> Virtual Identity AG
> Grünwälderstraße 10-14
> 79098 Freiburg
> tel. +49 761 207 58 -15
> fax. +49 761 207 58 -01
> frank.rittin...@virtual-identity.com
> http://www.virtual-identity.com
> Skype: frank.rittinger.vi
>  
>  
> 
> _____________________________________________________________________
> 
> Vorstand: Ralf Heller, Udo Möbes 
> Vorsitzende des Aufsichtsrates: Kirsten Heller 
> Sitz der Gesellschaft: Gruenwaelderstrasse 10-14, D-79098 Freiburg 
> Amtsgericht Freiburg HRB 6218
> 
> Versand am 16.12.2010 10:52 von rittinger frank
> Validation-Code: 2261135701674
> 
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
> ----------------------------------------------------------------
>  
> 
>  
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
> ----------------------------------------------------------------
>  
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
> ----------------------------------------------------------------
>  
> -  
> Best regards,
>  
> Jan Haderka, PhD.
> Magnolia International Ltd.
> http://www.magnolia-cms.com
>  
> http://twitter.com/magnolia_cms
> http://facebook.com/Magnolia
> --------------------------------------
> Magnolia®  - Simple Open-Source Content Management
>  
>  
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
> ----------------------------------------------------------------
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
> ----------------------------------------------------------------

-  
Best regards,

Jan Haderka, PhD.
Magnolia International Ltd.
http://www.magnolia-cms.com

http://twitter.com/magnolia_cms
http://facebook.com/Magnolia
--------------------------------------
Magnolia®  - Simple Open-Source Content Management



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to