> . . . I want the create button not shown to everybody, So I just tried:
>
> _create: { credentials: [no_exist] }
The books covers how to add a custom interaction, but how can I disable an existing interaction? e.g., how can I stop the create / delete interaction from showing?
> . . . I want the create button not shown to everybody, So I just tried:
>
> _create: { credentials: [no_exist] }
It works.
> But the create button is still there.
do not log in as admin.
Yes, if you are using sfGuard and logged in as admin though (because you then have all rights (or actually bypassing the credential system)), it will not work.
To remove/disable all actions for everyone you should declare an empty array:
list: actions: []
documented on: 28 August 2007, lvanderree
Sometimes, you want to do something just before or just after saving or deleting an object in the admin generator. To do that, you can override the saveObject() and/or deleteObject() method in your actions.class.php file:
protected function saveCustomer($customer)
{
// pre save hook
$customer->setManagerId($this->getUser()->getManagerId());
// call the parent save() method
parent::saveCustomer($customer);
// post save hook
}
You can also bypass the parent method if you want.
protected function deleteCustomer($customer)
{
$customer->isDeleted(true);
// save the customer object
$this->saveCustomer($customer);
// bypass the deletion by not calling the parent method
}
by Fabien Potencier on 2006-05-21, tagged admin
For example, say I access my 'apps/my_app/modules/my_mod' module via
The illustrated code should be put at:
apps/my_app/modules/my_mod/actions/actions.class.php
as
protected function saveMyMod($info)
{
}
If you need to access the values passed from the admin generator edit form, the
$this->getRequestParameter('my_mod');
would returns an array containing the values filled in the admin generator edit form.
documented on: 2007.08.23
Most often, it is better to override save() and delete() methods in model level, instead of doing in admin generator's actions.class.php, i.e., the view layer. This is how:
Say we are extending the 'MyObj' class. Put the following in file
lib/model/MyObj.php
<?php
/**
* Subclass for representing a row from the table.
*
* @package lib.model
*/
class MyObj extends BaseMyObj
{
// == Extend the model for business logic
public function save($con = null)
{
// == pre save hook
// fill prereq fields
// == call the parent save() method
parent::save($con);
// == post save hook
// fill extra fields
$update_comment = ...;
$this->doAddComment($update_comment);
}
}
documented on: 2007.08.22
I've watched the admin generator screencast several times but still wasn't able to figure out the trick:
when it is intially generated, the html drop-down list of lookup table, eg
author, was 1, right after custimization start, the html drop-down list
starts to be meaningful, eg, showing actual author names instead of
numeric 1.
the trick was not (clearly) explained in the vidoe, I'm just wondering what exactly the trick that enable it.
Implement the '__toString' function in lookup table object, Author & Category. Done in lib/model/Author.php & lib/model/Category.php.
T
documented on: 2007.02.01
you have to deal with __toString method of your model classes. Take a look at http://www.symfony-project.org/book/trunk/08-Inside-the-Model-Layer
documented on: 02 February 2007, Alessandro
[adapted from http://www.symfony-project.org/forum/index.php?t=msg&goto=23997#msg_23997]
I have a table with a foreign key. The referenced table contains a list of items which are possible to select for a field in the main table. I want to limit the referenced table drop down list in the filter part of list form. So
In my Peer class of the referenced table, I create a method doSelectTypeOne() which returns desired records, as mshramko suggested.
then add to my generator.yml…
list:
filters:
- FIELDNAME
fields:
FIELDNAME: { params: peer_method=doSelectTypeOne }
where FIELDNAME is the name of the foreign key field in my table.
However, the drop down list from filter still contains records from the whole referenced table, not the selected one.
What could be wrong?
> What could be wrong?
syntax mistake in generator.yml. Fixed in OP. Works perfectly well after being fixed.
I have a table with a foreign key. The referenced table contains a list of items which are possible to select for a field in the main table. When I add/edit data in the main table (after I created a __toString() method for the referenced table) all records from the referenced table are displayed as a drop down box.
The problem is I [want to limit] the referenced table [drop down list with] only those with field referencedtable.type = 1.
In your Peer class [of the referenced table] you create a method doSelectTypeOne() which returns only objects of type 1, as mshramko suggested.
then add to your generator.yml…
edit:
fields:
FIELDNAME: { params: peer_method=doSelectTypeOne }
where FIELDNAME is the name of the foreign key field in your table.
documented on: 19 March 2007, flat stanley
One of my most important problem is the reorder of the select menus generated with the foreign values.
Order are done by id and I can't find how to change that.
In order to order the dropdown list, ie, the foreign look up table, you need to define a custom sort order using the peer_method. Here is an example.
Here, the foreign table is staff and foreign key is staff_id.
In the generator.yml on the main admin generator form:
edit:
fields:
staff_id: { params: peer_method=getSortedByName }
In lib/model/StaffPeer.php:
class StaffPeer extends BaseStaffPeer
{
// return staff list in the order of First name, Last name
public static function getSortedByName() {
$c = new Criteria();
$c->addAscendingOrderByColumn(StaffPeer::FIRST_NAME);
$c->addAscendingOrderByColumn(StaffPeer::LAST_NAME);
return StaffPeer::doSelect($c);
}
. . .
Fields definitions can be found in 'lib/model/om/BaseStaffPeer.php'.
xpt
documented on: 2007.09.20
> do i have the opportunity to list my items in the select tag of my edit form > by name ?
I think it might be possible to define a custom sort order using the peer_method.
documented on: 13 February 2007, mikenolan
Am I right in thinking that Aston wants to sort the order of your select tag?
Here's a quick example I just applied to my 'Page' class and admin generator. It has a parent_id which is a foreign key to itself.
In the generator.yml:
generator:
class: sfPropelAdminGenerator
param:
model_class: Page
theme: default
edit:
fields:
parent_id:
params:
include_blank: true
peer_method: getSorted
Then in the PagePeer class I added:
public static function getSorted() {
$c = new Criteria();
$c->addAscendingOrderByColumn(PagePeer::TITLE);
return PagePeer::doSelect($c);
}
Clear the cache and reload and your select tag should be sorted alphabetically!
documented on: 15 February 2007, mikenolan
Hi,
How to present content of the Many-to-Many List in the order that I want?
Using the book as an example, http://www.symfony-project.org/book/trunk/14-Generators#Many-to-Many%20Relationships
Listing 14-30 shows how to handle many-to-many relationships with a through_class parameter. Based on my reading, I should change it to something like:
edit:
fields:
article_author: { type: admin_double_list, params: through_class=ArticleAuthor peer_method=getSortedByName }
And in ArticleAuthorPeer class implement a method getSortedByName, something like:
// return staff list in the order of First name, Last name
public static function getSortedByName() {
$c = new Criteria();
$c->addAscendingOrderByColumn(ArticleAuthorPeer::FIRST_NAME);
$c->addAscendingOrderByColumn(ArticleAuthorPeer::LAST_NAME);
return ArticleAuthorPeer::doSelect($c);
}
But the problem is, ArticleAuthorPeer::doSelect don't have the ArticleAuthorPeer::FIRST_NAME, ArticleAuthorPeer::LAST_NAME fields. To use those fields, I should use doSelectJoinAuthor method, but what it returns is not comply with what the peer_method requires. So,….?
Please help
peer_method doesn't work with many to many controls.
I recently asked the same question on the mailing list and got this reply which worked for me….
You can override doSelect in your peer class [in the AuthorPeer class]:
public static function doSelect(Criteria $criteria, $con = null)
{
// by default order by name /// getOrderByColumns()
if(count($criteria->getOrderByColumns()) == 0)
{
$criteria->addAscendingOrderByColumn(self::NAME);
}
return self::populateObjects(self::doSelectRS($criteria, $con)); }
flat stanley
> > You can override doSelect in your peer class > > Could you elaborate a bit more please? Sorry to be dense, here are my > confusions. > > By peer class, I guess it's the peer class of the table that holds the > Many-to-Many List. I.e., the ArticleAuthor. If so, > > However, the Many-to-Many table only contains 3 fields, id of its own, and > ids for the link. In your example, how can you sort by name then?
In your example, you have articles and authors.
So, for instance, you might choose to use the "admin_check_list" control in the admin module for articles. When you edit an article, you can assign authors to it by selecting the check boxes but the list of authors will be ordered by id. If you want the list in alphabetical order, you can override the doSelect function in the AuthorPeer class to return the results ordered by name, if no other order has been assigned. (as is shown in the example from my previous post).
documented on: 05 April 2007, Jonathan, aka, flat stanley
Well, I had to use a special select for the AllObjects list of admin_double_list and so I modified symfony the following way to support a peer_method param for admin_double_list…
I would like to see my changes in PEAR/symfony/addon/propel/sfPropelManyToMany.class.php and PEAR/symfony/addon/propel/sfPropelManyToMany.class.php to be included in symfony.
I've implemented the patch and attached it under the ticket #1633 in the symfony trac. (see http://trac.symfony-project.org/trac/ticket/1633)
I don't know if fabien decides to merge it, though.
documented on: 18 July 2007, JanBlaha
I had always been wondering, how can I make use of the existing Admin Gen generated code, save and use them somewhere else, then twist it further which might beyond symfony's capability, or as the last step to arrange the input fields better, eg, group several entries on one line instead of spreading them vertically, etc.
Plese help/comment.
In the meantime, I notice an interesting topic going on at: http://www.symfony-project.org/forum/index.php?t=msg&th= 7947&start=0&
Which indicates that, there are at least 3 ways doing so:
twist directly in cache, which face the problem that the changes can be overwritten at any moment.
copy them to myapp/modules/module/template folder, and twist there.
or change theme if you want to make the changes happen automatically.
Furthermore, instead of the current list/edit actions, can we add our own actions, eg, view1, view2, so that we can have multiple views to the same module? Ref, currently the symfony AdminGen interface lacks the possibility to have multiple views to the same module (msg posted at http://www.symfony-project.org/forum/index.php?t=msg&th= 7705),
thanks
I think you answered your first question yourself.
You can copy the files from cache to your module/template folder and alter them there.
If you want to have these changes in more than one module it is wise to change your theme instead.
About your second question, about I think a good solution is to create a second module for the same object, but give it an other name.
The command-line for that is simply
symfony propel-init-admin <app> <module-name-2> <object-name>
E.g., I have a module assignment and I created a new module assignment2 by only typing:
symfony propel-init-admin backend assignment2 Assignment
And when i browse to http://localhost/backend_dev.php/assignment2 it works immediately.
and edit your generator to match it for your other view, maybe change the actions.class.php file to redirect the edit action to the first module and change the actions.yml file of the first module to redirect you back to module2 once you have saved your changes.
An other solution for your second problem would be to add this capability in your theme as well. Which is probably even nicer.
documented on: 28 August 2007, lvanderree
> I understand that the administration-generated modules don't have a show > action by default. How could I add it?
+1 , i'd really like this functionnality too, for exemple for a user that wouldn't have the write to edit but to view the record.
documented on: 02 February 2007, COil
ok guys, here you have it:
admin generator theme with show functionality
FIRSTLY: do not overwrite your Symfony installation, copy the files into your project directory!
with_show.zip - the actual generator themeextract the content into:
{PROJECT_DIR}/data/generator/sfPropelAdmin/
main.css - replacement for the current admin css (download the file from my next reply) I've made two little changes to display the show page in simmilar way to the edit page put it into your web/sf/sf_admin/css/ directory
Usage:
form generation:
symfony propel-init-admin <APP_NAME> <MODULE_NAME> <CLASS_NAME> with_show
the ending 'with_show' is crucial, otherwise the generator will use the default theme
customisation using generator.yml, similar way as with edit forms
I haven't tested this thoroughly so use it at your own risk.
IF YOU FIND BUGS DO NOT BUG THE SYMFONY TEAM. this is not part of the official release.
If you find it valuable I'll submit the code to trac.
documented on: 03 February 2007, pezetgee
> put it into your web/sf/sf_admin/css/ directory
The directory for admin theme is not more valid, it must be part of a plugin now in 1.0.0
documented on: 03 February 2007, COil
> I have upgraded on of my project to 1.0 but now my custom admin theme is > simply ignored.
Create it as a plugin, it works.
My structure is
/plugins/adminTheme/
/data/
/generator/
/sfPropelAdmin/
/myTheme/
/skeleton/
/template/
documented on: 11 December 2006, Draven
> My theme param is myTheme > > theme: myTheme > > But the adminTheme directory is not specific ?
Yes it was just the name I choose to use, it doesn't matter what you call it.
The theme: "name" does need to match what you called your theme in the sfPropelAdmin/ folder.
documented on: 11 December 2006, Draven
> i tried to move it in : > > plugins\sfBackendPlugin\data\generator\sfBackendAdmin\ > > and in my generator.yml > > theme: sfBackend > > where is (skeleton and template dir) > > what is correct or way to proceed ?
Francois wrote :
plugins\sfBackendPlugin\data\generator\sfPropelAdmin\sfBackend\
Don't forget to clear the cache even in dev mode
documented on: 13 December 2006, COil