How to Fix Joomla File Paths After Moving a Website
Identify which paths are actually broken
Record the error and the exact old filesystem path it references. Joomla configuration can contain absolute server paths for logs and temporary files, while extensions can store their own cache, export, backup, upload, or command paths. Do not replace every occurrence of an old directory until you know whether it represents a filesystem path, URL, or historical data.
Find the new Joomla document-root path
Use the hosting control panel, SSH, or provider documentation to determine the absolute server path to the migrated Joomla root. Browser URLs such as https://example.com are not filesystem paths. If Joomla Administrator works, System Information and directory information can help confirm which paths PHP sees and whether important directories are writable.
Correct Joomla's log and temporary paths
Open configuration.php and review log_path and tmp_path. Joomla's site-copying documentation specifically notes that these values can become unwritable after a server move and should be changed to paths valid on the destination. Point them to existing directories intended for Joomla and verify the PHP/web-server user can use them.
Review web-server rules for old directory assumptions
Inspect .htaccess, Apache virtual-host configuration, Nginx rules, IIS settings, reverse-proxy configuration, and any custom RewriteBase or path-specific rules. A Joomla file move can leave the application files correct while the web server still rewrites requests according to the former directory layout.
Check extensions and custom code for absolute paths
Backup tools, media managers, import/export extensions, scheduled scripts, template build tools, and custom PHP can store server paths independently of Joomla's core configuration. Search configuration screens and code for the confirmed old path. Change supported settings first and avoid blind database-wide replacements in serialized or encoded extension data.
Correct ownership and permissions after path changes
Moving or extracting files under another account can change ownership. Ensure the destination host's PHP/web process can read Joomla files and write only where required. Joomla security guidance advises against using 777 as a shortcut; common Unix/Linux defaults are 755 for directories and 644 for files, subject to the host's execution model.
Retest file operations, not just page rendering
Verify extension installation, media upload, cache operations, logging, temporary-file creation, backups, scheduled jobs, and any extension that writes exports or generated files. A migrated page can render normally while log_path, tmp_path, or an extension storage path is still broken. Review logs for remaining references to the old server path.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.