Handle .htaccess and Other Server-Control Files During QCBM Recovery

Server-control files can contain routing, redirects, PHP handlers, access rules, compression, headers, RewriteBase directives, and host-specific configuration. A file that is correct on the source server can break a different destination.

QCBM therefore treats these files separately from the ordinary file-recovery strategy and applies extra safeguards during cross-domain or cross-path recovery.

The Server-Control Files Setting

Under Advanced configuration options, the Recovery Runner offers three strategies:

  • Restore source server-control files — Recommended for Recover This Site.
  • Preserve destination server-control files.
  • Use clean Joomla-compatible .htaccess rules.

Same-Site Recovery

For same-site recovery, restoring the backed-up source server-control files is the normal recommendation. This helps prevent stale destination-only rules from surviving a clean recovery.

QCBM can restore source .htaccess, .user.ini, php.ini, and web.config files while retaining non-activated source versions under dated backup names when appropriate.

Cross-Domain or Cross-Path Recovery

For a genuine move to another domain or filesystem path, QCBM does not blindly activate a source root .htaccess. It quarantines the source file because it may contain redirects, RewriteBase values, directory paths, PHP-handler directives, or access rules tied to the old environment.

If the destination already has an .htaccess, QCBM can retain it. On Apache/LiteSpeed with no destination file, QCBM can create a temporary Joomla-compatible baseline from Joomla's htaccess.txt and check normal and SEF routes.

The Needs Attention Review

When QCBM preserves a source .htaccess for review, the recovered administrator shows a persistent Needs Attention item until an administrator reviews the preserved rules and explicitly marks the item reviewed.

Do not clear that warning just to make the dashboard look clean. Compare the source rules with the destination and activate/merge only what is appropriate.

What to Test Before Marking .htaccess Reviewed

  • Homepage and several internal menu URLs.
  • SEF URLs and routing.
  • Administrator access using the site's normal protected route.
  • Login and logout.
  • Redirects and canonical host behavior.
  • Protected paths and downloads.
  • Uploads and APIs/extension routes.
  • Subfolder applications.
  • Caching, compression, headers, and PHP behavior.

Watch for RewriteBase and Path Differences

A source site's RewriteBase may be correct in one directory and wrong in another. Likewise, absolute paths and hosting-specific handler directives can change when moving between servers.

If the recovered site returns 404s, redirect loops, 403s, or PHP-handler errors, review server-control files before assuming the Joomla database recovery failed.

Preserve Evidence

Download or retain the preserved source file and the final Recovery Report until the destination has been stable. The report records the server-control decisions and warnings used during recovery.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.