Operations
Troubleshooting
Resolve common setup, editing, mail and deployment problems without weakening security.
On this page
Cannot open bin/console
Run commands from the CMS project directory, not your Windows home directory. Check that bin/console and vendor/ exist. Install dependencies first, then run the installation steps from a normal local terminal.
A required PHP extension is missing
php --ini
php -mCheck the configuration used by the actual PHP executable. On Windows CLI and web-server PHP can use different ini files. Enable the required extension, restart the process and run setup again. Do not install a random DLL from an untrusted site.
Missing table or cold-cache timeout
Apply the documented migrations after a backup. If the first local request times out while Symfony rebuilds its development container, stop the old server and use the supplied Windows startup script, which warms the cache outside the first HTTP request. Do not edit vendor files or simply raise the live request timeout as the first fix. Check application logs privately; never publish logs containing session details, tokens or personal information.
Login code does not arrive
For local development, start Mailpit and inspect its private inbox at port 8025. For real SMTP, check credentials, TLS, sender permissions and provider delivery logs. Use the verified SMTP setup flow; do not disable two-factor verification.
Stale content or conflicting edits
A stale-save conflict means another edit changed the version. Keep your recovery copy, reload and reconcile. For display cache problems, use the administrator cache controls and review hosting caches; do not delete the database or private settings.
Broken assets or old DNS target
Confirm the document root exposes public/, image URLs resolve against the correct CMS host, the certificate covers the requested hostname and DNS points to the intended server. A browser cache reset does not change an incorrect DNS record or server document root.
Features you cannot find
Hooks/webhook registration, custom taxonomies, public content writes, automatic billing and WordPress migration are not dashboard features in this build. Ask for a reviewed extension rather than pasting code from another CMS API into this one.
Something unclear? Contact me about this guide.