Configuration

Minimal configuration

Make sure to setup at least the following settings (see /Configuration/TypoScript/constants.txt or /Configuration/Sets/Default/settings.definitions.yaml 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
plugin.tx_t3extblog.settings.blogsystem.pid = 123

# PID where the "Subscription Manager" plugin is located
plugin.tx_t3extblog.settings.subscriptionManager.pid = 789

# E-mail address where notification mails were send to
plugin.tx_t3extblog.settings.subscriptionManager.admin.mailTo.email = mailadress@of-the-admin.tld

General configuration

Key prefix is plugin.tx_t3extblog.

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
• Search for links in comment text

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

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: domain.com/page/article/2020/12/30/post-title/ but it's easy to change this by either:

• Remove the datePrefix option completely, resulting in no date prefix in the URL:

  domain.com/page/article/post-title/

• Use any date format string with according prefix. For example with speaking month names:

  datePrefix: 'Y/F/' and datePrefixRegex: '#^[^\/]*\/[^\/]*\/#' resulting in URLs like domain.com/page/article/2020/December/post-title/ (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)

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/
           }
       }
}