-
-
Notifications
You must be signed in to change notification settings - Fork 490
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
BaseGroup.mongodb.xml is invalid #1120
Comments
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Yes, bug is still relevant, to fix it the following changes
should be applied to the following files:
But it will break backward compatibility with |
This is not a BC break as long us you update the composer definition for this lib. Can you provide a PR @javer |
@sonata-project/release-managers Can you please tag a new release |
Closing as this was released already in 4.5.2 |
I still have the issue with the following packages: "require": {
"php": "^7.4",
"ext-ctype": "*",
"ext-iconv": "*",
"ext-intl": "*",
"friendsofsymfony/user-bundle": "^2.1",
"sonata-project/admin-bundle": "^3.93",
"sonata-project/doctrine-mongodb-admin-bundle": "^3.7",
"sonata-project/exporter": "2.x",
"sonata-project/intl-bundle": "^2.10",
"sonata-project/translation-bundle": "^2.7",
"sonata-project/user-bundle": "^4.11",
"symfony/apache-pack": "^1.0",
"symfony/dotenv": "^4.4",
"symfony/flex": "^1.12",
"symfony/framework-bundle": "^4.4",
"symfony/http-kernel": "^4.4",
"symfony/yaml": "^4.4",
"twig/twig": "^2.9"
}, Refs: |
Let me correct this. The mapping for this bundle has indeed been fixed: <?xml version="1.0" encoding="UTF-8"?>
<doctrine-mongo-mapping xmlns="http://doctrine-project.org/schemas/odm/doctrine-mongo-mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://doctrine-project.org/schemas/odm/doctrine-mongo-mapping http://doctrine-project.org/schemas/odm/doctrine-mongo-mapping.xsd">
<mapped-superclass name="Sonata\UserBundle\Document\BaseUser">
<field name="createdAt" type="date"/>
<field name="updatedAt" type="date"/>
<!-- Profile fields -->
<field name="dateOfBirth" type="date"/>
<field name="firstname" type="string"/>
<field name="lastname" type="string"/>
<field name="website" type="string"/>
<field name="biography" type="string"/>
<field name="gender" type="string"/>
<field name="locale" type="string"/>
<field name="timezone" type="string"/>
<field name="phone" type="string"/>
<!-- social fields -->
<field name="facebookUid" type="string"/>
<field name="facebookName" type="string"/>
<field name="facebookData" type="hash"/>
<field name="twitterUid" type="string"/>
<field name="twitterName" type="string"/>
<field name="twitterData" type="hash"/>
<field name="gplusUid" type="string"/>
<field name="gplusName" type="string"/>
<field name="gplusData" type="hash"/>
<!-- extra security fields -->
<field name="token" type="string"/>
<field name="twoStepVerificationCode" type="string"/>
<lifecycle-callbacks>
<lifecycle-callback type="prePersist" method="prePersist"/>
<lifecycle-callback type="preUpdate" method="preUpdate"/>
</lifecycle-callbacks>
</mapped-superclass>
</doctrine-mongo-mapping> But with the packages mentioned above I the the error for the
|
I linked the following issue there: FriendsOfSymfony/FOSUserBundle#2948 |
I have a symfony 4.3.5 application with sonata admin. A few days ago I had to perform the dependency update and this error is appearing in the package. I try, installing different versions but they all found me this error, which I didn't find documentation for their solution
Resources/config/doctrine/BaseGroup.mongodb.xml is invalid: Line 2:0: Element '{http://doctrine-project.org/schemas/orm/doctrine-mapping}doctrine-mapping': No matching global declaration available for the validation root.
COMPOSER.JSON
Can you help me verify what is happening? Thank you!
The text was updated successfully, but these errors were encountered: