Forum Replies Created

Viewing 15 replies - 1 through 15 (of 97 total)
  • Leopard-Lady


    Hi Guys – @hongpong and @kouteki
    Forgive me, but I’m confused as to which of you is taking care of this plugin now?

    And which update to go with?

    I’m currently running Nemanja’s v1.11.8

    @hongpong – is your update different from this and better in some way?

    @kouteki – I am running PHP v7.3.4 and it seems to be running fine. I don’t see any errors in the debug log. Unfortunately, I’m not able to test it with PHP Compatibility Checker for you, as they have not yet implemented testing with PHP 7.3.x

    @forest-skills – Thank you for your added input on this 🙂

    Thanks guys,



    Hi Nemanja – @kouteki
    I just realized I should NOT have posted this issue to you. 404 header status output has nothing at all to do with your plugin ==> DUH!!! I am so sorry.

    Thank you for all your hard work on Broken Link Checker! I’ve relied on it for a few years now. It seems to always work very well.

    Again, my apologies for this post. You can delete even, if you’d like.

    Have a good day,



    Hi Joel – @joelcj91
    This is awesome good news. Thank you for working on a way to implement this.

    As thoughton pointed out, it is troublesome that the 404 header is not fired correctly. And not only from the perspective of search engines indexing non-existant or removed page URLs, but also in regards to external broken link checkers and even broken link check plugins. They’re all looking for the 404 status code.

    You might be interested in another discussion on this matter. Turns out cache plugins play a significant part in this too. I’ve done quite a bit of research on this and posted my findings in the other discussion. I don’t want to overload this discussion by pasting all of the info over here too.

    Here is the other discussion ==>


    Hi @thoughton
    It turns out my advice above to use the 404Page plugin in conjunction with this one (404 to 301) is NOT a solution after all.

    2 problems arose:
    1 – Cache plugins serving up the error URL as 200 status
    2 – It very quickly STOPPED this plugin from working correctly

    Apparently, my post above is now too old for me to be able to edit or delete it.

    Please see the link above to the other discussion to better understand the other issues that come into play on this.

    Also, you can use Bing Webmaster Tools to remove your unpublished pages and error URL’s from their index 🙂


    The more I dig into this issue, the more problems I’m finding in regards to WordPress properly handling 404’s in general. The problem is present in themes and plugins not handling it correctly.

    You’d think by now WordPress would have a better solution for managing 404’s. As it is, WordPress and many themes DO have a 404 template that fires the 404 status correctly. BUT most people are not able to properly set up their desired design and layout on them because it has to be hard-coded. There is no way to handle them in the page editor.


    Joel – @joelcj91
    Please do let us know when you have this figured out.

    I’d be happy to test it for you too before you release it 🙂

    Thanks guys!!

    Hi @bungeshea
    Thank you for your help with this. Very kind of you.

    Here is my CSP header – currently in report only mode as I continue to fine tune it AND figure out how to unset it in the admin area:

    add_header Content-Security-Policy-Report-Only "default-src https:; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline'; img-src 'self' https:; font-src 'self'; connect-src 'self'; child-src 'self'; form-action 'self' https:; upgrade-insecure-requests; block-all-mixed-content; report-uri;";

    Thank you,

    I’m seeing this on a couple of sites too.

    They are currently running WP v4.9.8 and do NOT show WP needs to be updated to v5.1.1

    I run “check again” and still no update options.

    These sites are hosted at HostGator on a dedicated server with cPanel. In both cases cPanel was NOT used to install and manage WP. WP was installed manually on both.

    Has anyone figured this out yet?

    Thank you,

    Thank you for your reply @bungeshea

    I realize I can set the CSP header via the .conf file.

    My question is: once the CSP header has been set up for the front-end of the site is it possible to “UNSET” or “REMOVE” it in the WP admin area via functions?

    CSP headers render the WP admin area nearly useless.

    I’ve tried everything I can find to use via functions – ie. header_remove, header_unset, <location…> based. Nothing is working.

    Thank you,

    I second this request, please.
    7.3 released over 3 months ago.
    Thanks guys! Your plugin ROCKS!



    Hi Guys,
    I am having the same issues as @synchro, and I’m sure thousands of others trying to better secure their WP sites.

    I just checked your changelog and see no mention of this as of yet.

    Are you guys in fact working on a long term solution to remedy this security issue with your plugin?

    Thank you,

    Hi Peter,
    Just touching base to see if you’ve been able to figure anything out on this issue yet?
    Thank you,

    Hi Peter – @petersplugins,
    Thank you for your reply. I dug into this last night. Here is what I’ve come up with so far:

    Please try to activate the “Force 404 error after loading page” option

    This did NOT resolve the issue.

    WP Fastest Cache does not allow to exclude a page from caching. Excluding is only possible by URL

    Using search query “exclude a page from caching in WP Fastest Cache” several pages reference how to do this.

    The first 2 in particular are of intereset:
    1 – Exclude Page
    2 – Ultimate Guide To WP Fastest Cache

    So, here’s what I’m thinking on this issue . . .

    – With 404to301 all 404’s resolve on my custom error page URL = /error404/
    – 404to301 does log the ACTUAL 404 URL in the back-end to manage them

    – With 404Page all 404’s resolve to the ACTUAL 404 URL, instead of my custom error page URL

    – EXAMPLE: using this broken URL –
    – 404to301 resolves to –
    – 404Page resolves to –

    It seems the first step would be for 404Page to resolve all broken URLs to the custom page URL as 404to301 does.

    This would allow us to exclude this page from caching in WP Fastest Cache via manually adding the exclusion – yes?

    Also, this would prevent Google from indexing all of the broken URL’s from cache – yes? — I could see this particular issue becoming an SEO nightmare.

    Automatically excluding the page from caching is a planned feature for a future version. The first caching plugin I’ll care of is WP Super Cache. Maybe I can add this for WP Fastest Cache also sometime in the future.

    It looks like the solution to this is NOT actually plugin specific, just simply “cache” function regardless of cache method.

    By using: define( ‘DONOTCACHEPAGE’, TRUE ); seems best option
    Or possibly: Filters ‘bypass_cache’ maybe?

    There are several threads on here regarding “donotcachepage” method.

    These 3 in particular may be of interest to you:
    Creating a custom header if DONOTCACHEPAGE is True
    How to Exclude a page from being Cached
    DONOTCACHEPAGE for this plug-in

    There are a couple threads regarding Filters ‘bypass_cache’:
    Filters ‘bypass_cache’ not working
    How to exclude CPT Archive from cache

    It seems that “donotcachepage” method is the best option of the two?

    Lastly, I am stumped as to why 404to301 stopped working? Right at first when I enabled 404Page both plugins worked just fine. Then 404to301 stopped unless/until I disabled 404Page. — Don’t know if this comes into play on this issue or not, but after installing 404Page, I did run 2 plugin updates and those were:
    – CAOS for Analytics
    – WP Fastest Cache

    I’m inclined to think it was the WP Fastest Cache update that caused them to no longer work together? – Let me know if you want me to test this by rolling WP Fastest Cache back to the previous version to see if they work together again.

    Getting the 404 header status code correct is an issue I really need to get resolved, as I’m sure many others do as well.

    Appreciate your time and help on this, Peter! You ROCK!

    Best regards,

    • This reply was modified 3 months, 3 weeks ago by Leopard-Lady.

    I’ve found a simple solution to this problem and want to share it with others having the same problem.

    Install the 404page plugin –

    Follow the instructions to select your custom 404 page, leave the Send an 404 error if the page is accessed directly by its URL setting enabled AND also enable Activate Compatibility Mode — compatibility mode ensures that these 2 plugins work correctly with each other.

    Now your custom 404 page outputs the proper 404 HTTP header status code AND you still have all of the functions of the 404 to 301 plugin.

    I use 404 to 301 because I want to receive immediate notification of 404’s on my sites and have the ability to easily redirect them from the 404 logs. This helps me to control redirects for SEO purposes, alerts me to unintentional 404’s due to errors I’ve made and also makes it easy to add nefarious IP’s to my WordFence firewall blocking rules for tighter security management.

    Hi Peter,
    My pleasure to post a review for you! Your plugin helped me solve a long standing problem in a matter of 60 seconds 🙂

    I use 404 to 301 because I want to receive immediate notification of 404’s on my sites and have the ability to easily redirect them from the 404 logs. This helps me to control redirects for SEO purposes, alerts me to unintentional 404’s due to errors I’ve made and also makes it easy to add nefarious IP’s to my WordFence firewall blocking rules for tighter security management.

    Thank you!

    Thank you for these instructions! You saved me from my own blunder 🙂

    Hi Konstantin,
    I love the concept of your plugin. As a CDN it seems to work perfectly.

    It would be awesome if we had the option to use this ONLY as a CDN – as it stands now. In other words, the “service worker” and “PWA” options could be enabled or disabled.

    Otherwise, from the PWA perspective . . . it is difficult to figure out. There are some settings in the plugin and some settings in the Baqend dashboard. Unfortunately both areas are really lacking in documentation. And the plugin itself is lacking in ease of settings / setup.

    While you do have the “guide” it seems to mostly focus on the API and is written for tech savy people rather than the rest of us. – It does appear, via the API, it is quite extensive, but a person has to understand the API coding, where to enter it and how to customize it.

    I like Super PWA because setup is so easy, it is well documented and it is built to work with OneSignal Push Notifications. You enter your settings and the plugin takes care of the coding.

    I see that yours can also do push notifications, but the whole setup of it is confusing. I can’t figure out if it requires the use of a push notification service (like OneSignal) or not. Or whether there are tracking and statistics. Or if I can segment the subscribers.

    Again, I do think your plugin / service is a groovy concept, but I’m having a hard time figuring out how to use it. Where Super PWA makes it very simple to set up.

    Unfortunately, it looks like I’ll end up having to remove yours (sorry!), set up a CDN and use Super PWA with OneSignal to get the results I’m after.

    Is it possible to use your service as a CDN ONLY(!) on WordPress? I do like how that part of it works.

    Thank you,
    Rhonda (aka LL)

    Ok – good to know.

    I’ll leave misspellings alone from now on – LOL.

    Thank you for clearing that for me.

    Very kind of you!

Viewing 15 replies - 1 through 15 (of 97 total)