StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15680268
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-28T11:10:59.483
FavoriteCount
0
LastActivityDate
2013-03-28T11:10:59.483
LastEditDate
2017-05-23T11:47:08.517
LastEditorUserId
-1
OwnerUserId
995072
ParentId
15665114
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
In the end, the most straightforward solution was to define a var in the Admin class as follows: <pre><code> <?php namespace Acme\AcmeBundle\Admin; use Sonata\AdminBundle\Admin\Admin; use Sonata\AdminBundle\Datagrid\ListMapper; use Sonata\AdminBundle\Datagrid\DatagridMapper; use Sonata\AdminBundle\Validator\ErrorElement; use Sonata\AdminBundle\Form\FormMapper; class AcmeAdmin extends Admin { // two options to define var and make them available to twig by admin. mechanism public $dateFormat = "Y-m-d";// ---> this var is available in twig : admin.dateFormat // or to allow better relation to context public $parameters = array();// ---> this array is available in twig : admin.parameters.x.y.z protected function configureListFields(ListMapper $listMapper) { // assuming the $dateFormat is not set, by convention it could be defined here with proper intent in mind // it could then be contained in an array like that $this->parameters = array('listmapper' => array('dateFormat' => 'Y-m-d',),); // then specialized in twig : admin.parameters.listmapper.dateFormat $listMapper ->addIdentifier('acme_field') ->add('date', 'date', array( 'template' => "AcmeBundle:CRUD:list_date.html.twig",// checking admin.parameters.listmapper.dateFormat )) ->add('_action', 'actions', array( 'actions' => array( 'edit' => array(), 'delete' => array(), ), )) ; } </code></pre> Then in twig: <pre><code> {% block field%} {% if value is empty %} &nbsp; {% else %} {# retrieving the dateFormat variable from the listmapper by convention... twig is very forgiving in eval, so checking for defined var is peachy e.g if admin.parameters is not defined or empty then else is triggered #} {% if admin.parameters.listmapper.dateFormat is defined %} {{ value|date(admin.parameters.listmapper.dateFormat)|title }} {% else %} {{ value|localizeddate('medium', 'none')|title }} {% endif %} {% endif %} {% endblock %} </code></pre> Thanks to <a href="https://stackoverflow.com/questions/11482910/sonata-admin-add-custom-triggers-actions-to-list-edit-action?rq=1">Sonata Admin: Add custom triggers/actions to list/edit action</a> I realized/remembered/connected the dots... that twig has access to the admin variable, so by defining a variable in the class we can retrieve it in twig. Now, it is just a question of convention to put in place a sort of constraint to a container for the admin variables. (cf parameters array) For this particular case, this solution does not add any point as localizeddate serves well my purpose, however, for the sake of the argument it is good to know IMHO. Cheers, Hope that helps! Vinz
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIn symfony2 with sonata: How to pass a variable to the template defined for a given field of the listmapper in the method configureListFields?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USMediaVince
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.