Hi Ismael,

Sorry, I forgot to disable 2FA temporarily, but it is now. To answer your questions, yes, I did have some animations in one of the reported fields but I turned it off after reading other threads on this topic. However, this has not improved my score. As for your custom script question, the answer there is no.

Again any help or insight you can provide is greatly appreciated.

-James

Hi Nikko,

Thank you for getting back to me.

All of my images are 1000 x 1000px, for the first item I created an image 2000 x 2000px (2 times bigger) which didn’t change in height or width. I figured out that creating an image at 16:9 will take up 2 column spaces wide but obviously not in height and 9:16 will take up 2 columns spaces in height but not in width. Still don’t have a solution that takes up 2 column spaces both in height and width.

I think this approach is too hit-and-miss for what I am trying to achieve, as well as the lightbox image then presenting the image at that cropped size, where it would be better if it displayed the full uncropped image.

What other options do I have? I don’t want to add a third-party plugin.

Can I modify the masonry_gallery.php in a way where I can specify my own HTML? that way I can create the layout without modifying the size of the images.

<div class="grid">
  <div class="grid-item">...</div>
  <div class="grid-item grid-item--width2">...</div>
  <div class="grid-item">...</div>
  ...
</div>

Or modifying that function you shared https://kriesi.at/support/topic/change-image-size-on-masonry-gallery/ here to achieve my layout?

My only other thought to achieve this is to create a custom element in my shortcodes folder and have the user input images in Advanced Custom Fields.

Your help would be greatly appreciated.

Thanks in advance
Sean

Hi Ismael

Thank you for your response, that’s my issue I have triple checked and can’t see where the custom tags go “Toggle Sorting Tags” field doesn’t exist in the accordion section?

Could you add a couple of dummy text fields so I can visually see what I am missing?

Andrew

Let me try a deeper explanation of #1 above.

I have a single product in a store.
I have added the PayPal standard checkout.
The checkbox for accepting the site’s Terms & Conditions is required.
The “container” at the bottom of the checkout page contains the PayPal buttons and the required T&C checkbox.
The required T&C checkbox is BELOW the PayPal buttons.
Customers can not see the checkbox.
Customers attempt to pay via PayPal, but of course it will not process.

SOLUTION NEEDED: HOW DO I MOVE THE CHECKBOX ABOVE THE PAYPAL BUTTONS? SAME AREA, DIFFERENT ORDER.
Checkbox first. PayPal buttons below.

NOTE: I have tried several checkout plugins for managing checkout fields. None so far have options for the payment area.

There is also some hint from the quform support:

“Unfortunately the Enfold theme uses very strong CSS selectors (prefixed with #top) for fields which overrides the base Quform field CSS.
It’s possible to override it though with custom CSS. Something like the code below should work to set the border/background of Text, Email and Textarea fields. You can add it to Forms – Settings – Custom CSS & JS – Custom CSS (All devices).”

#top .quform .quform-element-text input[type="text"],
#top .quform .quform-element-email input[type="email"],
#top .quform .quform-element-textarea textarea {
    border: 1px solid #ccc;
    background-color: #fff;
    color: #555;
}
#top .quform .quform-element-text input[type="text"]:focus,
#top .quform .quform-element-email input[type="email"]:focus,
#top .quform .quform-element-textarea textarea:focus{
    border-color: #66afe9;
}

Adjust the colors to suit.”

