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

Hi,

I do not think it is the length of the file but some code inside that breaks it.

But glad it is working now.
I will close this topic. You can open a new one whenever necessary.

Have a great day.

Best regards,
Günter

Hi,

@Guenni007

Your solution will not work in masonry entries with load more button and when the entry is queried with the load more by ajax.
I’ve already a solution for that.

For backwards compatibility I think we must have an option to activate it.

And I will check other ALB elements to add it.

Best regards,
Günter

Hey Guenter,

This can be done after update any time.

Best regards,
Günter

Hey BlutVampir,

Use

Avia_WPML()

to get the instance of the class for the handlers.

e.g.:

remove_filter( 'wp_nav_menu_items', [ Avia_WPML(), 'handler_append_lang_flags' ], 9998, 2 );

Best regards,
Günter

Hi,

I added the following filter ‘avf_el_styling_responsive_styles_ignore’ for next release:

			/**
			 * Allow to ignore responsive styles handling on element basis and use for all screen sizes
			 *
			 * @since x.x.x
			 * @param boolean $skip
			 * @param array $atts
			 * @param \aviaShortcodeTemplate|null $sc_context
			 * @param string $id
			 * @param string $container
			 * @param aviaElementStyling $this
			 * @return false|mixed						anything except false will only use default setting for
			 */
			if( false !== apply_filters( 'avf_el_styling_responsive_styles_ignore', false, $atts, $sc_context, $id, $container, $this ) )
			{
				$rule = isset( $this->callback_settings[ $id ]['styles'] ) ? $this->callback_settings[ $id ]['styles'] : array();

				if( ! is_array( $rule ) || empty( $rule ) )
				{
					return $added;
				}

				$this->add_styles( $container, $rule );
				$added++;

				return $added;
			}

and also added the $this parameter to filter ‘avf_el_styling_responsive_styles_skip’.

I hope this will help.

We try our best to stay backwards compatible, but it is impossible for all possible cases.

Best regards,
Günter

Hey Thomas,

You can use the following filter:

add_filter( 'avf_allow_drag_drop', 'custom_disable_alb_drag_drop', 100, 1 );

This will hook after our filter in enfold\functions-enfold.php line 2227.

in your function

custom_disable_alb_drag_drop( $disable ) 
{
// add logic to decide what to do
}

return true to allow drag/drop or false to lock.

Hope this helps you.

Best regards,
Günter