Download the PHP package oliverklee/seminars without Composer

On this page you can find all versions of the php package oliverklee/seminars. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package seminars

TYPO3 extension seminars

TYPO3 V11 License GitHub CI Status Coverage Status

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:

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

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:

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

On the command line

To run all functional tests on the command line:

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

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:

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.

All versions of seminars with dependencies

PHP Build Version
Package Version
Requires php Version ^7.2.0 || ~8.0.0 || ~8.1.0 || ~8.1.0 || ~8.2.0 || ~8.3.0
ext-json Version *
ext-pdo Version *
doctrine/dbal Version ^2.10 || ^3.7.1
oliverklee/feuserextrafields Version ^5.3.0 || ^6.0.0
oliverklee/oelib Version ^5.1.0 || ^6.0.0
pelago/emogrifier Version ^6.0.0 || ^7.0.0
psr/event-dispatcher Version ^1.0.0
psr/http-message Version ^1.0
psr/log Version ^1.0 || ^2.0 || ^3.0
sjbr/static-info-tables Version ^6.9.6 || ^11.5.5 || ^12.4.2
symfony/console Version ^4.4 || ^5.4 || ^6.2 || ^7.0
symfony/mailer Version ^4.4 || ^5.4 || ^6.2 || ^7.0
symfony/mime Version ^4.4 || ^5.4 || ^6.2 || ^7.0
typo3/cms-backend Version ^10.4.37 || ^11.5.37
typo3/cms-core Version ^10.4.37 || ^11.5.37
typo3/cms-extbase Version ^10.4.37 || ^11.5.37
typo3/cms-fluid Version ^10.4.37 || ^11.5.37
typo3/cms-frontend Version ^10.4.37 || ^11.5.37
typo3fluid/fluid Version ^2.6.10
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package oliverklee/seminars contains the following files

Loading the files please wait ....