mmc/guestbook

A guestbook plugin providing several mechanisms for spam prevention

Installs: 300

Dependents: 0

Suggesters: 0

Security: 0

Type:typo3-cms-extension

2.0.3 2021-10-03 00:49 UTC

This package is auto-updated.

Last update: 2021-10-03 00:50:36 UTC


README

What does it do?

This is a guestbook built on TYPO3 extbase. It uses several mechanisms for spam prevention:

  • Honeypot fields
  • Minimal form submission time (spambot prevention)
  • Unique hash for every form post (prevent post replay by spam bots and makes faking the timestamp impossible)
  • Form html scramble (can be disabled in TS constants)
  • Security question: user has to solve a simple random addition (can be disabled in TS constants)
  • New entries can be stored hidden to allow redactional review by email before publishing (can be enabled in TS constants)
  • Email-review of new entries (can be enabled in TS constants). Links in the mail allow to decide if the post is spam or not.
  • Block IP’s of entries marked as spam (can be disabled in TS constants)
  • If the field “url” is used, links in the guestbook list view are generated with the attribute “rel” set to “nofollow”. This makes spamming uselesss, as search engines will not follow the link.

Available fields for a guestbook entry record are:

  • name
  • first name
  • place (city)
  • email
  • url (visitor’s website)
  • message
  • comment (for editor’s comment)

Also each guestbook entry uses these fields for spam prevention:

  • is spam: checked if the entry is spam
  • remote ip: stores the ip of the poster
  • post hash: unique hash for every form post, will be stored to detect POST-replay

By default IPs of entries marked as spam will be blocked for further posts.

Configuration Reference

Include the static template of the extension in your site template

Typoscript Constants:

scrambleForm Scramble the subscription form HTML (spambot protection). The form will be written to the DOM by javascript. Checked by default.

blockSpamIps Posts from IPs of guestbook-entries marked as spam will be ignored.

useMathTest Show a simple randomly generated addition in the form that the user has to solve to prove it's a human!

reviewNewEntries For every new entry, an email will be sent to the redactor that can decide if the post is spam or not. Two links in the mail allow to commit the decision. You have to provide an email-address to make this work (‘reviewEmailAddress’).

hideNewEntries New entries will be stored hidden, this option makes most sense in combination with the 'reviewNewEntries' option.

pageSize Number of guestbook entries to show on one page.

reviewEmailAddress Email address to send new entry review mails to.

reviewEmailSenderAddress Email sender address for review mails.

reviewEmailSenderName Email sender name for review mails.

reviewEmailSubject Review mail subject.

minFormSubmissionTime Minimal time in milliseconds that has to pass between the generation of the form to the submission. A human usually can’t fill in and submit a form in 2 seconds providing a meaningful message.. a spambot can.

secret This string will be used to generate hashes for the form and the review-links. You should change this to any random string to make it unique for your guestbook.

Storage for guestbook entries

Set up the system folder to store the guestbook entries:

  • TS-constant “Default storage PID” [plugin.tx_mmcguestbook.persistence.storagePid] or
  • In the plugin (Behaviour > Record Storage Page).

ChangeLog

2.0.3

  • Fix version inconsitency
  • Move JS to footer
  • Rename files .ts to .typoscript

2.0.2

Bugfix: $isSpam default value in Model

2.0.1

Bugfixes (thanks to Loek Hilgersom):

  • EntryController->getStandaloneView overrides original controller-context in TYPO3 10
  • TypoScript condition in old style

2.0.0

Changed major version to 2 (dropped TYPO3 8 support)

1.3.6

Upgraded jquery core to 3.5.1
include js via typoscript-setup, use includeJSLibs for jQuery inclusion
bugfix: missing option to include jQuery

1.3.5

Fix in ext_emconf.php

1.3.4

Remove autogenerated comments in ext_emconf.php

1.3.3

Remove ext_icon.gif

1.3.2

Remove .gitignore

1.3.1

Fix Viewhelper ifHasErrors
Fixed sendReviewMail bug

1.3.0

TYPO3 9.5 / 10.4 compatibility

1.2.1

rename constants.txt / setup.txt to *.ts
bugfix in constants.ts

1.2.0

Composer ready TYPO3 version constraint ^8.7

1.1.1

Bugfix (default value DomainModelEntry isSpam)

1.1.0

TYPO3 8 compatibility

1.0.3

Small bugfix; thanks to Ralf Klett

1.0.2

Multiple view-paths in typoscript-setup for TYPO3 7

1.0.1

TYPO3 7.6.xx compatibility
Changed state from 'beta' to 'stable'
Bugfix: hidden entries have not been found by approve/mark as spam

0.9.6

Bufix (Form was cached)

0.9.5

Added several spam protection features

  • Block form POST replay (spambot-blocker)
  • Minimal form submission time (spambot-blocker)
  • Form HTML scramble (spambot-blocker)
  • Security question (simple random addition to solve)
  • Entries are markable as spam -> block further posts from this IP
  • Redactional review of every new entry (by email)

Hash of [timestamp+random+secret] is submitted with the form. The hash will be checked server-side, if valid it will be stored with the new entry to prevent POST-replay. The timestamp (to check form submission time) can’t be faked this way, too.

The security question is a simple addition, randomly generated. The result is hashed with secret and submited with the form and then compared serverside. There is also a client-side validation by js.

New entries can be either published right away, or first be stored hidden. An email for redactional review can be sent, the reviewer can decide if the post is spam or not, just by clicking one or the other link. These links are also protected by a hash. If the new entry was stored hidden, it will be published now if the decision is “not spam”. If the entry is marked as spam, further posts from it’s origin IP will be blocked (can be disabled in TS constants).

Server side form validation

Validation works completly server side if you disable client side validation. To remove client side validation, just remove the “onsubmit” attribute of the form.