Hey Steve,
Thank you for your patience and for the link to your page, I see your accordions in the “Specs” tab but I don’t find any “strange” behavior when I use them, perhaps you could explain further what you are experiencing.

Best regards,
Mike

Hey shawnbanack,
Thank you for your patience and the links and screenshots. I did see the jump of the page when the toggle was clicked in Chrome and I also noticed that each time the page was reloaded it would move up slightly, so if I started at #ouradvantages and kept reloading I would soon be at #aboutus, I thought this might be related the “slow scroll” action of your menu anchor links because the toggles use a “fake” ID hashtag to enable the javascript for toggling… but I believe that I was way overthinking it because I didn’t see any of these errors in the Brave browser which is also built on Chromium, the engine of Chrome.
After testing this css: body{overflow:hidden !important;} and this jQuery:

function custom_script() { ?>
    <script>
(function ($) {
$(".toggler").click(function(){
  $("body").css({'overflow':'hidden'});
});
})(jQuery);
</script>
    <?php
}
add_action('wp_footer', 'custom_script');

to correct the behavior in Chrome, I wanted to post the version of Chrome I was using which was Version 89.0.4389.128 (Official Build) (64-bit) but it then updated to Version 90.0.4430.72 (Official Build) (64-bit) which is the same Chromium version in my Brave Brave Version 1.23.71 Chromium: 90.0.4430.72 (Official Build) (64-bit) so when I went back and tested your toggle again I didn’t have the same issues, so I’m thinking this is a Chrome issue?
Anyways, check your Chrome version and you are welcome to also try the css and or the jQuery if you like, but I believe most users will be getting the Chrome update shortly.
Your second issue is the webkit-focus-ring which is a built-in accessibility color for Chrome & Safari, you can override it with this css, but it is considered bad form in accessibility circles:

#top #wrap_all .toggler:focus,
#top #wrap_all .toggle_wrap:focus {
  outline: 0 !important;  
  outline: 0 -webkit-focus-ring-color !important; 
}

Best regards,
Mike

Hi,
Sorry I didn’t realize you were using a “staging plugin”, I thought you were using your webhost options for creating a staging site, which is much better, are you using cPanel? How to Deploy a Staging Site With cPanel
So comparing your Single Event page and mine are the same, so perhaps it is something else causing the issue? I would still like to see the error it would help me understand better.

Best regards,
Mike

Hi,
Thank you but unfortunately, an editor profile doesn’t allow me to see the options for plugins, appearance, tools, settings, nor any of the Enfold theme options.
But that is ok because as this is your live site and seeing the issue requires the Events Calendar plugin to be updated it would be better for you to create a staging site so your live site will remain live and un-touched, I believe you have done this before so perhaps this would be the best approach.
When you look at the layout of the Single Event page on my demo site do you see the error that you are referring to? Other than minor css differences I don’t see any layout issues between your current old version and my new version.

Best regards,
Mike

Hi,
Thank you for your patience and for the login to your site, I moved the login above to the Private Content area and found that it was a membership login with no backend access so I have limited ability to determine what issue you are having. I tried to research your previous posts and replies but couldn’t figure it out. So I installed The Events Calendar v5.5.0.1 on a demo server and imported an official demo file from the plugin site, and used some of your images as their demo didn’t include images, and the layout of the Single Event seems fine to me?
Naturally, the css is not exactly the same but I don’t see anything major in terms of a layout issue, perhaps you can explain further?
I do note that it looks like you are also using some other plugins or customizations, so I’m not sure if this also has a bearing on the issue you are experiencing, have you tested without your other plugins or customizations?

Best regards,
Mike

Hi,
Glad we were able to help, we will close this now. Thank you for using Enfold.

For your information, you can take a look at Enfold documentation here
For any other questions or issues, feel free to start new threads in the Enfold forum and we will gladly try to help you :)

Best regards,
Mike

Hi,
Glad we were able to help, we will close this now. Thank you for using Enfold.

For your information, you can take a look at Enfold documentation here
For any other questions or issues, feel free to start new threads in the Enfold forum and we will gladly try to help you :)

Best regards,
Mike

