THX!!!!
everything works ( position, behavior when shrink,social button position)

for people who are loking for the same needs, finally i put:

#top #header .av-main-nav > li > a {
line-height: 140px !important;
}
#top #header.header-scrolled .av-main-nav > li > a {
line-height: 44px !important;
}
#header_main nav .social_bookmarks {
top: 80%!important;
}
#header.header-scrolled #header_main nav .social_bookmarks {
top: 50% !important;
}

Thx again

BR
Noelle

Also – while you are in there, check out the top left corner of the text block when you open it to look at the text / css……

I noticed this text overlaying each other AFTER I updated to the most recent version. Not really a big deal to me, just thought I’d let you know.

Screenshot:

Why do I need clickable columns? Many of my client designs call for clickable containers that do not have an image and many clients do not have the knowledge to write the html or edit it and rather use a page builder element. Other Enfold forum users have the same need.

Clickable columns work fine if I override columns.php in a child theme, but I don’t want to break a site if columns.php is updated on the parent side. By adding a new clickable columns tab, this way the only element that would break are clickable columns not every column in the entire site.

Here is the pastebin: https://pastebin.com/NPH0MEcM

However, I only changed the class name, $atts and this code:

// Linkable columns
				$link = $atts['link'];
				$linktarget = $atts['linktarget'];
				
				$blank = (strpos($linktarget, '_blank') !== false || $linktarget == 'yes') ? ' target="_blank" ' : "";
				$blank .= strpos($linktarget, 'nofollow') !== false ? ' rel="nofollow" ' : "";

				$link = aviaHelper::get_url($link);

				$tag = !empty($link) ? array("a href='{$link}' {$blank} ",'a') : array('div','div');
				
				$output  .= '<'.$tag[0].' class="flex_column '.$shortcodename.' '.$extraClass.' '.$first.' '.$meta['el_class'].' '.avia_sc_columns_linkable::$extraClass.' linkable-column" '.$outer_style.'>';
			
				//if the user uses the column shortcode without the layout builder make sure that paragraphs are applied to the text
				$content =  (empty($avia_config['conditionals']['is_builder_template'])) ? ShortcodeHelper::avia_apply_autop(ShortcodeHelper::avia_remove_autop($content)) : ShortcodeHelper::avia_remove_autop($content, true);				

				$output .= trim($content).'</'.$tag[1].'>';	

Thanks!

When I deleted the first tab (which only had 1 x 1/2 column), then the other two tabs worked. As soon as I recreated the first tab, with only one 1/2 column again, then the other two tabs stopped working again. I added a second column in the first tab with no content and the other two tabs started working again.

It almost looks as though the system that decides whether to attach a “first” indicator to the column short codes counts how many columns there are, including in previous tabs.

Is this a bug that will be fixed in a future update, or did I do something wrong when I set up the tab section?

Hi Victoria,

Thanks for your reply. I’m not sure why I have a copy of /js/avia.js in the child theme. It’s not something I normally do during development.

I’ve tried updating the file with the contents from /enfold/js/avia.js and the gallery is now working as expected.

I then removed this from the child theme thinking that if it was no longer present that it would default to the parent but it doesn’t. It leaves me with an area on the website where the gallery should be but no content and the sliders also stop working.

Can you advise?

Thanks.

This post has a Featured Image of the ‘normal’ size, 700px x 467px. It has this code

.big-preview img {
	width: auto;
}

in a child theme style.css to override the width: 100% in layout.css, for the FI to display at its ‘proper’ defined size. If you use Developer Tools to temporarily turn off this child declaration you will see the FI fill the whole of the outer entry-content-wrapper container (not what is required).

This other post has a FI of 467px x 467px. It is displaying at that ‘proper’ size – which is what I want – because of the child CSS override above. Again, turn this off temporarily and the 467px wide image fills the whole container.

So you can see that I have managed to override width:100% in layout.css.

Sometimes however an FI will be another smaller size so I need a solution that works for all FI image sizes i.e. stop the enlargement to fill the outer container, and my question is whether I have done it in the right way with width:auto or is another CSS statement a better / correct way e.g. inherit?

Great that works perfectly, when you increase the size of the icons they are too close together. Is there a way to space them out more. Also is there some code to resize the secondary menu text in the top bar?