This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
Releases: Addpixel/KirbyComments
Releases · Addpixel/KirbyComments
1.5.2
1.5.1
- Fixes a bug where an optional and empty name-field would not result in
$comment->rawName()
beennull
. - Adds
$commentPage
argument todid-save-comment
hook. - Adds support for optional core fields. The core fields (comment author name, email-address and website-address) are not stored anymore if the value is
null
. - Improves documentation by fixing typos and replacing deprecated method names with the modern equivalent.
1.5.0
- Fixes formatting email notifications.
- Depreciates the
setup.content-page.title
option. Use thedecide-comments-page-title
hook instead. - Depreciates the
pages.comments.title
option. Use theget-content-page-title
hook instead. - Adds support for custom fields. Custom fields can now be defined in Kirby’s config.php to store custom values alongside the standard comment data.
- Adds comment nesting. Comments can now be nested using
$comments->nestByField()
. This enables in conjunction with custom fields replying to other comments. - Adds hooks for listening for and altering the behavior of Kirby Comments.
- Adds
form.message.htmlentities
option. - Improves documentation.
- All classes now include PHPDoc comments.
- API documentation now includes more type information and better descriptions.
- Readme now includes a table of contents for faster navigation.
1.4.2-hotfix
- Fixes storing HTML escaped values in the fields of comment pages.
1.4.2
- Fixes assigning a ID which is already used by another comment on the same page after a comment has been deleted.
- Fixes not displaying the value of the website-field in the Kirby panel.
1.4.1
- Adds conformance to PHPs
Countable
interface toComments
. This means, that in addition to$comments->count()
you can now usecount($comments)
. - Improves comment preview, which now can be initiated without providing a valid authentication token. This makes it possible for cached HTML forms with a cached authentication token to request a preview. Submitting comments still requires a valid authentication token.
- Improves documentation by fixing a syntax errors in the options table.
1.4.0
- Fixes
$comments->process()
from executing more than once during a page rendering when invoked multiple times.$comments->process()
still returns the status of$comments
on repeated calls. - Fixes not allowing for not sending unused fields. If you don’t want to use e.g. the website field for comments, removing it no longer confuses the data validation process.
- Depreciates the
Comments
constructor. (see below) - Adds
$page->comments()
method to KirbyPage
objects.- This deprecates the
Comments
constructor, which should no longer be used. Instead, use$page->comments()
or the newComments::for_page($page)
. - Contrary to the old
new Comments($page)
, the new$page->comments()
andComments::for_page($page)
storeComments
instances which can be reused without adding any extra cost of time or memory. Therefore, repeated calls to$page->comments()
do not impact the performance of your page rendering.
- This deprecates the
- Adds convenience methods for
$comments->value()
:nameValue
,emailValue
,websiteValue
,messageValue
, andhoneypotValue
. - Adds
$comments->toArray()
method. - Improves README.
- Many parts of the documentation have now been rewritten and include copy’n’paste-able code snippets.
- Syntax-highlighting notation has been aligned with GitHub’s interpretation.
- An effort has been made to unify American and British English spelling into American English spelling.
- Improves included snippets.
- Method calls have been modernized to use the new convenience methods.
- Attribute order has been normalized.
- IDs now include the
comment
prefix as not to collide with existing IDs.
1.3.1
- Adds an option for removing the page index of comment pages:
pages.comment.visible
. Setting this option tofalse
will prevent Kirby Comments from adding page index-prefixes to comments pages. Related issue: #20 - Adds options for renaming standard templates:
pages.comments.template
andpages.comment.template
. This allows for custom template/blueprint names.