Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.14.2: libxml errors after patch release update #10626

Closed
ro0NL opened this issue Apr 13, 2023 · 3 comments
Closed

2.14.2: libxml errors after patch release update #10626

ro0NL opened this issue Apr 13, 2023 · 3 comments

Comments

@ro0NL
Copy link

ro0NL commented Apr 13, 2023

  - Upgrading doctrine/orm (2.14.1 => 2.14.2)

this PATCH release breaks our tree entities:

+ bin/console doctrine:migrations:migrate --allow-no-migration -v -n

In MappingException.php line 1005:
                                                                                                                                                                                              
  [Doctrine\ORM\Mapping\MappingException]                                                                                                                                                     
  libxml error: Element '{http://gediminasm.org/schemas/orm/doctrine-extensions-mapping}tree': No matching global element declaration available, but demanded by the strict wildcard.         
   in /app/config/doctrine/Entity.Some.orm.xml at line 18   
@ro0NL ro0NL changed the title 2.14.2: libxml errors 2.14.2: libxml errors after patch release update Apr 13, 2023
@greg0ire
Copy link
Member

Duplicate of doctrine/DoctrineBundle#1643

@greg0ire greg0ire marked this as a duplicate of doctrine/DoctrineBundle#1643 Apr 13, 2023
@ro0NL
Copy link
Author

ro0NL commented Apr 13, 2023

i guess. the breakage on our side was solely due Upgrading doctrine/orm (2.14.1 => 2.14.2)

@greg0ire
Copy link
Member

greg0ire commented Apr 13, 2023

Kinda… it should have happened when upgrading doctrine bundle to 2.9, but didn't because of a bug fixed in ORM 2.14.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants