Daniel Siepmann
bf1ae9540b
Sorry for fixing two things in one commit. First fixed bug is single offer and / or single price. Those lead to exception / fatal error and are now handled. Second fixed bug is wrong multi language handling. Instead of using supported languages from entity (which does not exist and was miss interpreted) we use configured system languages. Each record is inserted with default language. Also tourist attractions are inserted for all other languages. They are only inserted if they have a title for that language. |
||
---|---|---|
.github/workflows | ||
Classes | ||
Configuration | ||
Resources | ||
Tests | ||
.gitignore | ||
composer.json | ||
dependency-checker.json | ||
ecs.php | ||
ext_emconf.php | ||
ext_localconf.php | ||
ext_tables.php | ||
ext_tables.sql | ||
ext_typoscript_setup.typoscript | ||
phpstan-baseline.neon | ||
phpstan.neon | ||
phpunit.xml.dist | ||
README.md |
ThüCAT integration into TYPO3 CMS
ThüCAT is ¨Thüringer Content Architektur Tourismus¨. This is an extension for TYPO3 CMS (https://typo3.org/) to integrate ThüCAT. The existing API is integrated and allows importing data into the system.
Current state
The extension already allows:
-
Create static configuration to import specified resources, e.g. defined organisation or towns.
-
Support multiple languages
-
Import of the following types (not all properties are supported):
-
Organisations (responsible for content)
-
Towns
-
Tourist information
-
Tourist attraction
-
-
Backend module:
-
To inspect current existing organisations and their towns and tourist information
-
To inspect import configuration
-
To create import configuration
-
To inspect past imports and possible errors, as well as number of affected records
-
-
Frontend:
-
Content element to display tourist attraction
-
Page Type to reference tourist attraction
-
Short time goals
-
Content element to display town, tourist information and organisation.
-
Extending import to include further properties