Support » Theme: Blocksy » Latest update 1.8.2 had fatal errors

  • Resolved monkeydluffy

    (@monkeydluffy)


    I have a website with elementor pro, sitground hosting and blocksy theme. I updated the blocksy theme to the 1.8.2 version and I had some fatal warnings concerning siteground optimizer. I saw that the blocksy Companion had a fix with SiteGround caches. This might be a problem when disabled.

    NGINX cache is on but the dynamic and the memcache are disabled for now. I then updated the theme and it gave me these warnings:

    Warning: scandir(): Directory name cannot be empty in /home/customer/www/WEBSITE-NAME-PRIVATE/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher.php on line 385
    
    Warning: array_diff(): Expected parameter 1 to be an array, bool given in /home/customer/www/WEBSITE-NAME-PRIVATE/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher.php on line 388
    
    Warning: Invalid argument supplied for foreach() in /home/customer/www/WEBSITE-NAME-PRIVATE/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher.php on line 390
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/customer/www/WEBSITE-NAME-PRIVATE/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher.php:385) in /home/customer/www/WEBSITE-NAME-PRIVATE/public_html/wp-includes/functions.php on line 6362
Viewing 2 replies - 1 through 2 (of 2 total)
  • Theme Author creativethemeshq

    (@creativethemeshq)

    Hello @monkeydluffy,
    The latest theme version update should resolve this issue, did you updated to the lates version?

    Theme Author creativethemeshq

    (@creativethemeshq)

    @monkeydluffy Blocksy Companion 1.8.5 solves this issue. This was caused by a piece of code that resets all the SiteGround caches upon Blocksy theme/plugin update (SG changed something in their implementation recently which broke our code). The update that is now live is free of this and the mentioned exception won’t be raised again.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.