vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB3 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=111)
-   -   unable to turn forum off and censorship no longer works (https://vborg.vbsupport.ru/showthread.php?t=207759)

Sherrie 03-09-2009 01:36 AM

unable to turn forum off and censorship no longer works
 
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 03-09-2009 03:21 AM

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 03-09-2009 05:43 AM

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 03-09-2009 03:01 PM

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 03-10-2009 09:32 AM

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

Marco van Herwaarden 03-10-2009 10:22 AM

Do you use a file based datastore?

Sherrie 03-11-2009 09:06 PM

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 03-12-2009 11:36 AM

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 03-12-2009 07:35 PM

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 03-12-2009 07:51 PM

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

From here - The vBulletin Datastore:
Quote:

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.
Code:

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


snakes1100 03-12-2009 07:56 PM

The attributes are incorrect.

644 & 755 are not "world writable" attributes.

7 - "rwx" (r)ead, (w)rite, e(x)ecute, for Owner/User,
5 - "r*x" for Group,
5 - "r*x" for world/Other <-- No "world" write permissions

6 - "rw*" (r)ead, (w)rite, e(x)ecute, for Owner/User,
4 - "r**" for Group,
4 - "r**" for world/Other <-- No "world" write permissions

Sherrie 03-12-2009 08:47 PM

Thanks :) will give it a try now. I wonder why the one on my test forum still works?

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

I changed the attributes for the datastore file and rebuilt my post cache and all fixed, thank you very much :)


All times are GMT. The time now is 04:54 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
  • Page Generation 0.01072 seconds
  • Memory Usage 1,739KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_code_printable
  • (1)bbcode_php_printable
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (12)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete