Hi,

I want to understand, what you mean, if you say, it’s for aesthetic.

It means that the css or script were added to attain a certain design or layout. You can’t make a tab invisible without setting the visibility to hidden or without setting its opacity to 0 first. You can’t hide the next or previous slide without setting it’s display property to none, or without removing it completely from the DOM. I’m sure that the Google developers who are responsible for the detection script have seen a tab or an accordion before and probably added an algorithm or condition — if it does exists — that says “oh this is a tab, it can’t be deceptive, so let’s skip it and move on”.

You can find a few examples here that almost do the same thing.

// https://www.w3schools.com/howto/tryit.asp?filename=tryhow_js_accordion
// https://www.w3schools.com/howto/tryit.asp?filename=tryhow_js_tabs
// https://www.w3schools.com/howto/tryit.asp?filename=tryhow_js_full_page_tabs

They set the initial display property to none and only set it to block or make the element visible when someone click on the tab.

Best regards,
Ismael

Hi,

It is working properly on our end — we don’t get any error. Did you copy the code from your email? Please try to copy it directly from the forum to avoid conversion of symbols to something else, which is what probably caused the snippet to break. If it’s still not working after, please post the login details in the private field so that we can see what’s going on.

Best regards,
Ismael

Hey S.,

Thank you for the inquiry.

That is for aesthetic purposes and not in any way deceptive. The toggle_wrap has to be hidden by default and only display when a toggle or tab is active. This is the reverse or active toggle css.

.active_tc.toggle_wrap {
	position: static;
	visibility: visible;
	left: 0;
	width: auto;
	z-index: 1;
	display: none;
}

If that css technique is considered deceptive, most if not all websites with tabs or accordions will be flagged as deceptive sites.

Best regards,
Ismael

Hi,

That is actually expected because iOS and a few browsers on mobile devices only have partial support for fixed elements. You can find the browser compatibility stats in the following link — check the Notes and Known Issues tabs.

// https://caniuse.com/#feat=background-attachment

Most mobile devices have a delay in updating the background position after scrolling a page with fixed backgrounds.
1 Partial support refers to supporting fixed but not local
2 Partial support refers to supporting local but not fixed
3 Only supports local when -webkit-overflow-scrolling: touch is not used
4 Does not support fixed, and due to a bug only supports local if a border-radius is set on the element. Firefox does not appear to support the local value when applied on a textarea element.
Chrome has an issue that occurs when using the will-change property on a selector which also has background-attachment: fixed defined. It causes the image to get cut off and gain whitespace around it.
iOS has an issue preventing background-attachment: fixed from being used with background-size: cover – see details

Please note that the css code above doesn’t fix the issue, it actually disables the fixed effect and changes the behavior of the background so that it scrolls relative to the page as it does normally.

Best regards,
Ismael

Hi,

Sorry for the late response. Looks like you’ve managed to add the h1 element or title using the Special Heading element. Let us know if you need more help.

Best regards,
Ismael

Hey bts-de,

Thank you for the inquiry and sorry for the delay. You will have to create a duplicate of the portfolio file in the child theme’s shortcode path, so first you have to create a new shortcode path in the child theme. Please check this documentation for more info.

// https://kriesi.at/documentation/enfold/intro-to-layout-builder/#add-elements-to-alb

Best regards,
Ismael

Hi,

What does helper-assets.php do at line 342?

The line is a loop, which iterates through the global variable $posts and the error occurs because the said variable is not found or undefined. Did you add a video in the page? Please check the following thread for a possible fix.

Related thread:

// https://kriesi.at/support/topic/php-warning-message/#post-1192124
// https://kriesi.at/support/topic/invalid-argument-supplied-for-foreach-in-helper-assets-php-on-line-327/#post-1042129

Best regards,
Ismael

Hey kjwaggz,

Thank you for the inquiry.

Did you change the selector “vid1” to the actual id of the player inside the color section? This is the markup of the video in the color section.

<video class="avia_video av-mediajs-loaded" autoplay="" loop="" preload="metadata" muted="" id="player_19_1393522152_1410262048_html5" src="https://d1g9724afgpznt.cloudfront.net/wp-content/uploads/sites/13/2020/04/23064701/bigstock-a-jib-shot-of-a-beautiful-farm-12593079411.mp4"><source src="https://d1g9724afgpznt.cloudfront.net/wp-content/uploads/sites/13/2020/04/23064701/bigstock-a-jib-shot-of-a-beautiful-farm-12593079411.mp4" type="video/mp4"></video>

The id is “player_19_1393522152_1410262048_html5”.

Best regards,
Ismael

Hey Luc,

Thank you for the inquiry.

How to remove this image size in functions.php child ?

You can move the provided filter from the previous thread in the child theme’s functions.php file. And if you want to retain other sizes, just look for these lines:

remove_image_size('magazine');
 remove_image_size('portfolio_small');

The lines above disable the “magazine” and the “portfolio_small” thumbnail, so if you want to retain those thumbnails, you have to delete those lines.

Best regards,
Ismael

Hey Walter Pisarnik,

Thank you for the inquiry.

There were a few users who reported issues with the plugin but only minor ones, so it should work fine but you should expect some template modifications to make the plugin completely work with the theme. Another LMS alternative is Learndash.

Related threads:

// https://kriesi.at/support/topic/lms-learning-management-system
// https://kriesi.at/support/topic/latest-enfold-5-not-installing-javascript-for-lifterlms-plugin

Best regards,
Ismael

Hi,

Yes, you should be able to add extra content in the socket container, but you have to modify the footer.php file directly. This is the socket container I(line 191).

				<footer class='container_wrap socket_color' id='socket' <?php avia_markup_helper(array('context' => 'footer')); ?>>
<div class='container'>

If you have any additional questions at this time we kindly ask that you open them up in a separate thread. The longer threads get in the forum, they become more difficult to support as they tend to drift off topic and they also make it troublesome for users trying to search for solutions. Keeping threads relevant to their original inquiry ensures that we can keep better track of what has been resolved and that users can more effectively find answers to similar issues they might be experiencing.

Thanks!

Best regards,
Ismael

Hi,

Glad to know that you managed to make it work. If you have any additional questions at this time we kindly ask that you open them up in a separate thread. The longer threads get in the forum, they become more difficult to support as they tend to drift off topic and they also make it troublesome for users trying to search for solutions. Keeping threads relevant to their original inquiry ensures that we can keep better track of what has been resolved and that users can more effectively find answers to similar issues they might be experiencing.

Thanks!

Best regards,
Ismael

Hi,

Sorry for the delay. You can add this css code to center align the arrow.

.av-tab-arrow-container {
	width: 210px;
}

Best regards,
Ismael

Hey nm,

Thank you for the inquiry.

Did you to try adjust the Refuse Cookie Warning text from the Enfold > Privacy & Cookies > Cookie Handling panel? You can also use the Loco Translate plugin to manually adjust the translations.

// https://wordpress.org/plugins/loco-translate/

Best regards,
Ismael

Hi,

Thank you for the info.

Looks like the color section renders a main tag inside the container. Unfortunately, we can’t adjust it without editing the enfold\config-templatebuilder\avia-shortcodes\section.php file directly. You’ll find the main element around line 1314:

					$markup = 'main '.avia_markup_helper(array('context' =>'content','echo'=>false, 'custom_markup'=>$custom_markup));

And the closing tag is located around line 1344:

$avia_section_markup = false;
			$close_markup = '</main><!-- close content main element -->';

Best regards,
Ismael