mediaessenz / me-google-calendar

v6.1.1 2026-10-26 20:13 UTC

Requires

• php: ^8.2
• typo3/cms-core: ^13 || ^14
• typo3/cms-extbase: ^13 || ^14
• typo3/cms-fluid: ^13 || ^14

Requires (Dev)

• phpunit/phpunit: ^11.2 || ^12.1
• typo3/testing-framework: ^9.7

GPL-2.0-or-later

• Alexander Grein

• plugin
• calendar
• google
• frontend
• fullcalendar
• TYPO3 CMS
• googlecalender

Published on Packagist.org on 2026-10-26 19:14 UTC

README

Make use of the jQuery Plugin FullCalendar (v3.10.2) to generates a skin-able calendar with different views (month, week, day, week list, day list etc.) from one or more Google Calendar XML Feed(s).

Running the tests

The unit tests live in Tests/Unit and use the TYPO3 testing framework. The development dependencies are installed into .Build (ignored by git):

composer install
composer test:unit

In a DDEV project the commands can be executed in the extension directory:

ddev exec -d /var/www/html/vendor/mediaessenz/me-google-calendar composer install
ddev exec -d /var/www/html/vendor/mediaessenz/me-google-calendar composer test:unit

Releasing

A release is published to the TYPO3 Extension Repository (TER) by the GitLab CI (.gitlab-ci.yml).

1. Raise the version in ext_emconf.php and in composer.json (extra.typo3/cms.version).
2. Add the changelog entry - v.<major>.<minor>.<patch>: <changes> to Documentation/Changelog/Index.rst.
3. Commit, create an annotated tag and push it. The tag message is used as upload comment in the TER:

   git tag -a v6.1.0 -m "Added unit tests and the TER release automation"
   git push origin v6.1.0
   

   Push the tag on its own: GitLab doesn't create pipelines, if more than four tags are pushed at once.

4. The pipeline of the tag runs the tests and the job release-checks (version of the tag equals ext_emconf.php and composer.json, changelog entry exists), then ter-package builds me_google_calendar_<version>.zip: the tag without the files listed in .gitattributes (e.g. Tests/, Build/). The package is available as job artifact.
5. Check the package, then start the manual job ter-publish. A version published to the TER can't be changed or deleted. After the upload the job gitlab-release creates the GitLab release of the tag.

Required setup in GitLab: the CI/CD variable TYPO3_API_TOKEN (a TER access token, see typo3/tailor, flags masked and protected) and the protected tags v*.

The package can be built locally with sh Build/ci/build-ter-package.sh v6.1.0 /tmp (needs a committed tag).