I clicked it!!! I clicked it!!! I did, I did! :banana:
I had a really cheap (well, free actually) and nasty (well, crap actually) shoutbox from my phpbb board, but this kicks ass over it. I especially am glad it is member limited too, in that it restricts spambots and such like. Good stuff!
In response to some of the above posts, regarding it not working on vb3.5.4, my forum is running 3.5.4 and this shoutbox worked 1st time without a single glitch or error for me.
However, as I'm new to vb in general and have only been a user of it for a couple or so weeks, my board is virtually untouched aside from a couple of google ads thrown in through my own editing of the templates as well as some code given by the vbulletin team on the .com brother site to here. The only single other mod i have is an autogreet for new sign-ups, so my plugin's are empty aside from one.
I can only assume this is the issue for some of the more experienced users amongst this thread, that other plugins - especially for those that are heavily modified - are creating the reported issues.
Okay, so yours works without many modifications. That makes it narrowed down to being affected by mods. So what in THIS mod would keep all other mods working, but totally blank out vbshout? I am not a coder, so I am just trying my best to pinpoint the problem...
Okay, so yours works without many modifications. That makes it narrowed down to being affected by mods. So what in THIS mod would keep all other mods working, but totally blank out vbshout? I am not a coder, so I am just trying my best to pinpoint the problem...
agree, it was a very good information we was given there, >>Working on a NON modified board".
But I'm not a coder my self, but I'll hope these info, will help solve the problem
Okay, so yours works without many modifications. That makes it narrowed down to being affected by mods. So what in THIS mod would keep all other mods working, but totally blank out vbshout? I am not a coder, so I am just trying my best to pinpoint the problem...
Unfortunately, I don't know coding well enough to even hazard a guess. I used to program in +3 BASIC when I was a teenager, so although I can 'roughly follow' what I see in the code, I dont' have enough php nor mysql experience to comprehend the full workings of it. I would assume, logically, that there is a table or variable collision. For example, it could be that this MOD (purely example purposes so don't quote me on this) uses a variable called $somestuff and you have another MOD that also uses the same variable $somestuff.
For this moment, that's all I can think of, sorry. Perhaps you could attemp to disable all MODs except this (shout). Then re-enable your other MODs one by one. Although it might take a good bit of tedious fiddling within your admincp, it would guarantee a confirmation of which other MOD is clashing with the shout-MOD.
Once narrowed down, you could manually locate the clashing variable and then manually edit it (eg use $something-b in place of $something).
I do hope a resolve is found in the near future for your problems, but the shout does work well.