Work-Related/events
Work-Related/events
1
0
mirror of https://github.com/werkraum-media/events.git synced 2024-11-23 07:56:11 +01:00
Code Issues Activity
events/Resources/Private/Language/locallang_csh_import.xlf

123 lines
6.7 KiB
Text
Raw Normal View History

Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" datatype="plaintext" original="messages" date="2022-01-27T08:22:40Z" product-name="Events">
<header/>
<body>
<trans-unit id="tx_events_domain_model_import">
<source>Import Configuration</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.div.typo3">
<source>TYPO3</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.div.rest">
<source>REST</source>
</trans-unit>
Support import of HTML variant for detail text (#65) Provide a new option within configurations to turn on import of HTML from destination.one for detail text of each event. Resolves: #10629
2024-08-20 08:58:31 +02:00
<trans-unit id="tx_events_domain_model_import.div.import">
<source>Import</source>
</trans-unit>
Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
<trans-unit id="tx_events_domain_model_import.palette.relations">
<source>Relations</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.palette.typo3_storage">
<source>TYPO3 Storages</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.palette.categories">
<source>Categories</source>
</trans-unit>
Integrate destination data features Import alongside of categories. Use TYPO3 sys_category again.
2022-07-05 14:08:14 +02:00
<trans-unit id="tx_events_domain_model_import.palette.features">
<source>Features</source>
</trans-unit>
Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
<trans-unit id="tx_events_domain_model_import.title">
<source>Title</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.title.description">
<source>Only for backend search and UX, not used for actual import.</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.storage_pid">
<source>Storage Page</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.storage_pid.description">
<source>TYPO3 page to use for storing imported data.</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.region">
<source>Region</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.categories_pid">
<source>Categories Storage Folder</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.categories_pid.description">
<source>TYPO3 page to use for storing imported categories.</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.category_parent">
<source>Parent Category</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.category_parent.description">
<source>Existing TYPO3 category used as parent for all categories created during import.</source>
</trans-unit>
Integrate destination data features Import alongside of categories. Use TYPO3 sys_category again.
2022-07-05 14:08:14 +02:00
<trans-unit id="tx_events_domain_model_import.features_pid">
<source>Features Storage Folder</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.features_pid.description">
<source>TYPO3 page to use for storing imported features.</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.features_parent">
<source>Parent Features Category</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.features_parent.description">
<source>Existing TYPO3 category used as parent for all features created during import.</source>
</trans-unit>
Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
<trans-unit id="tx_events_domain_model_import.files_folder">
<source>Folder</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.files_folder.description">
<source>TYPO3 folder to use for storing imported files.</source>
</trans-unit>
Migrate TypoScript import settings Those are now part of the import, or hard coded. Resolves: #11483
2024-11-04 14:30:18 +01:00
<trans-unit id="tx_events_domain_model_import.rest_license_key">
<source>License Key</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_license_key.description">
<source>See: https://developer.et4.de/reference/current/#eT4META-search-param-licensekey.html</source>
</trans-unit>
Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
<trans-unit id="tx_events_domain_model_import.rest_experience">
<source>Experience</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_experience.description">
Migrate TypoScript import settings Those are now part of the import, or hard coded. Resolves: #11483
2024-11-04 14:30:18 +01:00
<source>See: https://developer.et4.de/reference/current/#eT4META-search-param-experience.html</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_mode">
<source>Mode</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_mode.description">
<source>See: https://developer.et4.de/reference/current/#eT4META-search-param-mode.html</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_limit">
<source>Limit</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_limit.description">
<source>See: https://developer.et4.de/reference/current/#eT4META-search-param-limit.html</source>
Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_search_query">
<source>Search Query</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.rest_search_query.description">
Migrate TypoScript import settings Those are now part of the import, or hard coded. Resolves: #11483
2024-11-04 14:30:18 +01:00
<source>See: https://developer.et4.de/reference/current/#eT4META-search-param-q.html</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.import_repeat_until">
<source>Repeat events until</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.import_repeat_until.description">
<source>Some events will repeat. This will define how many dates will be created. See: https://www.php.net/manual/en/datetimeimmutable.modify.php</source>
Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
</trans-unit>
Support import of HTML variant for detail text (#65) Provide a new option within configurations to turn on import of HTML from destination.one for detail text of each event. Resolves: #10629
2024-08-20 08:58:31 +02:00
<trans-unit id="tx_events_domain_model_import.import_features">
<source>Import Features</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.import_features.description">
<source>Enable certain features related to the import.</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_import.import_features.html_for_detail">
<source>HTML for Event Details</source>
</trans-unit>
Add import configuration record It is now possible to create "Import" records in TYPO3 system. Those records can then be imported via two new commands. There is no need to configure everything within the command itself. That allows: * To allow editors to maintain import configuration. * Have proper labels, description, csh and UI to create import. It no longer is necessary to copy UIDs, instead proper wizards from TCA are available to select pages. Relates: #9649
2022-01-27 14:14:02 +01:00
</body>
</file>
</xliff>
Copy permalink