`wp.hooks` implementation overridden by AFC PRO about acf HOT 9 CLOSED

Hi @gziolo

Thanks for the bug report.

Yes, it looks like the wp.hooks library I use does not check for an existing instance.
I'll have this fixed in the next version.

from acf.

Hi @mejta

Hmmm.. looks like WP is requiring strict usage rules for the wp.hooks library.
I'm currently using a '/' in the action names as a namespace, but will need to change this to a '_' to avoid the errors.

Thanks for letting me know, I'll add this change to my to-do list.

from acf.

Thanks for the updates on this one everyone. Had a client just upgrade to WP v5 and date fields stopped working. Easy fix by upgrading to the latest and greatest :) Also bought a developer subscription so that future updates are easier to manage for all clients. Love your work.

from acf.

Hi @gziolo

This has been fixed in ACF PRO 5.6.10. When you have a chance, can you please update and test it out? If the problem persists, please let me know and I'll continue to investigate.

from acf.

@elliotcondon, thanks for quick fix. I will let you know once it is confirmed by users who filed this issue 👍

from acf.

@elliotcondon

Hi, thank you for fixing that. But update introduced new bug:

This is how it looks with ACF Pro 5.6.10 deactivated:

And this is with ACF Pro 5.6.10 activated:

The hook name can only contain numbers, letters, dashes, periods and underscores.

from acf.

Has this been fixed yet? I'm currently having this issue still :/

from acf.

Hi @Rekenna

This has been fixed in the latest 5.7 build and will be available within 5.7-beta4 later this week!

from acf.

Awesome! Thanks for your hard work :D

from acf.