Meerkat Comment System for Statamic 2 Release Notes

Corrects a casing issue for case-sensitive file systems

Protects against null dates when determining if comments are enabled

1.5.87 - Removes default filters from all-comments to improve compatibility with the filter syntax - Disables default filters on responses when filters are present - Adds an additional check to the user:from_auth check to handle cases where user ID is present, but set to null.

1.5.86 - Fixes a bug that incorrectly checks for a reply comment ID. - Fixes a bug that would throw a fatal exception if validation keys were not matched with messages.

1.5.85 - Dramatically expands the thread filtering features. Learn more in the Filtering Comment Threads guide.

1.5.84 - Fixes an issue when resolving comments with all-comments when more than one filter are applied

• Adds a utility tag all-comments to easily filter comments by user or context
• Adds a comment's context information to the resolve comment with the comment_context data key
• Exposes the POST /!/Meerkat/delete endpoint for Statamic theme developers

Adds new data attributes to comments to make it easier to implement in-line comment editing. See https://github.com/Stillat/meerkat-examples for an example of implementing in-line editing using JavaScript.

Fixes an incompatibility between Statamic's Collection Tags and Meerkat's Collection Tags Helpers

Force rebuild

1.5.74

• Improves compatibility between Recaptcha addon and Meerkat Replies through replies-to

1.5.73 - FIX: Multiple issues preventing CP actions from completing, or correctly display messages or current state - FIX: Corrects an overly-aggressive validation check that prevent replies from being detected correctly

• FIX: Corrects the behavior of recursive comments For best results, please wrap the recursive call in the parent element (ul in this case):

    {{ meerkat:responses as="replies" }}

        <ul>
            {{ replies }}
            <li>
                {{ id }} - {{ comment }}


                {{ if has_replies }}

                <ul>{{ *recursive replies* }}</ul>

                {{ /if }}
            </li>

            {{ /replies }}
        </ul>

    {{ /meerkat:responses }}

• FIX: Removes un-needed findWhere calls.

1.5.70 - FIX: Corrects an issue preventing comments from being correctly saved - FIX: Corrects a bug that prevented error messages from being displayed - NEW: Adds a errors.error_in translation string that is used when reporting errors on the Control Panel - NEW: Adds a errors.comment_no_content translation string that is supplied when a comment manifests without content - Improvements: - If an error occurs when loading a comment from the data-source, it will not block all comments from loading - Exception output and comment IDs logged to the Error log. - Source data stored internally with the comment submission, to make mutation observation more reliable - Control Panel error messages provide more details - Comment Actions visible by default (increased opacity) - New UI that displays ongoing comment action - Expands Spam Guard CP error reporting (Guard contract expanded) - Third-party Guard service failures no longer block save operations - CP error messages will correctly reflect Guard operation results - Simplified comment save logic

• Translation Strings Added:
  • actions.approving
  • actions.unapproving
  • actions.replying
  • actions.spam_submitting
  • actions.delete_removing
  • errors.error_in
  • errors.comment_no_content
  • errors.guard_service_error
  • errors.guard_comment_saved_error
  • errors.guard_comment_ham_saved_error
  • errors.guard_multiple_spam_submit_errors
  • errors.guard_multiple_ham_submit_errors

• Adds the getPublishedCommentCount helper function the Meerkat API to easily get the total number of replies, including replies for a comment stream.
  • Usage (from within site/helpers/Tags.php) $this->api('Meerkat')->getPublishedCommentCount($postId)

• Emits the Statamic Form.submission.creating event to provide compatibility with other plugins
  • If a third-party, or configuration value, causes the 'creating' event to fail, a 'creating' error entry will be provided
  • Control Panel, or other authenticated users, will be by-pass "captcha" validation messages by default This behavior can be changed by adding a captcha_auth_bypass configuration entry to settings/addons/meerkat.yaml and setting it's value to false

• Patches the Meerkat Statamic Control Panel translations with fallback values when appropriate
• Improves locale detection in the API Comments response

• Ensures that reply-to fields are an array to prevent errors

1.5.8 - Allows for greater control over user permissions in the Control Panel. See https://stillat.com/meerkat/docs/permissions for more details. - Improves overall Meerkat security though improved access control - IMPROVE: Removes internal use of Meerkat helpers.php file in favor of instance methods: - Reduces global function pollution - Issue(s) where helpers would not load on some installations - NOTE: The existing helper functions have not been removed for compatibility with existing integrations - Renames /Http/Composers/JavascriptComposer.php to /Http/Composers/JavaScriptComposer.php - Deprecates the use of Meerkat's Compass Server and Bag purchases - license_key removed from the default Meerkat settings.yaml - Replaced {{ meerkat_trans() }} in Blade resources with {{ translate('addons.Meerkat::XXXXXXXX) }}`

• Restores the comments section when viewing a post in edit mode (CP)
• Allows non-super admins to moderate contents
• Prevents Akismet API call failures from stopping requests
• Fixes a bug that would cause comment failure on non well-formed comment submissions

Resolves issue #10 Problems with Meerkat success and notification messages

Change notes:

• Updates the Meerkat code base to emit events that conform to Statamic's Form submission events, and stores submission success messages in Statamic's Form flash session.

Bug Fixes

• Resolves an issue with the comments count API
• Corrects the Meerkat form configuration issue (regression)

Improvements

• Provides compatibility with Statamic v 2.11.12

Resolves a JavaScript path issue Improves the Composer setup and installation process

Fix - Fixes an issue with missing files on add-on setup - Fixes an issue with the latest versions of Statamic

• N/A Changelog not available.

• N/A Changelog not available.

• N/A Changelog not available.

• N/A Changelog not available.

• N/A Changelog not available.

• N/A Changelog not available.