Hi @BigBatT,

Thank you a lot again for contributing the translations. Will be added to core.
Have a great day.

Best regards,
Günter

Hey Tim,

Thanks for reporting this. There is a weak CSS selector for empty cells in table.css line 234:

.pricing-table li.empty-table-cell{
	display:none;
}

As a temporary fix change it to or add it to Quick CSS in theme options:

.avia-pricing-table-container .pricing-table li.empty-table-cell{
	display:none;
}

Do not forget to toggle and save theme options to rebuild the merged CSS files.

I will add a fix for next release.

Best regards,
Günter

Hi,

I thought based on topic title you are using a plugin.

I’ve changed the implementation that this “feature” must be activated by user in child theme functions.php:

add_theme_support( 'avia_include_cookiebot' );

As there are too many files involved I would like to send you a complete copy of the theme to check. Let me know, to which E-Mail I can mail it please.

Best regards,
Günter

Hi,

No problem – it will also take me some time to investigate.
I’m tagged to this topic.

Best regards,
Günter

Hi,

Sorry for the late reply.

Do you have any other error messages in the error logs of WP and the php server ?

You probably know, but just to be sure.

There are 2 memory limits to set: PHP and WP

https://www.atatus.com/blog/the-php-memory_limit-what-you-need-to-know-about-increasing-it/

As you investigated – it seems to be a problem of PHP 8.1 in conjunction with a large amount of images.

There are 2 possible problems:

– caused by our image element
– caused by WooCommerce core or a plugin you use

PHP 8.1 also has a stricter type management – this also might cause a problem somewhere.

It is impossible for us to setup a test site with 116.000 products and to debug the problem on a live site is not really possible without breaking the site as we would need to insert debug code and also change php code of the image element including frontend output to locate the problem.

Do you have a chance to duplicate the site to a dev server where we can get free access (also ftp, to error logs, …) to investigate closer?

Best regards,
Günter

Hey kreativeseite,

Very sorry for this problem. Will be fixed in next release.

Meanwhile can you please replace

…\wp-content\themes\enfold\config-templatebuilder\avia-shortcodes\section\section.php

with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_5_6_11/avia-shortcodes/section/section.php

I added at line 1495:

$skipSecond = false;

Do not forget to make a backup of the original file for a fallback and clear server and browser cache.
If you need help with this let us know.

Best regards,
Günter

Hey Jan,

I tried to add a solution with WP filter – that would be a solution to maintain code in one place and also for other plugins to hook.

If you could please test it before we add it to final core.

1.) replace enfold\js\avia-js.js with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_5_6_10/js/avia.js

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_5_6_10/js/avia-js.js

Check class aviaJSHelpers in this file.

2.) in the files you mentioned instead of your code add:

		//	allow 3-rd party plugins to hook (see enfold\js\avia-js.js aviaJS.aviaJSHelpers)
		if( window['wp'] && wp.hooks )
		{
			allow_continue = wp.hooks.applyFilters( 'aviaCookieConsent_allow_continue', allow_continue );
		}

3) To load WP hook js in enfold\functions.php around line 574:

		wp_enqueue_script( 'avia-js', "{$template_url}/js/avia-js{$min_js}.js", array(), $vn, false );

replace with:

		wp_enqueue_script( 'avia-js', "{$template_url}/js/avia-js{$min_js}.js", array( 'wp-hooks' ), $vn, false );

Thank you for checking in advance and your help.

Regards,
Günter

Hi,

Best regards,
Günter

Hi @Webvriend,

Best regards,
Günter

Hi Rob,

@goldengate415

Fix will be in next release 5.6.11. Icons will be below title before content field.

Best regards,
Günter

Hi,

For next release 5.6.11 I also added a filter:

https://github.com/KriesiMedia/enfold-library/blob/master/actions%20and%20filters/ALB%20core/avf_sync_sc_defaults_array.php

Best regards,
Günter

Hi,

Please read chapter https://kriesi.at/documentation/enfold/custom-element-templates/#custom-elements-advanced-options and use

add_theme_support( 'show_advanced_custom_element_options' );

This will enable more options.

And also further down https://kriesi.at/documentation/enfold/custom-element-templates/#custom-elements-advanced-option-custom-elements-for-subitems

Best regards,
Günter

Hi,

Thank you for reporting this bug – I’m sorry for that mistake.

It is fixed in next release 5.6.11.

Have a great day.

Best regards,
Günter

Hey Tim,

I had a quick look.

The whole sale badge logic is managed by WooCommerce core – and also the template logic for display.

I do not see an easy way to hook into this.

Sorry I have no better news at the moment. I will keep it in mind for future.

Best regards,
Günter

• This reply was modified 10 months ago by Günter.

Hi,

Also die Fehlermeldung vom 18.1. kann nicht mehr der Grund sein. Ich habe die Typüberprüfung auf WP_Post entfernt.

Warum WP keine detailierte Fehlermeldung liefert – keine Ahnung.

Einzige Möglichkeit ist noch das PHP Error Log vom Server direkt und das WP Error Log (https://marketpress.de/wp-debug-log-fehlermeldungen-in-wordpress-ausgeben/). Ich würde aber WP_DEBUG_DISPLAY auch auf true setzen zum Testen.

Evtl. musst Du Deinen Systemadministrator / Hoster kontaktieren um die entsprechenden Debug Logs zu aktivieren.

Best regards,
Günter