The error notice showing on Back-end after updating the pluging

  • navas007

    (@navas007)


    4 years, 7 months ago

    Instead of this “I did the changes as per your doc. (remove Javascript and clear Before Update field and Save it, checked is there any admin like ‘systemusers’ or ‘systemuses’ or ‘woosales_wp’ no admins have in this name and re-install the theme and plugins also)”, i did all thigs then also am not getting any solution for the issue, Still am getting error notification on the back-end(https://prnt.sc/pbqaka). The filter is working fine on front-end, I don’t know why the error notification showing on the back-end. How i can fix the issue. please help…

    Mention
    “I followed the document but still the notification is showing.”

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Dmytro Holovnia

    (@dholovnia)

    4 years, 7 months ago

    Hi,

    If you will read the notification fully you will notice that there is a link “I read and understand the problem. Close it”. If you will click it back-end notification will be hidden.

    regards,
    Dima

    Thread Starter navas007

    (@navas007)

    4 years, 7 months ago

    why the error notification showing after updating?

    Plugin Author Dmytro Holovnia

    (@dholovnia)

    4 years, 6 months ago

    To notify plugin users that they could have such issue and how to resolve it.

    István

    (@juhosistvan)

    4 years, 6 months ago

    Making those changes on version 1.3.3.2 – does it resolve the security issue?
    I cannot update to the latest version (1.4.0.1), beacause it breaks wp super ache.
    I think the new version does POST request instead of GET, even if it is set to do GET instead of post, or maybe Output Buffering is in conflict with wp super cache, I don’t know. Anyway, 1.3.3.2 is working well with wp super cache, but 1.4.0.1 does not work.

    István

    (@juhosistvan)

    4 years, 6 months ago

    Errors from wp-super-cache when I enable 1.4.0.1

    Not caching POST request.
    11:02:36 1122 /URL-TO_PAGE/ wp_cache_maybe_dynamic: returned $buffer

    So it seems to me, that 1.4.0.1 is making POST request instead of GET, and that prevents WP-SUper cache from creating supercache files.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘The error notice showing on Back-end after updating the pluging’ is closed to new replies.