This application has different permission levels (company owners &
general system owners). To avoid copying functionality we want use the
same "user listing" (admin generated) action for those only with
different criteria. For this we are overriding the buildCriteria
method. This is a piece of cake.

Now, how can we distanciate the 2 different list views ? To explain :

- Normal User Listing (for company owner) : /user
- Admin User Listing (for system admins) : /user?view=admin

Now the problem is the generated templates (_pagination.php &
_list_th_tabular.php) do not pass this parameter when paging or
changing sorting.

There should be a simple way to avoid this ?

I already tried manually overriding the different templates, but every
change in generator.yml would mean you'd have to update/rewrite those
templates.

I tried this, and i do not seem to manage.
What i found in documentation :

The post http://www.symfony-project.org/blog/2008/10/31/new-in-symfony-1-2-the...
sais :

[quote]
If you want to tweak the admin generator to create your own theme, or
to bundle your extensions in a plugin, you will find that it is much
more easier now:
    * You don't need to copy all the files of the default theme to
create a new one. Just copy the files you need to override.
[/quote]

In sf1.2 book #admin generator http://www.symfony-project.org/book/1_2/14-Generators#Administration

[quote]
The generator templates are cut into small parts that can be
overridden independently, and the actions can also be changed one by
one.

However, if you want to override those for several modules in the same
way, you should probably create a reusable theme. A theme is a sub-set
of templates and actions that can be used by an administration module
if specified in the theme value at the beginning of generator.yml.
With the default theme, symfony uses the files defined in
$sf_symfony_lib_dir/plugins/sfPropelPlugin/data/generator/
sfPropelModule/admin/.

The theme files must be located in a project tree structure, in a data/
generator/sfPropelModule/[theme_name]/ directory, and you can
bootstrap a new theme by copying the files you want to override from
the default theme (located in $sf_symfony_lib_dir/plugins/
sfPropelPlugin/data/generator/sfPropelModule/admin/ directory):
[/quote]

So what i did :

I created a plugin and activated it (plugins/
tmpPropelGeneratorThemePlugin). Then i created the directory structure
from the instructions (above). See screenshot : http://www.shareapic.com/public/view/29772
Now i just copied the indexSuccess and added some various "blabla" in
the template to check if the template is used.

Then i changed the generator.yml to :

generator:
  class: sfPropelGenerator
  param:
    model_class:           UserProfile
    theme:                 tmp
    non_verbose_templates: false
    with_show:             false
    singular:              ~
    plural:                ~
    route_prefix:          autouser
    with_propel_route:     1

Now when i access the list view again :

