Lass uns mal gerade deutsch hier miteinander reden.

In dem Beispiel oben (nicht Enfold) ist es aber wohl schon so wie jetzt bei mir im Beispiel.

Wie gesagt die Sache wird einfacher, wenn man die footer.php dahingehend bearbeitet, dass die interessierenden Container ( in deinem Fall nun beide) nicht mehr in Main liegen. Die bearbeitete footer.php landet dann halt in child-theme folder.

Das ist der momentane Code (wobei ich wirklich kein Profi bin, was die php und jquery Sachen betrifft – ich denke da ließe sich einiges abändern):

add_action('wp_footer', 'ava_custom_script');
function ava_custom_script(){
?>
<script type="text/javascript">
(function($) {
    $(document).ready(function(){
        $(document).scroll(function(){

		    var socketh = $('#socket').outerHeight(),
			footerh = $('#footer').outerHeight(),
			spacerh = $('#socket').outerHeight() + $('#footer').outerHeight();

                    if( $(window).scrollTop() >= $(document).height() - $(window).height() - socketh )
                    {   
                        $('#socket').css('position', 'fixed' );
			$('#main').css('padding-bottom', socketh );
                    }
                    else {
                        $('#socket').css('position', 'relative' );
			$('#main').css('padding-bottom', 0 );
                    }
        });
    });
})(jQuery);
</script>
<?php
}

weiß nicht ob ich die document ready funktion wirklich brauche. Die scroll funktion gibt mir zurück, ob ich den Bottom erreicht habe.
Wenn das so ist wechsel ich ein paar css Anweisungen.

Ich glaube ich muss mich jetzt endlich mal in jquery einarbeiten – scheint ja viele möglich zu sein.
Ich versuche mal die Seite oben umzustricken.

PS : die outerHeight nahm ich damit ich margins und borders gleich mitberücksichtige.

• This reply was modified 8 years, 5 months ago by Guenni007.

i’m not shure if this is what you try to get:

http://webers-testseite.de/elegant/

i don’t like the way it removes on scrolling back it would be nice to have here a animation of footer gone.

your idea to make it before li is good because otherwise on hovering the separtator will do the same thin as the link itself.

The only thing is positioning
But please overwrite your input on that

The first rule is to have no sign in front of first list point (:first-child is what it says the first li after ul)
the li.menu-item-top-level is to prevent that submenu list points will have a sign in front of their links.

.av-main-nav li.menu-item-top-level:first-child::before {
    content: "";
}

.av-main-nav li.menu-item-top-level::before {
    content: "/";
    font-size: 30px;
    font-weight: 400;
    position: absolute;
    top: 50%;
    transform: translateY(-50%);
}

sorry – i can not help you now – my family wants to eat something with me :wink
an no – that does not help anyway. – and i’m a participant as you are. so for now its enough – you got your default mode back.

PS it will be heavy to realise because you got a lot of links in sublevel they have a top-level link too.
Contact f.e. is sometimes the support on sublevel etc.

• This reply was modified 8 years, 5 months ago by Guenni007.

sorry : can you please erase first code completely and then i will have a look again.

it is just the problem to stay in first-level rules and not to influence submenu aswell.

But – I think this is only a nice feature for screens with more than 768px – so pack it into a media querry
not enough place for content with a fixed footer. Maybe set the footer to display: none

and perhaps we should take instead of .height( ) the .outerHeight( )

see Result here: Link

btw: the footer background-color is a gradient – just a test – nothing i will realy work with.
And diagonal backgrounds are just to see what happens realy ( landing page )

• This reply was modified 8 years, 5 months ago by Guenni007.

Well i guess you are not familiar with css coding?

<center><font size=”6px” color=”black”>Get this <font color=”red”>Free CD</font> that will give you <br><br>
a step-by-step proven process to <br><br>
hire winners instead of wimps <br>

