Steve Truman

we will run some tests with a clean divi install and see if we can replicate the issue and get back to you.

What makes you think that a3 Lazy Load is causing that issue?

@dim795

Thank you! Have a great day.

Steve

@ritapalopoli

Please give me link to your site where I can see this happening.

Steve

Yes I have it and have been able to follow the Wordfence link to the vulnerability page on their site. I am not sure why we did not get a notification from Wordfence about this. Its a minor issue, maybe that is why – it was published just last week.

As their description says the vulnerability

“This makes it possible for unauthenticated attackers to hide product categories.“

We will get a patch for this released today.

Thank you for bringing this to our attention.

Steve

Hello @utahcoffee

This is a very strange post. I am the plugin author and am not aware of this. Please tell me more?

Steve

Thanks for the link – it is working fine for me

https://somup.com/cZnriapvMv

Steve

Hello @davsvatos

Thanks for posting the warning messages – most helpful.

The warning message you’re seeing is related to a PHP configuration issue on your web server. Specifically, it’s about the open_basedir restriction, which is a security directive in PHP’s configuration that limits the files that can be opened by PHP to the specified directory-tree.

The message indicates that a PHP script is trying to access a file (/pvc_mixins.less) that is not within the allowed path(s) specified by the open_basedir directive. The allowed path(s) in your case is /data/web/virtuals/281706/virtual, but the script is attempting to access a file outside of this directory.

Here’s how you can address the issue:

1. Review the PHP Configuration: The open_basedir setting is specified in your PHP configuration file (php.ini), or it might be set at runtime using the ini_set() function. You’ll need to check where the restriction is being set. If you have access to the php.ini file, you can modify the open_basedir directive to include the path where /pvc_mixins.less is located.

2. Adjust the open_basedir Path: You need to add the path to the directory containing the /pvc_mixins.less file to your open_basedir directive. Make sure you separate multiple paths with a colon (:) on Unix/Linux systems or a semicolon (;) on Windows.
OR
3. Contact Hosting Provider: If you’re on shared hosting or don’t have access to modify the php.ini file directly, you may need to contact your hosting provider for assistance. They can adjust the open_basedir settings for you.

I hope that helps you.

Steve

@wamwebdev & @itsmariosouza,

Thanks for the heads up and the nudge. Fix is in version 2.7.2 released last night.

Steve

@shameemreza

Thanks for following this up. As suggested the issue has been created here.

Have a great day.

Steve

@carolm29

Thanks for the update. Could I ask that you @a3rev on the github issue if / when it is opened so that I can keep tabs on the progress – want to remove the custom code if the issue is patched.

Thank you – Steve

Hi @(woo-hc)

Hi – we have just come come across this issue – and have checked it on the 7 sites that use single product FSE templates and in every one the HTML is stripped out and trimmed in the short description.

Thanks for pointing out the filter and we have fixed the issue by adding this custom code to the Child Theme functions.php file

add_filter('wp_trim_words', function ($text, $num_words, $more, $original_text) {
    if( is_singular( 'product' ) ){
        $text = wpautop( $original_text );
        return $text;
    }
}, 10, 4);

This is obviously a bug that needs a fix. I went to the Git repo thinking I’d find a ticket there. I could not find one – so I thought I’d ask you if you have raised the issue?

Steve

@hensterrsa

Thank you for reporting that – it has been updated in the version 6.0.0 release.

Make a great day.

Steve

@c2twebmaster

The error message you’re seeing from your WordPress site is related to a PHP memory limit issue. Let’s break down the message to understand it better:

• Date and Time: 2023-12-27 00:09:36 – This indicates when the error occurred.
• Pages Failed: This part of the message suggests that the error occurred while trying to load or process pages on your WordPress site.
• Allowed memory size of 536870912 bytes exhausted: This indicates that the script has reached the PHP memory limit set on your server. The number 536870912 bytes is equivalent to 512 MB, which is the maximum amount of memory that PHP was allowed to use for the script that was running.
• (tried to allocate 10485760 bytes): This part indicates that the script tried to allocate an additional 10485760 bytes (which is approximately 10 MB) of memory, but it couldn’t because the memory limit was already reached.

So your sites PHP memory limit of 512MB was already ‘red lining’ when tried to load another page that was downloading 10MB of content that triggered that error.

This is not uncommon on WooCommerce sites – setting your PHP limit at 1GB will resolve any memory issues you have.

The error message you posted does not mention WooCommerce Predictive Search and it uses very little memory – but if it or another script is trying to load after the memory time out sure you will see it mention in the logs regardless of how little or much memory it uses, because it can’t load.

Hope that helps.

Steve

Hello @moytopcom,

The way a3 Lazy Load works is that if the image has width and height specified then then the lazy_placeholder will show that. If the image being lazy loaded does not have those then nothing will be specified.

You can verify this for your self by

• disable our lazy load feature,
• open an incognito window and re run the Google Page Speed test.

You will see it show those images don’t have width and height specified.

Steve