[?php use_helper('I18N', 'Date') ?] [?php include_partial('profile/
assets') ?]
[?php echo
Fatal error: Call to a member function getValue() on a non-object in /
home/gnelisse/projects_local/trackmypeople/webroot/lib/core/lib/
generator/sfModelGenerator.class.php on line 284

I tried this, and i do not seem to manage.
What i found in documentation :

The post http://www.symfony-project.org/blog/2008/10/31/new-in-symfony-1-2-the...
sais :

[quote]
If you want to tweak the admin generator to create your own theme, or
to bundle your extensions in a plugin, you will find that it is much
more easier now:
    * You don't need to copy all the files of the default theme to
create a new one. Just copy the files you need to override.
[/quote]

In sf1.2 book #admin generator http://www.symfony-project.org/book/1_2/14-Generators#Administration

[quote]
The generator templates are cut into small parts that can be
overridden independently, and the actions can also be changed one by
one.

However, if you want to override those for several modules in the same
way, you should probably create a reusable theme. A theme is a sub-set
of templates and actions that can be used by an administration module
if specified in the theme value at the beginning of generator.yml.
With the default theme, symfony uses the files defined in
$sf_symfony_lib_dir/plugins/sfPropelPlugin/data/generator/
sfPropelModule/admin/.

The theme files must be located in a project tree structure, in a data/
generator/sfPropelModule/[theme_name]/ directory, and you can
bootstrap a new theme by copying the files you want to override from
the default theme (located in $sf_symfony_lib_dir/plugins/
sfPropelPlugin/data/generator/sfPropelModule/admin/ directory):
[/quote]

So what i did :

I created a plugin and activated it (plugins/
tmpPropelGeneratorThemePlugin). Then i created the directory structure
from the instructions (above). See screenshot : http://www.shareapic.com/public/view/29772
Now i just copied the indexSuccess and added some various "blabla" in
the template to check if the template is used.

Then i changed the generator.yml to :

generator:
  class: sfPropelGenerator
  param:
    model_class:           UserProfile
    theme:                 tmp
    non_verbose_templates: false
    with_show:             false
    singular:              ~
    plural:                ~
    route_prefix:          autouser
    with_propel_route:     1

Now when i access the list view again :

[?php use_helper('I18N', 'Date') ?] [?php include_partial('profile/
assets') ?]
[?php echo
Fatal error: Call to a member function getValue() on a non-object in /
home/gnelisse/projects_local/trackmypeople/webroot/lib/core/lib/
generator/sfModelGenerator.class.php on line 284

On Nov 7, 9:01 pm, Loïc Vernet <qrf_c...@yahoo.fr> wrote:

I did try/read this post (a long time ago). That post is a 1.0
tutorial and clearly not what i am trying to achieve.
I want to override only the templates i want to change, instead of
copy pasting the entire admin generator theme.

[quote]
The generator templates are cut into small parts that can be
overridden independently, and the actions can also be changed one by
one.
[/quote]

I did try/read this post (a long time ago). That post is a 1.0
tutorial and clearly not what i am trying to achieve.
I want to override only the templates i want to change, instead of
copy pasting the entire admin generator theme.

[quote]
The generator templates are cut into small parts that can be
overridden independently, and the actions can also be changed one by
one.
[/quote]

On Nov 7, 9:29 pm, Loïc Vernet <qrf_c...@yahoo.fr> wrote:

I tried this, and i do not seem to manage.
What i found in documentation :

The post http://www.symfony-project.org/blog/2008/10/31/new-in-symfony-1-2-the...
sais :

[quote]
If you want to tweak the admin generator to create your own theme, or
to bundle your extensions in a plugin, you will find that it is much
more easier now:
    * You don't need to copy all the files of the default theme to
create a new one. Just copy the files you need to override.
[/quote]

In sf1.2 book #admin generator http://www.symfony-project.org/book/1_2/14-Generators#Administration

[quote]
The generator templates are cut into small parts that can be
overridden independently, and the actions can also be changed one by
one.

However, if you want to override those for several modules in the same
way, you should probably create a reusable theme. A theme is a sub-set
of templates and actions that can be used by an administration module
if specified in the theme value at the beginning of generator.yml.
With the default theme, symfony uses the files defined in
$sf_symfony_lib_dir/plugins/sfPropelPlugin/data/generator/
sfPropelModule/admin/.

The theme files must be located in a project tree structure, in a data/
generator/sfPropelModule/[theme_name]/ directory, and you can
bootstrap a new theme by copying the files you want to override from
the default theme (located in $sf_symfony_lib_dir/plugins/
sfPropelPlugin/data/generator/sfPropelModule/admin/ directory):
[/quote]

So what i did :

I created a plugin and activated it (plugins/
tmpPropelGeneratorThemePlugin). Then i created the directory structure
from the instructions (above). See screenshot : http://www.shareapic.com/public/view/29772
Now i just copied the indexSuccess and added some various "blabla" in
the template to check if the template is used.

Then i changed the generator.yml to :

generator:
  class: sfPropelGenerator
  param:
    model_class:           UserProfile
    theme:                 tmp
    non_verbose_templates: false
    with_show:             false
    singular:              ~
    plural:                ~
    route_prefix:          autouser
    with_propel_route:     1

Now when i access the list view again :

[?php use_helper('I18N', 'Date') ?] [?php include_partial('profile/
assets') ?]
[?php echo
Fatal error: Call to a member function getValue() on a non-object in /
home/gnelisse/projects_local/trackmypeople/webroot/lib/core/lib/
generator/sfModelGenerator.class.php on line 284

If you want to tweak the admin generator to create your own theme, or
to bundle your extensions in a plugin, you will find that it is much
more easier now:
    * You don't need to copy all the files of the default theme to
create a new one. Just copy the files you need to override.

This is exactly what i am trying todo. I do appreciate your help, but
i have created many 1.0 & 1.1 admin generator themes without a
problem. This problem is different.

On Nov 7, 9:40 pm, Loïc Vernet <qrf_c...@yahoo.fr> wrote:

On Nov 7, 10:03 pm, Loïc Vernet <qrf_c...@yahoo.fr> wrote:

In the generated actions class of the new admin gen in sf 1.2, the
executeFilter(sfWebRequest $request) function does not merged
parameter with the existing filters. Thus from an author index page,
if you create an action to link from an author directly to its list of
articles (i.e. http://..//backend_dev.php/articles/filter?author_id=1,
you are redirected to your articles index page but nothing is
filtered.

To achieve my gooal I have overwrited the executeFilter method by
modifying the line :

$this->setFilters($this->filters->getValues()) to $this->setFilters
(array_merge($this->filters->getValues(), $request->getParameterHolder
()->getAll()));

=> I have tested both with sfpropelplugin and sfdoctrineplugin.  It
also populates your filter form.

Note that I opened a ticket for it (please visit :
http://trac.symfony-project.org/ticket/4871) but I do not know if it
will be included in the generator regarding Fabiens' answer.

Regards,