EXT:thuecat
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.
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.
Import of specific resources via static URLs. This allows import of specific tourist attractions and towns.
The following data types can be imported (not all properties are supported):
Allows to create new import configurations.
Allows to inspect:
Figure 1-1: Overview of currently available configurations and Organisations.
Figure 1-2: Overview of executed imports and their results.
A dedicated content element is provided to display tourist attraction.
A dedicated Page Type is provided to reference tourist attraction.
The extension can be installed via composer, see t3gettingstarted:extensions-management. The composer package can be found at packagist.org.
Integrators can include and configure TypoScript once it is installed and enabled. See Include TypoScript from extensions. All available configurations can be found at Configuration.
At least one import configuration needs to be created and imported. See Import configuration.
Some API requests are only possible by providing an API Key. This key can be configured via "Extension Configuration".
The configuration of imports is stored within TYPO3 records.
Those records can be created via backend module.
Each new record is stored on a default page. The default is 0.
That would prevent editors from creating and editing records.
This page uid can be configured via TypoScript:
module {
tx_thuecat {
settings {
newRecordPid {
tx_thuecat_import_configuration = 10
}
}
}
}
Each import is defined via a special import configuration record. This record can be created via TYPO3 backend module.
There are different configurations available:
syncScopeId to the configuration to update the given resources
for that specific sync scope.
This requires an configured API Key.All configurations also provide an input to define the page where records should be stored and updated. This page uid is also used to fetch accordingly site configuration. The related languages are used during the import.
Nothing
Allow none admin users to import.
There was a broken configuration of corresponding TCA tables. It forced to insert log entries on root, whiteout allowing users to insert on root.
Nothing
Nothing
Nothing
Prevent Error: Call to undefined method TYPO3\ with newer TYPO3 v13 versions.
We now check for the old API, falling back to the new.
All of this is still @internal TYPO3 API.
The corresponding core change was commit 45a50e455955c78f6baa2aec3af3865101ee06b9.
We also need to update codappix/ dev dependency for the same reason.
composer.lock file.
As this is an extension without a lock state.
We have different TYPO3 versions as supported versions and it should be easy to switch between them for testing and development.phpstan.neon formatting.Nothing
Removed content element.
No Content element is provided any longer. We recommend to build your own tailored content elements instead.
Nothing
Nothing
Nothing
Nothing
Nothing
typo3/cms-install .
As this provides the upgrade wizard feature.Nothing
Nothing
getSlogans is added which will return the array of slogans.Nothing
Nothing
Nothing
Nothing
Add support for additional images added via TYPO3. Some installations might need to add further images to records imported from ThüCAT. The records are now extended to support adding images by editors. The images are not touched during import. The images are also ignored during clean ups, the editor is in full control.
This feature for now is only added to tourist attractions by default.
The feature is implemented in a way that all objects extending the WerkraumMedia\ThueCat\Domain\Model\Frontend\Base class are usable by adding an editorial_images field to their table.
AccessibilityCertification.
That prevents mapping exceptions for objects containing the corresponding certification with more info than a single value.Nothing
schema:containsPlace entries.
Each of them will be imported.Filter and sort opening hours. Filter out opening hours from the past, they are not available to the template anymore. Sort opening hours from early to later based on their end timing.
This should improve the UX of website visitors. It is not possible yet to sort opening hours by hand within the thuecat backend.
getExtraImages() which will return everything from
getImages() except the getMainImage().
We now also filter out the main image from other images, it will not exist twice
anymore.getParkingFacilitiesNearBySortedByAlphabet().types was added. This is an array of types, e.g. CityBus or
Streetcar.
These can be used with f:translate ViewHelper to provide proper none technical labels.schema:givenName and schema:familyName of schema:author for media.
We only respected schema:name until now.copyrightAuthor holding the actual author for convenience.
It will pick the author value falling back to license.author.Handle multiple thuecat:offerType values within Offer.
The API is none breaking, the models still return only a single offer.
They will filter down to the first offer which contains Offer within the value.
Examples:
Given: Childcare and CourseOffer will result in CourseOffer.
Given: Childcare will result in Childcare.
Existing imported data is still handled.
: in German translation of content.distanceToPublicTransport.
This was the only label with :.Nothing
Nothing
Nothing
Nothing
Changed Fluid templates:
Nothing
Nothing
Nothing
Use proper extension name for translation within templates.
This was sitepackage and was changed to Thuecat.
Changed Fluid templates:
Improved composer authors:
Nothing
Nothing
Nothing
Nothing
Nothing
Nothing
Nothing
Nothing
Nothing
List of changes that need to be done for maintenance reasons. Those affect the extension itself, not users of the extension.
E.g. changes once we drop a certain TYPO3 version. We might have new code backported for compatibility in older TYPO3 versions. Those changes are documented so we know what to do once we drop an older version.
Necessary for Extbase/Symfony. Those are necessary (at least with TYPO3 v12) because of Extbase and the underlying Symfony component.
Extbase uses the PHPDocExtractor first, before using the Reflection, both part of Symfony property-info package.
The Reflection will check the mutator followed by accessors prior checking the property itself.
Some of our properties have different return values by accessors than the stored value that is set to the property.
We therefore need to keep the PHPDoc block as this is checked first.