Broken styles in the backend
-
With the latest update of ACF (6.5.0), the styles in the backend are messed up. When I deactivate ACF Extended, it works normally again. Will there be an update soon?
Best regards
-
Hello,
Thanks for the feedback!
The latest ACF Extended 0.9.1.1 adds compatibility with ACF 6.5+. Please update the plugin to fix the issue.
Thanks!
Regards.
Hello Konrad,
I am waiting for over a month for your reply to my ticket (#ZOQM7).
I am a pro user and pay for a license each year.
In the changelog I can see the plugin has had only 1 minor update in 2025 so far.
Is this plugin becoming abandoned?
KeesKonrad responded to my reply today and he confirmed to me that ACF extended is not abandonware.
Hello,
The latest update implemented compatibility with the recent ACF 6.5+ version, and was released 2 days after the ACF patch. That’s not exactly a sign of being abandoned.
Regarding your ticket, I understand the answer time can be frustrating. It is explained by two factors:
During the holiday season, I take some rest, since I’m constantly working on this project the rest of the year. As a person, I have to maintain my sanity to keep working on this plugin for the years to come, and that’s one way I found to do it.
During that time, I keep monitoring tickets in the background, in case of breaking bugs. For your ticket it wasn’t the case, since it was a visual display bug and it couldn’t be reproduced on a blank WP install. So it was most likely because of some custom code. This is why it was considered as a low priority ticket for that period.
I should have probably give a quicker answer, like: “Your issue can’t be reproduced”. But I’m not a huge fan of that kind of responses, as they feel automated. I prefer manually crafted answers, with video demo showing the use case actually working as a proof, and interact with users as a human-being.
But I can see why users would prefer an automated answer rather than nothing. So this is something I should work on for the next holiday season.
Regarding the updates pace. You asked me the same question 3 years ago, when the development was more quiet. In my opinion, the development cycle of such project has different periods. There is a time for quick iterations and joy, and a time for silent boring ground work.
I can understand the passion, but it’s not like if the plugin was broken. Considering the large user base, and how vital this plugin is for developers, there would be constant spam of tickets if that was the case. Even users who use pirated & modified version of the plugin published reports here after the release of ACF 6.5.
As a final note, I would like to add something that I already mentioned in your ticket; I have a lot of things being worked on in the backlog, and they will be only released when ready. I refuse to rush releases for the sake of it.
If a user is not happy with the pace of development, he is free to stop his license/subscription. I’ll not compromise the software stability to chase new updates and stats growth. This plugin does zero marketing for a reason. That’s not my mindset.
Thanks.
Regards.
Hello Konrad,
Once again, thanks for your extended reply.
I really get your point of view considering automated (useless) answers. I do appreciate your thorough processing of my ticket. But, like you say, a quick ‘I will look into this on a later moment’ is better than no reaction at all.
Since your plugin is a vital part of a lot of websites, my concern was not especially about the issue itself, but the fact I could not get in touch with anyone for over a month.
I’m really glad to hear that you are actively working on the plugin, keep up the great work!
KeesHey,
I’ll be working on finding a way to make answers smoother for the next year holiday season.
Thank you for your understanding and support!
Cheers!
The topic ‘Broken styles in the backend’ is closed to new replies.