So i have a WordPress-based site with a custom Genesis child theme. Once the site goes live, we are obviously going to need to make changes periodically to the child theme's code — modifying CSS and similar. These are the problems i've run into:
I don't have shell or FTP access, so i can't just replace the files on the server (they wanted to use one of those dedicated WordPress hosting providers for security and ease of maintenance).
It's not possible to upgrade an active theme 'in place' when using the Web-based Upload functionality (you can only do this with themes installed via WordPress's repository thing).
To get around the above limitation, i thought maybe i'll just put the git revision hash or whatever in the theme name each time i build the zip file, which will make WordPress see it as a separate theme, and then i can just switch from the old one to the new one. This does work, except that it causes WordPress to reset some of its settings (in particular, which menu is set as the 'Navigation Bar').
To be clear, i am NOT asking how i can test/see changes before making them in production (i have a development server), my issue is specifically with the mechanism of making the change.
Given my circumstances, is there any way to do this without causing interruption / having to make configuration changes each time we update?