Commit graph

9 commits

Author SHA1 Message Date
2e0102894f Allow to configure storage pid for each import configuration
Each import configuration now offers an input to define storage pid.
That enables integrators to have different storage folders per
configuration.
2021-02-17 15:37:49 +01:00
92c8bbedaa Add multi language handling
Import entities in all available languages.
Provide translated records in frontend.
2021-02-17 14:51:00 +01:00
46144de0a7 Add first functional tests for import
To ensure the whole process is still working.
Setup environment and execute request of backend module through extbase.

Ensure expected records are created.
2021-02-17 09:20:24 +01:00
6478526004 Add media to tourist attraction 2021-02-17 09:20:24 +01:00
eab2eee8b3 Add address to tourist attraction 2021-02-17 09:20:24 +01:00
9176ba0cec Import tourist attraction only in German language
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.
2021-02-16 12:01:35 +01:00
ce787c90b6 Use storage pids from example setup
As long as those are hard coded, use matching storage pids from example
setup.
2021-02-16 11:09:18 +01:00
ded93e0d8e Integrate phpstan 2021-02-16 11:09:18 +01:00
dc1c45f1c1 Initial import mechanism
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
2021-02-16 11:09:18 +01:00