Fix Shut-Down CMS Web App

My content-management web application was running smoothly until the original developer, unhappy about a payment dispute, deliberately disabled it. The stack is a mix of JavaScript on the front end, Python services, and a PHP admin layer. I still have full server and repository access, so the code is intact – it just no longer serves pages or lets me log in.

What I need now is a calm, skilled developer who can quickly trace how the site was taken offline, roll back (or rewrite) whatever kill-switch was planted, and get the whole CMS live again. Along the way I want the codebase reviewed for any other hidden “time bombs” so I’m not left vulnerable in the future.

Key outcomes I’m looking for:
• Public-facing pages and the admin dashboard load without errors.
• All content can be added, edited, and published as before.
• Any malicious hooks, hard-coded credentials, or obfuscated snippets are removed or documented.
• A short hand-over note describing what you fixed and how to avoid a repeat incident.

If you’re comfortable jumping into an unfamiliar JavaScript / Python / PHP blend, spotting sabotage, and getting a CMS back online fast, let’s talk.