Can I go from 3.7 RC 4 to 2.6.10?

[jambo310]

Because 3.7 RC 4 really messed up everything for me....need to wait for a stable 3.7

[King Kovifor]

There is no option to downgrade except to revert to a backup. Maybe someone on here can help you through your problems if you post them.

[jambo310]

Erm ok well here is the main one...on ANY shoutbox I get I get this after text posted securitytoken=9f81552b3d78f1caea329484efa8a70f9c 0e4bde

This only happened in RC4 and all th eother beta's and Rc's were fine.......also another big problem for me is the quick reply...when users quick reply it doesnt relode the page with their reply...it just relodes into a plain white page this happened on all 3.7's

[King Kovifor]

Erm ok well here is the main one...on ANY shoutbox I get I get this after text posted securitytoken=9f81552b3d78f1caea329484efa8a70f9c 0e4bde

This only happened in RC4 and all th eother beta's and Rc's were fine.......also another big problem for me is the quick reply...when users quick reply it doesnt relode the page with their reply...it just relodes into a plain white page this happened on all 3.7's

The quick reply is an odd error, and most likely vB.com can help you with that one. The securitytoken sounds like an incorrect working of the new CSRF code. Is this an AJAX product?

[jambo310]

Yes there oth AJAX (I say both because it is bot shoutbox's that have this error, I am using cchatbox and inferno pro 2.5)

[King Kovifor]

Hm... I am not good with AJAX, but if you post the JavaScript that goes along with it, I should be able to look at the code and spot it.

[jambo310]

Sorry I don't know what you mean...just in the shout box if i typed hi and hit enter (or pressed submit) it would say hisecuritytoken=9f81552b3d78f1caea329484efa8a70f9c 0e4bde

[Opserty]

Its a problem with the modification, it isn't yet compatible with RC4 or 3.6.10. Even if you downgraded you'd still get this problem anyway so there wouldn't be much point in doing so.

[jambo310]

I seriously doubt that...it was compatible with 3.7 RC4 and is compatible with 3.6.10 because my friend has it on that..but not cchatbox...just inferno

[King Kovifor]

it seems to be a problem with CChatbox then. You would need to request the author update his modification with CSRF fixes (instructions are provided for coders).

[jambo310]

but it is the same exact thign with inferno

[Opserty]

I seriously doubt that...it was compatible with 3.7 RC4 and is compatible with 3.6.10 because my friend has it on that..but not cchatbox...just inferno
It is, trust me, I know what I'm talking about ;)

Please see the final post in the vBulletin 3.6.10/3.7 RC4 release thread. http://www.vbulletin.com/forum/showthread.php?p=1545680#5

[King Kovifor]

What do you mean? You said your friend had Inferno alone and didn't have this problem.

[jambo310]

No I said I had both and my friend has inferno...and to Opserty..inferno is comaptible with 3.6.10 (at least on the forum I saw) and RC3 (i said RC4 it was a typo sorry) but cchatbox is only compatible with RC 3 and below

[Opserty]

RE: Inferno vBShout working on vB 3.6.10 http://forums.infernotechnologies.net/vBulletin-CSRF-RC4-Updat-t482.html

The problem you describe in your above posts is related to the new security token CSRF fix. The only (major) fix in 3.6.10 was the CRSF fix, the problem your experiencing with the other shoutbox is because of this.

You need to wait till an update for the hack is released, your shoutbox will no longer function correctly in future releases otherwise.

[jambo310]

Oh ok thanks

[Opserty]

The fix (for 3.7 RC4) I linked to in my previous post should work for both the shout boxes you may want to try it out.

[Ohiosweetheart]

The MGC Chatbox EVO is updated and working, if you want to try that one.