![]() |
I did disable one by one yesterday and it didn't make a difference till disabled from the config. Will try again today.
|
Disable plugins via config if this fixes the problem enable plugins again via config, then disable one plugin at a time until you find the problem one
To temporarily disable the plugin system, edit includes/config.php and add this line right under <?php PHP Code:
PHP Code:
|
That was already covered Force.
@plumwd, do you have any plugins running under vBulletin? |
Quote:
|
That's admirable, but the original post was not how to disable hooks via the config, and the OP already knew how to do this. So all your post is doing is taking the thread off topic. :)
|
Going to try disabling each again and see if I can catch it. Maybe it was a weird caching issue.
FWIW I'm a programmer and completely understand how to edit code. I'm just new to vbulletin development. |
Quote:
|
Right, it was stated that by disabling plugins via config solved the problem, then you come and say to disable plugins via config, makes no sense. :)
|
Anyway.... you've already tried disabling the products and that didn't fix it. My guess is the hackers created a single plugin that will show up in your Plugin Manager.
|
As I asked in post #13
Quote:
|
All times are GMT. The time now is 02:20 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|