Hi @soulity,
Thanks for the details. This points to a failed or incomplete WooCommerce 10.5.0 update, which is why you’re seeing the missing trait error and why WooCommerce can’t be deactivated from the admin.
This usually happens when a bulk update is interrupted, leaving WooCommerce files out of sync. It’s not caused by your theme or PHP version.
What to do:
- Download a fresh copy of WooCommerce from ww.wp.xz.cn
- Connect via FTP or your host’s file manager
- Go to
wp-content/plugins/ and delete the woocommerce folder
(This will not remove orders, products, or settings)
- Upload and extract the fresh WooCommerce ZIP
- Clear caches and reload the site
- If prompted, run WooCommerce → Status → Tools → Update database
This restores the missing core files (including the RestApiCache trait) and should resolve the fatal error.
If the issue persists after a clean reinstall, please share the system status report and any new errors from the debug log.
I can confirm this — we’ve seen the same error after interrupted bulk updates.
The missing RestApiCache trait is a clear sign of an incomplete WooCommerce file set, and a clean reinstall via FTP (as described above) is the correct fix. Data won’t be lost since everything is stored in the database.
One small extra check: after reinstalling, make sure no leftover woocommerce files remain before uploading the fresh copy.
That should fully resolve it.
Hi there!
Thank you for sharing these detailed observations that’s very helpful.
We’re currently working on WooCommerce 10.5.1, which will address several critical issues identified in the recent release. Once it’s available, we recommend updating and monitoring whether the behavior persists.
We appreciate you raising this and sharing your findings with the community. If you continue to see this after updating, please let us know so we can investigate further.
In the meantime, please try deactivating WooCommerce, then deleting and reinstalling it from Plugins → Add New. This can help resolve issues caused by incomplete updates or corrupted files, while keeping your store data intact.
Once reinstalled, please check if the issue persists and let us know how it goes.
hi @saivutukuru I am experiencing a critical issue on my WooCommerce store where customers cannot complete registration due to a server error that occurs immediately after they submit the registration form.
Issue Description:
- Customers can fill out the registration form on my account page
- After clicking the “REGISTER” button, the form submits successfully
- Instead of being logged in and redirected to their account dashboard, they see:“There has been a critical error on this website.”
- The user account is created in the database (I can see new users in WordPress admin), but they cannot access the site
-
This reply was modified 4 months, 1 week ago by
soulity.
Hi,
This looks related to the same incomplete WooCommerce 10.5.0 update issue.
The fact that the user is created successfully, but the site throws a critical error immediately after registration, strongly suggests missing or mismatched WooCommerce core files (especially REST / session handling).
We’ve seen this happen when a bulk update is interrupted.
Recommended fix:
- Download a fresh copy of WooCommerce 10.5.0
- Delete the existing
wp-content/plugins/woocommerce folder via FTP
- Upload the clean plugin files
- Clear all caches
- Run the WooCommerce database update if prompted
This does not remove users, orders, or settings.
If the issue persists after a clean reinstall, enabling WP_DEBUG should reveal the exact failing file.
hi @pouyaebrhm
Hi,
Thank you for the quick response and recommendations.
I have already completed all the steps you suggested: What I’ve Done:
- Downloaded fresh WooCommerce 10.5.0 from ww.wp.xz.cn
- Deleted the entire
/wp-content/plugins/woocommerce/ folder via Hostinger File Manager
- Uploaded and extracted the clean plugin files – verified all core files are present
- Cleared all caches (site cache, browser cache, LiteSpeed cache if applicable)
- Ran WooCommerce database update – completed successfully without errors
- Verified in WooCommerce → Status – all base tables are present and correct
❌ Issue Still Persists:
After the clean reinstall:
- ✅ User accounts are still being created successfully in the database
- ✅ WordPress admin panel works perfectly
- ✅ WooCommerce settings and pages load correctly
- ❌ Customers still get “Critical Error” immediately after clicking Register
- ❌ Browser console shows:
POST https://soulity.in/my-account-2/ 500 (Internal Server Error)
Hi there!
Thank you for the details. The 500 Internal Server Error you’re seeing for /my-account-2/ occurs because WooCommerce POST requests are being sent to a page that isn’t properly configured as the My Account page. This often happens when there’s a duplicate page or a page slug mismatch.
To resolve this, please try the following steps:
- Clear permalinks: Go to Settings → Permalinks and click Save Changes to refresh rewrite rules.
- Check WooCommerce page settings: Go to WooCommerce → Settings → Advanced → Page setup and make sure the My Account page is set to
/my-account/ and not /my-account-2/.
- Remove the duplicate page: Go to Pages → All Pages in WordPress and delete or unpublish
/my-account-2/.
- Check for custom registration plugins: Are you using any custom plugin for registration or login? If so, please confirm.
- Confirm previous behavior: Was the registration/login process working correctly before the last update?
Critical errors like this usually appear due to plugin conflicts or conflicts with custom code. To help isolate the issue, please run a conflict test following this guide:
How to Test for Conflicts
Once you’ve run the test, please let us know what you find so we can guide you on the next steps.
Hi, Thanks for confirming the clean reinstall — that helps narrow this down a lot.
At this point, since:
- users are created successfully
- admin and WooCommerce settings work
- the error happens only after submitting the registration form
- and the request returns a 500 Internal Server Error
this strongly points to a runtime PHP fatal error triggered during login/session initialization, not a file integrity issue anymore.
Most common causes at this stage:
- A custom hook on
user_register, wp_login, or woocommerce_created_customer
- A plugin or theme function accessing WooCommerce session / REST objects too early
- PHP 8.3 incompatibility (WooCommerce is still safest on PHP 8.1 / 8.2)
Next steps to pinpoint it:
- Temporarily switch PHP to 8.1 or 8.2 (very important)
- Enable logging:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
3. Reproduce the registration error
4. Check /wp-content/debug.log — the fatal error should be logged there
5. Also temporarily disable all non-essential plugins (especially security, cache, custom login, or REST-related plugins)
A 500 error after registration almost always leaves a trace in debug.log. Once we see the exact fatal error, the cause should be clear. Let me know what shows up in the log.
We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.
Your feedback helps others – please consider leaving a review: https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/
