unable to turn forum off and censorship no longer works

[Sherrie]

Hello

I am having some issues with my forum, upon moving my forum from a shared hosting server to a VPS as well as upgrading to 3.8.0 a month a go I have started noticing that censorship no longer works and then when going to turn my forum off this morning to try to upgrade I couldn't do that either!!!

I had 4 plugins installed, 3 (vbseo Sitemap generator, cron based email sending, You replacement) I have uninstalled. I also have a post thank you hack installed but when I try to uninstall that I get database errors and am unable to view posts.

I have tried upgrading my old test forum to the version I am running now with no plugins and these features work.

Could the post thank you hack be causing this after upgrading the forum to 3.8 or could something else be happening? I just don't understand why this thank you hack would cause censorship and turning my forum off to not work? I am a little worried that perhaps something else is going on?

I have also tried installing the post thank you hack on my test forum and these features still work.

Thanks

[Lynne]

Try disabling your modifications/plugins and see if you still have this problem.
Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

PHP Code:

define('DISABLE_HOOKS', true); 


Don't forget that for vbseo, disabling the modification means to also get rid of anything extra you added to your htaccess file.

[Sherrie]

There is actually a setting within vbulletin where you can disable the plugin/hook system for troubleshooting which I tried but still had the same issues.

[Lynne]

Have you looked in your error_logs to see if anything is turning up there?

Is your test forum also on the new server?

[Sherrie]

Yes same server didn't think to check any error logs.

[Marco van Herwaarden]

Do you use a file based datastore?

[Sherrie]

I don't think so?

--------------- Added [DATE]1236811752[/DATE] at [TIME]1236811752[/TIME] ---------------

Ok just had a looksie in the config.php and I am using filecache if that is what you meant?

[Marco van Herwaarden]

Make sure that the directory used for the filecache was moved correctly and is world-writable, also ensure the files inside the directory are writable.

[Sherrie]

Hello Marco,

I found a directory titled datastore with the attributes 755 and in there a datastore.php file that has not been modified since I moved with the attributes 644. I compared it with the datastore on my test forum and both the directory and the datastore file have the same attributes but this datastore file has been modified last time I used it.

So there definitely seems to be something up in that it doesn't seem to be using the datastore since I moved, but the attributes seem the same?

[Lynne]

The datastore directory should be 755, but the datastore_cache.php file should be 777.

From here - The vBulletin Datastore:

vB_Datastore_Filecache
This option saves the datastore data in the /includes/datastore/datastore_cache.php file. Reading from the filesystem is generally less load-intensive than querying the database.

To use this option, you'll need to make sure that the /includes/datastore/datastore_cache.php file is writable and readable by PHP. Usually this is chmod 777. Then, uncomment the following line in the config.php file.

// $config['Datastore']['class'] = 'vB_Datastore_Filecache';