Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter sermalefico

    (@sermalefico)

    This happens as of version 3.0.16.

    Another problem that occurs is that the taxonomy custom field type loses the “Taxonomy” field type when saving the group of custom fields and becomes a text field type. If you save again it becomes a text field and you lose all the settings.

    nelsoncarterconsulting

    (@nelsoncarterconsulting)

    It also breaks any Conditional Logic applied to fields in the ACF interface.

    This happens even on the Pro version (I’m posting this here because the support forum for Pro users has been removed from the plugin developers website without explanation).

    nelsoncarterconsulting

    (@nelsoncarterconsulting)

    I recommend you roll back to the previous version and don’t expect a support answer here any time soon – only six out of 35 support requests on here have been answered in the last 2 months and even on their Facebook Page, the most recent comment is someone complaining that they haven’t received an answer in 7 days.

    Yet the developer continues to advertise the Pro version of the plugin so I guess it must still be maintained, although I would call into question the “with great support” statement on the website.

    nelsoncarterconsulting

    (@nelsoncarterconsulting)

    Shabti, please provide a means to download an older version of the Pro plugin that still works. I have it installed on a live site which now doesn’t function correctly because of your erroneous update.

    Thread Starter sermalefico

    (@sermalefico)

    the lasts updates i think is all fine and fixes the errors. I dont`know if the pro version have errors. I understand that mantenance a free plugin is takes time, and now is holidays…, but developer reads the support posts here and update with fixes.He hasn′t time to post a response, i understand…

    Plugin Author Shabti Kaplan

    (@shabti)

    Regarding this issue, there was a problem with the validation on the backend since version 3, but we fixed it in one of the most recent updates. 3.0.28 should work perfectly. If it doesn’t please create a new topic here with a useful explanation of what exactly doesn’t work so that we can attempt to reproduce the issue or walk you through a fix.

    Regarding our support, you are requested ght that we haven’t lived up to our promise of great support, but that is all behind us. We are now providing incredible support. Still this forum will probably still get less attention then our support emails.

    Regarding downloading a previous version of the pro version, for now such a request must be made to our support email.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Last update breaks validation of requiered fields in admin backend’ is closed to new replies.