Viewing 7 replies - 16 through 22 (of 22 total)
  • Thread Starter woltis

    (@woltis)

    There is no change after deleting the code.

    Plugin Author bgermann

    (@bgermann)

    Yes, I changed the comment form to be non-AJAX only. That results in appending the GET parameter cfemail to the HTTP redirect followed by the form submission. I guess there was a security issue with this in older cformsII versions so that Wordfence included a rule. You can switch back to 14.10.1 and I will investigate it.

    Thread Starter woltis

    (@woltis)

    Just disabled Wordfence, but 403 remains. Must be another reason for this.

    The change to non-Ajax only is sad, because ajay is the main reason why I use cforms for comments. without Ajax cforms would not make sense.

    I will switch back to 14.10.1 in a minute.

    Plugin Author bgermann

    (@bgermann)

    And you do not need to paste the mod_rewrite rules.

    Thread Starter woltis

    (@woltis)

    Now 14.10.1 is back again and the ajax-comment-form works like a charmw ??

    Plugin Author bgermann

    (@bgermann)

    I am sorry, but as I personally do not use the WP Comment feature, I do not want to support it any longer. The AJAX version rebuilt some WordPress stuff (reimplementing the things you extend is very bad engineering). And actually WordPress is built in a way that it does not expect someone posting comments via AJAX. A good way to do it would include having an actual implementation for the WordPress comment interfaces and exchanging them. Maybe there is another plugin that does something like this.

    You seem to be the only one who uses WP Comments at all, because I only got bug reports for this from you. You should think of switching to normal WordPress comments really.

    Actually I just removed the Tell-a-Friend feature for 14.12 as this feature requires a lot of manual fiddeling with the theme and I do not like the use case. One should be able to manually send a recommendation email with a link to friends. They then see that this is really coming from you and is not spam from any odd webserver. Did you check how often that feature is used on literaturcafe.de?

    However as long as there are no security issues with 14.10.1 you can continue to use it. The Q&A and CAPTCHA features have issues in that version. They can be guessed programmatically.

    Thread Starter woltis

    (@woltis)

    Thank you for this honest evaluation. I disabled the WP Comments feature and returned to the normal comment form.
    I also disabled the TAF-feature.
    So now I updated to version 14.11.4.

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘Comment-form broken in 14.11.2’ is closed to new replies.