yellowpages2
jweiland/yellowpages2
main
en
Stefan Froemken, Hoja Mustaffa Abdul Latheef
This document is published under the Creative Commons BY 4.0 license.
Thu, 10 Sep 2026 12:46:02 +0000
With yellowpages2 you can build your own industry directory.
Table of Contents:
yellowpages2 builds a small industry directory for your TYPO3 website. It ships a list view and a configurable
detail view, an A-Z glossary above the list to jump directly to entries starting with a given letter, and an
optional frontend form so visitors can submit their own company entries for review.
Target group: Editors
yellowpages2General PluginPlugin, select Industry Directory from the selectboxSwitch between the list and the detail view.
Move the detail view onto another page for a different layout. Set its page ID here.
If you have set a PID for the detail page, set this value too, so the plugin can generate correct links back to the list page.
Preselect a trade to narrow down the result list on page load.
Narrow down the result list to a single district.
CompanyTarget group: Administrators
Install yellowpages2 like any other TYPO3 extension.
composer require jweiland/yellowpages2If you cannot use Composer, install yellowpages2 through the Extension Manager instead:
Get Extensionsyellowpages2This chapter describes the various configuration settings of yellowpages2.
Configure yellowpages2 in the backend module Admin Tools > Settings > Extension Configuration.
Only relevant if EXT:maps2 is installed. While creating a company record on the frontend, the address is geocoded and a maps2 record is created for it automatically. Define the storage page ID for these records here.
yellowpages2 ships a console command that hides company records older than 13 months and
informs their owners 12 months after creation, asking them to renew the entry. The reminder
email links back to this page ID, which should have the plugin configured for editing.
Sender address used for all notification emails triggered when a visitor creates or updates a company record on the frontend.
Sender name used for the notification emails described above.
true
Recipient address for the administrator notification sent whenever a visitor creates or updates
a company record on the frontend. This is also the address that receives the moderation link to
edit or activate the record. Unlike email, there is no fallback: leaving this empty
causes sending to fail once a company is created or updated on the frontend.
Recipient name for the administrator notification described above.
| Name | Type | Default |
|---|---|---|
| integer | 0 | |
| string | (empty) | |
| string | (empty, falls back to the install-wide default from address) | |
| string | (empty, falls back to the install-wide default from name) | |
| string | (empty) | |
| string | (empty) |
yellowpages2 ships its configuration as the Site Set jweiland/. Add it to the
dependencies list of your site configuration (config/),
then override any of the following settings for your site in
config/:
yellowpages2.storagePid: '21,45,3234'
yellowpages2.pidOfMaps2Plugin: 12| Name |
|---|
string
"EXT:yellowpages2/Resources/Private/Templates/"
Path to template root
string
"EXT:yellowpages2/Resources/Private/Partials/"
Path to partial root
string
"EXT:yellowpages2/Resources/Private/Layouts/"
Path to layout root
string
Folder for storing records and fetched data
page
0
PID where maps2 plugin for detail view is inserted
int
0
Starting/Parent UID of all available categories for this plugin
int
2
UID of the default district to show in selectbox
page
0
Leave empty to show details on current page
page
0
List Page UID: If empty, the current page ID will be used.
int
1
The user group allowed to create new companies. This determines the rendering of the edit and create links on the list page.
int
15
How many items should be displayed on one page
bool
1
Should pagebrowser be displayed on top of the list
bool
0
Should pagebrowser be displayed at bottom of the list
int
5
Define maximum amount of pages which should be displayed
This chapter describes how to manage the extension from a superuser point of view.
Configure RouteEnhancers to get speaking URLs for the company list, letter, and detail views.
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 TYPO3 Core's Simple to navigate through records with first,
previous, next, and last buttons. If you need something more complex, like
1, 2 ... 56, 57, 58 ... 123, 124, use another pagination library or build your own. The following
steps show how to plug in Georg Ringer's numbered_ extension instead.
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 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.
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.
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.
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}">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.
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.
Currently, no problems are known.
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
The issue tracker and GitHub repository links are maintained in guides..