nestormarius

Hey! Ah, ok, thanks for clarifying. I’m not using WooCommerce, so there must be another plugin using Action Scheduler. Thank you for your time!

Hello, I have the same issue. I thought that you addressed this bug in the latest version of the plugin, but reinstalling it, activating the option in Advanced settings to delete all the plugin data, and uninstalling it ended up adding more orphaned tables to my database.

Now I have aioseo_cache aioseo_crawl_cleanup_blocked_args aioseo_crawl_cleanup_logs aioseo_notifications and aioseo_posts left behind in the WordPress database after uninstalling the plugin.

Is it safe to remove these tables via PhpMyAdmin? Thanks!

• This reply was modified 6 months, 1 week ago by nestormarius.

Thank you! I’ve removed the orphaned tables and it’s all good.

Hi @nawawijamili

Thank you so much for your help and quick reply. For now, I’ve increased the PHP memory limit to 512MB (the maximum allowed on my shared hosting) and enabled Real-time monitoring.

Docket Cache didn’t crash my site anymore.

I will keep monitoring this and if it crashes the site again I’ll proceed with your instructions. Thank you!

Hi @alinclamba

No, it still doesn’t work. Anyway, thanks for your help.

Best regards!

Hi @alinclamba

Thank you so much for your reply. The code snippet worked and now the data-jetpack-boost="ignore" attribute has been added to the client_main.js file when I look at the HTML output.

However, when I enable the “Defer Non-Essential JavaScript” option in Jetpack Boost, the client_main.js script no longer works as expected, therefore the site no longer functions correctly.

I should mention the fact that the script gets a ?m=1695225095 appended to the end of the file name (e.g. client_main.js?m=1695225095)

<script type='text/javascript' data-jetpack-boost=”ignore” src='/wp-content/plugins/darkmysite/assets/js/client_main.js?m=1695225095'></script>

Any ideas?

Hi @bizanimesh and thanks for your reply. Could you please help me add data-jetpack-boost=”ignore” to the code below?

client_main.js is the JS file I want Jetpack Boost to ignore when I enable the Defer Non-Essential JavaScript option.

function darkmysite_client_enqueue()
{
if($this->darkmysite_is_dark_mode_allowed()){
wp_enqueue_script('darkmysite-client-main', DARKMYSITE_JS_DIR.'client_main.js', array(), DARKMYSITE_VERSION);
}
}

Thank you!

• This reply was modified 1 year, 2 months ago by nestormarius.
• This reply was modified 1 year, 2 months ago by nestormarius.
• This reply was modified 1 year, 2 months ago by nestormarius.

Nevermind… The issue was created by Jetpack Boost which defered DarkMyStyle’s script so it was loading late, creating the white flash issue due to the white background of the theme’s default light style.

I understand. Thank you, I will continue to use your plugin only to insert AVIF images inside posts and use WebP for the featured image.

Keep up the good work!

No, we are talking about the featured images of posts. When I use WebP format, these are previewed automatically on social media (Twitter, Facebook) when pasting the post’s URL. The preview is fetched immediately along with the featured image.

When using AVIF as a featured image in a post, these are no longer fetched when sharing the post in social media.

Any recommandations? I believe that I should avoid using AVIF for featured images, right?

@spacetime thank you. I’ve only pasted the new lines you’ve added in the ad-inserter.php file, which apparently define the HTTP_HOST array key.

    $host = isset ($_SERVER ['HTTP_HOST']) ? $_SERVER ['HTTP_HOST'] : '';
    if ($host == '' && isset ($_SERVER ['SERVER_NAME'])) {
      $host = $_SERVER ['SERVER_NAME'];
    }

and changed the modified line

    $url = remove_debug_parameters_from_url ((isset ($_SERVER ['HTTPS']) && $_SERVER ['HTTPS'] === 'on' ? "https" : "http") . '://'. $host . $_SERVER ['REQUEST_URI']);

So far no more errors. Thank you!

Hello,

I had the same issue upon installing the plugin. After applying the recommendations of @nawawijamili the backend is smoother again now. Thank you!

I believe it can be fixed by adding $array['HTTP_HOST'] = [];

+1 for this feature to be implemented

v3.0.1 works without issues. Thank you!