Hi,

I forgot to mention, that the fix will be part of next release 4.5.2.

So you can actually replace the 2 original files in ..\enfold\js\…

No need to copy to child theme.

Script from Yigit is not correct, as it loads the same code twice (.min is minified only).

@Guenni007

Your code should work. Depending on theme option either the normal version of the file or the .min. version is loaded.
If you do not upload a .min. version you can skip {$min_js} (or set it to ” hardcoded).

Best regards,
Günter

Hi,

If you do not need the WP block editor (= Gutenberg) Enfold has an integrated option to disable it without the need of any plugin:

Theme Options Enfold -> Theme Options tab -> Select Your Editor at bottom.

And if you want to switch depending on page/post you edit you can also do that with

add_theme_support( 'avia_gutenberg_post_type_support' );

This adds additional options on options page and links to open a page/post

Best regards,
Günter

Hey Guenter,

Thanks for pointing at this.

We missed to update it. Kriesi will upload a correct version.

Best regards,
Günter

Hi Roger,

@EZWebdesign

Thank you very much. I added it to core.
Have a great day.

Best regards,
Günter

Hi,

I added a working filter to functions.php in your child theme.

You also find it here:

https://github.com/KriesiMedia/enfold-library/blob/master/actions%20and%20filters/ALB%20Elements/Blog%20Posts/avf_blog_content_in_loop.php

But please keep in mind that displaying ALB content might break the layout.
We had users who faced this problem, thats why we removed it by default.

We will add it to the description of the option.

Best regards,
Günter

Hey Guenter,

This is the intended and default Enfold behavior that in a blog content created with ALB is not executed.
If you use a standard editor (even with shortcode) it is displayed correctly.

see loop-index line 130 ff.

If you really want to display the executed shortcode you can use the filter (line 130):

$current_post['content'] = apply_filters( 'avf_the_content', '', 'loop_index' );

and return whatever you like.

Best regards,
Günter

Hi Thomas,

Glad I could help you.

Also happy New Year.

Best regards,
Günter

Hi,

Yes I think it should. Using the option “Performance -> Show Advanced -> Custom Font Loading Source” (5.4) will supress the output of @font-face in dynamic css file.
So if you copy the files to your CDN and handle the @font-face CSS rule by yourselfe it should work.

Best regards,
Günter

Hi,

Yes, changes are in 5.3.1

Best regards,
Günter

Hey kisys,

Thank you for reporting this.

You have enabled WP_DEBUG on that install.

If you disable it, this error will disappear.
As a second hotfix you can remove the two following lines in enfold\config-templatebuilder\avia-template-builder\php\base-classes\class-object-properties.php

throw new \InvalidArgumentException ( $message );

We added these checks with 5.3 during development to catch problems – we will change it to debug notices in the next release so it does not break any longer.

Very sorry for the inconvenience.

Best regards,
Günter

Hi,

The waypoints script is now enqueued seperate right before the avia.js in functions.php around line 496.

We removed it from avia.js because we needed to make changes to the original script to be compatible with jQuery 3.5 and WP 5.6 and to avoid conflict with the minify routines we added.

Hope this helps you.

Best regards,
Günter

Hey loghash,

Thank you for using Enfold.

PHP 5.5 is totally outdated and also for security reasons you should consider to update to a newer version.

The problem you see here is already solved in 5.6 (https://www.javatpoint.com/php-variable-length-argument-function).

There is a workaround for it:

https://www.php.net/manual/en/functions.arguments.php#functions.variable-arg-list

and

https://www.php.net/manual/en/function.func-get-args.php

You will need to modify theme core file

enfold/config-templatebuilder/avia-template-builder/php/base-classes/class-element-styling-base.php after line 633.

But keep in mind you must modify this with every new release. We will not add this to core.

If you need help with it let us know.

Best regards,
Günter

Hi,

Yes. Only ‘av_icon_circles’ are changed.

Best regards,
Günter

Hey geektech-42,

The easiest way would be to add your customs fonts to the “Websafe Font” section in the dropdown.

You can do that and manipulate this array with the following filter:

function custom_available_websafe_fonts( $fonts )
{
	$fonts['Montserrat'] = 'Montserrat';
	$fonts['Aclonica'] = 'Aclonica';

	return $fonts;
}

add_filter( 'avf_available_websafe_fonts', 'custom_available_websafe_fonts' );

Then you have to load your @font-face declarations on all backend post types that support ALB and in frontend.

As a start you could add it to enfold-child\style.css which will do it.

To see a rough preview on theme options page you must also load it there. There is no special file in the child theme for that.
You can use the following action hook only called on theme options page to enqueue your own backend file containing the @font-face declarations:

			/**
			 * Allows to add additional submenus
			 *
			 * @used_by				aviaElementTemplates::handler_ava_menu_page_added     10
			 *
			 * @since 4.8
			 * @param string $top_level
			 * @param avia_adminpages $this
			 * @param string $the_title
			 * @param string $menu_title
			 */
			do_action( 'ava_menu_page_added', $top_level, $this, $the_title, $menu_title );

Example fo Font Face declarations:

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

I hope this helps you.

Best regards,
Günter

Hey Gabriel,

Thanks for reporting this.

Sounds a bit strange as I work with 8.0 and get no notices.

But I added fixes for the next release for both problems. Can you wait for that or do you need the fixes now?

Best regards,
Günter