Page Loads™
The system must load without white screens, fatal errors or missing includes.
- Shell loads
- Provider ID is carried
- No fatal error
- Correct active menu
No activity has been detected. You will be returned to the login page soon for security.
Provider system health, routing, module readiness and live check control.
System health is not just whether a page opens. It is whether the shell loads, provider data connects, operational modules respond, and errors are visible before they hurt the business.
Opening the page is step one. The real test is whether data, workflows, payments, printing, SMS and provider isolation all behave correctly.
Every DCME system health check should be split into four simple buckets.
The system must load without white screens, fatal errors or missing includes.
The system must be able to connect to the right provider data.
The system must complete the core operational action.
The system must leave enough evidence to troubleshoot.
This page checks whether common DCME include files and module entry points exist on the current server.
10 of 10 key files were found.
Status: Strong file availability.
File existence is not the same as full system health. Live transactions, permissions, database credentials, SMS, payments and printing still need module-level testing.
| Check | Purpose | Path | Status |
|---|---|---|---|
| DCME Shell | Loaded by this page through /includes/dcme_shell.php. | /includes/dcme_shell.php | Found |
| Master DB Include | Core master database include for provider lookups. | /includes/db_master.php | Found |
| Provider Index | Main provider command centre. | /providers/index.php | Found |
| Operations | Daily business operating centre. | /operations/index.php | Found |
| Factory | Production and factory workflow centre. | /factory/index.php | Found |
| POS | Counter and ticketing system. | /pos/index.php | Found |
| Routes | Driver and delivery system. | /routes/index.php | Found |
| BotFlow | Dashboard automation and customer flow builder. | /dashboard/botflow/index.php | Found |
| Marketing | Growth campaign intelligence. | /induscore/marketing/index.php | Found |
| Website Builder | Provider website control module. | /website-builder/index.php | Found |
System failures create business failures when they block orders, pickups, production, payments or customer communication.
A dry cleaner can lose revenue quickly if POS, factory, routes, payment links, SMS or printing stops working. The goal is to find small faults before they become counter pressure or customer complaints.
Can the team take work in, process it, notify the customer, collect payment, print what is needed and prove what happened?
These are the mistakes that make technical problems harder to fix.
A page can load while POS, routes, factory or provider database connections are broken.
White screens usually leave clues in error_log or PHP logs.
A good file uploaded to the wrong directory looks like a failed rebuild.
Links must keep provider_id so the user stays inside the right provider environment.
Printing, SMS and payment functions need their own live tests.
Always keep a known-working copy before replacing production files.
Health connects into the provider dashboard, operations, factory, business truth and automation layers.
Tools that can later connect to logs, credentials, module tests and live provider data.
Checks if key include and module files exist on the server.
Confirms provider_id carries through core links and modules.
Reads recent fatal errors and groups them by module.
Tests QZ Tray, receipt output and pickup slip readiness.
Tests payment link, gateway configuration and callback readiness.
Tests SMS provider credentials, sender and delivery response.
Turn technical checks into repeatable staff and owner procedures.
Open the core dashboards and confirm provider routing, POS, factory, drivers and logs.
LOW COSTSafe process for replacing PHP files and keeping a backup copy.
LOW COSTHow to read fatal errors and restore a working page quickly.
LOW COSTTest QZ, receipts, payment gateways and SMS flows after changes.
LOW COSTMake sure one provider cannot access another provider environment.
System health knowledge becomes owner, manager and support training.
Plain-English training for checking pages, reading errors, protecting provider links and knowing when to escalate.
When staff know what is broken and where to report it, technical problems get fixed faster and fewer customers are affected.
System Health Audit™ is designed to review shell loading, provider routing, module links, database access, error logs, printer readiness, payment links, SMS and operational workflows.
System health information should be confirmed using server logs, module testing and actual provider workflow checks.
Important: This page is operational guidance and live file availability checking. It does not replace full server administration, database auditing, payment gateway testing, printer testing, SMS provider testing or security review.
Before replacing live files, keep a backup copy. After upload, test the exact public URL with provider_id and check the error log immediately.