Fixing Resource Editors That Stop Opening After a Hosting Migration

If resources and configuration pages stop opening after a hosting move, while snippets, templates, and chunks still work, the problem is usually concentrated in the document-editing part of the manager rather than in the whole backend.

This is similar to the classic blank editor problem, but migrations add more possible causes: broken paths, changed PHP behavior, partial file copies, stale manager assets, or environment differences that affect only certain manager actions.

Where to look first

• manager-side JavaScript errors,
• resource-edit form plugins and widgets,
• paths and URLs in manager configuration,
• file integrity after the move.

Because templates and snippets still open, the content database is often not the root issue. The editor layer for resources is simply hitting a different code path that the migration exposed.

The fastest path is to compare the document-edit action against a clean install and disable custom manager enhancements until the editor returns.