yellowpages2
jweiland/yellowpages2
main
en
Stefan Froemken, Hoja Mustaffa Abdul Latheef
This document is published under the Creative Commons BY 4.0 license.
Fri, 06 Feb 2026 09:00:04 +0000
With yellowpages2 you can build your own industry directory.
Table of Contents:
With yellowpages2 you can build your own little industry directory for your TYPO3 website. It comes with a list and a configurable detail view. Above the list view we implemented an A-Z navigation to jump directly to industry directory entries which will start with clicked starting letter.
Target group: Editors
General PluginPlugin select Industry Directory from selectbox.Choose View
You can select between List and Detail view
PID of detail page
If you want another Style for detail view it may make sense to move indistry directory onto another page. Define its PID here.
PID of list page
If you have defined an PID for detail page, it may make sense to set this value within the plugin on detail page to generate correct links back to this list page.
Preset trade
Select a trade to reduce the result on website to your selection on startup.
District
Reduce industry directory records on website to this district
CompanyTarget group: Administrators
The extension needs to be installed like any other extension of TYPO3 CMS:
Get Extensionsyellowpages2This chapter describes the various configuration settings of yellowpages2.
Some general settings for yellowpages2 can be configured in Admin Tools -> Settings.
Default: 0
Only valid, if you have installed EXT:maps2, too.
While creating location records we catch the address and automatically create a maps2 record for you. Define a storage PID where we should store these records.
Default: empty
yellowpages2 comes with a scheduler task to invalidate records after 13 months. It informs the customers to renew their entries after 12 months. This information mail contains a link to review companies record. Define a page UID where you have added the plugin to review the companies record.
Default: empty (use value from INSTALL_TOOL)
With yellowpages2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add an email address of the sender, if a new record was created over the frontend.
Default: empty (use value from INSTALL_TOOL)
With yellowpages2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add a name of the sender, if a new record was created over the frontend.
Default: empty
With yellowpages2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add an email address of the receiver, if a new record was created over the frontend.
Default: empty
With yellowpages2 you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add a name of the receiver, if a new record was created over the frontend.
Tip
You must configure the extension yellowpages2 first to run this extension correctly.
Default: Value from Constants EXT:yellowpages2/Resources/Private/Templates/
You can override our Templates with your own SitePackage extension. We prefer to change this value in TS Constants.
Default: Value from Constants EXT:yellowpages2/Resources/Private/Partials/
You can override our Partials with your own SitePackage extension. We prefer to change this value in TS Constants.
Default: Value from Constants EXT:yellowpages2/Resources/Layouts/Templates/
You can override our Layouts with your own SitePackage extension. We prefer to change this value in TS Constants.
Set this value to a Storage Folder (PID) where you have stored the records.
Example: plugin.
Default: 0
Example: plugin.
Define the page UID where the EXT:maps2 plugin is located to show an address on a map.
Default:
If you need frontend editing you should set this value to a parent category UID whose sub-categories should be assigned to the category selector.
Default:
If you need frontend editing you can set this value to be a preset for new companies in frontend.
Default: 0
Example: plugin.
If you have inserted the Industry Directory plugin for detail view onto another page, you can set its PID to this property here.
Default: 0
Example: plugin.
If you have inserted the Industry Directory plugin for detail view onto another page, you can set the PID of list page here to have correct links back to list view.
Default:
If you will allow for frontend users to create and edit their own business listings you have assign them a frontend usergroup and add this group UID to this property.
Default: 1
Example: plugin.
Merge record titles starting with numbers to 0- in glossary.
Default: 1
Example: plugin.
Prepend an additional button in front of the glossary to show all records again.
Default: 15
Example: plugin.
Reduce result of records to this value for a page
This chapter describes how to manage the extension from a superuser point of view.
With TYPO3 9 you have the possibility to configure RouteEnhancers
routeEnhancers:
Yellowpages2Plugin:
type: Extbase
extension: Yellowpages2
plugin: Directory
routes:
-
routePath: '/first-company-page'
_controller: 'Company::list'
-
routePath: '/company-page-{page}'
_controller: 'Company::list'
_arguments:
page: '@widget_0/currentPage'
-
routePath: '/company-by-letter/{letter}'
_controller: 'Company::list'
-
routePath: '/show/{company_title}'
_controller: 'Company::show'
_arguments:
company_title: company
requirements:
letter: '^(0-9|[a-z])$'
company_title: '^[a-zA-Z0-9]+$'
defaultController: 'Company::list'
aspects:
company_title:
type: PersistedAliasMapper
tableName: tx_yellowpages2_domain_model_company
routeFieldName: path_segmentyellowpages2 uses the Simple from TYPO3 Core to navigate through
your records with first, previous, next and last buttons. If
you need something more complex like 1, 2 ... 56, 57, 58 ... 123, 124 you
should use another pagination library or build your own one. In the next steps
I explain you how to implement the numbered_pagination solution
of Georg Ringers.
Install numbered_
Install and activate numbered_ extension from Georg
Ringer. Please check in your SitePackage extension that
numbered_ is set as a dependency and will be loaded
before yellowpages2 and your SitePackage.
Change pagination class in TypoScript
plugin.tx_yellowpages2.pageBrowser.class = GeorgRinger\NumberedPagination\NumberedPaginationChange path to yellowpages2 partials
Set constant partial to a location within your SitePackage:
plugin.tx_yellowpages2.view.partialRootPath = EXT:site_package/Resources/Private/Extensions/Yellowpages2/Partials/Create Pagination template
Create file Resources/
with example content from numbered_pagination
https://github.com/georgringer/numbered_pagination/blob/master/Resources/Private/Partials/Pagination.html
<html lang="en"
xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers"
data-namespace-typo3-fluid="true">
<ul class="f3-widget-paginator">
<f:if condition="{pagination.previousPageNumber} && {pagination.previousPageNumber} >= {pagination.firstPageNumber}">
<li class="previous">
<a href="{f:uri.action(action:actionName, arguments:{currentPage: pagination.previousPageNumber})}" title="{f:translate(key:'pagination.previous')}">
{f:translate(key:'widget.pagination.previous', extensionName: 'fluid')}
</a>
</li>
</f:if>
<f:if condition="{pagination.hasLessPages}">
<li>…</li>
</f:if>
<f:for each="{pagination.allPageNumbers}" as="page">
<li class="{f:if(condition: '{page} == {paginator.currentPageNumber}', then:'current')}">
<a href="{f:uri.action(action:actionName, arguments:{currentPage: page})}">{page}</a>
</li>
</f:for>
<f:if condition="{pagination.hasMorePages}">
<li>…</li>
</f:if>
<f:if condition="{pagination.nextPageNumber} && {pagination.nextPageNumber} <= {pagination.lastPageNumber}">
<li class="next">
<a href="{f:uri.action(action:actionName, arguments:{currentPage: pagination.nextPageNumber})}" title="{f:translate(key:'pagination.next')}">
{f:translate(key:'widget.pagination.next', extensionName: 'fluid')}
</a>
</li>
</f:if>
</ul>
</html>Clear Cache
Needed to reload the fluid templates.
If you update EXT:yellowpages2 to a newer version, please read this section carefully!
This version is focussed 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.
If you make use of 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 adopt your code to use QueryResult. You can retrieve
the extbase query with method get.
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 Flush Cache button in Installtool
to re-build 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}">We have moved a lot of code of yellowpages2 controllers to EventListeners. Please flush cache in maintenance module.
As a developer you should check, if you have overwritten some methods of MapController or CompanyController and adopt them to new structure.
We have removed column wsp_member as this column was a specific column for one of our customers. If you have used it you have to add it back with help of EXT:extender.
We have removed column icon from table sys_category. That way we also have remove fallbackIconPath, too. If you have used it you have to add it back with help of EXT:extender.
We are using the API of glossary2 now. Please check, if your own queries are still working.
Currently, no problems known.
The links to issue and the GitHub repository are maintained in the Settings.cfg.
You may want to remove this file if all important links are already handled in Settings.cfg.
Contribution to yellowpages2 is very welcome.
If you wish to contribute, please follow these conventions:
Please see the general GitHub documentation for more information, for example Creating a pull request