Forum Replies Created
-
Posts
-
Check out this page:
I noticed that the 4.5.2 changelog mentioned there was a fix to the mobile css for the full-width submenu, so I went ahead and updated. It’s not really fixed quite yet though as the submenu is no longer sticky at all in browser-widths I noted above. I expect the element to not be sticky while on a mobile phone (or anything narrower than 750px, but it should stick at the top of the browser between 750 and 970. Thanks for the help again.
I noticed that on the enfold demo page, the same issue happens. Maybe you guys can debug from there if that’s easier? The full width sub menu here doesn’t stick fully to the top (there’s a gap above the menu) at the browser widths I noted in the first comment.
If it were up to me I’d give you admin access, but our government hosting team doesn’t allow more than a few ip addresses into the back end. If that’s an issue I’ll see if I can get that changed for you.
If this info helps…I’ve tried to disable plugins and any custom css to see if that fixes the issue and it hasn’t. So far, the only way I can get the full width sub menu to work is by changing the header to not be sticky at all browser widths.
Very good timing on your part, haha. I just figured out a way to make it stay showing. I added a # to the link field for the first image and now it stays put for some reason. Before, the link field was blank for that image and would show for a second and then hide, making all the other images shift to the left. Not sure why it was doing that, but it only started doing that after updating to 4.0.4.
update: i changed my backend settings from custom pixel value of 65px to slim and the menu returns to normal. I still would like to keep my custum pixel value though.
Hi Yigit,
This solves the problem of it showing up off the screen; however, I remember before the 3.0 update that all of the 3-columned mega menus appeared in the same location on the screen. For example, the “Hazards” and “For Teachers” mega menu divs on my site both show up in the same location on the screen. Was this changed with the update? Out of curiosity, I removed all of my quick-css to see if it was affecting it, and it wasn’t. I guess what I’m getting at, is that I was hoping that all of my mega-menus would continue to take up the same physical location on the screen like before (Is this still possible?).
Thanks!
Thank you for your help. That fixed the issue. I really appreciate all the hard work you guys put into this product.
Is this something I’ll need to edit manually after updating Enfold or will this be addressed in the next version?Thanks again!
Disabling plugins didn’t help either unfortunately. I would love to continue using the layer slider. Do you know where in the code the skinspath declaration is being constructed (I haven’t been able to find it)? There wasn’t a problem with the most recent version of Enfold.
I just downloaded the newest version of enfold directly from themeforest.net and there is no init.php file. What am I missing here? http://i.imgur.com/5ZyoqU4.png
That may be my problem…I don’t have a init.php in that folder path…I have an index.php and layerslider.php and a bunch of other folders.
Yes, I’ve been testing this all morning. IE’s debugger was the most helpful (I know, right?), and pointed out the problem. Here’s the Error:
Console: SCRIPT1023: Expected hexadecimal digit
Debugger: lsjQuery(“#layerslider_10”).layerSlider({responsiveUnder: 1920, layersContainer: 1920, hideOnMobile: true, hideUnder: 400, twoWaySlideshow: true, loops: 10, skin: ‘fullwidth’, navStartStop: false, navButtons: false, hoverBottomNav: true, showCircleTimer: false, thumbnailNavigation: ‘disabled’, skinsPath: ‘http://beta.geology.utah.gov/wp-contentE:\www\ugsweb\wp-content\themes\enfold\config-layerslider\LayerSlider/static/skins/’})
I bolded the problem (I don’t know how to fix it though since the problem is a folder path is the root folder for my entire site). I guess /u is unicode and expects a hexidecimal digit afterwards (http://msdn.microsoft.com/en-us/library/ie/13ht9e2w(v=vs.94).aspx). If the /u is to be interpreted literally, there needs to be a //u. Any ideas how to fix this?
@Josue I just made a new thread https://kriesi.at/support/topic/layer-slider-enfold-3-0-not-working/
