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,
I’m glad that this has helped and placed you on the right track I recommend that you continue along with the plugin developer. But supporting third-party plugins such as this is beyond our intended support scope.

Best regards,
Mike

Hi,
Thanks, but I believe my IP is being blocked because I’m not seeing the WordPress login form just this:

I can see your dev site front page fine, it looks like you are using the “Shop Demo” 🙂

Best regards,
Mike

Hi,
Thank you for the login details, but I’m getting a 403 error for the login page, perhaps this is a security setting, if so please whitelist my IP in the Private Content area.

Best regards,
Mike

Hi,
Thank you for your patience, in comparing these pages and the un-minified css I found that the plugin css is being overwritten by the theme css because of css specificity, to correct this we can give the plugin a higher specificity by adding two IDs to the rules, for example, currently the plugin css is this: .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > input but adding two IDs before the rule will give it more specificity: #top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > input , so you could edit the plugin stylesheet and add the two IDs to every rule and this would solve all of your current and future issues, or you could add this css to your current custom stylesheet which would solve the issues that I see on the two pages that you have linked to:

#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field > label.active {
    -webkit-transform: translateY(-150%);
    transform: translateY(-150%)
}

#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > input,#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > textarea,#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > label,#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > .validate ~ label,#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > .autocomplete-content {
    padding-left: 2.5em;
    margin-left: 0;
    width: calc(100% - 3em)
}

#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > input,#top #main .ipt-uif-custom-material-custom.eform-override-element-boxy .input-field.has-icon > textarea {
    width: calc(100% - 3em - 2px)
}

then if you find any future issues with other elements in your forms you will know to follow the same procedure with the css rules for that element.
Please don’t forget to clear your browser cache before checking.

Best regards,
Mike

Hi,
Thank you for your patience and for the link, when I check your site it looks like there is only one section that is having an issue with the gold edge in mobile, #therapieangebote so in that case I modified Rikard’s css a little to this:

@media only screen and (max-width: 767px) {
.avia_mobile #top.home #wrap_all #therapieangebote > .avia-full-stretch {
	background-attachment: fixed !important;
}
}

please try this instead and clear your browser cache and check.

Best regards,
Mike

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