I just tried all: is_secure: on
default: is_secure: on media: is_secure:on job: is_secure: on media and job being my main data types Is that what you mean? Either way, none of the above worked for me. On Feb 25, 1:34 pm, vadim <[email protected]> wrote: > Maybe you should try to write in your /module/security.yml like this: > > your_action: > is_secure: on > > another_action: > is_secure: on > > I don't know why, but writing "is_secure: on" for the whole module in > global security.yml file (like in sfuardPlugin's readme chapter) > doesn't work for me. > > On 25 фев, 15:28, ckemmler <[email protected]> wrote: > > > I did the whole tutorial once again - this time the sfGuardPlugin was > > kind enough to download and install... and work. > > Then I redid it once again, this time modifying the name of the > > classes to fit my needs. Everything worked fine until the end... I > > installed the sfGuardPlugin again, and set is_secured to "on" in > > security.yml, etc etc. BUT... it's just not working, i.e. I'm not > > prompted for a password whenever I try to get the backend console. > > > What could I have done wrong? Where can I look. > > > Thanks in advance, > > > Candide --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
