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?

Hi Ismael,

it does look good and works, so I decided to stop calling it a workaround and think of it as a solution now ;-) So I am fine, thanks a lot.

For all others: As written above I wanted to have a submenu below the slider on this site: http://o2bln.de/
Instead of some complicated fiddling with the header height, the top-margin of the submenu when scrolled to top and so on I simply set the submenu to 72px height and moved the whole slider container up by 72px:

#top .av-submenu-container { height: 72px; } 
#fullscreen_slider_0  { margin-top: -72px; }

The slider is cut off those 72px at the top, but I can live with that.

Cheers,

Michael

Hi again,

I had another look myself at how the sticky fullwidth submenu script works, but as a non-programmer I couldn’t figure it out how to change the top-margin the script gives the container when scrolled up :-(

So any input is more then welcome :)

Cheers,

Michael

Solved it myself. To remove MegaMenu, simply remove this line in functions.php (Enfold, not Child):

/*
 * add support for responsive mega menus
 */
add_theme_support('avia_mega_menu');

Now the plugin works just fine ;-)

Ismael, I get your support policy and everything. I know there’s got ot be a limit of what the support team can provide. But as soon as the theme itself changes or hooks into core wordpress functionality it often is simply not enough to “direct questions to the plugin author” as he/she has no way of knowing what your theme does.
I know other theme author that have some kind of “premium forum”, where you pay a monthly fee for being able to ask the more complicated questions/requests. Still no big customisations, mind you, simply the questions that tend to be rejected, because they are out of the scope of free support.
I for one would gladly pay a fee for something like this here too, as I tend to use only very few themes but am mostly relying on the support by teams like yours. Hiring a freelancer (actually I am one, but with a completely different focus/skill set) is often uneconomical, as they tend to have no idea about this or that theme and need an hour to find their way around the code, where the theme supporters need 5 minutes. So I’d rather pay you 10 bucks a month for 5 minutes than somebody else 50 bucks for one hour ;-)
Just an idea…..

Cheers

Michael

Found the problem, it was my Firefox. Tested in a VM and it works just fine. Thanks Yigit for your excellent help and your patience.

tbh, I see no difference to before :-(

Almost, we’re getting there. Yeah… ;-)

To specify: I am talking about reducing the expanded height, not the smaller height when the page is srolled down. A link might help ;-)
http://witteconsult.de/