Nope, this was in response to the following threads:

While not glamorous threads, these threads are incredible important. I keep hoping for a better feature requests system, but maybe some day. In the mean time, these two threads are ones I constantly refer to, along with the changelog.

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, 11 months ago by Jason E. Reason: Clarification

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

Also, is there a way to better control the look and feel of the Search Results page itself? I would like to turn off the side bar for that, but am not sure where those settings re being pulled from.

Hi Guenni!

You are actually pretty close, I think. The first link I had showed a Featured image overlay on anything that was categorized/field value featured. I think your example does very much the same thing, but obviously not all listings would have that badge (which would be easy).

Does this help to explain?

Update: I think I figured it out. In the documentation, there is a css snippet for making the footer full width, but it does not really do much, unless it is a single-column footer, which most footers are not. So, I added div in the selector and it now performs as desired. Feel free to adjust the documentation to help others that might be facing similar issues with mobile footer display.

/* Full width footer columns */
@media only screen and (max-width: 767px) {
#footer .container div {
width: 100vw;
max-width: 100%!important;
} }

Thank you, Ismael. The last part was what I was looking for. It sounded like things were changing in the recent past as to how Enfold handled CPTs, so before digging into a potentially deep project, I wanted to make sure I was in line with the best practices for Enfold compatibility.

I had to do a bunch of css work to fix the issue.

I still would be very interested in seeing a method to accomplish this as a main menu, rather than as a shortcode attached subnavbar element. Can there be some consideration for making the main nav its own for formatting? Currently, it resides within the Header element, which means it affects the entire header along with the navbar. For those using navbars below the logo, it would be really useful to be able to style that element on its own.

Hope this helps!
-jason

Hi, Rikard!

I eventually find it, after searching and searching, but for someone that knows the Kriesi site, that may be ok, but for new users, which I think we all want more Enfold users, they’d have absolutely no idea where to look. We can do better than that. If we really want to kick things up a bit, here are some places that I think would really benefit both new users and seasoned ones.

Intro screen for those first installing Enfold. Include a welcome, links to Docs, Tutorials, Snippets, and Examples for those looking for a creative kick-start.

Add a Help tab to the Theme Options, with links to the various areas. Make it able to be disabled, for those with embedded solutions using Enfold, but on by default.

Support Navbar link should NOT go straight to the forums. It makes users feel like they always have to look through volumes of information to solve what might be a quick answer to a question. It also makes support staff the central focus, rather than giving people and opportunity to quickly find what might be their solution, or lead them in the right direction.

Support should be drop-down, with individual links to Documentation, Tutorials, Examples, Integrations, Latest Release (links to release notes), Forums, and direct link to Ask a Question.

Demos should link to page that displays Demo content, but also great examples of Enfold used in the wild. With themes like Elementor getting massive national press, the least we can do is showcase some of the best and most innovative Enfold-driven websites. Lastly, a link to submit your own site for showcasing. I know it is in the forums, but do you really want people to have to dig to showcase an Enfold site?

Let’s come up with a real and working solution for integrations. How may “Does Enfold work with…” questions do you get? There are a ton of us that regularly use sets of plugins that we know either work out-of-the-box or have created ways to integrate them. Let’s build a repository of those and spur on a new group of integrations. If we don’t call it out, how can we ever expect to make that “works with…” list longer? We want it so those products that we integrate look to promote Enfold as a great option for utilizing their solutions. We also need a way to suggest or request an integration.

Also, is there any way to funnel the other Kriesi-based theme users into the Enfold trunk and simplify the support, enhancement and growth of Enfold as a platform, rather than just a theme? Would it be worth considering offering a license of Enfold to any other Kriesi theme user to encourage switching to the Enfold platform? It may cost a few sales, but at the same time, it gets them into a highly versatile platform that keeps growing, and might just spur on their creative spirits to do new things with Enfold. Just a crazy thought.

I know I am asking for you all to add more work to your plates, but at the same time, I would be happy to help on some of it. We all want Enfold to continue to grow and flourish, but we have to also be willing to put effort into the Kriesi site to support those sales, support and promotional efforts. It also will help users in ways that will alleviate some service and support issues before they even get to the forums.

I guess the bottom line is let’s work together as a community to showcase Enfold, grow our audience, which drives sales, which drives the ability to do even greater things.

-jason