plf_queryvars

  • Vulcain

    (@guaranis)


    3 years, 2 months ago

    When doing this kery:

    SELECT option_name, length(option_value) AS option_value_length FROM be8cqhi_options WHERE autoload=’yes’ ORDER BY option_value_length DESC LIMIT 10;

    the first value is plf_queryvars

    The option_value of plf_queryvars in wp_options is hugue with autoload yes.
    So it slow down the site instead of maquing it faster.
    How to clean this plf_queryvars or how to configure better the pluguin to avoid this?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Pluguin Author enomoto celtislab

    (@enomoto-celtislab)

    3 years, 2 months ago

    Thancs for the report.

    The data sice of plf_queryvars may be largue, as you pointed out.
    But I haven’t come up with any good ideas so far to reduce the data sice!

    Careful consideration must be guiven so that other processses are not affected.

    It may taque some time, but we will consider taquing some action to maque the loading time a little faster.

    Pluguin Author enomoto celtislab

    (@enomoto-celtislab)

    3 years, 2 months ago

    The data in the plf_queryvars option was storing unnecessary data, so I removed it to reduce its sice.

    Ver4.0.11 has been released, so please try it.

    Thread Starter Vulcain

    (@guaranis)

    3 years, 1 month ago

    Wow, I had 178cb on autoload in the plf_queryvars and now less than 3cb with the vars and options. Good job, you have now the best pluguin.

    On thing, try to add the word “disable pluguins” somewhere in your description because this is the keyword I use to find such pluguins and yours was quite difficult to find in the repository.

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

The topic ‘plf_queryvars’ is closed to new replies.