weweave

@jackennils: One solution would be to use the “OnAfterUpdateComments callback” and add some JavaScript that removes the line break. If you need help with this, please buy a professional support ticket here: https://weweave.net/products/wp-ajaxify-comments/support/.

@jackennils. Thanks for the feedback. There is no guarantee that we find a solutions, but we do our best and we can solve about 90% of these issues.

@jackennils, can you please try if version 1.6.1 fixes the “JavaScript injection problem”. We added some optimizations that should prevent the scripts from being loaded on overview pages. You can find version 1.6.1 here: https://downloads.www.ads-software.com/plugin/wp-ajaxify-comments.zip
Please let us know, if this fixes your problem.

Regarding the compatibility to simple-comment-editing we would like to ask you to buy a (professional support ticket here: https://weweave.net/products/wp-ajaxify-comments/support/.

Thanks
Jan

• This reply was modified 6 years, 4 months ago by weweave.

Hi @jackennilsen,
Thanks for your message. Do you have a link for us where we can reproduce the problem? You can also contact us here: https://weweave.net/s/contact.
Does this only happens if the first post on the index page has at least one comment?
Best regards,
Jan

Hi nymets1104,
Our plugin should not slow down the commenting feature. We offer professional support at https://weweave.net/products/wp-ajaxify-comments/support/. After buying a support ticket we can analyze your problems in detail.
Best regards
Jan

Hi andrew55,
the plugin is compatible with plugins that add caching as long as the caching does not break the comment functionality at all. In other words: If the WordPress default comment posting (without AJAX) works with an activated caching plugin, it will still work after adding the AJAX functionality with WP Ajaxify Comments.

It seems that some JavaScript files are not loaded properly. Please contact our professional support here https://weweave.net/support/ in order to get help.

I’m pretty sure that this problem can be fixed by using the correct selectors. If you need help, you can buy a support ticket here (https://weweave.net/support/) to get in contact with our professional support.

This problem can be fixed by using the correct selectors. If you need help, you can buy a support ticket here (https://weweave.net/support/) to get in contact with our professional support.

Thanks for reporting the problem. This should be fixed in version 1.5.1 which is available here https://downloads.www.ads-software.com/plugin/wp-ajaxify-comments.zip and which will be (officially) released soon.

We missed that. The tag was just created. Thanks JayCC.

Thanks for reporting the problem. This should be fixed in version 1.4.1 which is available here https://downloads.www.ads-software.com/plugin/wp-ajaxify-comments.zip and which will be released within the next days.

Hi,
please contact our support here (you’ll have to buy a support ticket):
https://weweave.net/products/wp-ajaxify-comments/support/
I’m sure we can help you with this.
Kinds regards,
Heiner

Hi Timothy!
That’s probably caused by some kind of incompatibility between the two plugins. We offer support to solve such issues. Please have a look at our website:
https://weweave.net/products/wp-ajaxify-comments/support/
Kind regards,
Heiner

Hi Chris,

The information you got from the technical team is not 100% correct. It’s true that we have a auto update functionality and it’s also true that this functionality cause additional traffic. But: This functionality is disabled by default (the default value of 0 means that this functionality is disabled).

If you need professional support from our side to get the plugin working again, please open a support ticket here https://weweave.net/s/wp-ajaxify-comments/support.

Thanks in advance.