I already have sfGuardUserGeneratorConfiguration.class.php in my
application, so adding this function to it is exactly what i
needed :-)
I like this solution.
Thank you very much.
On 4 bře, 10:14, Daniel Lohse <annismcken...@googlemail.com> wrote:
> There is another way. It's one that does not involve these "hacky" things.
>
> Simply copy the sfGuardUserGeneratorConfiguration.class.php to your
> apps/backend/modules/sfGuardUser/lib/ folder and add the following code:
>
> public function getFilterDisplay()
> {
> $display = parent::getFilterDisplay();
> unset($display['permissions_list']);
>
> return $display;
>
> }
>
> Then copy the actions.class.php of the sfGuardUser module to
> apps/backend/modules/sfGuardUser/actions/ and change the include like so:
>
> require_once
> dirname(__FILE__).'/../lib/sfGuardUserGeneratorConfiguration.class.php';
>
> I know it's a bit involving. But: you don't lose anything by doing it this
> way, you can upgrade the plugin, it stays extensible and this way is not
> hacky in any way. :)
>
> Cheers, Daniel
>
> On 04.03.2010, at 09:56, Tom Ptacnik wrote:
>
>
>
> > I found a solution, not nice, but it's simple and it works for me
>
> > filter:
> > display: [username, is_active, is_active, is_active]
>
> > It somehow overwrites the array of the original generator.yml, and the
> > is_active is showed only once.
>
> > On 4 bře, 09:52, Tom Ptacnik <to...@tomor.cz> wrote:
> >> Hi,
>
> >> I have problem with customizing the generator of the sfGuardUser. I
> >> want to remove the permissions_list from the filter form.
>
> >> I've copied the generator.yml file from the plugin folder to my apps/
> >> backend/modules/sfGuardUser/config/generator.yml
>
> >> If I siply remove the permissions_list from the generator filter
> >> settings nothing happen...
>
> >> original:
> >> filter:
> >> display: [username, is_active, groups_list, permissions_list]
>
> >> my change:
> >> filter:
> >> display: [username, is_active, groups_list]
>
> >> Do you have some solution? Thank you.
>
> >> I found that others have problem with that to and the only know
> >> solution is dirty - remove the original generator.yml from the plugin
> >> folder
>
> >> related ticket, topic:
> >> http://trac.symfony-project.org/ticket/8139
> >> http://forum.symfony-project.org/index.php/m/43279/
>
> > --
> > If you want to report a vulnerability issue on symfony, please send it to
> > security at symfony-project.com
>
> > You received this message because you are subscribed to the Google
> > Groups "symfony users" group.
> > To post to this group, send email to symfony-users@googlegroups.com
> > To unsubscribe from this group, send email to
> > symfony-users+unsubscr...@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/symfony-users?hl=en
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
