It's me again, once again clearly doing things that the CMS doesn't like. Using window.location within my code, I have seemingly broken the CMS's ability to load the design tab.
In preparation for the deployment of a new site, a coworker asked me to redirect all pages from the old site to the new site's top page.. the only problem is that having only worked here for one week, no one thought to give me access to those credentials yet. The two people who are in charge of that stuff took today and Friday off to give themselves a long break due to our public holiday tomorrow. In short, my coworker wanted the redirect done today but I had no way of doing it server side, as it should be done.
So I told this coworker that I could do a stopgap piece of JS in the master template which would throw the user to our new site once the DOM had finished parsing. I put it in the very top zone of the Master page template of the site. The redirects worked perfectly so I thought I would jump back in and comment the code a bit to let the other devs why such a strange piece of code was present.
That is when I discovered that I had broken the CMS with that one line of code
<script>window.location = "www.google.com";</script>. It turns out that the CMS allows the JS to run in the design tab even when the "Web part content" checkbox is off. So anyway, what happens now is that when I try to edit any page through the design tab in the pages app, it instantly redirects the inner frame to the new site, which breaks it obviously.
All I need to do is delete one line from one defined zone, but I can't access it. Any and all help would be much appreciated.
Edit: Oh and by the way, reverting to previous "versions" did nothing to solve the problem.