Remove Error: "Warning: Plugins are currently globally disabled via config.php."

[sickstrings]

We're bangin our heads against the wall on this one--your assistance appreciated!

Goal: Move board to new server and upgrade from 3.53 to 3.62
Error: "Warning: Plugins are currently globally disabled via config.php."

Steps Taken

• saved / backed up tables from server-old to local hard drive
• loaded tables from local hard drive onto server-new
• saved / backed up all files in the server-old vbulletin folder to local hard drive (these are the 3.53 files)
• moved vbulletin (3.53) files from local hard drive to server-new
• tested boards and everything seemed to work fine, though i didn't specifically check the plugins
• downloaded 3.62 files from vbulletin.com, expanded, and transferred (used ASCII) to server-new
• ran the upgrade script (ran through smoothly with no errors)
• checked the board, and it appeared to be fine
• in "manage products", we're getting the message: "Warning: Plugins are currently globally disabled via config.php."

Things we've tried and checked


#1

• in config.php, changed the following to say both false, and true
  • define('DISABLE_HOOKS', false);
• result: no change

#2

• renamed the config.php to make sure the software was in fact looking at the config.php i thought it was
• result: app didn't work when renaming, verifying that i was checking the correct config.php file

#3

• checked plugin/hook system under vbulletin options
• toggled it to 'no'
• result: no change
• toggled it to 'yes'
• result: no change

#4

• did a search of this board, and the only suggestions we found are the ones we tried

[Marco van Herwaarden]

Try removing the "define('DISABLE_HOOKS', false);" line, and make sure you don't have another line like that in your config.php.

[sickstrings]

Try removing the "define('DISABLE_HOOKS', false);" line, and make sure you don't have another line like that in your config.php.

That seemed to do the trick!

I'm curious... what is actually going on there. After commenting out the line, it worked, then we uncommented it, and it still didn't work. So we're leaving it commented out, but still curious.

Thanks!

[Marco van Herwaarden]

It is only checked if DISABLE_HOOKS is defined, not what the value is.

[sickstrings]

It is only checked if DISABLE_HOOKS is defined, not what the value is.

OK, but then why am I the only one who has seemed to have this problem? Isn't it defined in all installations by default?

[Zachery]

No that line is not in config.php by default

[sickstrings]

No that line is not in config.php by default

Oh... OK! Thanks for the clarification