Update on ACF support

I am so incredibly frustrated with trying to get CPT and ACF to work within Enfold.

All I wanted was simple Colors CPT, with a field group from ACF to display within a normal page as a grid of colors, and one the single cpt post as the detail record.

I have spent nearly two days trying to figure out how to get anything more than the Colors CPT to show. Looking through the few forums entries referencing CPTUI and ACF has yielded me pulling my hair out.

Why does it have to be this $%^&*( complicated?
Displaying Meta content should NOT be this hard.

I have messed with the child theme (Spark) functions, tried more shortcake combinations than lines of CSS, and rebuilt things more times than I care to admit.

I try not to bug anyone here until I have exhausted every other option, but really need some help to get this working.

Hi, Rikard!

I think the biggest challenge for us is the inability to easily add custom content without resorting to digging in templates. My hope was that Avia could use the normal post type taxonomy selector, and then it would pull up a list of the fields available under that taxonomy. To me, it feels like Avia is so close to solving this, but the one thing missing is the bridge between taxonomies and ACF data. I am probably way over-simplifying things, but I have found in the past that sometimes the answer is right in front of us.

That said, with the constant need for custom content and content types, was the intended technique always to hand-code templates for CPTs? There are several good and established options out there (CPTUI, ACF, Pods, etc.), with a ton more coming. I guess what I am asking is instead of waiting for our theme competition to seize on it, can we find a way to lead the charge with a solution that is equally as powerful as Enfold?

If it is a matter of time or cost, let developers like us find a solution for that. I would have no problem paying more to have a more enhanced feature set, and I have said that many times in the past. We need tools to continue to promote Enfold as the best solution, especially with WordPress trying to eat everyone’s lunch these days. I don’t want to be stuck with only Automattic solutions, and the idea of Elementor and its bloat scares me almost equally.

If you build a solution for CPTs and Custom Fields, or even a solution that ties in with them, we will have no problem with additional licenses to support those efforts. It would open tons of opportunities to push Enfold way beyond the scope it was designed for.

Additionally, we would have no problem paying for a Pro version of Enfold. In fact, we would welcome it with open arms, as it would be a way to contribute to building out Enfold with more resources, rather than just the recurring support residuals. Let us know what it would take.

-jason

Can we get an update to this? We are at a crossroads where we need to determine whether Enfold still works for us. I love Enfold and promote it every place I can, but websites are not just posts, pages and portfolios anymore. Websites need to be more, and while adding animation is cool and glitzy, it does not account for the need for more solid data-handling capabilities that most other major themes have baked in at this point. Enfold led the way with one of the best implementations for showing taxonomies, but that was over a half decade ago.

Thank you, Günter, for the response and more clarification of the status of this within the Enfold platform.

My trouble with this, is that it feels like just another message that will allow the can to be kicked down the road for another indeterminate point of time. Many of us have been asking for field support for years, and we continue to be told that it will recommended and for us to be patient. Rikard acknowledged this back in October, as have others over the years.

Günter, we need this.
Yes, I am making this statement more than just a request.

We have been asking, begging, pleading for support, so that we can continue to use a tool that is capable for current needs, when the clientele come to us and ask for functionality they can get in other tools. We have found every possible way to work around it, but are running out of reasons (and at this point, excuses) that the centerpiece of our toolset, Enfold, still does not even have a plan to integrate, despite continuing to tell us it will be a consideration.

We have worked with, promoted, developed, and championed Enfold since nearly the beginning of it. We do more than just purchase Enfold. We are coming to you now, begging for you to put more than just thought into this. We are asking, so that we may remain using it.

We don’t want to use Gutenberg. We don’t want to use Elementor. We don’t want to use Avada. We want to see Enfold do what we know it can do, and do it better than the others, just like it used to. Fields integration may not be glamorous like display functionalities, but it will lead to entirely new ways we can do incredible things with Enfold, and that results in new audiences, who also grow the capabilities of the Enfold platform.

We don’t care if you have to charge more for it. We just can’t keep waiting for someone to finally realize its importance and make it real.

-jason

• This reply was modified 1 year, 7 months ago by Jason E. Reason: Clarification

Thank you, Günter!

This is what we need, and it will benefit a lot of other Enfold proponents, too.

We eagerly look forward to a whole new chapter unfolding with the new functionality!

Hi team Kriesi,

I hate to continue to be a persistent pest, but I continue to be asked about it and don’t have any answer to give anyone. Any timeline yet? With that functionality being actively advertised, used and showcased on many other themes/builders/frameworks, it is really hard to not be looking to other frameworks to achieve this functionality.
-jason

Good day, Günter!

I just wanted to check in and see how progress was going. Any updates?

-jason

It is going to be worth it and probably the best thing to happen to Enfold since it came onto the market! Really, really excited to unlock a whole new way of managing and displaying content in a more meaningful, sustainable and organized way!

Thank you Team Kriesi for finally making this possible! It has been a long time, but think this will unlock a sorts of new use cases for Enfold.

-jason