[Forum] No such file or directory error when using full editor

[CalvertUK]

Can anybody help me with this error?

Warning: require_once(includes/functions_ghsom.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions_newpost.php(532) : eval()'d code on line 38

Fatal error: require_once() [function.require]: Failed opening required 'includes/functions_ghsom.php' (include_path='.:/usr/lib/php') in /home/------/public_html/aspiescentral/includes/functions_newpost.php(532) : eval()'d code on line 38

I get that error when I attempt to reply to or preview a thread response using the full editor. It should be noted that my site recently got infected with malware and as I couldn't locate all of it for deletion, I removed all of the files from my server and then re-uploaded everything using clean backups. I did not alter the database, install or do the upgrade process. Everything seems to be working fine, all of the posts and settings are in place except for this one error.

Any suggestions on what to do?

[Final Kaoss]

go to the vbulletin members page, grab a package & upload the contents, replacing your existing files.

[CalvertUK]

I've already done that. Should I do the install or upgrade process? I want to use an existing database?

[Final Kaoss]

You would make it go through the upgrade process and it will attempt to revert templates & whatnot back to the vbulletin defaults.

[CalvertUK]

Hmm Done that and still got the same problem...

[Zachery]

Add the following to your config.php file:

define("DISABLE_HOOKS", true);

[CalvertUK]

Add the following to your config.php file:

define("DISABLE_HOOKS", true);

Thanks! Seems to be working now.

[Ace]

go to the vbulletin members page, grab a package & upload the contents, replacing your existing files.

That's probably not going to help fix the error for the missing Glowhost SpamOMatic files.

[Dustin L.]

This is a GlowHost Spam-O-Matic issue. You can re-enable your plugins by removing that line of code Zachery gave you, but make sure to disable the aforementioned plugin in the admincp. Support for this plugin is not given here. You might find help over at vBulletin.org.