Work-Related/thuecat
Work-Related/thuecat
1
0
mirror of https://github.com/werkraum-media/thuecat.git synced 2024-11-15 09:46:12 +01:00
Code Issues Activity
thuecat/Resources/Private/Templates/Backend/Configuration/Index.html

151 lines
6.3 KiB
HTML
Raw Normal View History

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-01 14:14:05 +01:00
<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers"
xmlns:f="http://typo3.org/ns/TYPO3/CMS/Core/ViewHelpers"
xmlns:f="http://typo3.org/ns/TYPO3/CMS/Backend/ViewHelpers"
data-namespace-typo3-fluid="true">
<h1>{f:translate(id: 'module.overview.headline')}</h1>
<f:flashMessages />
<h2>
{f:translate(id: 'module.importConfigurations.headline')}
<f:link.newRecord
table="tx_thuecat_import_configuration"
Allow editor to create and edit import configuration Import Configuration can now be stored on folders, beside the site root. That way editors can create and edit records. The default storage pid for new records can be defined via TypoScript. Resolves: #24
2021-06-01 09:44:14 +02:00
pid="{settings.newRecordPid.tx_thuecat_import_configuration}"
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-01 14:14:05 +01:00
title="{f:translate(id: 'module.importConfigurations.actions.new')}"
>
{f:icon(identifier: 'actions-document-add')}
</f:link.newRecord>
</h2>
<f:if condition="{importConfigurations}">
<f:then>
{f:render(section: 'ImportConfigurations', arguments: {importConfigurations: importConfigurations})}
</f:then>
<f:else>
<f:be.infobox
title="{f:translate(id: 'module.importConfigurations.missing.title')}"
state="1"
>
{f:translate(
id: 'module.importConfigurations.missing.text',
arguments: {
Allow editor to create and edit import configuration Import Configuration can now be stored on folders, beside the site root. That way editors can create and edit records. The default storage pid for new records can be defined via TypoScript. Resolves: #24
2021-06-01 09:44:14 +02:00
0: "{f:uri.newRecord(table: 'tx_thuecat_import_configuration', pid: settings.newRecordPid.tx_thuecat_import_configuration)}"
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-01 14:14:05 +01:00
}
) -> f:format.raw()}
</f:be.infobox>
</f:else>
</f:if>
<h2>{f:translate(id: 'module.organisations.headline')}</h2>
<f:if condition="{organisations}">
<f:then>
{f:render(section: 'Organisations', arguments: {organisations: organisations})}
</f:then>
<f:else>
<f:be.infobox
title="{f:translate(id: 'module.organisations.missing.title')}"
state="1"
>{f:translate(id: 'module.organisations.missing.text')}</f:be.infobox>
</f:else>
</f:if>
<f:section name="ImportConfigurations">
<table class="table table-striped table-hover">
<thead>
<tr>
<th>{f:translate(id: 'module.importConfigurations.title')}</th>
<th>{f:translate(id: 'module.importConfigurations.lastChanged')}</th>
Show last import time beside each import configuration in backend module (#77)
2022-09-29 15:17:06 +02:00
<th>{f:translate(id: 'module.importConfigurations.lastImported')}</th>
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-01 14:14:05 +01:00
<th>{f:translate(id: 'module.actions')}</th>
</tr>
</thead>
<tbody>
<f:for each="{importConfigurations}" as="importConfiguration">
<tr>
<td>{importConfiguration.title}</td>
<td>{importConfiguration.lastChanged -> f:format.date(format: 'd.m.Y H:i')}</td>
Show last import time beside each import configuration in backend module (#77)
2022-09-29 15:17:06 +02:00
<td>
<f:if condition="{importConfiguration.lastImported}">
<f:then>
{importConfiguration.lastImported -> f:format.date(format: 'd.m.Y H:i')}
</f:then>
<f:else>
{f:translate(id: 'module.importConfigurations.lastImported.never')}
</f:else>
</f:if>
</td>
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-01 14:14:05 +01:00
<td>
<f:link.editRecord
uid="{importConfiguration.uid}"
table="{importConfiguration.tableName}"
title="{f:translate(id: 'module.importConfigurations.actions.edit')}"
>
{f:icon(identifier: 'actions-document-edit')}
</f:link.editRecord>
<f:link.action
action="import"
controller="Backend\Import"
arguments="{importConfiguration: importConfiguration}"
title="{f:translate(id: 'module.importConfigurations.actions.import')}"
>
{f:icon(identifier: 'actions-download')}
</f:link.action>
</td>
</tr>
</f:for>
</tbody>
</table>
</f:section>
<f:section name="Organisations">
<table class="table table-striped table-hover">
<thead>
<tr>
<th>{f:translate(id: 'module.organisation.title')}</th>
<th>{f:translate(id: 'module.organisation.towns')}</th>
<th>{f:translate(id: 'module.organisation.lastImported')}</th>
<th>{f:translate(id: 'module.actions')}</th>
</tr>
</thead>
<tbody>
<f:for each="{organisations}" as="organisation">
<tr>
<td>{organisation.title}</td>
<td>
{f:render(section: 'Towns', arguments: {towns: organisation.managesTowns})}
</td>
<td>{organisation.lastImported -> f:format.date(format: 'd.m.Y H:i')}</td>
<td>
<f:link.editRecord
uid="{organisation.uid}"
table="{organisation.tableName}"
>
{f:icon(identifier: 'actions-document-edit')}
</f:link.editRecord>
</td>
</tr>
</f:for>
</tbody>
</table>
</f:section>
<f:section name="Towns">
<f:if condition="{towns}">
<f:else>
{f:translate(id: 'module.organisation.towns.none')}
</f:else>
</f:if>
<f:for each="{towns}" as="town">
{town.title} {f:render(section: 'TouristInformation', arguments: {touristInformation: town.touristInformation})}
</f:for>
</f:section>
<f:section name="TouristInformation">
<f:if condition="{touristInformation}">(</f:if>
<f:for each="{touristInformation}" as="info">
{info.title}
</f:for>
<f:if condition="{touristInformation}">)</f:if>
</f:section>
</html>
Copy permalink