wp_options w3tc_pagespeed_data_ still autoloaded

  • Resolved T4ng

    (@schwipps)


    7 months, 1 week ago

    Hi there,

    I’ve just inspected my wp_options table for autoloaded options and noticed a lot of w3tc_pagespeed_data_[mysitename] entries, with autoload set to “yes”.

    Then I found this ticket where you, @vmarko, claim that the v2.7.0 sets the option to false for these w3tc_pagespeed_data entries (I’m using version 2.8.6)

    W3 Total Cache version 2.7.0 was recently released that includes a fix that sets the “auto-load” flag for “w3tc_pagespeed_data_[mysitename]” option to false.

    Then I found this other ticket where you say, again, that these are not autoloaded anymore.

    Sorry if I get you wrong, but why are these entries still there, with the parameter autoloaded set to ‘yes’? I basically tend to assume that:

    • Since v2.7.0, these should be set to false
    • If not, everything set to yes being autoloaded, they still are autoloaded.

    Should I remove them from the database?

    Thanks for your explanations.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    7 months, 1 week ago

    Hello @schwipps

    Thank you for reaching out and I am happy to help!
    It’s deffinatelly set to “no”, however, if you used Google Page speed tool before the 2.7.0 update, it may have been set to yes before and autoloaded in this case.
    Can you please remove it from the DB table and re-run the Google Page speed and let me know if it’s still autoloaded?

    Thank you!

    Thread Starter T4ng

    (@schwipps)

    7 months ago

    Hi,

    As suggested, I removed theses wp_options w3tc_pagespeed_data entries from the wp_options table.

    Then enabled PageSpeed again, succesfully achieved a PageSpeed Test, with results.

    After which, I can’t find any wp_options w3tc_pagespeed_data (LIKE %…%) entries in the table anymore.

    Is it the expected behavior? My understanding is that these should still be there, just not autoloaded.

    Thanks

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    7 months ago

    Hello @schwipps

    Thank you for the confirmation
    Yes, this is the expected behavior since the entry is not autoloaded in this case.

    Thanks!

    Thread Starter T4ng

    (@schwipps)

    7 months ago

    OK.

    Now, I don’t want to keep that PageSpeed function on, so removed the access. So now, I get 401 errors from the general thumb.

    View post on imgur.com
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    7 months ago

    Hello @schwipps

    Thank yopu for your feedback.
    Have you shared any screenshot because I am unable to see anything

    Thanks!

    Thread Starter T4ng

    (@schwipps)

    6 months, 3 weeks ago

    Mmh, surprizing, I can see it from the editor and the page while not connected.

    Anyway… Here is the link to the screenshot: https://imgur.com/ts15ItT

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    6 months, 2 weeks ago

    Hello @schwipps

    Sorry for the late reply.
    I was not able to replciate this. Can you pelase let me know if you used gmail to authorize this?
    Do you have any security plugins that may be blocking the requests?
    Thanks!

    Thread Starter T4ng

    (@schwipps)

    6 months, 2 weeks ago

    As explained, I didn’t want to keep that PageSpeed functionnality on, so disabled it. So there shouldn’t be any further request to PageSpeed.

    Therefore, the question was not “Why PageSpeed requests won’t go through?”, but rather “Why do I stil get a W3TC>PageSpeed error, thus PageSpeed requests at all?”

    Anyway, I just re-enabled / disabled the PageSpeed authorization. Which was followed with that message:

    View post on imgur.com

    … and I don’t see any error message anymore.

    I don’t know what happened during my last request, but this seems solved now.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘wp_options w3tc_pagespeed_data_ still autoloaded’ is closed to new replies.