I’ve searched and searched for help. I haven’t messed with my website for quite a few months (personal issues), but now I need to get it up and running to sell my crafts with woocommerce. A window on top woocommerce CONSTANTLY tells me to update the database. I hit the update button and it immediately errors on a new page saying “Sorry, you are not allowed to access this page.”. I’ve turned off ALL plugins and still the same. I’ve validated the database header in the login.php file to the header on my phpadmin. Still the same one since I created the website in 2016. I tried to run the database update in woocommerce/status/tools/ It tells me it is scheduled in the background. But if I look in the scheduled actions, nothing. Of course as soon as I hit the update, that window on top warning to update the database. I even ftp to my website and completely deleted the woocommerce plugin since the delete is greyed out in the plugins section. When I reinstalled woocommerce, everything is the same, like it never got deleted. I am pulling my hair out how to fix this. Can anyone help please?
I’ve already deactivated ALL plugins, uninstalled woocommerce and reinstalled it. After that I looked in the settings and it’s like it never got uninstalled. Anyway, here is a screen shot of the console from the browser inspect when I hit the “update database”
The page /wp-admin/admin.php?page=stats to my knowledge, relates to Jetpack stats page. Does it help if you re-activate Jetpack, make sure it is connected to WordPress.com services and the stats module enabled?
Currently the Jetpack plugin is off, and the stats page is invalid, probably why you see the error.
You can re-enable it and see if you still get the error in the console, or something else when you click on “update now”
Interesting. Unfortunately I removed that quite a while ago because it was giving me other issues and I can’t remember what, but removing it cleared it up. But I DO NOT like plugins that when you deactivate or especially delete the plugin, a bunch of crap remain. That is BAD BAD progrmming and should be reported.
The next problem is.. I have no clue which jetpack it was. There are a dozen different ones and I AM NOT going to install all of them. Is there any way to clean up their garbage that the plugin left?
Thanks for the clarification. You can install Jetpack from this link: https://ww.wp.xz.cn/plugins/jetpack/, connect your site to WordPress.com, and then test again to see if the issue is resolved.
If you later choose to uninstall it, be sure to use a plugin like Advanced Database Cleaner after deleting Jetpack to remove any leftover data it may leave behind.
Ok, as I said before, I do not want to reinstall jetpack. I’ve had serious issues with it in the past and I do not want it on my website anymore. Perhaps this issue is a darn good reason why folks should be reporting jetpack as garbage! I did install that WB DB Cleaner and ran the cleanup, then deleted anything related to jetpack. Unfortunately, the woocommerce database update still goes to “not allowed” This is totally ridculous. And I am now beginning to believe that the jetpack once again screwed my website over and now I don’t know how to fix it without wiping the whole website and starting over. Since the website (and database) are messed up, backing this up is worthless. Last time I wiped my website clean, I used ftp and just deleted everything. But that took a few hours since there were so many files and directories. Is there a faster way to wipe it clean and start a new?
The URL i mentioned can remain in the system, despite Jetpack being removed and despite Jetpack ensuring all clean up on its end. It can remain if there is a layer of caching that is still holding on to that URL. I see in the back scroll that you have cleared the server cache. It would be great if you can check once with your hosting provider if they have any other layer of caching that could cause this, to rule out cache.
I request you to try these steps once too:
Browse to WooCommerce > Status > Tools
Click the Clear transients button beside WooCommerce transients and Expired transients
Click the Clear button along Clear system status theme info cache , Clear analytics cache and Clear template cache
I understand how exhausting this has been since you’ve gone through a lot of troubleshooting already.
From everything you’ve described, it sounds like the database has already been updated, but WooCommerce is stuck showing the banner due to some lingering cache, transients, or old scheduled tasks. The “Sorry, you are not allowed to access this page” message might be pointing to an old or broken link, especially if Jetpack used to be installed and left behind a trace.
Let’s try this final round of cleanup:
Go to WooCommerce > Status > Tools
Click the following buttons to clear: a) WooCommerce transients b) Expired transients c) Analytics cache d) Template cache e) Theme info cache
Install the free plugin WP Crontrol from the Plugins menu
Go to Tools > Cron Events a) Look for any tasks related to woocommerce_db_update or wc_update b) If you see any stuck or overdue ones, you can safely delete them
Lastly, if the notice still shows up but your store is running fine, you can temporarily hide it using a small code snippet via the “Code Snippets” plugin:
Hopefully, this will get things back to normal and finally stop that banner from haunting your dashboard. Let us know how it goes, rooting for you to get this resolved!
Ok, I did everything you asked about clearing transients. I installed and searched the WP Crontrol and didn’t find anything abnormal. There were 2 events failed. I deleted them but they were nothing to do with woocommerce. I installed and run the snippet. I am STILL getting the update woocommerce database message. And I get the “not allowed” when I hit the update.
Yes, the store is running fine. But I only have one main product roght now and I am afraid to add anymore with this persistent issue.
Btw, in that WP Crontrol, there are a bunch of jetpack event. I try to delete them and the screen refreshes and they are right back. As I said, I believe that jetpack is the root of ALL my problems and it is a nightmare to me. My only recorse is the wipe the server and start over. Of course I will never install that jetpack.
I took a closer look at your site’s ( https://abovecreations.com ) source code and found some peculiarities. I am adding a few technical details here, not to overwhelm you, but to perhaps help other volunteers or staff to troubleshoot this better:
1. On a usual WordPress site, within the browser tools Source tab, we generally see WordPress related folders like wp-content https://snipboard.io/yxgbeO.jpg
2. On your site I seem to see a different folder structure, as though your site is using a headless WordPress implementation, where the site hosts only static files.
If you are unaware of this, you may want to check with the site host ( ?Hostinger?) in case they are doing any minification or site acceleration. It would be good if they can momentarily disable it, or exclude the admin pages from it. You will also need to ask them to purge any cache of the admin section they may have at their end.
Unless you do this, no matter what changes you do on the database or the site, the cached page of the admin that is being served will not see that the DB is already updated, and will continue to show a banner. It will then point to a page that is invalid giving you the error.
Ok, I asked my host about this and they replied with this:
Hostinger does not automatically apply minification or site acceleration to your website by default; these features must be enabled through plugins or specific settings in your website's CMS, such as WordPress. If you are seeing references to "Drupal 11" in your WordPress web pages, this is unusual and may indicate leftover code, a plugin conflict, or a file mix-up. Please check your installed plugins and themes for anything related to Drupal, and review your site's files for unexpected content. If you need further help, let me know your website's domain so I can provide more targeted guidance.
Also, in both the Cron Events, I am seeing 4 cron jobs schedule by Jetpack. jetpack_sync_full_cron every 5 minutes jetpack_sync_cron every 5 minutes jetpack_clean_nones every hour jetpack_v2_heartbeat daily I select them and apply to delete. A message claims they were deleted, but they reappear. I am telling you, that jetpack is the source of ALL my problems, I do believe. I don’t know how to clean this crap up and I was going to wipe my website ans start over but I can’t. There are just too many settings that would take alot of resources to redo. Such as google links, stripe links, woocommerce payment stuff. Many of these things were established over a long period of time and I could chance lossing those settings. I NEED to get this jetpack crap OUT of my website!
Ok, I am getting desperate. I went ahead and reinstalled the jetpack plugin. Perhaps possibly it may shed some light to my issue(s). So now I still see the message that the woocommerce database was updated each time I go to the dashboard. Then I click woocommerce and there is the message window asking to update the woocommerce database. I click the update button and NOW it goes to the Jetpack Stats page. So I go back to woocommerce and there the the message window STILL asking to update the woocommerce database.
So now it is a fact. Jetpack is responsible for that broken link prior to installing jetpack. Is there some way to positively get rid of jetpack and ALL of its crap screwing up my website? Again, they (jetpack people) should be reported! I’m sure I’m not alone in this nightmare.
Thanks for reaching out to the host and getting their reply.
Jetpack services are essential sometimes, for instance, if you use WooPayments. In that case Jetpack services ( not the plugin ) are used to render essential services for payments and correct fees to get applied.
Not ruling out leftover Jetpack code, but there is certainly something else happening on your site, since Jetpack would not inject a Drupal meta in your site header as shown. There is some plugin related to acceleration / speed / caching, or mobile optimization, that is causing Drupal to show. There is a layer of caching happening somewhere, else you would see the folder structure I shared in the screenshot. Sorry for not being too helpful here.
Thanks again for your detailed updates, and we truly appreciate your persistence in getting this resolved.
After a closer review of your site’s status, I can confirm that your WooCommerce database is fully up to date (currently at version 9.9.5). The message you’re seeing is most likely just a leftover notification, not an error, and your store is functioning correctly.
To help us understand exactly what’s triggering the message, could you please share a screenshot of the update notice you see? There are a few different types of notices, and the wording can tell us what’s actually causing it. You can use https://snipboard.io to share the screenshot.
It’s also possible that a background job responsible for the upgrade (run via something called Action Scheduler) is stuck or was skipped. We’ll be happy to help check that further once we see the message itself.
Also, just to clarify, WooPayments uses a Jetpack connection in the background for essential services like handling payments and fees. This doesn’t mean Jetpack the plugin needs to be actively used for other features, but a connection is still present.
Looking forward to your screenshot, that’ll help us get to the bottom of this for good!
I just checked the site and it does not seem to be showing the Drupal header or the static generator type files. I am seeing a proper WordPress file structure now.
Ok, the screenshot of when I click the woocommerce button.
And the only thing I done different is that reinstalled the Jetpack plugin. I didn’t do anything different besides anything you all asked me to install or preform. Hopefully you can help indentify what is causing this database message and I reslly want to uninstall the jetpack plugin. I do not like it and I think it is the root cause of all my issues. But I’ll wait to uninstall it for now.
