Blog Sections Open
Fixing Errors After Restoring a Database Backup
A practical recovery note for sites that break after a database import even though the backup itself looked valid.
A restored database is only one part of a working site. If errors appear immediately after the import, the real mismatch is often between the restored data and the current filesystem, PHP environment, or site configuration.
Typical causes
- Different charset or collation settings.
- Old paths or domains still stored in configuration rows.
- Table structures that do not match the code currently on disk.
- Incomplete backups that restored data but not the matching files.
The right response is to compare the restored data against the current runtime assumptions, not just to keep re-importing the same SQL dump. Database recovery is always partly a deployment-alignment problem.
Fixing ajaxSubmit and eForm 500 Errors in Evolution CMS
How to troubleshoot AJAX form submissions that trigger a 500 error when ajaxSubmit and eForm are combined in an Evolution CMS project.
Running MultiTV on cp1251 Sites Without Breaking Output
How to reason about MultiTV behavior on older cp1251 Evolution CMS sites and why encoding assumptions often cause the visible breakage.