Target group: Administrators


Minimal configuration

Make sure to setup at least the following settings (see /Configuration/TypoScript/constants.txt for more details!):

# PID of the blog sysfolder containing all blog related records
plugin.tx_t3extblog.persistence.storagePid = 456

# PID where the "Blogsystem" plugin is located = 123

# PID where the "Subscription Manager" plugin is located = 789

# E-mail address where notification mails were send to = mailadress@of-the-admin.tld

General configuration

Key prefix is plugin.tx_t3extblog.

Property Description
settings.blogName Name of your blog
settings.blogsystem All settings of your blog system, i.e. pagination, comment handling…
settings.subscriptionManager Configure the subscription process, i.e. admin email, notification email…
settings.blogSubscription Configure blog (new post) subscription form
settings.categories Some settings for the categorie-module
settings.latestPosts Some settings for the latest posts module
settings.latestComments Some settings for the latest comments module
settings.rss Basis rss-settings (see /Configuration/TypoScript/RSS/setup.typoscript for page config)
settings.backend Configure the backend output
settings.debug Some debug configs
settings.*.privacyPolicy.enabled Enable the privacy policy checkbox in the subscription forms
settings.*.privacyPolicy.typolink Set a typolink as the privacy policy link Localize date format, used within the fluid templates
lib.tx_t3extblog.month Localize month format, used within the fluid templates

Like most other extensions, settings can be overwritten via TypoScript.

Have a look at /Configuration/TypoScript/setup.typoscript and its includes (see /Configuration/TypoScript/Includes/Settings).

SPAM checks

A comment has two additional visibility flags (besides TYPO3 default hidden and deleted flags): is approved and is spam. Comments not approved or marked as SPAM are not displayed.

Admins configure if a comment should be approved by default or always needs manual approval. In addition multiple basic SPAM checks flag every new comment as SPAM or not SPAM:

  • Simple “I am human” checkbox (no real check for bots!)
  • Honeypot fields
  • Cookie support check
  • User agent check

Each of these checks has a configurable spam point value. The sum of all spam points is compared to multiple configurable threshold values in order to trigger specific actions:

  • mark comment as spam but save it anyway
  • block comment and allow user to try again
  • redirect user to a configurable page

See TypoScript for full configuration:

  • plugin.tx_t3extblog.settings.blogsystem.comments
  • plugin.tx_t3extblog.settings.blogSubscription


Built in SPAM protection may be insufficient to protect your blog from serious attacks and does not prevent brute force attacks.

Speaking URLs

This extension include a predefined setup for the TYPO3 CMS core feature speaking URL, see t3extblog/Configuration/Routes/Default.yaml for details.

Default will render URLs for blog posts like this: but it’s easy to change this by either:

  • Remove the datePrefix option completely, resulting in no date prefix in the URL:
  • Use any date format string with according prefix. For example with speaking month names:
    datePrefix: ‘Y/F/’ and datePrefixRegex: ‘#^[^/]*/[^/]*/#’ resulting in URLs like (please note: you will need to adjust requirements.post_title to ^d{4}/p{L}{3,10}/[p{Ll}d-_]+$ in order to make this work; you might want to enable datePrefixLowercase too)


Option datePrefix uses the date() method, see here for possible options:


This extension include a predefined setup for RealURL auto configuration, see typo3conf/ext/t3extblog/Classes/Hooks/RealUrl.php for details.

When using EXT:realurl or similar extension you will need to add additional StaticTS template T3Extblog: additional RealUrl config (t3extblog) (/Configuration/TypoScript/RealUrl/setup.txt).

When using RSS, add a config.tx_realurl_enable = 1 to your TS to get RealUrl running in the RSS-Feed.


Since version 5.x (and therefor TYPO3 9.x) it’s recommended to use the core speaking URL feature (see above).


Add this static TS to the blogsystem plugin page only to preserve cache!


When not using the realurl autoconfig feature, you need to add the configuration by yourself!

Responsive image rendering

T3extblog is able to make use of TYPO3’s RWD image rendering (sourceCollection feature).

This works by using a cObject ViewHelper within the templates which processes a TypoScript Lib: lib.tx_t3extblog.responsiveImage (defined in /Configuration/TypoScript/setup.txt)

This feature is configured via TypoScript as described here:

By default, T3extblog makes uses of the tt_content image rendering configuration. It’s possible to adjust the rendering for t3extblog by modifying this TypoScript lib or by using a custom (i.e. Fluid) rendering.


Since version 5.x (and therefor TYPO3 9.x) this feature has been removed as no longer provided by the TYPO3 core.

Overwrite templates

It’s possible to copy only the needed files and have a fallback.

Use the constants or change the TS setup:

plugin.tx_t3extblog {
view {
                   # "Email/" is appended to the final template path when rendering emails
    templateRootPaths {
        0 = EXT:t3extblog/Resources/Private/Templates/
        10 = {$plugin.tx_t3extblog.view.templateRootPath}
        20 = EXT:my_theme/Resources/Private/T3extblog/Templates/
        30 = fileadmin/templates/ext/t3extblog/Templates/
    partialRootPaths {
        0 = EXT:t3extblog/Resources/Private/Partials/
        10 = {$plugin.tx_t3extblog.view.partialRootPath}
        20 = EXT:my_theme/Resources/Private/T3extblog/Partials/
    layoutRootPaths {
        0 = EXT:t3extblog/Resources/Private/Layouts/
        10 = {$plugin.tx_t3extblog.view.layoutRootPath}
        20 = EXT:my_theme/Resources/Private/T3extblog/Layouts/