Title: Works Flawlessly…almost
Last modified: August 21, 2016

---

# Works Flawlessly…almost

 *  [Storyman](https://wordpress.org/support/users/storyman/)
 * (@storyman)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/works-flawlesslyalmost/)
 * Great plugin that works as advertised. The only issue is that another installed
   plugin limits the number of characters that can be submitted and when the user
   goes back in to edit the comment there is no character limit.
 * Is there any possibility of adding a feature so that submissions could be limited
   in character count?
 * [http://wordpress.org/plugins/wp-ajaxify-comments/](http://wordpress.org/plugins/wp-ajaxify-comments/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [janjonas](https://wordpress.org/support/users/janjonas/)
 * (@janjonas)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/works-flawlesslyalmost/#post-4128447)
 * Hi Storyman,
 * what’s the name of the other plugin that limits the number of characters that
   can be entered? I’m sure there is a way to add compatibility to the WP-Ajaxify-
   Comments plugin.
 *  Jan
 *  Thread Starter [Storyman](https://wordpress.org/support/users/storyman/)
 * (@storyman)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/works-flawlesslyalmost/#post-4128467)
 * Hi Jan,
 * Thanks for a prompt reply. The plugin is [Greg’s Comment Length Limiter](http://wordpress.org/plugins/gregs-comment-length-limiter/).
 *  [janjonas](https://wordpress.org/support/users/janjonas/)
 * (@janjonas)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/works-flawlesslyalmost/#post-4128571)
 * Hi,
 * the only problem I can see in my development environment is, that the counter
   is not reseted properly after the commments have been reloaded.
 * This could be fixed by setting the “‘OnAfterUpdateComments’ callback” option 
   to
    `gcllCounter($("#comment")[0]);`
 * Please also upgrade to the most recent developer version 0.17.1 ([http://downloads.wordpress.org/plugin/wp-ajaxify-comments.zip](http://downloads.wordpress.org/plugin/wp-ajaxify-comments.zip))
   which includes a bug-fix for the “OnAfterUpdateComments” event.
 * If anything else is not working as expected please send me a link to your blog,
   where I can reproduce the issue.
 * Hope this helps…
    Jan
 *  Thread Starter [Storyman](https://wordpress.org/support/users/storyman/)
 * (@storyman)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/works-flawlesslyalmost/#post-4128578)
 * Hello Jan,
 * Thank you for the time you took to find a solution and must apologize that I’m
   at a loss as to where to place gcllCounter($(“#comment”)[0]);. Your guidance 
   is appreciated.
 *  [janjonas](https://wordpress.org/support/users/janjonas/)
 * (@janjonas)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/works-flawlesslyalmost/#post-4128642)
 * Hi,
 * you find the “‘OnAfterUpdateComments’ callback” option on the plugin’s settings
   page (WordPress Backend > Settings > WP-Ajaxify-Comments) and please (as written
   above) also upgrade to the most recent developer version 0.17.1.
 *  Jan

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Works Flawlessly…almost’ is closed to new replies.

 * ![](https://ps.w.org/wp-ajaxify-comments/assets/icon-256x256.png?rev=2962290)
 * [Ajaxify Comments - Ajax and Lazy Loading Comments](https://wordpress.org/plugins/wp-ajaxify-comments/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-ajaxify-comments/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-ajaxify-comments/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-ajaxify-comments/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-ajaxify-comments/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-ajaxify-comments/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [janjonas](https://wordpress.org/support/users/janjonas/)
 * Last activity: [12 years, 8 months ago](https://wordpress.org/support/topic/works-flawlesslyalmost/#post-4128642)
 * Status: not resolved