plugin triggered by GET working in dev but not in production
-
Our company has a multisite that I’ve been tasked with getting to work. The programmer who made it appears to have made things a little difficult for me.
A login module/plugin stopped working recently. It triggers when you go to any url on the website followed by ?plugin_name (e.g whatever.com/posts?plugin_name)
On one installation (dev) it works fine, on the other (production) it does not seem to trigger at all. I tried this by replacing functionality to just echo a “hello world”.
I know the plugin has the exact same code/Structure, but I have no idea how it can trigger by appending the ?plugin_name to the URL (or why). Does anyone use this convention? and HOW? I don’t know where to look at since the plugin uses the same code
- The topic ‘plugin triggered by GET working in dev but not in production’ is closed to new replies.