Chapters

28 Chapters | 2:24:59 |

01

Give me Clean URL Strings (slugs!)

5:39
02

DoctrineExtensions: Sluggable

4:59
03

Refactoring Carefully

3:41
04

ManyToMany Relationship

5:18
05

Inserting into a ManyToMany

5:27
06

Fetching Items from a ManyToMany Collection

3:45
07

ManyToMany: The Inverse Side of the Relationship

6:45
08

Removing a ManyToMany Item

5:16
09

Hooking up the Scientist Removal JavaScript

2:50
10

ManyToMany & Fixtures

3:30
11

Joining Across a ManyToMany + EXTRA_LAZY Fetch

5:34
12

EntityType Checkboxes with ManyToMany

5:39
13

Saving the Inverse Side of a ManyToMany

4:03
14

Form by_reference + Adder and Remover

4:40
15

Synchronizing Owning & Inverse Sides

4:03
16

ManyToMany with Extra Fields

8:20
17

Join Entity App Refactoring

2:40
18

Using the new OneToMany Collections

5:46
19

Embedded Form: CollectionType

6:36
20

Collection Delete & allow_delete

4:49
21

Deleting an Item from a Collection: orphanRemoval

5:14
22

CollectionType: Adding New with the Prototype

7:07
23

Adding to a Collection: Cascade Persist

6:04
24

Embedded Form Validation with @Valid

5:05
25

Customizing the Collection Form Prototype

5:56
26

Form Events: A readonly Embedded Field

4:46
27

Collection Filtering: The Easy Way

6:05
28

Criteria System: Champion Collection Filtering

5:24

> Symfony 3 > Doctrine Collections: ManyToMany, Forms & other Complex Relations

Buy Access to Course

13.

Saving the Inverse Side of a ManyToMany

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

6 Comments

Sort By

Login or Register to join the conversation

Alessandro-D 6 years ago edited

I am having such a hard time trying to fix this issue.
Basically I have a "User" and "Profession" entity and I have a ManyToMany relationship between the two.
The user has the ability to edit their own profile, which they can do it via the form. The form at the moment display all basic information contained in the User table.
I now want to allow users to edit their own professions too, therefore I added the following to my ProfileFormType class:


            ->add('profession', EntityType::class, [
                'class'=> Profession::class,
                'multiple'=> true
            ])

When I try now to edit the profile, I can see the "profession" field with all the options and the one already assigned to the user are selected. The problem starts when I try to add/remove additional professions. When I try to save them, it doesn't do anything and I don't know why.
Inside the "User" class I have this:


    /**
     * @ORM\ManyToMany(targetEntity="App\Entity\Profession", mappedBy="user")
     */
    private $professions;
    ...
    ...

    public function addShowreel(Showreel $showreel): self
    {
        if (!$this->showreels->contains($showreel)) {
            $this->showreels[] = $showreel;
            $showreel->setUser($this);
        }

        return $this;
    }

    public function removeShowreel(Showreel $showreel): self
    {
        if ($this->showreels->contains($showreel)) {
            $this->showreels->removeElement($showreel);
            // set the owning side to null (unless already changed)
            if ($showreel->getUser() === $this) {
                $showreel->setUser(null);
            }
        }

        return $this;
    }

    public function getProfessions(): Collection
    {
        return $this->professions;
    }

    /**
     * @return Collection|Profession[]
     */
    public function getProfession(): Collection
    {
        return $this->professions;
    }

and inside the Profession class, I have this:


    /**
     * @ORM\ManyToMany(targetEntity="App\Entity\User", inversedBy="professions")
     */
    private $user;
    ...
    ...
    /**
     * @return Collection|User[]
     */
    public function getUser(): Collection
    {
        return $this->user;
    }

    public function addUser(User $user): self
    {
        if (!$this->user->contains($user)) {
            $this->user[] = $user;
        }

        return $this;
    }

    public function removeUser(User $user): self
    {
        if ($this->user->contains($user)) {
            $this->user->removeElement($user);
        }

        return $this;
    }

My Profile controller (in the edit function) I have this:


$user = $this->getUser();
$form = $this->createForm(ProfileFormType::class, $user);
$form->handleRequest($request);
if ($form->isSubmitted() && $form->isValid()) {
            $em->persist($user);
            $em->flush();
            return $this->redirectToRoute('grm_profile');
}

Sorry for the length of this post, but I really need some help. I have tried slack, IRC but I can't find anyone who can help me understand what is wrong with it.

