Hi Rikard,

We used query monitor – It doesnt tell us anything useful.
It appears there is a memory leak somewhere or something in Enfold is picking up the wrong memory limit when it isnt specified.

For our site we just had to tell wordpress what the memory limits are by adding the following to wp-config.php
For us the 2gb limit per action looks like this:

define('WP_MEMORY_LIMIT', '2048M');
define('WP_MAX_MEMORY_LIMIT', '2048M');

For some reason the error code in the console was suggesting that the memory limit was around 512mb (written in bytes).

For context we actually have a 4gb memory limit – So there shouldnt have been a problem anyway but specifying a figure in wp-config seems to have solved the issue. I’ll report back if I can recreate it again.

The problem does not occur in PHP 8.0 but does occur in all versions above this.
With this in place the problem seems to have stopped and we are running PHP 8.2 again now. So it looks like there is an issue with the memory allocated to some actions in Enfolds interface not able to use the available ram fully.

Someone else reported a simillar issue here:

I was writing a reply on the post above explaining this when you closed it too early!!!!
Can you reopen it and add my suggestion above!

If you want me to raise this on github with screenshots please let me know.

Hi Mike,

Can you send me a link to the Github account so I can raise the concern?

This has effectively increased the capacity of our dedicated server from about 300 websites to about 1000.

The ramifications of this problem are huge.

Following on from this

I can 100% confirm this was the cause of our server issues.

Essentially ALL Enfold websites with WooCommerce installed will gradually use up the ram and see mysql memory usage rise until the server crashes.

The bots getting stuck crawling all of the ?avia_extended_shop_select=yes queries includes:
Even with the rel-nofollow:
Bing bot
Google bot
A majority of major search engines
AI crawlers – New aggressive bots that ignore all instructions

See screenshot of the before and after. Our Ram use fell from almost 90GB of ram used to 8GB used on average.
Physical Ram usage screenshot
https://www.dropbox.com/scl/fi/tw8p399gfdr9cclorc5j9/ramuse-screenshot.PNG?rlkey=d9ty4xvui4w3m2ycb9b9ez94s&st=28aameqn&dl=0
Mysql memory usage screenshot
https://www.dropbox.com/scl/fi/iixhdd5vpe7253tbavbxf/mysql-memory-usage.PNG?rlkey=15061shf0haiu3d36cdy0be3t&st=ep9fncx5&dl=0

SOLUTION
I propose that Enfold removes the custom sort by options and reinstates the default Woocommerce ones.
The defaults use form fields and JS so there are no a href links in the default woo sort by dropdown. Bots cannot follow these links because there are no urls in the HTML.

In your child theme functions.php add the following to remove the enfold filters and reinstate the woo ones.

// remove the enfold sort by filters
function avia_woocommerce_frontend_search_params()
{
   return;
}
// reinstate the woo default sort by filters
add_action( 'woocommerce_before_shop_loop', 'woocommerce_catalog_ordering', 20 );

Add the following CSS to quick CSS and tweak depending on your sidebar position:

.sort-param-count {
display:none;
}
.product-sorting {
padding-top:0px;
}
div .product-sorting ul, div .product-sorting li {
font-size: 16px;
}
div .product-sorting ul {
width: 200px;
}
.main_color .sort-param a {
    color: #000000;
}
.sort-param-sort a, ul.sort-param-order {
border: 1px;
border-color: #969696;
border-style: solid;
}
@media only screen and (max-width: 767px) {
    .responsive #top .woocommerce-ordering {
        position: relative;
        float: left;
        clear: both;
        margin: 0;
        padding-bottom: 25px;
        padding-top: 15px;
        top: 0px;
    }
}
@media only screen and (min-width: 768px) {
    .responsive #top .woocommerce-ordering {
        position: relative;
        float: left;
        clear: both;
        margin: 0;
        padding-bottom: 25px;
        padding-top: 15px;
        top: 0px;
    }
}
#top.woocommerce-page .woocommerce-ordering select {
width: 100%;
font-size:16px;
}

Install the Redirection Plugin:

Add the following RegEX expression to redirect the queries so that the URL redirects BEFORE the query runs on the DB

Source URL: ^/(.*?)/\?avia_extended_shop_select=.*
Enable: Ignore Case, Regex and Ignore Slash
Target URL: /$1/
Hit Save
This will redirect any attempt to crawl the enfold filters back to the current category

Thats a good shout! I’ll investigate this further. At least we have identified that the video was the problem not enfold!

Cloud Convert seems to encode well with a good balance of compression. We will try tweaking the settings in VLC as the output file was about 50% smaller.

The Location it is scrolling to on the page is also slightly off. Scrolling too far down not showing the accordian tab itself.

I’ve sent it to the email on your website. Thanks Guenii, Really appreciate your help.

Thanks Gunter

Well swap it on our test site and reply back shortly.

Hi Guenni007,

Thanks for this. I can see it seems to be working on your test server.

This is odd as our test was stock enfold without a child theme.

Im going to download your video from your test site and try looping that in our demo site and see if it works.

Hi Gunter,

No change here.

It still doesnt work.

If you open one accordian tab and change the # to the next tab in the list it disappears completely.

Hi
This requires investigation none of the video options are looping in the current version of enfold (6.04)
Please can you take a look at this in a clean version of enfold
Thank you

• This reply was modified 3 months, 3 weeks ago by thinkjarvis.

Hi Gunter,

I’ll try disabling the plugins and report back.

Solution: Reinstate the default woo dropdowns – Applies to all Enfold sites:

The default woo filters are dequeued in enfold > config-woocommerce > config.php and config-365.php

We can requeue them and disable the Enfold filters by adding the following to functions.php in the child theme:

// Removes Enfolds sort by dropdowns
function avia_woocommerce_frontend_search_params()
{
   return;
}

// Re-adds the default sortby dropdown
add_action( 'woocommerce_before_shop_loop', 'woocommerce_catalog_ordering', 20 );

Styling fixes
Add the following css:

@media only screen and (max-width: 767px) {
    .responsive #top .woocommerce-ordering {
        position: relative;
        float: left;
        clear: both;
        margin: 0;
        padding-bottom: 0px;
        padding-top: 15px;
        top: 0px;
        margin-top:60px;
    }
}

@media only screen and (min-width: 768px) {
    .responsive #top .woocommerce-ordering {
        position: relative;
        float: left;
        clear: both;
        margin: 0;
        padding-bottom: 15px;
        padding-top: 15px;
        top: 0px;
        margin-top:0px;
    }
}

#top.woocommerce-page .woocommerce-ordering select {
width: 100%;
font-size:16px;
padding: 8px;
line-height: 1.2em;
}

• This reply was modified 3 months, 4 weeks ago by thinkjarvis.

If you look at the default store front theme
It has two filters not three I think this is the root cause of the problem.
https://themes.woocommerce.com/storefront/shop/?orderby=price-desc
https://themes.woocommerce.com/storefront/shop/?orderby=price-asc

Why are we adding the extra parameter for
?avia_extended_shop_select=yes
and
product_order=price when the default woo filters dont use these queries at all?

Is there a way to just use the default woocommerce filters instead of the modified Enfold ones?

• This reply was modified 4 months, 1 week ago by thinkjarvis.
• This reply was modified 4 months, 1 week ago by thinkjarvis.