https://docs.whmcs.com/9-1/tags/post-update/Recent content in post-update onHugo -- gohugo.iohttps://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/application-configuration-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/application-configuration-errors/Documents “Application configuration file is not writable” logged after an update, caused by configuration.php permissions preventing new optional TLS placeholder entries, noting no action is required or providing the manual entries to add.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/feature-issues-after-update/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/feature-issues-after-update/Documents WHMCS features malfunctioning or displaying incorrectly after an update, caused by outdated custom template files, with steps to compare Release Notes template changes against custom templates and empty the template cache via System Cleanup.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/guardedforupdate-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/guardedforupdate-errors/Documents the “GuardedForUpdate: WHMCS Config Setting record is guarded against updates” error after an update, caused by leftover files from an earlier version in the /admin directory, with a MySQL query to check and correct the ShowNotesFieldonCheckout setting name or re-upload the /admin directory.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/legacy-module-removal-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-updates/legacy-module-removal-errors/Covers “A recent WHMCS update failed to remove legacy modules” caused by the Automatic Updater being unable to delete discontinued module files, with the fix of manually deleting the listed module files from the /modules directory.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-licensing/no-connection-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-licensing/no-connection-errors/Covers the No Connection admin login error caused by cURL or DNS problems, with steps to test connectivity via login.php?conntest=1 against a.licensing.whmcs.com, verify DNS for whmcs.com, and a PHP 7 workaround for restrictive shared or reseller hosting.