Hi,
Thank you, I did see the login info in the Private Content Area, but for some reason I was having issues logging in, anyways I was able to get it today. So in comparing your standard post using the classic editor and your custom post type using the classic editor, I note that the backend sidebar panel Layout is not available which is what allows the use of the “page as a footer” option. I believe that you need to enable ALB for any post type by following the steps in the documentation.
Please add and edit the function via FTP as I’m unsure how your plugin will behave with this function and your site may crash, hopefully not, but it is better to be ready to remove the function via FTP should this occur. Hopefully this will allow the Layout sidebar panel to be available and thus allow the “page as a footer” to show.

Best regards,
Mike

Hey markwilliams,
Thank you for your patience, unfortunately, replacing the ALB content is not as easy is replacing “the_content()” or “get_the_content()” try looking in “\enfold\template-builder.php” on line 76 $content = apply_filters( 'avia_builder_precompile', get_the_content() ); I believe you will find the comments there helpful.
This sounds like it is similar to the issues that Toolset and Advanced Custom Fields have when trying to replace “the_content()”, there were some older filters specific to these two plugins but I believe the theme files were changed since then, and since this is not what you are trying to do it won’t help.
The best option is to use the elements and their available options instead of trying to rewrite them as the elements are advancing with new options such as with the “CET” and your edits may cause problems for your site in the future.

Best regards,
Mike

Hi,

@bloomfashion unfortunately your issue is not the same as this user was having, but I see that you have opened your own thread, which is a better place to address your issue, thank you.

Best regards,
Mike

Hey kevinhaag,
Thank you for your patience please give this script a try, in the functions.php:

function custom_script() { ?>
    <script>
(function($){
      var int = '';
      function a() {
          var isMobile	 = $('.av-burger-menu-main').css('display'),
              htmlString   = $('#header_main .social_bookmarks').find('li a'),
              mobileMenu   = $('.av-burger-overlay'),
              socialString = [];
  
              if(isMobile == 'none') return;
              if($('.burger-social').length) clearInterval(int);
  
              htmlString.each(function() {
                  var socialClass	= $(this).parent('li').attr('class'),
                          socialItems = $(this).wrap('<li class="'+ socialClass + ' av-active-burger-items burger-social"></div>').parent().unwrap();
                  socialString.push(socialItems);
              });
  
              $(socialString).each(function() {
                  $(this).appendTo('#av-burger-menu-ul');
              });
      }
  
      $('#header').on('mousedown', '.av-main-nav-wrap', function() {
          int = setInterval(function() {
              a();
          }, 500);
      });
  
  })(jQuery);
  </script>
    <?php
}
add_action('wp_footer', 'custom_script');

the css:

#av-burger-menu-ul li.burger-social {
    float: left;
}
#av-burger-menu-ul li.burger-social a {
    padding: 10px !important;
    border-bottom: none !important;
}
#av-burger-menu-ul li.social_icon_1 {
 padding-left: 40px
}

Best regards,
Mike

Hey xfilegirl,
Thank you for your patience, can you link to the thread you found about the edit you tried, I didn’t find it and would like to try it. It sounds like the issue you are having is only with the third child-level menu correct?

Best regards,
Mike

Hi,
Thank you for the feedback, I thought the intention was to have the “Skip to Content” within the <body> tag, where before it was outside, aka before the <body> tag, so I used insertBefore(‘#wrap_all’); to get it above <wrap_all> and under <body> aka within the <body>
I tried to append to the <body> but that doesn’t work because the “Skip to Content” needs to be it’s own <div>
So when I check now it seems to me that it is now working as intended.

Best regards,
Mike

Hi,
Thank you @Guenni007, the Wayback machine is a good idea so send the chocolate to Bonn/Germany ;)

Best regards,
Mike

Hey jodyrussell,
Thank you for your patience and the catchy title, I see that you are using Enfold v3.8 with WordPress v5.1.8
I’m pretty sure Enfold v3.8 was using PHP v5.x which most webhosts won’t allow anymore so your probably on PHP v7.x now?
I would try downgrading WordPress to at least v4.x but I’m not sure how low you can go and still work with your PHP version, you may try alternating downgrading WP & PHP to get as low as to can go and at a point I believe that you will find your site will work again enough that you can login to the backend and perhaps clone it to a localhost and try rebuilding it.
But looking at your homepage, which seems to be the only page that works, it seems basic and seems that it would be easier to recreate from scratch, I personally would create a new install on a localhost of the latest versions of WordPress & Enfold and copy (scrape) the text and images from the frontend, or just make a completely new site. Sorry, this is probably not very helpful, but WordPress changed so much at version 5 that salvaging Enfold v3.8 may not be worth your time?

Best regards,
Mike