Installation
Installation with Composer
If your TYPO3 installation works in composer mode, please execute following command:
composer req jweiland/glossary2
vendor/bin/typo3 extension:setup --extension=glossary2
If you work with DDEV please execute this command:
ddev composer req jweiland/glossary2
ddev exec vendor/bin/typo3 extension:setup --extension=glossary2
Installation with the Extension Manager
On non composer based TYPO3 installations you can install glossary2 still
over the ExtensionManager:
-
Login
Login to backend of your TYPO3 installation as an administrator or system maintainer.
-
Open ExtensionManager
Click on
Extensionsfrom the left menu to open the ExtensionManager. -
Update Extensions
Choose
Get Extensionsfrom the upper selectbox and click on theUpdate nowbutton at the upper right. -
Install
glossary2Use the search field to find
glossary2. Choose theglossary2line from the search result and click on the cloud icon to installglossary2.
Include the TypoScript of glossary2
glossary2 delivers its TypoScript as site set and as static TypoScript
template. Use either the site set or the static template, not both.
The static template imports the TypoScript of the site set, so including
both would load the same TypoScript twice.
Add the site set (recommended)
Add the site set jweiland/ (Glossary2 Set) as
dependency to the site set of your site package:
name: my-vendor/site-package
label: Site package
dependencies:
- jweiland/glossary2
Alternatively, add the set in module Site Management > Sites to the sets of your site configuration.
The settings of the site set can be adjusted in module Site Management > Settings, see Site settings and TypoScript constants.
Include the static template (alternative)
If your site does not use site sets, edit your TypoScript record in module Site Management > TypoScript and include the static template Glossary 2 (glossary2).
The static template provides its constants under the names used before
version 7.0.1 (for example plugin.).
Adjust them in the Constant Editor. Constants with the names of
the site settings (for example glossary2.) take precedence.