Ah, I see. Thanks for the quick reply. Is there a previous release of the mod that might get the url right? I noticed in the changelog of one of the last updates a mention regarding something similar being an issue that was corrected.

This randomly changed in a previous version of vB5 but was reverted again, so I'm guessing this current change will be reverted too.

In either case, there's no readily accessible archive at this time, sorry.


Fillip

I'm running the 6.1.0 Alpha 8 version. Is that the latest one you have? We were using the same version of your mod on VB 5.1.x and didn't have this problem that I recall.

Like I said, the changes were applied to the version available @ our site. It was a hotfix, it did not increment the version number.

That's because the change that broke our mods did not occur on your particular version(s) of vB5. It has occurred once before, whether it was in 5.0.x or 5.1.x I cannot say.


Fillip

Ah, well, OK that all makes sense. Thanks again for the super quick replies! They were so quick, in fact, I was still responding to your previous ones before I got to see that you were another one ahead of me already! :)

One quick thought/question: Is there perhaps a way to invoke the "save" command beside the button then? Like I said, by manually editing the url I can reach the settings and permissions area and make changes but the only thing I'm missing is some way to save them. Totally frustrating that it's so close, yet so far to make basic changes from the default settings. I have users that can't see the shoutbox because of the current permissions, but guests not logged in can.

Would the easier solution not just be to go here: http://www.dragonbyte-tech.com/store/8-vbulletin-5-x/ and download any of the vB5 mods you're using?


Fillip

That's exactly where I got the latest download from and the one I'm having this issue with. I completely uninstalled and reinstalled from scratch using this download because we were getting the "200 parseerror" after upgrading from VB 5.1 to 5.2 at first and I read that others having the same error were able to correct it by doing so.

We've been running this same version of the mod all along on lower versions of VB5 since we moved to it last year (5.0.x and 5.1.x) but I didn't have the source files from when we first installed it back then, so had to download a new copy to perform the reinstall this weekend.

The 200 parseerror problem did go away (and it also fixed another problem with the font formatting buttons not appearing previously come to think of it) but at the tradeoff of this new problem.

In that case I can't assist any further right now. The mod is working for me on vB 5.2.0 (Final), if newer versions of vB 5.2 broke it AGAIN then that's something I'll have to look into further when I have the time.

As you might imagine, I would strongly recommend avoiding vB5 if you intend to run custom modifications on your forum as these issues seem to have no end.

Fillip

I am running this on vb 5.2.1 and it works, but the "200 parseerror" comes up for a while every time upon first loading the site homepage, and then goes away as the shoutbox eventually works normally.