Hi Ismael,

I did modify it and I also testet without it, the problem is the same and seems not to be header.php related (I just added the top header div)

Cheers,
Michael

Hi Rikard,

sure thing, I made you Super-Admin (Multisite).

Thanks
Michael

Hi Victoria,

I found it’s even easier to use the selector Firsh recommended, i.e. “.justified-image-grid a”
and place that under “exclude” in the lightbox activation script in js/avia.js

(function($)
	{
		$.fn.avia_activate_lightbox = function(variables)
		{
			
			var defaults = {
				groups			:	['.avia-slideshow', '.avia-gallery', '.av-instagram-pics', '.portfolio-preview-image', '.portfolio-preview-content', '.isotope', '.post-entry', '.sidebar', '#main', '.main_menu'], 
				autolinkElements:   'a.lightbox, a[rel^="prettyPhoto"], a[rel^="lightbox"], a[href$=jpg], a[href$=png], a[href$=gif], a[href$=jpeg], a[href*=".jpg?"], a[href*=".png?"], a[href*=".gif?"], a[href*=".jpeg?"], a[href$=".mov"] , a[href$=".swf"] , a:regex(href, .vimeo\.com/[0-9]) , a[href*="youtube.com/watch"] , a[href*="screenr.com"], a[href*="iframe=true"]',
				videoElements	: 	'a[href$=".mov"] , a[href$=".swf"] , a:regex(href, .vimeo\.com/[0-9]) , a[href*="youtube.com/watch"] , a[href*="screenr.com"], a[href*="iframe=true"]',
				exclude			:	'.noLightbox, .noLightbox a, .fakeLightbox, .lightbox-added, a[href*="dropbox.com"], .justified-image-grid a',
			},

Is there a way now to do this permanently, i.e. via function php so it survives theme updates?

Hi Ismael,
seems to work fine, thank you so much!
Cheers,
Michael

Thanks Yigit!

Hi Yigit, thanks again. But honestly, whatever I’ll do via CSS can only gloss over the fact that these templates are not fully responsive with a true content choreograpy. So I’ll have to come up with a replacement anyway :-(

Hi Andy, achieve what, what customization? I am talking about a snippet postet by Ismael, not a customization I want. Ismael’s snippet doesn’t seem to be working correctly, so maybe we should ask him?

Basilis,

I am calling bullshit on that one now. It took you a mere 2 minutes to answer 3 of my tickets, so you didn’t even read them. Your answer to this ticket makes it very clear, that you have been too lazy to read and understand the question. Because that’s what it was, a question and not a request. I don’t want any customisation here, I am pointing to an irregularity in behaviour. And you should be interested in that, as it is your job to find such irregularities, confirm them and report them to your boss @Kriesi, if they turn out to be of interest to others too.

But you didn’t even get that. So let me put my question in very simple words:

When you search for something, the search widget displays realtime results while you are typing. It displays some results in the order result A, result B, result C. Then you hit enter. The Enfold search result page opens. You see the results ain a different order, e.g. result A, result C, result B. Why ist that.

This is not correct. Call it a bug, call it whatever you like. But I haven’t asked for customisation , so don’t call it that to get it out of the way. As I have writtten, it a rather small issue. But if you don’t even bother to understand it in oder to weigh it’s importance and report it or tell me that it’s to small of an issue to be reported, then your are wasting your time and mine here.

Ok, I understand

Oh, before you ask regarding issue 1. – I have moved the sidebar to the right, but I did it according to the available instructions and it should be correct and should work.

//BEGIN PRODUCT WIDGET AREA IN THE RIGHT SIDEBAR
// adjust settings on init
add_action('init','ava534345953_init', 50);
function ava534345953_init() {
	add_action( 'woocommerce_after_single_product_summary', 'avia_add_sidebar', 25);
}

function avia_close_image_div() {
	echo "</div>";
}

function avia_add_sidebar() {
	if(is_product()) {
	$avia_config['currently_viewing'] = "shop_single";
	get_sidebar();
	}
}
//END PRODUCT WIDGET AREA IN THE RIGHT SIDEBAR

Hi Josue,

I’ve been fiddling a little with the javascript, but since I am no java programmer, I can only try minor things and all those didn’t have the desired effect (the image was scaled correctly, but wasn’t positioned at the top anymore and so on).

So I’ll have to wait if you guys or Kriesi comes up with anything, otherwise I’ll have to make use of some plugin do do what we need.

I am having the same issue at another customer’s website, there we make use of the category headers in the shop. http://verlag-pfeil.de/fachrichtung/palaeontologie/

We have stopped using other theme mostly because Enfold is the best, most complete and very well coded. But the parallax is not on par with others. For example they do it right: http://bridge9.qodeinteractive.com/about-us/ (and they have one of the very very few themes, that come close to Enfold – but they all use VC and I try to avoid it)

Hi Ismael,

The height is calculated based on the browser height multiplied by avia-parallax-ratio plus the parent section height.

I know, that’s exactly what I am saying is wrong resp. not very elegant. It would be better to ONLY use the parent section height multiplied by avia-parallax-ratio. Since we have no influence on the latter and cannot make that negative, the image size needed can never be higher than the parent section height and that is either fixed or a percentage (25%,50%,75%,100%) of the browser height. So if Kriesi would change the script to only use the parent section height for calculation, the whole thing would make much more sense.

I am not against the usage of “cover” there, it make most sense most of the time, but without a proper height calculation the positioning of the image is almost useless.

But apart from that, I still would prefer to be able to choose cover, contain or 100% – and surely will have to live with the results ;-)

This is only set if you select the “Stretch to Fit” option.

Not true, the avia-full-stretch class is always applied to any parallax image, no matter what you set in the options (e.g. see here http://dasschloss.info/ihr-event-im-schloss/). So it is a bug, right?