Thanks,
Alessandro

|

weaverryan SFCASTS Alessandro-D 6 years ago edited

Hey Alessandro!

Hmm, ok. Here are the things that I'm looking at to make sure this works correctly:

1) You added a profession field to your form - but the property on your entity is called professions (with an "s"). This should have caused an error. If there is no error, it must mean that you have (I'm guessing?) a getProfession() and setProfession() method in your User class? Those should not be there. Basically, make sure that in your form, the field is called professions (with an s).

2) Assuming the name of the field in the form is professions, I would next look to make sure that your User class has addProfession() and removeProfession() methods. These should have been generated for you if you created the relationship via make:entity. You should not have a setProfessions method. Basically, because the field in your form is called professions, when you submit the form, Symfony will first look for a setProfessions() method. If it exists, it will call it. We actually don't want that :). If it does not find this method, it will then look for addProfession() and removeProfession: it will call each method one time for all the professions that were added/removed by the user in the form. We WANT this.

3) Side note: in Profession, it looks like the name of the property is "user". It should be "users" for clarity: it will hold an array of User objects :).

4) Here is the key: ultimately, because the Profession.user (which really should be Profession.user for clarity) is the "owning" side of the relationship, we ultimately need that side of the relation to be set. If the new data were only set onto User.professions, Doctrine will not save the updated data in the database. This is almost definitely what's happening to you. To make that happen, if you used make:entity to generate the relationship, the code inside the addProfession() and removeProfession methods will already contain code to do this. That will be enough to updating the Profession.user property and everything will save.

The easiest way to get things cleaned up might be to:

A) remove the relationship entirely from Profession and User (remove all the "user" code from Profession - the property, methods, etc and then remove all the "profession" code from User).

B) Re-generate the relationship with make:entity so that all the properties and methods are set up correctly.

Let me know if this helps!

Cheers!

1 |

Paul Z. 8 years ago

Where is this in the ''finish' code folder?

|

Victor SFCASTS Paul Z. 8 years ago

Hay Dave,

What exactly can't you find in the "finish/" folder?

Cheers!

|

Paul Z. Victor 8 years ago

I couldn't find any of the code to save the inverse many-to-many. I understand now that the finish folder is the end of this whole course, not this chapter. At the end of this course the many-to-many is turned into a one-to-many / many-to-one so that's why it's not there. Sorry for my misunderstanding, although it would be nice to have the code after each chapter since things keep changing.

|

Victor SFCASTS Paul Z. 8 years ago

Hey Dave,

Sorry for misleading you. Actually, we have an issue about this, but it's not prioritized yet. But for now, you can use our handy expandable code block below each video. You can even expand the entire file by pressing "Show All Lines" button (double arrows in the left top corner of each code block) to get more context. Plus, keep in mind "Copy" button in the right top corner, it prevent you to select the code manually.

Cheers!

|

This course is built on Symfony 3, but most of the concepts apply just fine to newer versions of Symfony.

Symfony 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "symfony/symfony": "3.4.*", // v3.4.49
        "doctrine/orm": "^2.5", // 2.7.5
        "doctrine/doctrine-bundle": "^1.6", // 1.12.13
        "doctrine/doctrine-cache-bundle": "^1.2", // 1.4.0
        "symfony/swiftmailer-bundle": "^2.3", // v2.6.7
        "symfony/monolog-bundle": "^2.8", // v2.12.1
        "symfony/polyfill-apcu": "^1.0", // v1.23.0
        "sensio/distribution-bundle": "^5.0", // v5.0.25
        "sensio/framework-extra-bundle": "^3.0.2", // v3.0.29
        "incenteev/composer-parameter-handler": "^2.0", // v2.1.4
        "composer/package-versions-deprecated": "^1.11", // 1.11.99.4
        "knplabs/knp-markdown-bundle": "^1.4", // 1.9.0
        "doctrine/doctrine-migrations-bundle": "^1.1", // v1.3.2
        "stof/doctrine-extensions-bundle": "^1.2" // v1.3.0
    },
    "require-dev": {
        "sensio/generator-bundle": "^3.0", // v3.1.7
        "symfony/phpunit-bridge": "^3.0", // v3.4.47
        "nelmio/alice": "^2.1", // v2.3.6
        "doctrine/doctrine-fixtures-bundle": "^2.3" // v2.4.1
    }
}

Previous Chapter

Next Chapter