Hi Brent,
I checked the production website and the footer was gone already, so I thought I do a test. I added a footer from scratch called Another X test
. It has a simple Text element, it worked with no problem, even if I assign it as a global footer it works correctly and I can edit that later.
Then I created a template from the development website and imported it to the production website called Another X test 2
and it did not work and is blank.
This shows that the footer in question has a problem and you need to check that. I suggest that you try to recreate the footer on the production website and in each step save the footer, make it global and test the case. This will make sure that you will find the step that causes the issue.
I guess that something is different between the options of the development server and the production server which causes the issue, something that does not trigger the error on the development website but causes an unexpected behavior in the production.
I do understand that this will be a burden to start over on the production website and it might get blank midway, but that is the only way that you can see which action causes the issue on the production website.
Thank you for your understanding.