Databases
StackOverflow2013
Postsdbo
POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
    primarykey
    data
    text
    <p>I've hitting my head against the wall for countless hours now and I hope SO can be of help!</p> <p>I have Retailer, Branch and RetailerBranches entities which work just fine, retailers can have many branches and a branch can only have one retailer. The hard part happens when trying to make Sonata Admin (SonataAdminBundle) play nice with that relationship. In their simplest form, they look like this:</p> <p><strong>Retailer entity</strong></p> <pre><code> /** * @ORM\Column(name="ID", type="integer", nullable=false) * @ORM\Id * @ORM\GeneratedValue(strategy="IDENTITY") */ private $id; /** * Relation * * @ORM\OneToMany(targetEntity="RetailerBranches", mappedBy="Retailer", cascade={"persist"}) */ protected $branches; public function __construct() { $this-&gt;branches = new ArrayCollection(); } </code></pre> <p><strong>RetailerBranches join table</strong></p> <pre><code> /** * @ORM\Column(name="ID", type="integer", nullable=false) * @ORM\Id * @ORM\GeneratedValue(strategy="IDENTITY") */ private $id; /** * @ORM\JoinColumn(name="Retailer_ID", referencedColumnName="ID", nullable=false) * @ORM\ManyToOne(targetEntity="Retailer", inversedBy="branches") */ private $retailer; /** * @ORM\JoinColumn(name="Branch_ID", referencedColumnName="ID", nullable=false, unique=true) * @ORM\OneToOne(targetEntity="Branch", inversedBy="retailer") */ private $branch; </code></pre> <p><strong>Branch entity</strong></p> <pre><code> /** * @ORM\Column(name="ID", type="integer", nullable=false) * @ORM\Id * @ORM\GeneratedValue(strategy="IDENTITY") */ private $id; /** * Relation * * @ORM\OneToOne(targetEntity="RetailerBranches", mappedBy="branch", cascade={"persist"}) */ private $retailer; </code></pre> <p>The harder part happens when trying generate the form to allow that relationship to take shape:</p> <p><strong>RetailerAdmin</strong></p> <pre><code>protected function configureFormFields(FormMapper $formMapper) { $formMapper -&gt;with('Branches') -&gt;add('branches', 'sonata_type_collection', array( 'required' =&gt; false, 'by_reference' =&gt; false ), array( 'edit' =&gt; 'inline', 'inline' =&gt; 'table', )) -&gt;end() ; } </code></pre> <p><strong>RetailerBranchesAdmin</strong></p> <pre><code>protected function configureFormFields(FormMapper $formMapper) { if ($this-&gt;hasRequest()) { $link_parameters = array('context' =&gt; $this-&gt;getRequest()-&gt;get('context')); } else { $link_parameters = array(); } $formMapper -&gt;add('succursale', 'sonata_type_model_list', array( 'class' =&gt; 'VeloRetailerBundle:Branch', 'required' =&gt; false, ), array( 'edit' =&gt; 'inline', 'inline' =&gt; 'table', )) ; } </code></pre> <p><strong><em>The problem:</em></strong></p> <p>All this sort of works, here's a screenshot: <img src="https://i.stack.imgur.com/YPX0L.png" alt="enter image description here"></p> <p>There's a Retailer and its Branches. Yay.</p> <p>Problem 1: The "Add new" button at the bottom attempts to add a RetailerBranches object instead of a simple Branch object which obviously doesn't work.</p> <p>Problem 2: This method also doesn't allow the user to modify a Branch inline.</p> <p>I feel like I'm close to the solution, but I just cannot quite get there. Any help would be greatly appreciated!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPier-Luc Gendreau
    1. USPier-Luc Gendreau
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
      1. USwhiteletters in blankpapers
      1. VTFavorite
    3. VO
      singulars
      1. POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis Sonata again... I see so many people fighting it longer than it'd take to write all that stuff yourself. Why do you need it at all? If you need stuff like Sonata, you probably want a CMS, not a framework.
      singulars
      1. POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
      1. USElnur Abdurrakhimov
    2. COThat's what I'm about to do. It's a neat piece of code, but the documentation is so, so poor.
      singulars
      1. POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
      1. USPier-Luc Gendreau
    3. COI have found another way to get this done, will work on it tomorrow and post my findings.
      singulars
      1. POSymfony2 1:M / 1:1 Relationship and Sonata Admin Form
      1. USPier-Luc Gendreau
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload