Updating
If you update EXT:yellowpages2 to a newer version, please read this section carefully!
Upgrade to version 9.0.0
This version closes a security issue and changes how company logo and image uploads are handled.
The activate action, used by the link in the administrator notification email to publish a
company record straight away, previously had no authorization check at all. Anyone who knew or
guessed a company's UID could activate it. activate, edit, and update now require a signed
moderation request argument in addition to (or, for activate, instead of) the existing
frontend user check. If you have overridden Templates/ or
Templates/ in your own site package, add moderation to the arguments of
both f: calls, otherwise the links in the email no longer work:
<f:link.action action="edit" controller="Company" absolute="1"
arguments="{company: company, moderationToken: moderationToken}">
Edit record
</f:link.action>
Company logo and image uploads have been migrated to Extbase's native # API
(TYPO3 >= 13.3), replacing the extension's own Upload property mapper and
Assign, both of which have been removed. If you have overridden
Partials/ or Images., replace the old per-index upload fields
(logo., images. through images.) with the native multi-file pattern:
<f:form.upload property="logo" multiple="1"/>
<f:form.upload property="images" multiple="1"/>
Domain, get, get, and
get have been removed. Their former callers should use get,
get, get, and get instead, which now return the underlying
Object directly rather than a plain array. Code iterating these values in Fluid keeps
working unchanged; PHP code expecting a plain array must call ->to itself.
The classic static template registration under Configuration/ has been removed in
favor of the jweiland/ Site Set. If your site still relies on the classic "Include
static (from extensions)" template mechanism instead of Site Sets, add the
jweiland/ Site Set to your site's dependencies in config., see
Site Set settings.
Upgrade to version 7.0.0
This version is focused on upgrading the compatibility version to TYPO3 version 12 LTS. We moved some extension functionalities from PSR-14 Event Listeners to Middlewares as the request setArgument not possible anymore with TYPO3 version 12.
Upgrade to version 6.1.0
If you make use of the Modify or
Modify event:
We have changed the strict type of TYPO3 QueryBuilder to Extbase
QueryResult. Yes, this is a breaking change, but it seems that no one
makes use of it. Please adapt your code to use QueryResult. You can retrieve
the Extbase query with method get.
Upgrade to version 6.0.0
As TYPO3 has deprecated the ObjectManager, we have changed many properties in our
scheduler task Update yellowpages. Please remove that scheduler task completely
and create a new one of type Inform users to update their company record.
We have changed a lot of classes. Please click the Flush Cache button in the Install Tool
to rebuild the Dependency Injection cache.
If you have maps2 version 9 installed you have to override or change following
part in Properties. from:
<f:link.action title="Map detail"
action="show"
controller="PoiCollection"
extensionName="maps2"
pluginName="maps2"
pageUid="{settings.pidOfMaps2Plugin}"
arguments="{poiCollectionUid: company.txMaps2Uid}">
to:
<f:link.action title="Map detail"
action="show"
controller="PoiCollection"
extensionName="maps2"
pluginName="maps2"
pageUid="{settings.pidOfMaps2Plugin}"
arguments="{poiCollection: company.txMaps2Uid}">
Upgrade to version 5.0.0
We have moved a lot of code of yellowpages2 controllers to EventListeners. Please flush the cache in the maintenance module.
As a developer, you should check whether you have overwritten some methods of MapController or CompanyController and adapt them to the new structure.
Upgrade to version 4.0.0
We have removed column wsp_member as this column was specific to one of our customers. If you have used it, you have to add it back with the help of EXT:extender.
We have removed column icon from table sys_category. This also removed fallbackIconPath. If you have used it, you have to add it back with the help of EXT:extender.
We are using the API of glossary2 now. Please check whether your own queries are still working.