Installing this modification may help you figure this out - https://vborg.vbsupport.ru/showthrea...ighlight=token It may help you figure out what it is that is triggering the notices.

Will that work on 3.7x?

Found it out - I'm installing. Thank you.

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

Isn't sending the message - I made it so it would. It also is being stupid and still not working; I tried everything. It refuses to work - I don't even have any modifications.

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

I tried again, it's being retarded. :S

Have you tried looking in the php error_log?

Where is that? and I'm guessing it doesn't send automatically..

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

I got this:
Any ideas?

To troubleshoot this, please remove any hacks and disable your plugins, then see if you still have this problem.
Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

If so, reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server.

If your problem still exists, please create a new Style with no Parent set. Now browse the forum using this new style, do you still have the same problems? If you are troubleshooting login or guest issues, you will need to set this style as board default in the vBulletin Options.

Tried all those, nothing works.

What actions are the users undertaking that are causing the errors?

They are trying to access their UsercP (and sometimes the search feature) and it keeps giving this error. Mainly to normal members. Staff and other ranks don't seem to be affected.

Can you create a new user on your site that is a regular registered user and then get this error? If so, go to the page and view the source code and see if the security token is present in the form. (You can compare the same page as a registered user who gets the error with the staff member who doesn't and see what the differences are.)