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.5.1 2023-11-30 19:41 UTC

Requires

• php: ^7.2.0 || ~8.0.0 || ~8.1.0 || ~8.1.0 || ~8.2.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
• 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.3
• 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.22 || ^11.5.4
• typo3/cms-core: ^10.4.22 || ^11.5.4
• typo3/cms-extbase: ^10.4.22 || ^11.5.4
• typo3/cms-fluid: ^10.4.22 || ^11.5.4
• typo3/cms-frontend: ^10.4.22 || ^11.5.4
• typo3fluid/fluid: ^2.6.10

Requires (Dev)

• ergebnis/composer-normalize: ~2.19.0
• friendsofphp/php-cs-fixer: ^3.4.0
• helhum/typo3-console: ^6.7.6 || ^7.1.4
• helmich/typo3-typoscript-lint: ^2.5.2
• mikey179/vfsstream: ^1.6.11
• nimut/testing-framework: ^6.0.1
• oliverklee/phpunit: ^8.5.0
• php-coveralls/php-coveralls: ^2.7.0
• phpstan/extension-installer: ^1.3.1
• phpstan/phpstan: ^1.10.46
• phpstan/phpstan-phpunit: ^1.3.15
• phpstan/phpstan-strict-rules: ^1.5.2
• phpunit/phpunit: ^8.5.34
• saschaegerer/phpstan-typo3: ^1.8.4
• squizlabs/php_codesniffer: ^3.7.2
• typo3/cms-install: ^10.4.22 || ^11.5.4
• typo3/cms-scheduler: ^10.4.22 || ^11.5.4
• typo3/coding-standards: ~0.6.1

Suggests

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

Replaces

• typo3-ter/seminars: v5.5.1

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

This extension is not compatible TYPO3 12LTS/12.4 yet. Please consider supporting the crowdfunding campaign to make this happen.

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.

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 Configuration/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:

Configuration/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 Configuration/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:

Configuration/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 Configuration/FunctionalTests.xml, though.