Hi,
Very good we will go ahead and close this then, for your information through, column links are actually “fake” and are simulated within Enfold, the URL is actually added in a separate link element inside the column.

Best regards,
Mike

Hi,
Glad to hear this helped I pointed this out to the dev team for them to review. I believe that this solution is a bit hacky to be included in a release, but perhaps they will add something else. We will close this now. Thank you for using Enfold.
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,

@cnovey this is a core WordPress issue, for files to show in the media library they must be registered in the WordPress database.
The only way to do this is with a plugin, we do not recommend any certain plugin to achieve this, nor have we tested their current compatibility, but this tutorial recommends the Add From Server plugin, but please read about it carefully first and use it at your own discretion.
I recommend that you take Guenni007’s advice.
In the future please create a new thread for your questions instead of re-opening a 3-year-old thread, thank you for your understanding and for using Enfold.

Best regards,
Mike

Hi,
Thank you for the feedback, these two pages are your staging url’s so you are getting a CORS policy blocking error, please try correcting the links and you should not have any issues.

Best regards,
Mike

Hey Roger,
Thank you for your patience, can you link to a test page with a simple test quiz? I have two solutions from a while back that might still work, one is this css for your Quick CSS field:

dd.course_progress {
	width: 100%;
}

the other was this code to add to your functions.php file in Appearance > Editor:

function show_quiz_results() { ?
        >
        <
        script >
            (function($) {
                $(window).click(function() {
                    if ($('.wpProQuiz_sending').is(":visible")) {
                        $('.wpProQuiz_results').css({ 'display': 'block' });
                    }
                });
            })(jQuery); <
        /script>
        <?php
}
add_action('wp_footer', 'show_quiz_results');

but that might have been for the pro version, I don’t recall for sure and would need to test again if these don’t work today.

Best regards,
Mike

Hi,
I’m not sure that I understand your question, typically bold is not a different font, but if you want to use a different font for bold then you should follow the above steps.

Best regards,
Mike

Hi,
Do you mean that this would be the only font used on your entire site? Please see the @font-face article I linked to above as it explains how to use for “body” but overriding every font on your site could be achieved with something like this:

body,
#top #wrap_all h1,
#top #wrap_all h2,
#top #wrap_all h3,
#top #wrap_all h4,
#top #wrap_all p,
#top #wrap_all a,
#top #wrap_all .av-special-heading-tag,
#top #wrap_all .avia-menu-text {
  font-family: 'MyWebFont' !important; 
}

naturally you would replace MyWebFont with your font, and you could add elements to this list as needed.

Best regards,
Mike

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