What to send
After a host moves an OpenCart store to PHP 8, the usual symptoms are a white storefront, a blank admin page, an admin login that loops back to the form, or errors printed across product and checkout pages. To scope the fix, send:
- The store URL and the OpenCart version (shown in the admin footer, or in
index.phpasVERSION). - The PHP version before and after, and the date it changed.
- Which area fails: storefront, admin, checkout, or one extension screen.
- The last lines of
system/storage/logs/error.log(OpenCart 3 and 4 keep it under the storage folder) and your host's PHP error log. - Any extensions, OCMOD or vQmod files installed recently.
Send your OpenCart issue for a written scope and reply within 24 hours. Do not send config.php, database passwords or customer data in the public inquiry form.
Common causes after a PHP upgrade
- An OpenCart version that predates PHP 8. Community threads report that 2.3.0.x stores break on PHP 8 and that 3.0.3.x is the more compatible line. Old core code calls removed functions or passes null to strict built-ins.
- A hidden error. A blank page is a PHP fatal error with
display_errorsoff. The real message sits inerror.logor the host log, for exampleUncaught Error: Class 'ScssPhp\ScssPhp\Compiler' not foundafter a half-finished upgrade. - An extension written for PHP 7. Payment, shipping and theme modules often use
each(),mcrypt_*, curly-brace string offsets orcreate_function(), all removed in PHP 8. One bad module can blank the whole admin. - Stale or broken OCMOD output. Files under
storage/modification/are generated. A modification that patched a PHP 7 file can keep throwing errors until the modification is fixed and refreshed. - Storage or config path mismatch. After an upgrade,
DIR_STORAGEin the rootconfig.phpandadmin/config.phpmust point to the same existing, writable folder. A wrong path produces blank pages and admin login loops. - Sessions and permissions. An unwritable session or cache folder, or a changed session handler on the new PHP build, can cause the admin login loop.
- Memory and extension modules. A PHP build that lacks
mysqli,gd,mbstring,ziporcurl, or a lowermemory_limit, causes white screens on specific pages.
Hosting-side limits such as a PHP version your extension vendor no longer supports may need a decision from you or the vendor. The written scope will separate that from code SazM can fix.
Safe checks you can run yourself
- Make the error visible, briefly. Read
system/storage/logs/error.logand the host PHP error log first. Only if both are empty, turn on error display temporarily in the hosting panel, then turn it off again. - Compare the two config files. Open
config.phpandadmin/config.phpand confirmDIR_STORAGE,DIR_SYSTEMandDIR_LOGSmatch and the folders exist and are writable. - Roll PHP back as a stopgap. If the host panel allows it, return to the last working PHP version (7.4 for older 2.x/3.0 stores) to restore trading while the fix is prepared on staging.
- Isolate the module. On a staging copy, rename recently added extension folders (or disable the OCMOD in Extensions, Modifications), then click Refresh. If the page returns, the last module you disabled is the cause.
- Check the PHP modules. Confirm
mysqli,gd,curl,mbstringandzipare enabled for the new PHP version; modules are enabled per version in most panels.
If an hour of this does not isolate the file, stop editing core files on the live store; blind edits make later upgrades harder and can hide the original error.
Price, delivery and guarantee
Affordable and low-cost does not mean open-ended: one agreed OpenCart fix is a $99 fixed price, agreed in writing before work starts, delivered within 48 hours of receiving the required access.
- Fully written. No calls and no project managers.
- Fixed on a staging copy first, then released to production after you approve it.
- A test order is taken through checkout before and after the fix.
- You receive written proof: the root cause, what changed, before/after evidence and a rollback note.
- Money-back guarantee if the agreed root cause cannot be resolved.
A full OpenCart version upgrade, an extension rewrite or a migration to another platform is outside the fixed price and receives a separate written quote; see ecommerce development services. You work directly with Saravana Bhava, a senior developer with 20+ years in production (since Oct 2006), whose portfolio includes OpenCart stores.
FAQ
How much does it cost to fix OpenCart errors after a PHP upgrade?
The fix is $99 fixed price for the confirmed issue, including root-cause diagnosis, a staging check, the fix, written proof and a rollback note. Typical agency hourly rates are higher and open-ended, while very low marketplace gig prices rarely include root-cause diagnosis, staging tests or a guarantee.
What is the best way to fix an OpenCart blank page?
Find the real error in system/storage/logs/error.log or the host PHP log instead of guessing, fix that file or extension, test on staging, then release with a rollback plan. When choosing an OpenCart bug-fix service, look for a fixed price, staging first, root-cause explanation, written proof and a guarantee.
Should I upgrade OpenCart or just fix the error?
If one extension or file causes the failure, fixing it is the cheaper, lower-risk step. If the core is several major versions old, the scope will say so in writing and a fixed-price upgrade quote can follow.
Do I need to give you hosting or SSH access?
Not at first. Start with the error text and versions. If access is needed it is scoped and revocable, staging first, and you can rotate credentials afterwards.
Can this be done without calls?
Yes. Scope, questions, approval and delivery all happen in writing.
Next step
Send the error log lines and versions and get a written fixed-price scope within 24 hours. The related guide OpenCart PHP 8 dynamic property errors covers the deprecation messages in detail. If the store is slow rather than broken, see performance optimization.