All records which are not saved or useable are now skipped.
Some records were converted but could not be stored, e.g. because no
localization was configured for that table.
This should bring small performance improvement and also align import
log with actually imported (converted) records.
Logging is added as well, only debug level, to allow developer and
integrator to analyse why some records are skipped.
Ignore some errors which don't actually exist.
We already check type of entity, and logger is always injected.
Use Symfony components to map incoming JSON onto objects.
Those provide a mapping. They can then be used to fetch the data in a
common way and insert it into the system.
- Handle languages within JsonDecode
(normalize incoming data based on language)
- Handle Single Value and List of Values within Entities. They will map
incoming Data to proper Objects. (We now generally transform during
serialization process if target is array but we got single entity)
- Add missing tests for existing data.
- Finish migration of all existing data, this includes next step
- Provide discriminator to ObjectNormalizer to auto detect target class
based on "type" property. (Done for now by own registry)
- Combine generated object with current structure for import -> generate
data array out of it.
- Resolve foreign references to existing entities,
(images, contentresponsible, etc.)
This should ensure rendering works as expected.
Most important: This ensures data is available in frontend templates.
Add dev dependency to fluid_styled_content. This is necessary to test
our rendering integration with fluid_styled_content defaults.
Relates: #34
To ensure the whole process is still working.
Setup environment and execute request of backend module through extbase.
Ensure expected records are created.
Allows to import entity of type TouristAttraction.
Right now only in German, as this is most important.
Add output of tourist attraction via custom content element.
Provide first basic import mechanism.
It already allows to import entities into TYPO3 database.
Three entities are supported.
Entities are configured through import configuration.
This can be created, viewed, and edited through backend module.
Imports are tracked and accessible from backend module.
Still this is basic.
Importing lists of entities is not supported.
Multiple languages is not supported, etc.
Relates: #8214
