Hi:

The error after the update was showing because someone had activated the “show errors” in the server. That’s fixed, but the failed update is still an issue.

Thanks.

— Michael

Magnificent!

Thank you.

— Michael

I updated it successfully via FTP.

Thanks.

— Michael

I have found another soution. Right now, it’s good.

Thank you for your response!

— Michael

That’s very interesting—good information.

Thank you for looking into it.

— Michael

I don’t quite know what you’re referring to as “customization.” We develop websites and don’t need a freelancer—and were only looking to have the theme work as it should standardly as there has never been any trouble over the years like this.

I will try the update, thanks.

I have identified the issue only occurs on older MAC OS’s. This is the system where the problem is:

Mac OS 10/11.6
Chrome Version 66.0.3359.139 (Official Build) (64-bit)

It did work in Chrome on a more updated system below:

Mac OS 10/13.4
Chrome Version 66.0.3359.139 (Official Build) (64-bit)

So it looks like the issue is with a specific Mac OS as above.

I have just verified this is a Chrome for Mac only issue.

I have checked to see if LayerSlider on its own is compatible with Chrome, and it is. See this link:

Enfold is not compatible with LayerSlider on Chrome. See this link:

Please let me know if this is something you can address and fix or if I should look for another slider, test all and redevelop all website pages with sliders. I have five client websites with extensive use of LayerSlider that I will have to go back and redevelop—a lot of work for no pay.

Let me know.

All the LayerSlider transitions are not working after the 4.3 update. This breaks the majority of the pages site wide.

I will give you a chance to look at it, then if it cannot be fixed I will delete the entire site and restore from backup of the earlier Enfold version. I can see you are busy with 4.3 issues, so please let me know if this can be handled.

Thanks.

Thank you very much for taking a look. I have relayed your response to WPL.

— Michael

It is in the “Snippits” interface, a plugin for adding code outside the theme functions file—so it will not be overwritten with updates. Please see the “Snippits” menu in the left sidebar underneath “Plugins.” CLick “All snippits” and then edit the only one you will see.

Thanks.

This is a nice piece of code, thanks. I changed it so it opens at the first slide.

// custom script
function add_custom_script(){
?>
<script>
(function($){
setTimeout(function() {
$(“.aviaccordion-slide-1”).trigger(‘mouseenter’);
}, 1000);
})(jQuery);
</script>
<?php
}
add_action(‘wp_footer’, ‘add_custom_script’);

However, it does not resume the normal autorotation of the accordian slider after an interval. And, eventually it opens and closes slides 2 and 3, and sometimes 4 in random order and for random durations—sometimes. In other words, it seems to affect the autorotate so it does not work and affects some slides randomly so they open and close. The “mouseenter” does work fine to manually rotate the slides.

Is thre any way to run the script as you have it leaving the fist slide open for a certain interval, say 10 seconds, and then put that script to sleep and rectivate the built-in auto-rotate script so the autorotation again works?

Ideally, the first slide would load in an open position, hold that way for 10-seconds, then the autorotation would resume normally with the interval set in the accordian slider control settings.

Let me know.

Thanks for the help.

I have managed to figure out the CSS that makes it all work on both Android and iPhone. Something changed on some update somewhere since all this was not needed before. It may be a little heavy, but it seems to work across devices just fine. I didn’t want you to have to look into it if it’s now working. Thanks.

/* ---- KEEP MOBILE MENU VISIBLE SCROLL ---- */

#advanced_menu_toggle, #advanced_menu_hide {
position: fixed !important;
right: 3% !important;
top: 5% !important;
}

@media only screen and (max-width: 900px) {
   #wrap_all {overflow: hidden !important; /*needed for mobile menu scrolling */}
}

@media only screen and (max-width:767px) {
  .responsive #top #wrap_all #header {
    position: fixed !important;
  }
  .responsive #top #main {
    padding-top: 80px !important;
  }
}

@media only screen and (max-width: 767px) {
#top #menu-item-search {
display: none;
 }
}

@media only screen and (max-width: 767px) {
.main_menu{ right: -5px !important;}
}

@media only screen and (max-width: 767px) {
#top .social_bookmarks { display: none !important; }}

/* ---- END KEEP MOBILE MENU VISIBLE SCROLL ---- */

Hi:

Thank you for your response. The custom CSS makes no difference in or out. I have set up a dev site and will test all the plugins—though I hate doing it. Meanwhile, here is some ofher data:

– The menu problem is on both Android and iPhones—but in smartphone size only.
– Tablets work fine over 765 px. At 765 the menu changes and no longer sticks to the top with scrolling, plus loses the transparancy option and the shrinking action. iPad Air for example works fine. It is completely a smartphone issue below 765 px.
– In the “HEADER” section under the Enfold menu, these dialogs show that the “sticky header” is ignored on smartphones:

Sticky Header
If checked the header will stick to the top of your site if user scrolls down (ignored on smartphones)
Shrinking Header
If checked the sticky header will shrink once the user scrolls down (ignored on smartphones + tablets)

Both these are checked. Perhaps this code is preventing the custom CSS from working by overriding on smartphones below 765px? Can this be the case?

Again, tablet sizes work fine, but smartphone sizes do not. And the social icons dissappear, clearly there is code defining a different menu for smartphones below 765px. For some reason the custom CSS is not overriding this.

/* —- KEEP MOBILE MENU VISIBLE SCROLL —- */

#advanced_menu_toggle, #advanced_menu_hide {
position: fixed !important;
right: 3% !important;
top: 5% !important;
}

@media only screen and (max-width: 900px) {
#wrap_all {overflow: hidden !important; /*needed for mobile menu scrolling */}
}

/* —- END KEEP MOBILE MENU VISIBLE SCROLL —- */

I will let you know if I find anything in the plugins—and I can give you access to the dev site if you like.

Thanks.

— Michael

• This reply was modified 7 years, 3 months ago by blaircomm.

This is now working. Thank you very much.

– Michael