Hey Advantage09,

Thank you for the inquiry.

1.) The contact form has an option to display missing or invalid fields. Please set the Content > Frontend > Display Fields With Error settings to “yes”.

2.) Adding the following script in the functions.php might help.

function ava_custom_script() { 
	?>
	<script>
		(function($) {
			$(document).ready(function() {
				$('#top #avia-menu').attr('role', 'menubar');
			});	
		}(jQuery)); 
	</script>
	<?php
}
add_action('wp_footer', 'ava_custom_script');

Best regards,
Ismael

Hey flylanddesigns,

Thank you for the inquiry.

Unfortunately, adding this feature to the Masonry element would require significant modifications to the theme. You may have noticed that the AJAX Portfolio preview includes specific elements designed exclusively for the “portfolio” post type, which can be added using the dedicated Ajax Portfolio Preview Settings. These customization options and content fields are not available for other post types, and the Portfolio Grid element is the only component capable of displaying these elements. Additionally, the functionality provided by the AJAX preview script is specifically designed for the Portfolio Grid element and cannot be utilized with the Masonry element without substantial customization to the templates.

Best regards,
Ismael

Hi,
Thank you for the link to your site and the screenshots, the large gap under the slider was caused by the JetPack image lazyload option, I disabled it for you and cleared your Autoptimize cache and now it is solved;

For the footer of your SBC page I added this css to your Quick CSS, clear your browser cache and check.

@media only screen and (max-width: 767px){
.responsive #top #footer .flex_column {
    margin: 0;
    margin-bottom: 20px;
    width: 100%;
}
}

It looks like the page structure is not correct on that page but I’m not sure the cause for it, if this css works and you don’t see any other issues then fine, otherwise try disabling all of your plugins and check again, if this doesn’t correct please create a staging site so we can investigate further. Is this page a custom post type? I didn’t find it in with your pages in the backend. Is it using the Advanced Custom Fields plugin? Is this the only page with this issue?

Best regards,
Mike

Hi,
Thanks for posting your code, but I didn’t find anything in it for custom fields, please link to the thread where you found the customization.

// https://pastebin.com/7Kn8R4ZR
Best regards,
Mike

Hey jordan204,
I think you could do it with Pods – Custom Content Types and Fields or Advanced Custom Fields (ACF), and search YouTube for tutorials on how to set it up. I don’t use either, but I feel that you will have a steep learning curve and unless to are doing hundreds of them doing it manually would be faster. If you are going to do hundreds of them I would hire a freelancer on Upwork to set it up for you, it would be faster and reasonably priced.

Best regards,
Mike

Hi Jason,

Thank you for coming back.

I agree that this is getting an important feature and I have put this on top of my to do list with a high priority. Though it has heavy impact on the existing code and it will take some time.

I will try to have a first implementation for 5.7 (starting with standard WP custom fields and then ACF elements step by step).

I hope this gives you a roadmap for near future and allows you to stay with Enfold.

Best regards,
Günter

Hi,

