oliverklee/seminars

TYPO3 extension that allows you to create and manage a list of seminars, workshops, lectures, theater performances and other events, allowing front-end users to sign up. FE users also can create and edit events.

v5.8.0 2024-10-29 16:40 UTC

Requires

• php: ^7.2.0 || ~8.0.0 || ~8.1.0 || ~8.1.0 || ~8.2.0 || ~8.3.0
• ext-json: *
• ext-pdo: *
• doctrine/dbal: ^2.10 || ^3.7.1
• oliverklee/feuserextrafields: ^5.3.0 || ^6.0.0
• oliverklee/oelib: ^5.1.0 || ^6.0.0
• pelago/emogrifier: ^6.0.0 || ^7.0.0
• psr/event-dispatcher: ^1.0.0
• psr/http-message: ^1.0
• psr/log: ^1.0 || ^2.0 || ^3.0
• sjbr/static-info-tables: ^6.9.6 || ^11.5.5 || ^12.4.2
• symfony/console: ^4.4 || ^5.4 || ^6.2 || ^7.0
• symfony/mailer: ^4.4 || ^5.4 || ^6.2 || ^7.0
• symfony/mime: ^4.4 || ^5.4 || ^6.2 || ^7.0
• typo3/cms-backend: ^10.4.37 || ^11.5.37
• typo3/cms-core: ^10.4.37 || ^11.5.37
• typo3/cms-extbase: ^10.4.37 || ^11.5.37
• typo3/cms-fluid: ^10.4.37 || ^11.5.37
• typo3/cms-frontend: ^10.4.37 || ^11.5.37
• typo3fluid/fluid: ^2.6.10

Requires (Dev)

• egulias/email-validator: ^2.1.0 || ^3.2.1
• friendsofphp/php-cs-fixer: 3.4.0
• helmich/typo3-typoscript-lint: 2.5.2
• phpstan/extension-installer: 1.4.3
• phpstan/phpstan: 1.12.3
• phpstan/phpstan-phpunit: 1.4.0
• phpstan/phpstan-strict-rules: 1.6.0
• phpunit/phpunit: 8.5.39
• saschaegerer/phpstan-typo3: ^1.8.4
• squizlabs/php_codesniffer: 3.10.2
• symfony/property-info: ^4.4.49 || ^5.4.42 || ^6.4.10 || ^7.1.3
• symfony/yaml: ^5.4 || ^6.4 || ^7.0
• typo3/cms-extensionmanager: ^10.4.37 || ^11.5.37
• typo3/cms-install: ^10.4.37 || ^11.5.37
• typo3/cms-scheduler: ^10.4.37 || ^11.5.37
• typo3/coding-standards: 0.6.1
• typo3/testing-framework: 6.16.9
• webmozart/assert: ^1.11.0

Suggests

• oliverklee/onetimeaccount: for event registration without an explicit FE login
• typo3/cms-install: for running the upgrade wizards

Replaces

• typo3-ter/seminars: v5.8.0

GPL-2.0-or-later

• Oliver Klee

• event
• registration
• education
• seminars
• workshops
• talks

README

This TYPO3 extension allows you to create and manage a list of seminars, workshops, lectures, theater performances and other events, allowing front-end users to sign up. FE users also can create and edit events.

Most of the documentation is in ReST format in the Documentation/ folder and is rendered as part of the TYPO3 documentation.

Compatibility with TYPO3 12LTS/12.4

A TYPO3-12LTS-compatible version of this extension is available via an early-acces program.

Give it a try!

If you would like to test the extension yourself, there is a DDEV-based TYPO3 distribution with this extension installed and some test records ready to go.

Staying informed about the extension

If you would like to stay informed about this extension (including compatibility with newer TYPO3 versions), you can subscribe to the author's newsletter.

Running the tests locally

You will need to have a Git clone of the extension for this with the Composer dependencies installed.

Running the unit tests

On the command line

To run all unit tests on the command line:

composer ci:tests:unit

To run all unit tests in a directory or file (using the directory Tests/Unit/Model/ as an example):

.Build/vendor/bin/phpunit -c Build/phpunit/UnitTests.xml Tests/Unit/Model/

In PhpStorm

First, you need to configure the path to PHPUnit in the settings:

Languages & Frameworks > PHP > Test Frameworks

In this section, configure PhpStorm to use the Composer autoload and the script path .Build/vendor/autoload.php within your project.

In the Run/Debug configurations for PHPUnit, use an alternative configuration file:

Build/phpunit/UnitTests.xml

Running the functional tests

You will need a local MySQL user that has the permissions to create new databases.

In the examples, the following credentials are used:

• user name: typo3
• password: typo3pass
• DB name prefix: typo3_test (optional)
• DB host: localhost (omitted as this is the default)

You will need to provide those credentials as environment variables when running the functional tests:

• typo3DatabaseUsername
• typo3DatabasePassword
• typo3DatabaseName

On the command line

To run all functional tests on the command line:

typo3DatabaseUsername=typo3 typo3DatabasePassword=typo3pass typo3DatabaseName=typo3_test composer ci:tests:functional

To run all functional tests in a directory or file (using the directory Tests/Functional/Authentication/ as an example):

typo3DatabaseUsername=typo3 typo3DatabasePassword=typo3pass typo3DatabaseName=typo3_test .Build/vendor/bin/phpunit -c Build/phpunit/FunctionalTests.xml Tests/Functional/Authentication/

In PhpStorm

First, you need to configure the path to PHPUnit in the settings:

Languages & Frameworks > PHP > Test Frameworks

In this section, configure PhpStorm to use the Composer autoload and the script path .Build/vendor/autoload.php within your project.

In the Run/Debug configurations for PHPUnit, use an alternative configuration file:

Build/phpunit/FunctionalTests.xml

Also set the following environment variables in your runner configuration:

• typo3DatabaseUsername
• typo3DatabasePassword
• typo3DatabaseName

Running the legacy functional tests

Running the legacy tests works exactly the same as running the functional tests, except that you run the tests in Tests/LegacyFunctional/ instead of Tests/Functional/. You'll still need to use the configuration file Build/phpunit/FunctionalTests.xml, though.