<p style="text-align: center; font-size:6px; color:#000">Get this<span style="color:red"> Free CD</span> that will give your<br/><br/>
a step-by-step proven process to <br/><br/>
hire winners instead of wimps</p>

Edit : sorry the word “hire” seems to be automatically linked to a page here on board

you can take for p other tags like div or span

btw : you realy want to display the font-size 6px ?

• This reply was modified 8 years, 5 months ago by Guenni007.

on dashboard / appearance / menus – on top right of this window there is “Screen Options” push that little button.

Now you can choose what the menu options dialog should look like
under the “Show advanced menu properties” there are some interesting things f.e. you can give each list point an own class !
And for those little things in hamburger-menu the “description” that is the point you are looking for
check those things you like to have.

then you only must toggle the menu list point at that little arrow

• This reply was modified 8 years, 5 months ago by Guenni007.

but there has to be in the function an option for window resize – because footer height changes with content. On small screens we got a growing footer height (with socket too- but not so often)

It has to proof in time (dynamically) the height of socket and footer – how can we do that?
The code above works if we actualize the window but does not react on window-resize

• This reply was modified 8 years, 5 months ago by Guenni007.

by the way : for that page you use a fixed footer!
i would not set the z-index to 0 – that is a bit confusing.
isn’t it this way a bit looking better:

#footer {
    background-color: rgba(87, 98, 112, 0.9);
    bottom: 58px;
    left: 0;
    position: fixed;
    width: 100%;
    z-index: 1;
}

how did you do that with the spacer ?

.home #av_section_1 .av-special-heading-tag span {
    background: #000 !important;
    color: #fff !important;
    padding: 0 15px;
}

the padding is not necessary but i think it looks better.

Edit: ok if you are only changing vor that wp-content/uploads/dynamic-avia 777 is ok ! I did not follow your link and thought you did it for all files /folders so forget the rest here
But 777 is too much.
Go on reading how to set the correct file permissions.

I think for the files itself it is 640 and for the folders 750
but 644 and 755 seem to be ok too. For wp-config you should have 640 ( on normal Use)
Sometimes if you install f.e. Caching tools – they want to insert some code to wp-config – this has to be allowed for that moment.
only my uploads, upgrade and temp folders got a different permission.

For example the quick css info goes to wp-content/uploads/dynamic-avia
these files must have write permissions

BTW sometimes (it depends on your hoster) the file-permissions are ok but the owner-ship is wrong.

For my hoster f.e. i had to set the owndership to wp user (not ftp) and i have than the possibility to set the ftp-user react like a wp-user.
Only that setting allows me to have automatic updates of wordpress. etc –

________________

Security is a wide and complex field in wordpress.
The wp-config.php is a very important file to secure so there are a lot of things you can do

On apache Server you can use for that the htaccess file f.e.

<files wp-config.php>
order allow,deny
deny from all
</files>

• This reply was modified 8 years, 5 months ago by Guenni007.

Aber das ist dann wohl eher das browser problem und nicht enfold zuzuschreiben.

have a look here: https://kriesi.at/support/topic/mega-menu-top-level-styling-while-menu-is-active/

for mega-menu this is a bit easier: (but you will not have mega-menu on that template)

.open-mega-a {
    color: #0976ac !important;
}

but for your template i think this could be a good way:

#avia-menu > li.menu-item.current-menu-item a, 
#avia-menu > li.menu-item.active-parent-item a {
    background: #097ac0 ;
    padding-left: 10px;
}
#avia-menu > li.current-menu-item .avia-menu-text, 
#avia-menu > li.active-parent-item .avia-menu-text {
    color: #fff !important;
}

#avia-menu > li.current-menu-item .avia-menu-subtext, 
#avia-menu > li.active-parent-item .avia-menu-subtext {
    color: #efefef !important;
}

because the first level nav list points are allready bold there will be no big difference in selected or not

• This reply was modified 8 years, 5 months ago by Guenni007.