vB5 Errors
 

Hi,
I am getting following errors on my site. its a huge user db please help avoid these errors. i ve applied the patch released by vb for version 5.2.2 still recieving errors.

Uncaught exception 'vB5_Exception_Api' with message '<b>API Error</b><br><b>Controller:</b> content_privatemessage<br><b>Method:</b> getNotificationTypeCounts<br><b>Error(s):</b> <br><pre style="font-family:Lucida Console,Monaco5,monospace;font-size:small;overflow:auto;border:1px solid #CCC;">array ( 0 =&gt; array ( 0 =&gt; 'Your submission could not be processed because you have logged in since the previous page was loaded.&lt;br /&gt; &lt;br /&gt; Please push the back button and reload the previous window.', ),)</pre><br>' in /var/www/html/public_html/includes/vb5/template/runtime.php:510

vB5_Exception: Uncaught exception 'vB5_Exception' with message 'security_token_guest' in /var/www/html/public_html/includes/vb5/applicationabstract.php:584

The current version is 5.2.5, I suggest you update to that first.

Also, your question had nothing at all to do with the thread you posted it in, I have moved it.

update to 5.2.5?? no ways. you don't know what our tech team has gone through in this 5.2.2 vb upgrade.
recently, a patch released by vbulletin promised to fix security_token_guest 500 error. we did applied that patch but issue still persist.

Errors mentioned in the thread are difficult to reproduce on our end but our live error logs are filled with those errors.

Please let me know how can we fix it. these errors are faced by many vbulletin users.

Official support cannot be provided for obsolete versions. If you're advised to upgrade to help fix an issue, but you say "no ways I'm not upgrading", then that means the issue can't be fixed for you. There are lots of bug fixes in each release, it's very unlikely anyone's going to go hunting down your issue until you're running the latest release.

Sorry but that is the reality of it.

The guest token issue you mention is not happening on default 5.2.5 installations. I don't recall a patch being released for that specific issue, it may have been resolved in a full release - it's important to understand the difference between patches and full releases, otherwise you will tie yourself in knots.

I already told you the first step.

If you ignore it, then thats your choice, but we cannot help you.

And based on their current version support schedule, only the last 3 versions (currently 5.2.3, 5.2.4 and 5.2.5) would have security patch released if security issues occur in the future. Currently, no patch would be released for 5.2.2 and older.