1Footer documentation
Troubleshooting delivery and migrations
Resolve stale content, missing access, incorrect page targeting and delivery that stopped after a platform move.
Last reviewed
The footer disappeared after a move
Check the website’s current host and the account that publishes it. A migration can replace the old project, repository, theme or native installation. Keep the destination account connected so a supported repair can use the current site.
If your destination’s automatic adapter is still in development, use its released server/build package or supported delivery path from the platform guide. Do not enable an incompatible proxy to bypass a native integration requirement.
The footer shows old links
- Confirm you published the intended draft.
- Check the public website rather than an editor preview.
- Republish a static or CMS snapshot after exporting the new footer.
- Review caches and the latest delivery check.
- Check that you are viewing the correct domain and website publication.
A repair needs access
Reconnect the publishing account for this website and confirm it can access the current project or site. An account-wide connection does not authorize changing an unrelated project.
Publishing locks, manual pauses and source conflicts can prevent an automatic repair. Keep those controls intentional; resolve the conflict before retrying a supported repair.
The footer appears on the wrong page
Review include/exclude rules, paused delivery and any static snapshot still present in your templates. Test a fresh load and then client-side navigation. Check for a second legacy embed or manually installed footer.
Keep unrelated site navigation intact while removing only the obsolete 1Footer installation. If the active adapter cannot safely identify it, the repair should need attention rather than remove arbitrary page content.
Information that helps diagnose a problem
- The public domain and an affected page URL.
- The current platform and whether it recently changed.
- Whether the footer is missing, stale, duplicated or on an excluded page.
- The latest delivery status and whether you paused it.
- Never include API keys, application passwords or private provider tokens.