I’ve been tagged on this topic recently. I’ve not been using ACF up to now but I installed the free plugin to get an idea what it does. And I also had a look how Elementor handles it (https://elementor.com/help/elementor-acf/).

The problem is not to display the custom fields (which is actually only post meta data to read) but the overall integration of custom post types, taxonomies and how to display it.

It is possible to use our Advanced Layout Builder for custom post type “posts” (as we do already for the portfolio) but this is only for one post and (currently) not reuseable.

What you are looking for is to design a template (with the ability to show custom meta data) which is reused for other posts. And this for single post and multiple posts (blog).

This at the moment is only possible by creating or editing the underlying php template files using the default WP routing.

I will add this as a feature request to our dev repo and will keep an eye on it.

Best regards,
Günter

Hey fimondi,

Thank you for the inquiry.

You can use the SearchWP plugin to make a specific custom field searchable and include them in the search index. The preview text of the portfolio item is a custom field called “_preview_text”. Please check the documentation below for more info on how to include a custom field as one of the attributes in the search engine.

// https://searchwp.com/how-to-add-wordpress-custom-fields-search/

Best regards,
Ismael

Hi,
When I check your child theme I see that you had an old header.php but no footer.php these to files went together so I would expect an error using the old header.php and a new footer.php. But your header.php is disabled right now and you are seeing the error so it doesn’t point to that as the error.
I see you are using Advanced Custom Fields, is this what is adding the recipes?
I mean that your recipe post type only shows shortcodes so are these shortcodes injected into a custom post loop to display?
If so this might be added to page as a footer because the code is looking for a div like “content” or such.
This would explain why when you use no page as a footer and just the normal footer with widgets the error doesn’t occur.

Best regards,
Mike

Hi,
Thanks for the login, so your header.php is adding the Google Tag Manager code and some ontraport scripts, this can be added to the child theme functions.php and is not a big deal. We don’t recommend using a header.php or footer.php in your child theme or you will keep having to update these files in most updates.
Your footer seems to be adding some call-to-action scripts, so this can also be moved to the functions.php
Your custom single.php & related-posts.php files have minor edits and I have made updated versions for these for v5.2.1
But your loop-index.php has major customizations and the v5.2.1 version is quite different so you are going to need to customize a new v5.2.1 loop-index.php for when you update. If you had hired someone to do this before please ask them to help you again because I don’t understand the customization and it is beyond what I can help you with.
Your custom contentslider.php was only edited to show the arrow and dot navigation at the same time so it should be easy to update.
If the theme had not changed so much from 4.5.7 to 5.2.1 then you could have just used your custom files and updated with no issues, but back around v5 the theme added more features and changed many core files like the loop-index.php
I found that your Advanced Custom Fields plugin adds custom classes to your pages and your css is based on this, so this is why when we updated the elements on your homepage was so different because we had disabled all of your plugins so the Advanced Custom Fields plugin was not added the custom classes and your css was not working.
So at least we figured that out.
So we could probably update with the new files I made for you and most of your pages would be fine, but not your loop-index.php, so I imagine that you are going to want to wait to update until you get a new custom loop-index.php created.

Best regards,
Mike

Hi,
ACF is your plugin Advanced Custom Fields
I don’t see how the Header.php and Footer.php would change the layout it is not expected.
How about we try again, please restore the staging site back to the old version that is correct, and then I will investigate it first and then try to update again and see what happens.
Sorry for the back and forth, but I have not seen this kind of error before.

Best regards,
Mike

Hi,

The header_block class is not present on the page you linked to, please check. Also, you only need to add the class in the Custom CSS class field, not in all the fields.

Best regards,
Rikard

Hi,

Sorry for the delay. We are still not sure what is causing the issue, but it seems to only happen after the toggle_shipping function in the plugins\woocommerce\assets\js\frontend\cart.js file ran, which affects the quantity fields for some reason. Adding this script in the functions.php file might help to reactivate the quantity buttons after the shipping state changed.

function av_custom_inline_script() {
	wp_add_inline_script( 'jquery', 
		"
		(function($) {
			$( document.body ).on( 'country_to_state_changed', function() { 
				avia_apply_quant_btn();
			} );
		})(jQuery);
		"
	);
     }
add_action( 'wp_enqueue_scripts', 'av_custom_inline_script' );

Best regards,
Ismael

Hi,
Thanks for the link to your page, the top element is the special heading element and in the title field you have added an emoji, these title fields do not support HTML or HTML Entities
So each this you save the page they will be lost, if you open the element you will see it doesn’t show:

if you add HTML you will see the warning message, this is also for emoji’s I will recommend to the Dev Team to add the warning for emoji’s

To solve this you can add the emojis via CSS with the :before / :after selector see the example in this article.
For example:

.av-special-heading-tag::after {
    content: "💸";
    display: inline !important;
    border: none !important;
    box-shadow: none !important;
    height: 1em !important;
    width: 1em !important;
    margin: 0 0.07em !important;
    vertical-align: -0.1em !important;
    background: none !important;
    padding: 0 !important;
}

I would recommend adding a custom class the special headings that you want this to show on so it doesn’t show on all special headings, unless that is what you want.
I created a test page for you linked below with a special heading element and the custom class flying-money-emoji

Then I added this CSS in a code block on the page:

.flying-money-emoji .av-special-heading-tag::after {
    content: "💸";
    display: inline !important;
    border: none !important;
    box-shadow: none !important;
    height: 1em !important;
    width: 1em !important;
    margin: 0 0.07em !important;
    vertical-align: -0.1em !important;
    background: none !important;
    padding: 0 !important;
}

This is the result:

Please give this a try.

Best regards,
Mike