Frontend form problem of compatibility

Viewing 1 replies (of 1 total)
  • Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Thanks for the feedback!

    Please see the following related topic.

    This plugin has a pretty long history of incompatibilities with ACF Extended features. This is not the first time I get such report.

    My previous investigations, while trying to help some ACFE users, lead me to find out that its author copy/pasted some free ACF Extended feature (the Google reCaptcha field) and sell it in his Pro package, without credit or mention me, which is kinda edgy if you want my opinion. See related support discussion.

    I hope you’ll understand that I will not spend time debugging someone else code in these circumstances.

    Note: The ticket you linked is related to the “Taxonomy Terms” Field, which is a field from ACF Extended. The issue you report here is different, as it’s a Javascript error on the native ACF “Taxonomy” Field.

    Regards.

Viewing 1 replies (of 1 total)
  • The topic ‘Frontend form problem of compatibility’ is closed to new replies.