Troubleshooting & Maintenance
Identify, diagnose, and resolve issues quickly with the Alpha-Omega CMS troubleshooting guide.
Common Issues & Fixes
Check that your .htaccess includes the correct router rule:
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^ router.php [L]
Also confirm that mod_rewrite is enabled in Apache.
Verify that database credentials in app/Core/Config.php match your hosting environment. Example:
define('DB_HOST', 'localhost');
define('DB_NAME', 'alpha_omega_db');
define('DB_USER', 'username');
define('DB_PASS', 'password');
Run the following test query inside phpMyAdmin to confirm connectivity:
SELECT NOW() AS server_time;
Ensure the /storage/sessions/ directory is writable. PHP must have permission to create session files.
Also verify that your Session::init() call appears early in index.php.
Clear your browser cache and check that /themes/default/partials/ and frontend.php are accessible. Missing or renamed includes can cause 500 errors.
Maintenance Best Practices
router_debug.log to catch template or route errors.Diagnostic Log Reference
| Log File | Purpose | Location |
|---|---|---|
router_debug.log |
Tracks route dispatch and controller loading. | /storage/logs/ |
header_audit.log |
Records header/footer include success and failures. | /storage/logs/ |
system_error.log |
Captures PHP errors and unhandled exceptions. | /storage/logs/ |
Need Additional Support?
Visit the Alpha-Omega Help Center for advanced diagnostic tools, or reach out to our support team directly.
Help Center Contact Support