TYPO3 - Vehicle Search Migration

Version 3.0.8

If you've overridden the Fluid-Partial Fahrzeugsuche/List/Item/Bootstrap.html or Fahrzeugsuche/List/Item/Bootstrap.html, you need to add the data-fahrzeug-hash="{fahrzeug.hash}" into the <div id="fahrzeug-{fahrzeug.key}" … >.

Version 3.0.5

Better change {f:uri.resource(path: 'Images/no-image.png')} in your templates into {f:uri.resource(path: 'EXT:fahrzeugsuche/Resources/Public/Images/no-image.png')} in order to avoid issues, in case of having vehicles without images.

Version 3.0.0

Migrate Signal/Slots into Symfony Events.

Version 2.0.0

You need to remove the noCacheHash parameter from all Fluid-Templates.

The Partial Fahrzeugsuche/FahrzeugFields/Vehicle/Specifics/EmissionFuelConsumption/CombinedPowerConsumption.html must be renamed because of a maximum file length restriction. The new name must be Fahrzeugsuche/FahrzeugFields/Vehicle/Specifics/EmissionFuelConsumption/CombinedPowerConsum.html. Additionally you might have to modify your Setup-TypoScript configuration for that for this definition:

plugin.tx_fahrzeugsuche.settings {
  detail.displayFieldsets.emissionFuelConsumption {
    fields.70 = Vehicle/Specifics/EmissionFuelConsumption/CombinedPowerConsu`
  }
}

Version 1.16.3

• Please make sure the id field in the connection record contains an integer value. Re-Import all data from autoscout if the id changed.

Version 1.14.0

• The scheduler task "Cache Command" is now implemented as symfony command and has to be set up in the Scheduler. Theold scheduler task can be deleted.

• In the fluid layout "Default.html" the following attribute has to be added to the div element "tx-fahrzeugsuche":

  data-fahrzeugsuche-tracking-url="{f:uri.action(pluginName: 'JsonApi', controller: 'JsonApi', pageType: '1469968203', action: 'track', noCache: 1)}"

• In the fluid layout "Default.html" the attribute "data-fahrzeugsuche-bookmarks-pdf-url" has to be changed to this value:

  data-fahrzeugsuche-bookmarks-pdf-url="{f:uri.action(pluginName: 'JsonApi', controller: 'JsonApi', action: 'createBookmarksPdfUrl', pageType: '1469968203', noCache: 1)}">

Version 1.11.3

The Fluid-Partial file Fahrzeugsuche/FahrzeugFields/Vehicle/Specifics/EmissionFuelConsumption/EnergyEfficiencyClass.html needs to be renamed to Fahrzeugsuche/FahrzeugFields/Vehicle/Specifics/EmissionFuelConsumption/EnergyEfficiency.html because otherwise there might by some issues related to too long filenames in Fluid caching.

Version 1.11.0

Since this version the whole vehicle data is read and kept up to date by the scheduler task. Therefore you must ensure that the fahrzeugsuch:cache:refresh scheduler task is configured and sufficiently often executed.You may have to delete all tx_fahrzeugsuche_domain_model_fahrzeug records so that they are filled correctly.

Version 1.8.0

The vehicle search extension contains Connection records which are used to configure accounts.

migration steps

1. Create a data container and enter the page ID of the themes.configuration.container.fahrzeugsucheTypoScript constant.
2. Inside this container, create a connection record for each account.
3. Keep your system clean and easy to maintain by removing account definitions from Setup TypoScript.

The vehicle search also provides additional caching functions. These support the teaser function and ensure fast loading times, amongst other functions. The Cache CommandController does not need to be executed regularly by the Scheduler so make sure that the scheduler runs at least once a day, but preferably not more than once every hour.

Finally, after updating to this version, run the caching scheduler so that all caching entries are up-to-date.

Version 1.7.0

Migration steps

• The usage of the extension.loaded ViewHelp has changed.Previously:

  <fahrzeugsuche:extension.loaded extensionName="FahrzeugsuchePro">
      ...do something
  </f:if>

  After:

  <f:if condition="{fahrzeugsuche:extension.loaded(extensionName: 'FahrzeugsuchePro', then: '1', else: '0')}">
      ...do something
  </f:if>

Version 1.2.0

Migration steps

• We have moved our JavaScript into the HTML footer. Therefore you might have to check your JavaScript loading.
• In addition, the JavaScript-Settings are now passed by data attributes

Version 1.0.2