Support » Plugin: Fast Velocity Minify » Transients not all cleared on FVM Purge

  • Resolved G

    (@gnetworkau)



    Hi Raul, I noticed a while ago (1-2 months) that FVM was producing more transients in database – I am on Multisite. I have been clearing them manually to reduce database bloating. Even after doing FVM Purge their remain hundreds of transients. Is it possible when doing FVM Purge to have all transients deleted automatically?
    Regards, George

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Raul Peixoto

    (@alignak)

    Hi,

    Being a multisite setup, chance is that each site has its own set of transients.

    A FVM purge, should only delete it for the specific site you run that for, because each site may have a different owner…

    Is it that if you purge cache on site A, those transients are still not being deleted on the table, specifically for site A?

    G

    (@gnetworkau)

    Hi Raul,
    what I noticed was that after making changes to CSS, there would be more transients created. The more edits, the more transients. After doing FVM purge, which purges all sites, many transients would remain for the site that I had been editing.
    The transients stay under control generally, but if I do edits, I have to clear ALL transients as well as do FVM purge – otherwise there will be too many residual transients.
    It doesn’t bother me much, but if you could make all the transients disappear on a purge it would be great.

    Plugin Author Raul Peixoto

    (@alignak)

    As soon as your css files change there will be more transients, because immediately after purging, FVM will try to create new ones on a per request basis, unless there’s zero traffic on the frontend.

    I switched from transients to disk files sometime ago, so please make sure to update.

    But I may have forgotten some old transients code… I’ll take a look at this soon and see if that could be the case.

    G

    (@gnetworkau)

    I have the latest version. It may help if I de-activate and activate it again? Then I will keep an eye on it and report back soon too.
    cheers.

    G

    (@gnetworkau)

    After re-activating, transients are still produced, in this form:
    _transient_fvm-cache-1535113909f4a01f30
    _transient_timeout_fvm-cache-1535113909f08621d5

    Plugin Author Raul Peixoto

    (@alignak)

    Thanks, I found out some old code that was causing this.
    Will release a version asap with these and other fixes.

    G

    (@gnetworkau)

    Thanks, keep up the good work!

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