sponsoring
jweiland/sponsoring
main
en
Stefan Froemken
This document is published under the Creative Commons BY 4.0 license.
Wed, 06 May 2026 13:33:36 +0000
Display and manage sponsoring projects like competitions
Table of Contents:
With sponsoring you can create, manage and display projects/promotions like
f.e. a competition.
Money and Service
and add it to promotion value.Target group: Editors
Insert PluginPlugin select Sponsoring from selectbox.ProjectIf your TYPO3 installation works in composer mode, please execute following command:
composer req jweiland/sponsoring
vendor/bin/typo3 extension:setup --extension=sponsoringIf you work with DDEV please execute this command:
ddev composer req jweiland/sponsoring
ddev exec vendor/bin/typo3 extension:setup --extension=sponsoringOn non composer based TYPO3 installations you can install sponsoring still over the ExtensionManager:
Login
Login to backend of your TYPO3 installation as an administrator or system maintainer.
Open ExtensionManager
Click on Extensions from the left menu to open the ExtensionManager.
Update Extensions
Choose Get Extensions from the upper selectbox and click on the Update now button at the upper right.
Install sponsoring
Use the search field to find sponsoring. Choose the sponsoring line from the search result and click on the cloud
icon to install sponsoring.
Target group: Developers, Integrators
How to configure the extension. Try to make it easy to configure the extension. Give a minimal example or a typical example.
Sponsoring (sponsoring) We prefer to set a Storage PID with help of TypoScript Constants:
plugin.tx_sponsoring.persistence {
# Define Storage PID where project records are located
storagePid = 4
}Default: Value from Constants EXT:sponsoring/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:sponsoring/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:sponsoring/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 project records. If you have stored Organizers and Locations in another Storage Folder, you have to add theses PIDs here, too.
Example: 21,45,3234
Default: empty
Set this value to the pid where maps2 plugin is located. A link for the address will be redirected to that page.
Default: 0
Often it is useful to move the detail view onto a separate page for design/layout reasons.
Amount of records on a page
As an integrator you can override each key of language file:
EXT:
Example:
plugin.tx_sponsoring._LOCAL_LANG.de.listMyProjects = Show my projectsThis will include a default CSS Style to show a red border around input fields in Frontend, if an sponsoring field was filled with an invalid value.
If you have your own CSS we prefer to remove this setting:
plugin.tx_sponsoring._CSS_DEFAULT_STYLE >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:
SponsoringPlugin:
type: Extbase
extension: Sponsoring
plugin: Sponsoring
routes:
-
routePath: '/first-sponsoring-page'
_controller: 'Project::list'
-
routePath: '/show/{project_title}'
_controller: 'Project::show'
_arguments:
project_title: project
requirements:
project_title: '^[a-zA-Z0-9\-]+\-[0-9]+$'
defaultController: 'Project::list'
aspects:
project_title:
type: PersistedAliasMapper
tableName: tx_sponsoring_domain_model_project
routeFieldName: path_segmentIf you update EXT:sponsoring to a newer version, please read this section carefully!
We have remove the hard dependency to service_ and all related parts
in domain model Project, TCA and translation files. If you still need these
implementation you have to add that stuff with help of your site-package
extension again.
We have remove the Get ViewHelper. Please visit your overwritten
sponsoring templates for list and search actions. Replace
sp: with just promotions and remove the sp ViewHelper
registration at top of file.
We have removed TYPO3 9 compatibility
As f:widget.paginate is deprecated and POST requests are not allowed anymore in this widget, we have rewritten the widget to new TYPO3 Pagination API.
Please remove the f:widget.paginate from Templates and insert this code:
<f:render partial="Component/Pagination"
arguments="{pagination: pagination, paginator: paginator, actionName: actionName}" />We have changed some method arguments, please flush cache in InstallTool
We have added column path_ to project table which you can use in your
own RouteEnhancer configuration. If you have a lot of projects you can use
our UpgradeWizard to prefill path_ with a sanitized version of
project name column.
We have removed TYPO3 8 compatibility and added TYPO3 10 compatibility instead.
Contribution to sponsoring 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