---
title: "Developer Guide"
manual: "T3Extblog (T3Blog Extbase)"
version: "main"
permalink: "https://docs.typo3.org/permalink/felixnagel/t3extblog:developer-guide@main"
source: "DeveloperGuide/Index.rst"
rendered: "2026-11-04T21:49:38+00:00"
---

# Developer Guide {#developer-guide}

Target group: **Developers**

**Within this page**

-   [Extending T3extlog](https://docs.typo3.org/permalink/felixnagel/t3extblog:extending-t3extlog@main)
-   [Code insights](https://docs.typo3.org/permalink/felixnagel/t3extblog:code-insights@main)
-   [Translations](https://docs.typo3.org/permalink/felixnagel/t3extblog:translations@main)
-   [Documentation](https://docs.typo3.org/permalink/felixnagel/t3extblog:documentation@main)
-   [Testing](https://docs.typo3.org/permalink/felixnagel/t3extblog:testing@main)
-   [TER deployment](https://docs.typo3.org/permalink/felixnagel/t3extblog:ter-deployment@main)

## Extending T3extlog {#extending-t3extlog}

### Using interfaces {#dev-guide-extending}

Some internal services are implemented as interfaces. The actual class to use could be configured.
This way it is possible to use custom implementations.

**Before TYPO3 10**
See `config.tx_extbase.objects` configuration in \[ext_typoscript_setup.txt\](../../ext_typoscript_setup.txt).

**TYPO3 10 and later**
See interface registration configuration in \[Services.yml\](../../Configuration/Services.yml).

More info on the topic:
[https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/DependencyInjection/Index.html](https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/DependencyInjection/Index.html)

### Events {#dev-guide-extending-events}

T3extblog provides a couple of events to extend or change the default behavior.
This is done by using PSR-14 events functionality provided by TYPO3.

**Available events**

-   -   **`CommentCreatePrePersistEvent` (former `prePersist` signal)**

        in `FelixNagelT3extblogControllerCommentController:createAction`
-   -   **`CommentSubscriberConfirmEvent` (former `subscriberConfirmAction` signal)**

        in `FelixNagelT3extblogControllerPostSubscriberController:confirmAction`
-   -   **`CommentSubscriberDeleteEvent` (former `subscriberDeleteAction` signal)**

        in `FelixNagelT3extblogControllerPostSubscriberController:deleteAction`
-   -   **`PostSubscriberConfirmEvent` (former `subscriberConfirmAction` signal)**

        in `FelixNagelT3extblogControllerBlogSubscriberController:confirmAction`
-   -   **`PostSubscriberDeleteEvent` (former `subscriberDeleteAction` signal)**

        in `FelixNagelT3extblogControllerBlogSubscriberController:deleteAction`
-   -   **`CommentNotificationCreateEvent` (former `processNewComment` signal)**

        in `FelixNagelT3extblogServiceCommentNotificationService`
-   -   **`CommentNotificationChangedEvent` (former `processChangedComment` signal)**

        in `FelixNagelT3extblogServiceCommentNotificationService`
-   -   **`CommentNotificationSubscribersEvent` (former `notifySubscribers` signal)**

        in `FelixNagelT3extblogServiceCommentNotificationService`
-   -   **`PostNotificationCreateEvent` (former `processNewSubscriber` signal)**

        in `FelixNagelT3extblogServiceBlogNotificationService`
-   -   **`PostNotificationChangedEvent` (former `processChangedSubscriber` signal)**

        in `FelixNagelT3extblogServiceBlogNotificationService`
-   -   **`PostNotificationSubscribersEvent` (former `notifySubscribers` signal)**

        in `FelixNagelT3extblogServiceBlogNotificationService`
-   -   **`SpamCheckEvent` (former `spamCheck` signal)**

        in `FelixNagelT3extblogServiceSpamCheckService`
-   `SendEmailEvent` (former `sendEmail` signal) in `FelixNagelT3extblogServiceEmailService`

**More info**

on PSR-14 events  in TYPO3:

-   [https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Events/EventDispatcher/Index.html](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Events/EventDispatcher/Index.html)
-   [https://usetypo3.com/psr-14-events.html](https://usetypo3.com/psr-14-events.html)

## Code insights {#code-insights}

*This section is incomplete*

**Table mapping**

This extension uses TYPO3 Extbase table mapping to make use of existing EXT:t3blog tables.
Take a look at `Configuration/Extbase/Persistence/Classes.php` to see how this is done.

## Translations {#translations}

Translations could be added here:
[https://crowdin.com/project/typo3-extension-t3extblog](https://crowdin.com/project/typo3-extension-t3extblog)

Please consider opening a GitHub ticket so we can review new translations as soon as possible!

> [!TIP]
> German localization has been handled by local files before version `2.2.0`.
> Please see this issue for more information: [https://github.com/fnagel/t3extblog/issues/99](https://github.com/fnagel/t3extblog/issues/99)

## Documentation {#documentation}

Anyone is very welcome to help improving our documentation!
Just send a pull request or add an issue at GitHub.

This extension uses the PHP based rendering approach. See here for more info:

-   [https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Index.html](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Index.html)
-   [https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/RenderingDocs/Index.html](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/RenderingDocs/Index.html)
-   [https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/Migration/Index.html](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/Migration/Index.html)

Use this command to render the documentation locally (Docker is needed):

`docker run --rm --pull always -v "./:/project" -t ghcr.io/typo3-documentation/render-guides:latest --config=Documentation`

## Testing {#testing}

### Automated Tests {#automated-tests}

Install development dependencies:

```bash
composer install
```

Run all checks and tests:

```bash
composer test
```

Run individual test suites:

```bash
# Unit tests only (fast, no database required)
composer test-unit

# Functional tests only (requires pdo_sqlite PHP extension)
composer test-functional

# Acceptance tests only (requires pdo_sqlite PHP extension)
composer test-acceptance
```

Tests use SQLite by default. To use MySQL/MariaDB instead:

```bash
typo3DatabaseDriver=mysqli \
typo3DatabaseHost=127.0.0.1 \
typo3DatabaseName=typo3_test \
typo3DatabaseUsername=root \
typo3DatabasePassword=root \
composer test-functional
```

### Code Coverage {#code-coverage}

Coverage reports require either [PCOV](https://github.com/krakjoe/pcov)
(recommended, faster) or [Xdebug](https://xdebug.org/) PHP extension.

```bash
# Unit test coverage (Clover XML + HTML report)
composer test-coverage-unit

# Functional test coverage (Clover XML + HTML report)
composer test-coverage-functional

# Acceptance test coverage (requires running Selenium + webserver)
composer test-coverage-acceptance
```

> [!TIP]
> When using Xdebug, the coverage scripts for acceptance tests handle
> `xdebug.mode=coverage` automatically via `-d` flags.
> For unit and functional tests, set `XDEBUG_MODE=coverage` or
> configure `xdebug.mode = coverage` in your `php.ini`.

Reports are written to:

-   `.Build/coverage/unit-html/` and `.Build/coverage/unit.xml`
-   `.Build/coverage/functional-html/` and `.Build/coverage/functional.xml`
-   `.Build/var/log/_output/coverage.xml` (acceptance, Clover XML)

On GitHub Actions, coverage is collected automatically on the latest PHP version matrix entry.
A summary is displayed in the workflow job summary.

### Manual Testing {#manual-testing}

This needs to be done for latest supported TYPO3 versions in a multi-language site setup.
It is recommenced to install T3extblog in TYPO3's introduction package.

[https://extensions.typo3.org/extension/introduction](https://extensions.typo3.org/extension/introduction)

**What needs to be tested:**

-   -   **Creating blog posts (with and without preview image and text)**

        -   Check post preview
-   -   **Posting comments and subscribe for new comments**

        -   With and without SPAM check triggered
        -   Test field validation
        -   Test prefilling fields
-   Using the subscription manager (confirm and delete for new comment and post subscription)
-   -   **New comment subscription**

        -   Admin, subscriber opt-in and notification emails
        -   -   **Triggered by:**

                -   Frontend & backend (confirm and un-spam a comment)
                -   Edit button (BE module and core dashboard) and direct spam / confirmed toggle buttons

 *Make sure mails are sent with localized links for multi language setups*
 New post subscription
	 *Subscriber opt-in (frontend) and notification emails (button in BE module)*
 Dashboard widgets work as expected
 *Test RSS feed*
 Test request throttling
\* PSR-14 events

**Quick test procedure**

Make sure to have all related pages, folders and blog categories localized!

-   Create a new post and translate it
-   -   **Add comment with subscription (saved but marked as SPAM)**

        -   admin email sent
-   -   **Mark as non SPAM using the dashboard (in blog BE module)**

        -   subscription mail sent
-   Confirm subscription by email link (check localization and link)
-   When in subscription manager -> add new article subscription
-   -   **Add another comment (saved but marked as SPAM)**

        -   admin email sent
-   Edit the comment record you just created (in list BE module)
-   -   **Un-check the SPAM checkbox, save record**

        -   new comment mail sent (check localization and link)
-   -   **Add a valid comment for the translated post**

        -   admin mail sent (check localization and link)
-   -   **Make sure there**

        -   are two comments displayed for the default language post and only one for the localized post
        -   is no "new comment" email for the default language subscription
-   Click envelope icon in "all post" view (T3extblog BE module) -> New post subscription mail sent
-   Check dashboard blog widgets functionality
-   Check RSS functionality (and check localization and links)

## TER deployment {#ter-deployment}

TYPO3 TER deployment is done automated via GitHub action workflow. Just add a version tag and push to GitHub.
See `/.github/workflows/release.yml` for more information.

**How to release**

-   Create upgrade guide!
-   Change version information in `/composer.json` (`extra.typo3/cms.version`)
-   Change year in `/Documentation/guides.xml` if needed
-   Change year in `/Documentation/Index.rst` if needed
-   Commit changes: Use \[RELEASE\] prefix, this commit message will be the TYPO3 TER release notice
-   Add tag to release commit (format: "1.2.3")
-   Change version information in `/composer.json` to next bugfix version + "+dev" (example: "1.2.3+dev")
-   Push GIT changes incl. tag

**After a release**

-   Make sure the release has been pushed to the TER
-   Add t3x file rendered by TER to the GitHub release
-   Update maintained translations (German) on [https://crowdin.com/project/typo3-extension-t3extblog](https://crowdin.com/project/typo3-extension-t3extblog)

**Manual release**

Sometimes the tag based Github workflow fails. You can manually upload the release:

-   Create an archive: `git archive -o "t3extblog_x.y.z.zip" "x.y.z"`
-   Upload archive: [https://extensions.typo3.org/my-extensions](https://extensions.typo3.org/my-extensions)

> [!IMPORTANT]
> Please be careful when pushing tags.
> Do not push "non release" tags without changing the version number in `/ext_emconf.php` to a dev version number
> (see above)
