Lee Hodson (VR51)

I have the same bug. I have spoken with Spectra (Brainstormforce) about it but they seem unwilling to remove the plugin component that causes the fault.

For me the bug shows when using WP LiteSpeed Cache. When WPLS is disabled Spectra stops collecting the data. I think I know roughly what’s happening. Maybe this info will help Spectra solve the problem.

Thanks to your tip about setting autoload to ‘no’ on the ‘spectra_blocks_count_status’ row I now see that when WPLS is enabled that row reverts back to autoload=yes. I tested several times.

The issue appears to not happen when other cache plugins are used (I’ve tried with a few of them). With WPLS disabled I can set autoload=no and it will stay as autoload=no. Immediately I enable WPLS autoload=no switches to autoload=yes and within 2 minutes I have a wp_options table exceeding 2GB in size.

On a VPS server or any server with finite storage space, when the InnoDB database grows beyond the server’s storage capacity the database server crashes. That crash can damage any databases beyond repair. It happened to me twice on two different servers due to this bug in Spectra.

WPLS is a good plugin. Spectra was a great plugin. I just wish Spectra would fix this bug and stop denying that it exists. What do they want the data for? Is it even legal for Spectra to keep collecting the data?

This bug still exists in Spectra version 2.0.15.

When I activate the plugin Spectra begins to fill my wp_options table with data. Today, after the plugin update, I activated the plugin and watched my wp_options table grow from 40MB to over 800MB in under 10 minutes. I had to deactivate the plugin again and delete the bumph data.

Can you please take another look at this issue?

It’s not quite resolved.

For others who find this support request, the plugin had a bug introduced in version 2.0.12. This bug caused the plugin to fill up the database. The database in my particular site went from approx 200MB to over 50GB in the course of 24 hours, growing at about 1GB per 30 to 40 minutes. The bug is said to have been fixed in version 2.0.13. The BSF support team suggested I upgrade the plugin to version 2.0.14, which was already in use within my site.

The solution I came to was to delete the excess data. BSF were unable to advise me whether doing so would affect Spectra blocks in posts and thus affect the content of posts that contained Spectra blocks. I still have had no reply on this.

If your database is overflowing because of the fixed (?) bug in Spectra you can use the following SQL query in PhpMyAdmin to delete those superfluous rows of data (there should be backticks around wp_options, option_name and wp_collect_spectra_blocks_count_batch_%).

DELETE FROMwp_optionsWHEREoption_nameLIKE ('wp_collect_spectra_blocks_count_batch_%');

0. Take a backup of your database first, if you can do.
1. Open the affected database in PhpMyAdmin
2. Go to the SQL tab in PhpMyAdmin
3. Place the SQL query into the form and change wp_options to the name of your wp_options table.

Good Luck!

Not that I can see within the HTML of the site or the HTML of the embedded iframes.

Here is an example of an iframe (sensitive elements replaced by #[explanation]):

<iframe frameborder="0" src="#[add_script_location]" id="google_ads_iframe_/1030006/#[domain]/sticky_sidebar_0" title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="1" height="1" data-is-safeframe="true" sandbox="allow-forms allow-pointer-lock allow-popups allow-popups-to-escape-sandbox allow-same-origin allow-scripts allow-top-navigation-by-user-activation" data-google-container-id="3" style="border: 0px; vertical-align: bottom; height: 600px; width: 300px;" data-load-complete="true"></iframe>

Inspector shows loads of other HTML loaded by the iframe. I’m not seeing a ‘lazyload’ added to any part of the embedded content nor added to any of the site’s HTML (I keep lazyloading disabled because it affects the ads).

However…

The advertiser’s script includes ‘lazy: true’ e.g,

<script type="text/javascript">(function(w, d, s, id) {
  w.PUBX=w.PUBX || {pub: "#[domain]", discover: true, lazy: true};
  var js, pjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id; js.async = true;
  js.src = "//main.pubexchange.com/loader.min.js";
  pjs.parentNode.insertBefore(js, pjs);
}(window, document, "script", "pubexchange-jssdk"));</script>

The included external script also includes the word ‘lazy’: https://main.pubexchange.com/loader.min.js

I assume ‘lazy’ in the ad network’s scripts means lazyload.

Hi James. Thanks for this info. I realised after I posted the support request.

Was unable to modify the request because all my content is being held for moderation. Every. Single. Post.

I have the same problem. There must be a flag in the database that records whether the index upgrade occurred or not. I’m having a whale of a time looking for the flag ; that’s if it exists at all.

You can do the same by going to Dashboard > SEO > Tools. The button there might work for you.

Marc, thank you very much for looking into my suggestions.

I look forward to seeing the future of WP Optimize.

You can get the 5.x version from the Internet Archive 11th Feb snapshot of https://www.ads-software.com/plugins/google-analytics-dashboard-for-wp/

@phpbits I do confirm that the new post-meta file resolves the issue.

@phpbits and @brechtvds thank you both for your help with this.

Looks good on my end. Thank you so much, Aaron.

You would be surprised how some sites are set up. Generally, I agree with you. What if the page is put into draft, will that trigger 404 Solution when the page is requested?

Edit: I can answer that. Putting a post/page into draft triggers 404 Solution redirects for anonymous visitors but not for logged in users with permission to view or edit draft posts.

• This reply was modified 5 years ago by Lee Hodson (VR51).

You did understand correctly. I thought 404 could be used to create general redirects too?

I know what is happening.

404 Solution is ignoring manual redirects created for pages that actually exist within the site. I tested this with a dummy page. Once a redirected page is removed from the site the redirect begins to work again.

There has been nothing new added to the debug log.

Thanks Aaron. I must have edited my post while you were writing your reply. The debug log is empty. No new items were written to it. It is as though 404 Solution is not seeing the page request.

In a couple of hours I will retest. Could be a quirk in the network used by the host. Maybe there’s some request caching going on.