mediaessenz / domaincheck

v4.1.1 2026-10-26 12:38 UTC

Requires

• php: ^8.2
• ext-curl: *
• typo3/cms-core: ^13 || ^14
• typo3/cms-form: ^13 || ^14

Requires (Dev)

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

Suggests

• ext-json: *
• ext-xmlrpc: *

GPL-2.0-or-later

• Alexander Grein

• extension
• register
• domain
• whois
• typo3
• inwx
• domaincheck
• domainregister

Published on Packagist.org on 2026-10-26 11:39 UTC

README

What does it do?

Frontend plugin to check the availability of domains, with the domain robot API of INWX and an order form (EXT:form) for the found domains.

Documentation: https://docs.typo3.org/p/mediaessenz/domaincheck/main/en-us/

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/domaincheck composer install
ddev exec -d /var/www/html/vendor/mediaessenz/domaincheck 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 (:Version:, :Date:, :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 v4.0.1 -m "Added unit tests and the TER release automation"
   git push origin v4.0.1
   

   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 domaincheck_<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 v4.0.1 /tmp (needs a committed tag).