Forum Replies Created

Viewing 30 posts - 1 through 30 (of 433 total)
  • Author
    Posts
  • Hi Ismael,

    As per my previous response – I have swapped all of the elements from full width easy slider to background color sections. So the error is no longer present on the site.

    When you have transparent header enabled it is not running the animation properly on cached pages with a full width easy slider as the first item.

    Not sure of the cause. This is the first site we have encountered this error on.

    The client wasnt happy so I found a solution. Not ideal but works.

    I would image you have done a basic check on this function.

    The problem does not occur if you click VIEW PAGE from the bar at the top of the page.

    But it does if you reload the page or load the page from front end cache when signed out.

    Something is preventing the animation on the text running.

    I’ve swapped the elements to colour sections with background images instead of full width sliders which has solved the issue.

    But this is still a bug present in Enfold.

    Hi Ismael,

    Disabling the progress bar makes no difference.
    It is when the page is served from cache.

    It works fine when there is no caching.

    As above we have WP-Rocket running without any file processing. Something is preventing cached pages from running the animation.

    Following up on this we use WP-Rocket with no special settings. Just caching no file processing etc.

    The uncached page shows the caption and buttons

    The cached version if you return to the page again does not load them.

    in reply to: Bug – Abuse of /?avia_extended_shop_select= queries #1478310

    Hi Matt,

    Enfold have fixed the issue – However on sites where bots have alreaedy hit and created a sitemap for them to crawl – They will continue to try and crawl those links because they already know they exist.
    On new Enfold sites where Bots can no longer crawl the links – All is fine because there is no way for them to access the filter urls in the first place, therefore do not know the links exist.

    So on your existing site – Bots may continue to crawl the links for a while but should stop eventually.

    If you want to put a stop to them now. Follow my instructions to reinstate the Woocommerce defaults and add some redirects so bots can no longer access those query strings. This is what we have had to do on the sites where there are hundreds or thousands of products and categories – Otherwise the bots that are aware of the filter links will continue to crawl them.

    I hope this helps.

    You definitely had another report of a similar memory leak issue from a large blog. I mentioned it in my post above because you personally closed the issue as I was commenting on it.

    I’m going to take one more look at this but I am 99% sure this is caused by a query enfold is running which is filling the memory.

    I’ve already checked the server config several times. The PHP settings are correct and adjusting the memory limit makes no difference. It has 4gb of memory available and the server has about 100gb ram redundancy.

    Disabling caching or redis doesn’t help. This is a scalability issue with enfold – the query being ran is not getting the correct memory allocation.

    I’ll reply back again after another test.

    Hi Rikard,

    We can reliably recreate this issue.

    I need Enfold to investigate.
    I have enabled PHP 8.2 on the site in question.

    Can I send you admin access so you can see it for yourself?

    I will try deactivating some plugins and see if the problem resolves itself but there is nothing unusual about the setup of this site.

    I’ll reply back once I’ve tested things. I’ll need to clone the site to our staging area to do this.

    As above – I have disabled caching and i still get the error.

    If it were caching related then the other 70 enfold sites we have on our server would have the same issue and they dont.

    The site is extremely large so I think this is a scalability issue with Enfold and the ALB image element.

    It has thousands of images in the library.

    The issue has returned.

    We need to investigate a possible memory leak with the alb image element.

    Something is causing a memory leak or causing the query to fail.

    If we edit the homepage and then click on an image element to edit it we get an empty window and the errors below in the console in Plesk.

    If we have redis enabled:
    AH01071: Got error ‘; PHP message: PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 1310720 bytes) in /var/www/vhosts/domainname.com/httpdocs/wp-content/object-cache.php on line 2534’, referer: https://domainname.com/wp-admin/post.php?post=14&action=edit

    If we have redis disabled:
    AH01071: Got error ‘PHP message: PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 5242880 bytes) in /var/www/vhosts/domainname.com/httpdocs/wp-includes/class-wp-object-cache.php on line 239’, referer: https://domainname.com/wp-admin/post.php?post=14&action=edit

    This is accompanied by a console error:
    Failed to load resource: server responded with a status of 500 ()
    wp-admin/admin-ajax.php
    wp-admin/load-scripts.php
    I am assuming these two errors are because the process has stopped – And the cause is something to do with the issues above.

    This problem occurs in php 8.1 and above. It does not occur in php 8.0

    • This reply was modified 1 month, 4 weeks ago by thinkjarvis. Reason: extra note added

    Hi both site health and woocommerce system info show the 4gb max limit. I set 2gb because 4gb is too large and overkill.

    We run our own dedicated servers so it’s no issue with the provider. We set our own settings.

    I can confirm that there is nothing wrong with the PHP, MySQL, mariadb or Plesk config.

    The issue is for some reason some actions in the enfold builder are unable to allocate the required memory.

    My suggested solution forces WordPress to recognise the correct memory limit.

    As above the problem does not occur in php8 but started in php8.1 and above. I also checked the individual php fpm memory settings for each version.

    Adding the memory limit to the wp-config forces WordPress to accept the new value and appears to stop the process hitting a false memory limit.

    If this has fixed the problem then you guys need to investigate a possible memory leak or bug in the Avia builder in php8.1 and above.

    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!

    Following on from this – This could be caused by an assumption being made in the code somewhere.

    We have changed the PHP version back to version 8.2 latest.

    But this time added wp-config define memory limit and max memory limit lines stating 2gb max memory limit.

    The actual limit in the php settings is 4gb. but 2gb is the post max size so dont want the usage to exceed this ideally. These figures are the same for all of the php versions on our server. The only change is we defined it in WP-Config for the site.

    Upon first attempt this has worked. But quite often this has been the case so need to keep an eye on the issue.

    I guess we need to determine if anything in Enfold specifically related to the ALB image element looks for the memory limit?

    Can you let me know how we proceed with this?

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

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

    in reply to: Bug – Abuse of /?avia_extended_shop_select= queries #1474819

    Do we have any response to this yet?
    https://github.com/KriesiMedia/Enfold-Feature-Requests/issues/114

    Following my solution above to reinstate the default filters:

    I now use the following more aggressive redirect in the redirection plugin:
    Source URL: ^.*avia_extended_shop_select.*
    Enable: Ignore Case, Regex and Ignore Slash
    Target URL: https://www.domainname.com/shop/
    Hit Save

    in reply to: Bug – Abuse of /?avia_extended_shop_select= queries #1472055

    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.

    in reply to: Bug – Abuse of /?avia_extended_shop_select= queries #1472049

    I’ll be honest. I don’t know how you would recreate this without looking at an existing and well established enfold woocommerce site.

    I can provide some screenshots of the plesk logs if you like? As evidence.

    Our server is one of the most secure out there. We run three firewalls and have active malware protection. We even have bot blocking in place. But we cannot block Google and bing for obvious reasons.

    It appears that most ai bots and even Google and bing are ignoring the no follow added to the enfold filters on woocommerce sites.

    This is a really serious problem. You won’t be able to see this without a private server where you get full access to the logs.

    Please let me know if you want to see some examples. This hit every single enfold site on our server and has been going on for several years. It’s just reached a critical point due to newer ai bots joining in and crawling links they shouldn’t be.

    • This reply was modified 4 months, 1 week ago by thinkjarvis.
    in reply to: Bug – Abuse of /?avia_extended_shop_select= queries #1471720

    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

    Hi This issue has now been resolved.

    Theme Complete have updated the plugin to include the fix.

    No action to take this end.

    Cheers.

    Tom

    in reply to: Bug: No option for background video to loop #1468294

    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.

    in reply to: Bug: No option for background video to loop #1468292

    Hi Guenni,

    It was definitely an encoding issue.

    We’ve tried re-encoding the video and it runs absolutely fine

    I agree about Vimeo and youtube – But we have a specific use case for this one where it must be self hosted. (A project I hope to share assuming we can iron out the last of the bugs!)

    in reply to: toggle id’s in accordian #1468291

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

    in reply to: Bug: No option for background video to loop #1468289

    We’ve just tried re-encoding the video using cloud convert as an acid test….

    This works. Looks like our encoding wasnt right.

    Thank you for your help – Looks like we need to check the mp4 encoding settings.

    in reply to: Bug: No option for background video to loop #1468288

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

    in reply to: toggle id’s in accordian #1468287

    Hi Gunter,

    This seems to work ok if you go from a different url to a specific tab or you have anchor links on the same page

    However when you then change the ID in the address bar manually

    I.e.
    Copy and paste the url of the page the accordion is on with the ID hash:
    /pagewithaccodion/#toggle-id-1

    Then if you click in the address bar and change the #toggle-id-1 to a different ID like #toggle-id-2 then accordion toggle 2 vanishes and shifts off the page.

    So its nearly there but something isnt right still.

    in reply to: toggle id’s in accordian #1468283

    Thanks Gunter

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

    in reply to: Bug: No option for background video to loop #1468282

    We’ve tested it – The video you have used works.

    @guenni007

    can you confirm what software you used to compress or encode the video?

    We’ve used VLC media player to encode ours which is a free software.

    But we have Adobe Premier Pro and Adobe Media Encoder.

    in reply to: Bug: No option for background video to loop #1468281

    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.

    in reply to: Bug: No option for background video to loop #1468262

    Hi Ismael,

    We are using self hosted videos, not youtube. I imagine that youtube will work correctly because of how the embed works.

    Can you try uploading a video. See the link in private below;

    You can see the video plays once and then when it repeats the video doesnt actually play it just lags and plays the last second of the video.

    This applies to all enfold elements

    Colour section background video
    Easy Slider
    Full width easy slider
    full screen background slider
    ALB video element itself.

    The problem is with self hostred videos.For speed and latency reasons it would be better to host a small repeating background video locally vs on a public platform.

    in reply to: toggle id’s in accordian #1468181

    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.

Viewing 30 posts - 1 through 30 (of 433 total)