[Flow] Policy: different behaviour when switch context

[Bastian Waidelich]

On 07.05.15, at 14:47, Cornel Widmer wrote:

Hi Cornel,


> I've run into a problem after switching the context of my application.
> In Development context everything runs fine with my Policy.yaml. Then I
> switched the context and the very first page didn't work anymore.

Security should behave the same no matter what context of course.
Did you flush caches for all contexts? ("rm -Rf Data/Temporary/" to make 
sure).

If yes, you could compare the policy configuration for the two contexts 
in question via:

FLOW_CONTEXT=Development ./flow configuration:show --type Policy
FLOW_CONTEXT=Production ./flow configuration:show --type Policy

(you can pipe the result to a file with " > out.txt" and compare it with 
a tool like PhpStorm).


> I started to google around and found the information that in Flow 2.3.
> an acl for "everbody" is not needed anymore.

Where did you read that?


> Attached my Policy.yaml for both Contexts and this is the exception
> message:

Attachments don't work (for some clients) and cause unnecessary traffic 
(see [1]). Could you please upload the snippets somewhere or create a gist?


[1] http://typo3.org/support/mailing-lists/rules-guidelines


HTH

-- 
Bastian Waidelich