Snicker

[stani]

Snicker Plus - does not work (see attachment).

snicker.jpg (25.49 KiB) Viewed 4397 times

Old Snicker does not work on Bludit 3.22.0 (PHP 8.3) - makes the entire website inaccessible.

[lastpictures]

The current version of Snicker is completely outdated and should no longer be used in a production environment.

I can make my comment system available to you. You may need to adapt it to your local language.

Download: https://lastpictures.de/download/345d82 ... 16025c0c61

[stani]

Hi lastpictures, many thanks.

Is this "simplecomments" plugin something completely different from "Bludit Plugin Comments"?

[lastpictures]

Hi lastpictures, many thanks.

Is this "simplecomments" plugin something completely different from "Bludit Plugin Comments"?

No. It is a completely new development, without the baggage of other plugins.

[stani]

I'm testing it right now... It's pretty OK, but comment-reaction to another comment doesn't work.... I also think that deleted comments should remain in the "Moderation" folder, for possible later approval or tracking of email addresses.

[lastpictures]

I have thoroughly reviewed the plugin again, including the feature that allows you to disable replies to existing comments. Additionally, the email sender functionality has been made more robust, and you can now specify separate addresses for notifications and the sender.

Furthermore, a "soft-delete" feature has been implemented: comments are removed from the frontend but remain in the admin area (though permanent deletion is still possible there).

Storage has also been switched from a single central .json file to a per-page storage system (using SHA-256 filenames). This results in a noticeable speed boost, especially when dealing with a large number of comments. The existing .json file is automatically migrated; it is only backed up as `.legacy....bak` once all data has been successfully written and verified.

The admin interface has also been adjusted—specifically, the moderation features have been improved and the overview made clearer.

Please note: not all hosting providers may support every feature. You should therefore test the plugin yourself and make adjustments if necessary.

Download: https://lastpictures.de/download/345d82 ... 16025c0c61

[stani]

I wrote that it is not possible to respond to an existing (approved) post.
This message appears: "⚠ The answer does not match this page."
And in this context, I would be interested, if replying to posts would work, whether it's listed under the original post (crumb menu), or what it's like?


OK, thanks, I'll try the new later...

[stani]

OK lastpictures, I just tested it:

1) Comments are active by default on all pages. By default, it should be the other way around – inactive everywhere. In this context, there is also a missing mass button for all active/deactive

2) Comments are enabled not only under articles, but also in categories, under individual article previews – very distracting

3) I don't see a "soft delete" button anywhere

4) Email address: "Your email address will not be published. It will only be stored for additional questions and to prevent misuse." I don't understand this function a bit. Anyone can write any non-existent address in the form of "nothing@nothing.com" there and it will still work. It would make sense if, for example, the author was notified by his email that someone responded to his post. Therefore, either a) cancel entering the email address, or b) give it some meaningful function

[lastpictures]

Hello,

You are free to customize the plugin however you like!

In the "Manage Pages" section, you have options to filter and adjust settings. I have included a feature that disables the plugin on all pages by default. If the plugin is already in use, your existing configuration will be respected. You will therefore need to take action once—or uninstall the plugin and start over with the desired "disabled on all pages" setting. Either way, whether you identify where *not* to use the comment function or the reverse, the amount of work remains the same.

The "soft delete" feature is highlighted more clearly in the "Moderation" area.

The email address provided when posting a comment must be valid, as the user receives a confirmation request at that address. This email contains an activation link directing the user back to the page where they posted the comment. (The confirmation link is cryptographically secure: it uses a random 256-bit token—only the SHA-256 hash of which is stored with the comment—and the token has an expiration time and is deleted after successful confirmation, making it valid for one-time use only.) The user must then confirm the activation. This extra click prevents issues caused by GET requests. Such requests can be problematic because email clients, virus scanners, or link scanners sometimes automatically visit URLs. Theoretically, this could cause an email to be marked as confirmed even though the user hasn't clicked anything themselves. If the user does not complete the confirmation, the comment remains in the moderation queue, though the admin can still approve it manually. However, if the user *does* confirm their email address, the notification email is sent to the admin/author only at that point.

Regarding the issue where it is impossible to reply to an approved comment: I cannot reproduce this problem; there are no such issues with my Bludit configuration.
Take a look at the integration on my site—it works. Feel free to post a test comment to walk through the process.
For example, here: https://lastpictures.de/erzgebirgsschan ... orgenstadt

Please download the latest version using the link provided in the thread.

Here is a summary of the features:

SimpleComments adds a standalone comment and reply system to Bludit, featuring moderation, email verification, and various safeguards against abuse.

After installation, comments are disabled by default on all pages. They can be enabled for specific pages within the admin area. The page management interface includes search and filter functions, covering standard and static pages.

Visitors can post comments and reply to existing, approved comments. Configuration options include maximum nesting depth as well as character and link limits. The form also incorporates a CAPTCHA, a honeypot, a minimum submission time, and an adjustable rate limit to protect against automated or excessive submissions.

An email address is mandatory but is not displayed publicly. After submission, the user receives a verification link. Simply visiting the link does not complete the process; the user must explicitly confirm the comment on a separate verification page. The comment then awaits approval by the administrator.

The administrator retains full control throughout the process. Comments associated with unverified email addresses can still be manually approved; the lack of email verification remains clearly marked in the admin area.

Moderation categories include "Email Pending," "New," "Approved," and "Soft Deleted." Comments can be edited, approved, hidden, or restored. With a "soft delete," the comment remains stored and can be recovered; only the "Permanently Delete" option removes it for good.

The administrator can receive email notifications for new comments. Sender and recipient addresses, along with other thresholds and security settings, can be configured within the plugin. The built-in mail function also supports using the commenter's email address as the "Reply-To" address.

Comments are stored as files within the plugin's working directory. Write operations are protected against concurrent access, and corrupted JSON files are backed up during critical read operations before data is overwritten.

In short: The plugin provides Bludit with a moderated comment feature in which page approval, email verification, and publication are deliberately kept separate. The final decision regarding which comments are made public always rests with the administrator.

[stani]

Thanks, I downloaded it from that link, but it's still the same - the previous version...