Hi @indusvalleytech
I hope you’re well today and thank you for contacting us!
I see you’re using CloudFlare for site so I can’t see where the site is hosted but please check your host cPanel (or similar management pane that you have access to) and check if there’s any additional cache active.
If yes, please disable it for now.
Are you also using any other caching plugin on site? If yes, it should also be disabled for now. If you have access wot site’s back-end, you should be able to disable it from there, otherwise, you may need to do it by accessing the site via FTP (or cPanel File Manger) and renaming that other caching plugin folder in /wp-content/plugins folder.
Then the next step would be to temporarily disable Hummingbird (again – either via wp-admin if you have access to it or by renaming its folder inside /wp-content/plugins folder) and checking if the site is working after that.
If it is, then please make sure that WordPress debugging is enabled by adding these three lines to the “wp-config.php” file, right above “/* That’s all, stop editing */” line
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Once they are there browse the site (front- and back-end) for a while and check if there’s a file “debug.log” in /wp-content folder and if there are any (new) errors/issues logged in it.
The problem with the error that you are getting with Hummingbird is that it’s a “header” (as in “HTTP header”) related error and it may be directly related to Hummingbird settings headers – which it does in these lines – or that it’s sending these headers after server or other plugin already set them, in which case it would be a matter of unexpected conflict.
So by disabling other caches you’d minimize the chance for such conflicts on cache/server level. By checking debug.log we could find out if there are other errors which could possibly point to source of the conflict.
If there is no additional errors in debug.log, then a full conflict test would be required, as follows:
– keep all other caches (server/other caching plugins) disabled
– delete Hummingbird plugin folder from /wp-content/plugins folder on server
– disable all plugins (temporarily) on site and switch theme to Twenty Twenty-One
– install Hummingbird again via “Plugins -> Add new” and enable it
If the error doesn’t happen at this point:
– switch your original theme back on
– if still fine, start enabling plugins back one by one and once the error shows up again we’d know about what is causing the conflict – it would be the last enabled plugin.
Then we could see what to do next to fix it.
Let us know about results, please.
Best regards,
Adam
