Change the content type manager to work with the XML files
The content types should always be present. This issue should solve the problems when code is based on content types which are not available.
The requirements are using the following documentation on the Symfony website.
Here is explained how to `Load Resources` in your project. In the example is spoken about the Yaml loader. We prefer the Xml loader.
The directories added in can be registred with the CompilerPass. To check what kind of documents are set into the XML files, it’s an option to add the type of the document in the CompilerPass, see example.
The content types can’t be deleted in Integrated when they are added from the XML. The name of the `content type` can be changed by clicking on the edit button. The locked property shouldn’t be set in the Database. This will be build into the
The content type manager should read the XML files which are registred and add them to the database when not existing yet.
This manager is used several other files:
$definition->addMethodCall(’registerResource’, [ContentType:class, '@IntegratedContentBundle/Resources/config/integrated/content_types.xml']);
Undefined scenario, only for information
There is a possibility when there is already a content type added for example:
- id news
- class ContentType/Video
- label Video News
In the XML is added:
- id news
- class ContentType/News
- label News
What to do in this situation isn’t described in this document. Because the unique identifier is “id” the Content Type manager doesn’t do anything with this.
In de SPIKE is beschreven hoe het moet worden geïmplementeerd. Op basis van dit issue kan de documentatie geschreven worden.
.Notificatie preview gestuurd naar Integrated Marijn (email@example.com)
, i think that we need to discuss this instead of commenting. Can you plan in a meeting?
See the example in de the specs:
can you give your vision about the comments above? I was expecting it to work like my comments
the roles loader also uses a compiler pass, but looks into all bundles:
1. Should be discussed during the Integrated meeting
2. Removed (but comment should be placed into issue )
3. This should be a new issue (the specs are to use a compiler pass)