• Resolved jianping cheng

    (@chengjianping)


    When activating your plugin, the FlyingPress cache plugin will not cache, and the cache is always 0. After deactivating it, it will return to normal. How can I set it up to avoid conflicts? , URL:https://prnt.sc/2byJKDiAt0G8

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor kaggdesign

    (@kaggdesign)

    I have installed FlyingPress locally and do not see any issues. Cache is generated.

    Please note that the cache is created by default for not logged-in users only. (You can set “Cache logged in users” but it is highly not recommended unless you understand all the consequences). Therefore, to see cached page count incremented, you should open your site as not logged-in user (in incognito mode, for instance) and visit some pages.

    Plugin Contributor kaggdesign

    (@kaggdesign)

    1. On your site I see that hCaptcha is not active, but anyway, no pages are in the cache. I tried to visit some of your pages incognito – no result, they are not cached.
    2. I have mentioned that you use FlyingPress v5.1.1. I have subscription, but did not update FlyingPress for a long time and used v4. It works perfectly on some of my production websites and worked well on the local site when I answered you previously.
    3. Now I downloaded FlyingPress v5.1.1 from the official site and installed it locally. Without any other plugins activated, with the 2025 theme, it does not work at all. It creates cached HTML on disk, but doesn’t use it. Even when I enter my license in admin, it says “License Activated Successfully,” and after refreshing the page, it says again “FlyingPress is Not Activated”. Cached page count is always 0.

    Conclusion. FlyingPress v5 is buggy, and it does not create a cache even when no plugins are active. I recommend reaching out to FlyingPress authors and temporary roll back to FlyingPress v4.16.4.

    Moderator Support Moderator

    (@moderator)

    @kaggdesign “cannot ask access to you site. But if you offer it by yourself,”

    That is an admin ask, however you try to get around the rules. You’ve been placed on *modwatch* until we’re convinced such postings have stopped. Your account has *not* been banned, we just want to check things for a while before they’re public. If you wish to take issue with this, contact moderators via email at [email protected]

    While I know you have the best of intentions, forum policy is that you not ask users for admin or server access. Users on the forums are not your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
    If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
    Thankfully are other ways to get information you need:

    *Ask the user to install the Health Check plugin and get the data that way.

    *Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
    *Ask the user to create and post a link to their phpinfo(); output.
    *Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
    *Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
    *Ask the user for the step-by-step directions on how they can reproduce the problem.

    You get the idea.

    We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

    When you help users here and in public, you also help the next person with the same problem.

    And, @chengjianping, Please don’t offer to send or post logon credentials on these forums: https://ww.wp.xz.cn/support/guidelines#the-bad-stuff

    It is not OK to offer, enter, or send site credentials on these forums. Thanks for your cooperation.

    Thread Starter jianping cheng

    (@chengjianping)

    <font _mstmutation=”1″></font>I’m sorry to the moderator. He means well, and I took the initiative to make this request. Please don’t punish him. I will delete the link after he checks it. It has nothing to do with him. Thank you.

    Plugin Contributor kaggdesign

    (@kaggdesign)

    @moderator Apologies, I won’t proceed next time even if a user offers access to their site. Duly noted.

    Thank you for explanation.

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

The topic ‘Conflict with FlyingPress cache plugin’ is closed to new replies.