Deployment health overview
This page is now more complete and better arranged for first-time setup, error recovery, and post-upload diagnostics after deployment.
Back to loginHome
Smarter troubleshooting

Diagnose database issues, schema gaps, writable folders, and runtime logging from one cleaner surface.

The health screen now explains more, surfaces more context, and gives a better-arranged path through deployment repair tasks.

Database

Ready

Missing tables

0
Core checks
PHP version8.3.30
PDO MySQL extensionOK
Database connectionConnected
Required schema tablesReady
Uploads root writableOK
Recommended fix order
Follow these steps in order when the portal shows an error, a blank response, or missing database content after deployment.
  1. Open includes/config.php and verify database host, name, user, and password.
  2. Create the MySQL database from your hosting control panel if it does not exist.
  3. Click Run automatic setup / repair below to import database/schema.sql.
  4. Confirm uploads/ and its child folders are writable by PHP.
  5. Reload dashboard.php and confirm this page shows all green statuses.
Schema status
Missing tables are the most common reason for a failed first deployment.
All required tables are present.
Writable folders
CV uploads, application files, shared templates, and runtime logs all depend on write access.
uploads/
Exists: Yes Writable: Yes
uploads/profile_images/
Exists: Yes Writable: Yes
uploads/application_docs/
Exists: Yes Writable: Yes
uploads/shared_templates/
Exists: Yes Writable: Yes
uploads/app_logs/
Exists: Yes Writable: Yes
Runtime log location
When an uncaught exception happens, the portal writes the stack trace to a runtime log so the deployment does not fail silently.
/home/u315880141/domains/grants.chementor.in/public_html/uploads/app_logs/runtime.log