Support

Account

Forum Replies Created

  • Hello,

    I noticed exactly the same issue, was wondering if it was related to our hosting settings, but apparently not.

    I observed that bug indeed with Firefox 69.0 and ACF 5.8.x versions. First thought it was related to a bug in ACF 5.8.4, but apparently it’s not the case.

    Also, the issue doesn’t occur with some websites, even with FF 69.0. The problem never occurs with Google Chrome or FF 68.0.2.

    When looking at the source code, the correct field type is “selected”, so I’m wondering if it could not be related to some auto-complete feature of Firefox which goes over ?

    I wrote a ticket to ACF team to know if they could have an idea.

  • I can’t remove the “Solved” solution, apparently. Anyway I don’t think we should debate this here.

    Also, I got an answer from the support team and they will fix it in version 5.7.9.

  • Of course it is not a definitive solution. It’s a workaround. But you noticed that this forum has only the possibility to define an answer as a solution.

    For someone who would read this thread, he could then find that, at this stage, downgrading is the only solution to solve the problem.

    The definitive solution will be to update with the next version, fixed.

  • Well, we can discuss and argue that for hours. I marked this topic as solved as this is a workaround which works. So, if someone comes here, he can downgrade to 5.7.7 and he will be able to edit his posts again. And there is now drawback as the changelog between 5.7.7 and 5.7.8 doesn’t show lots of changes. So, you can perfectly live with version 5.7.7 and wait a few days for the version 5.7.9 to arrive, with the bugfix.

  • Some reported to see this error in the javascript console. Personally I didn’t.

  • ACF support has been contacted, they also advised me to rollback to version 5.7.7 which I did and it worked around the problem.

  • So, this is definitely an issue with ACF 5.7.8. I will not perform update on other installations.

    I will post an issue on the github of ACF. In general, do you know if they react quickly ?

    For the downgrade, I suppose this is only possible if there was no change in the database structure. And to do so, you simply replace the files in wp-content/plugins/advanced-custom-fields-pro ?

    Thank you.

  • I do not see this error. But the issue could be related to ACF 5.7.8 update and not WP 5.0.

    According to the Changelog:
    https://www.advancedcustomfields.com/blog/acf-5-7-8-release/

    * Fix – Fixed all metaboxes appearing when editing a post in WP 5.0.

    Wondering if this could be related. As soon as I’ve got time I will try to reproduce the issue between 5.7.7 and 5.7.8.

Viewing 8 posts - 1 through 8 (of 8 total)