“Enfold theme uses very strong CSS selectors (prefixed with #top) for fields which overrides the base Quform field CSS”

That sound incompatible to me, or do you have some trick to make quform work ?
Kind Regards
Jens

Hi Mike,

No, I don’t think it’s a matter of adding the option (although it’s always a good thing to do these days) Personally, I would have them select a pronoun or Mr/Ms/Mrs/etc for a more business like approach – but this was the client’s decision. (In this case)

This is that you have to explain what the field is about. Having something to select M or F, does not explain what they stand for. You need a Field Name.

Imagine this example. You offer invitations and give them a choice of ink color and paper color. So, you have two fields where you pick one option. If you do not show the title, how do you know what the customer picked? The paper or the ink?😳

You need to display the title as either all the titles are inlined or they are not. Listening to the people who requested removing it was a mistake. These are not marketing/business/conversion people – in my humble opinion. I would bring this part back. 😉

Warmly,

Havi <3

I’ve checked Safari as opposed to chrome and it’s still not displaying it on pages. Not sure how to attach a screenshot.

On the posts it’s there – the Layout Tab is on right hand side under categories and tabs. But on pages I’m just seeing Publish, Page Attributes and Featured Image. It’s also not underneath but there is a custom fields section which seems to be new and relate to layout but not sure what it’s supposed to do.

Hi, again
While I was waiting for your answer, I tried to investigate a bit more to find the solution to my “advanced fieds not displaying” problem.
I found out that to display these advanced custom fields, I needed to insert more code in the single.php file. This is the code:
<div class=”infos-service”>

• Collectivités : <?php the_field(‘collectivites’); ?>
• Adresse : <?php the_field(‘adresse’); ?>
• Téléphone : <?php the_field(‘telephone’); ?>
• Courriel : <?php the_field(‘courriel’); ?>
• Services et prestations : <?php the_field(‘services-et-prestations’); ?>
• Missions autres que documentaires : <?php the_field(missions-autres-que-documentaires’); ?>
• Rattachement hiérarchique : <?php the_field(‘rattachement-hierarchique’); ?>
• Nombre de personnes dans le service : <?php the_field(‘nombre-de-personnes-dans-le-service’); ?>
• Logiciel documentaire utilisé : <?php the_field(‘logiciel-documentaire-utilise’); ?>

</div>

I now have 2 questions:
– I’m supposed to insert these lines in the single.php file but there is no such file in the Enfold Child Theme larger file. Should I insert these code lines in the regular Enfold file?
– if so, my documentation (https://kinsta.com/blog/advanced-custom-fields/#display) tells me I should paste below the entry-content section… which does not exist in the Enfold single.php file. I’m pasting the whole file below, could you tell me where I need to paste the new code lines? Thanks in advance!

<?php
if( ! defined( ‘ABSPATH’ ) ) { die(); }

global $avia_config;

/*
* get_header is a basic wordpress function, used to retrieve the header.php file in your theme directory.
*/
get_header();

$title = __(‘Blog – Latest News’, ‘avia_framework’); //default blog title
$t_link = home_url(‘/’);
$t_sub = ”;

if( avia_get_option( ‘frontpage’ ) && $new = avia_get_option( ‘blogpage’ ) )
{
$title = get_the_title( $new ); //if the blog is attached to a page use this title
$t_link = get_permalink( $new );
$t_sub = avia_post_meta( $new, ‘subttenitle’ );
}

if( get_post_meta( get_the_ID(), ‘header’, true ) != ‘no’ )
{
echo avia_title( array( ‘heading’ => ‘strong’, ‘title’ => $title, ‘link’ => $t_link, ‘subtitle’ => $t_sub ) );
}

do_action( ‘ava_after_main_title’ );

?>

<div class=’container_wrap container_wrap_first main_color <?php avia_layout_class( ‘main’ ); ?>’>

<div class=’container template-blog template-single-blog ‘>

<main class=’content units <?php avia_layout_class( ‘content’ ); ?> <?php echo avia_blog_class_string(); ?>’ <?php avia_markup_helper(array(‘context’ => ‘content’,’post_type’=>’post’));?>>

<?php
/* Run the loop to output the posts.
* If you want to overload this in a child theme then include a file
* called loop-index.php and that will be used instead.
*
*/
get_template_part( ‘includes/loop’, ‘index’ );

$blog_disabled = ( avia_get_option(‘disable_blog’) == ‘disable_blog’ ) ? true : false;

if( ! $blog_disabled )
{
//show related posts based on tags if there are any
get_template_part( ‘includes/related-posts’ );

//wordpress function that loads the comments template “comments.php”
comments_template();
}
?>

<!–end content–>
</main>

<?php
$avia_config[‘currently_viewing’] = ‘blog’;
//get the sidebar
get_sidebar();

?>

</div><!–end container–>

</div><!– close default .container_wrap element –>

<?php
get_footer();

Hi, Ismael
Thanks for your anwsers, things are slightly improving… but are still not fully functionnal.

I installed the child theme and inserted the necessary code in the functions.php file. The custom post type can be displayed but only with its title and icon image. The advanced custom fields do not display at all… What is missing?

Thanks in advance for your answer… I’m sure we are almost there!
Take care

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