Hi,

Thank you for the feedback – and glad we found the solution.

No, I will merge it into 4.8.7.2. Only keep

add_theme_support( 'custom_uploaded_fonts_relative_url' );

Enjoy the theme and have a nice day.

Let us know, if you need further assistance – simply create a new topic.

Best regards,
Günter

Added:

Keep an eye on the changelog in case we might add a theme option to replace the add_theme_support in a future release.

Hi,

I think I found the problem. When creating the merged files we change relative urls in enfold.css to absolute urls.

I added to config-templatebuilder\avia-template-builder\php\class-asset-manager.php line 677:

			/**
			 * e.g. WPML needs relative paths when using directories for languages
			 * 
			 * @since 4.8.7.2
			 */
			if( current_theme_supports( 'custom_uploaded_fonts_relative_url' ) )
			{
				return $content;
			}

Now after merging files you find in avia-merged-styles-974f232210bc9596190f218f629b8b53—619b7b9d06faf.css the relative urls:

....

@font-face{
font-family:'poppins';
src:url('/wp-content/uploads/avia_fonts/type_fonts/poppins/poppins-black.ttf') 
format('truetype');
font-style:normal;
font-weight:900;
ont-display:auto
} 

@font-face{
font-family:'poppins';
src:url('/wp-content/uploads/avia_fonts/type_fonts/poppins/poppins-blackitalic.ttf') 
format('truetype');
font-style:italic;
font-weight:900;
font-display:auto
}

........

Can you check with the other language please.

Best regards,
Günter

Hi,

see private.

Best regards,
Günter

Hi,

Zunächst einmal Filter Lösung für ” Tag Archive for: “

https://github.com/KriesiMedia/enfold-library/blob/master/actions%20and%20filters/Basic%20Templates/tag.php/avf_tag_label_names.php

Best regards,
Günter

Hi,

uploading the font: Theme Options -> Import/Export -> Custom Font Manager

You can upload new fonts or delete already uploaded fonts (and reupload them).

—-

But I added a solution that removes the absolute URL part when creating the file dynamic_avia/enfold(_child).css on the fly.

Please update enfold\framework\php\font-management\class-avia-type-fonts.php with the content of

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_8_7_1/framework/class-avia-type-fonts.php

Around line 988ff you find theme support ‘custom_uploaded_fonts_relative_url’ (and filter ‘avf_custom_uploaded_fonts_url’).

Adding theme support will modify the output in dynamic_avia/enfold(_child).css to e.g.:

@font-face {
     font-family: 'lato';
     src:    url('/wp56/wp-content/uploads/avia_fonts/type_fonts/lato/lato-black.ttf') format('truetype');
     font-style:  normal;
     font-weight: 900;
     font-display: auto;
}
@font-face {
     font-family: 'lato';
     src:    url('/wp56/wp-content/uploads/avia_fonts/type_fonts/lato/lato-blackitalic.ttf') format('truetype');
     font-style:  italic;
     font-weight: 900;
     font-display: auto;
}

If WPML copies this file (or the merged files) to the other domain and the ttf files are in the same folder location there it should work.

Best regards,
Günter

Hi,

Sorry for the problems you have.

My knowledge about setting up WPML sites is not so good. It seem to be a problem in setup of WPML and Enfold.

If I understand it correctly you have a french domain and a seperate english domain.

Do you upload the fonts to french domain only or also to the english domain?

Second thing to check would be if you disable css file merging, save theme options (on both sites) and check the files:

../wp-content/uploads/dynamic_avia/enfold_child.css

in both domains. At the beginning you should find something like:

@font-face { 
     font-family: 'lato';
     src:    url('https://localhost/wp56/wp-content/uploads/avia_fonts/type_fonts/lato/lato-black.ttf') format('truetype');
     font-style:  normal;
     font-weight: 900;
     font-display: auto;
}
@font-face { 
     font-family: 'lato';
     src:    url('https://localhost/wp56/wp-content/uploads/avia_fonts/type_fonts/lato/lato-blackitalic.ttf') format('truetype');
     font-style:  italic;
     font-weight: 900;
     font-display: auto;
}
.....

It would be interesting to know the value of src: ….

If you have a staging site – can you give us WP admin access and FTP access so I can also see your backend.
It might be necessary that we get in contact with WPML support also to find a solution. So it might be necessary to forward your credentials to them also.

Added 16.11.:
=============

Could you please create a ticket at WPML support with reference to this thread and that they should pass it to head of compatibility team so we can find a solution.

If you give us the link to this ticket we can also get in touch with him additionally.

Best regards,
Günter

• This reply was modified 3 years, 5 months ago by Günter.

Hey Tim,

Thank you for sharing your ideas – a great help as always.

I agree – we need to think about updates to WC integration.

I added it to our dev repo to have an eye on it. But we already have a lot in queue there for ALB core improvements. So I cannot give an ETA when we can start with it.

We will add any updates on this to the changelog (or as a preview to https://kriesi.at/support/topic/enfold-upcoming-fixes/

Best regards,
Günter

Hi,

I updated

if(in_array($last_el['tag'], AviaBuilder::$full_el_no_section ))

to

if( is_string( $last_el['tag'] ) && is_array( AviaBuilder::$full_el_no_section ) && in_array( $last_el['tag'], AviaBuilder::$full_el_no_section ) )

in next release. This should fix the problem.
Best regards,
Günter

Hey Tim,

Thanks for your feedback.

I’ve already been adressed with this notice – see https://kriesi.at/support/topic/error-in-socket-menu-aria-aria-accessability-issue/#post-1327070https://kriesi.at/support/topic/error-in-socket-menu-aria-aria-accessability-issue/#post-1327070

But I have no idea how to remove/solve that.

Best regards,
Günter

Hi,

@Webvriend

Thanks for this positive feedback – and I hope everything works as expected.

I have an eye on the sticky mobile menu.

Best regards,
Günter

Hi,

@danowen777

This element is not working any longer due to changes since WP 5.5 in routing logic.

I updated the element and it will be part of next version 4.8.7.2.

Meanwhile please replace enfold\config-templatebuilder\avia-shortcodes\page_split.php

with the content of:

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_8_7/shortcodes/page_split.php

Do not forget to make a backup of the original file for a fallback and clear server and browser cache.

If you need help let us know and we can do it for you.

Best regards,
Günter

Hi,

Updated version:

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_8_7/shortcodes/page_split.php

Can you check please.

You can remove add_theme_support and it should work without your workaround with nextpage.

Best regards,
Günter

Hi,

Did you save theme options as well – to force recreating the post css files ?

Can you please create an admin account for us so we can check the backend. You can put it in private content.

Best regards,
Günter

Hi,

Sorry for the problems. Will be fixed in next update.

Meanwhile please replace content of enfold\config-templatebuilder\avia-shortcodes\grid_row\cell.php with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_8_7/shortcodes/cell.php

Do not forget to make a copy of the original file for a fallback and clear server and browser cache and save theme options to force a rebuild of the post-css files.

If you need help let us know and we can do it for you.

Best regards,
Günter

Hi,

I had a look into it.

I added to header menu:

<ul id="avia-menu" role="menu" class="menu av-main-nav">

But this does not solve the problem, in contrary I get the additional message:

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

But we have a structure:

role=”navigation”
– role=”menu”
— role=”menuitem”

I did not dig into the ARIA, but at the moment I have no idea how to solve this or what is wrong.

And also https://www.w3.org/WAI/GL/wiki/Using_ARIA_menus – Example Code at bottom is built in a similar structure.

Best regards,
Günter