Support

Account

Forum Replies Created

  • Just a friendly reminder that the ACF team has been successfully ignoring this bug for exactly 3 months.

  • For anyone waiting for solution like me, this is official reply from support:

    Unfortunately, we do not have an ETA on this, but the developers are working on it.

    In the meantime, the workaround, like copying the block out of the pattern editor, editing it on a page, then pasting it back, is currently the best temporary solution.
    We’ll keep you updated as soon as we have more information or a patch available.

    Make up your own mind, but this bug has been known for almost 4 months now. For example, HPOS was introduced in 2023, and ACF added support in 2025. So I guess we can expect a fix in about two years…

  • Honestly, it feels like ACF development has completely stalled. You’ve been working on micro features for months, but a major bug like this still isn’t fixed three months after being reported. It’s a shame – even a bit sad – that we’re paying for a yearly subscription when development feels dead and important bugs like this are just being patched with workarounds instead of real fixes.

  • The fix will be ready this or next year? Because it is like 2+ months when the bug was discovered.

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