Installation 

With Composer 

Just perform the following command on CLI:

$ composer req 'fgtclb/t3oodle':'^3.0@dev'

When composer is done, the extension is active. If the database schema has not been updated automatically, run typo3 extension:setup and update the database schema in Admin Tools > Maintenance > Analyze Database Structure.

Without Composer 

You can also fetch t3oodle from TER and install it the old-fashioned way.

Updating 

TYPO3 compiles its dependency injection container once and caches it, by default in typo3temp/var/cache/code/di/. A release of t3oodle may change the dependencies of its classes, so the container has to be rebuilt after an update.

With Composer this happens on its own: the cache identifier of the container is derived from composer.lock, so installing another release changes it.

Without Composer it does not. The identifier is derived from the TYPO3 version and the modification time of typo3conf/PackageStates.php, and replacing the files of an extension that is already active, by upload, FTP or the Extension Manager, changes neither. The "Flush all caches" button of the backend toolbar removes the container only in the Development context.

Extension settings 

t3oodle does not provide any extensions settings. Configuration is made in TypoScript setup.

Including the TypoScript 

There are two ways to include the TypoScript of t3oodle. Use one of them.

Site Set (recommended) 

Add the following site set to the dependencies of your site, in Sites > Edit site > Sets or in the config.yaml of your site:

dependencies:
  - fgtclb/t3oodle

Copied!

The optional Bootstrap styles are provided by a separate set (see below).

Static template 

Make sure to include the TypoScript t3oodle Main (required) in your template. This way remains available for existing installations.

In Configuration chapter, you see all TypoScript settings and its defaults.