Ok .. installed on my dev forums .. seems ok once I'd changed the links for the images in the vBXirc templates .. so that's cool ..
But! .. this whole templete thing is a bit of a bugger .. why doesn't/can't it just use the normal $navbar (and all the others) instead of having it's own? .. I use the java drop downs in my navbar and it's a pain not to be able to use it (if I add any other hack links I now have to add them twice etc) .. I've tried changing $vbxirc_navbar to just $navbar .. but it doesn't seem to like that .. how come?
Apart from that .. TOP work ..
Had the same problem after I got a member to download the zip for me. Didnt like the custom headers and see no reason to keep them so I just stripped the vbxirc_ from the following three lines in chat/index.php
I installed this hack yesterday and it was working just great but now some members can't connect while others can. What gives?
Error:
Connecting...
Unable to connect : null
Worked for me fine last night but tonight it doesn't.
I recently posted a fix for this at my forums.
Apparently pjIRC and IE have some conflict on allowing Java to grant the needed permissions for it in order to function.
Quote:
For reasons unknown, IE and Java, or maybe it's just this Java applet (pjIRC) and IE, don't get along.
In the case you accept a pop-up that says "grant permission to this applet," you likely aren't getting this error, and will be able to connect to our chat. Unless, you click "no" to that applet. The problem with not granting permission to this applet is you might not get the "grant permission" pop-up window ever again (well, maybe on reboot).
Java by default denies applets 3 of 4 permissions to Java sockets (your ip address/port), which are accept, connect, and resolve. It grants listening to the port, to see if it's available. This is why you sometimes get the pop-up that says "grant permission to this applet."
You can bypass this by editing your java.policy, forcing the 4 permissions for all applets under safe sockets.
I wish everyone didnt use IE
it really holds us back from using better web coding in terms of css
and codes that are wc3 compliant sometimes don't work in IE
for example my friend converted his site to Xhtml and had the right doctype and everything
but when he tried to run it in IE it didn't work at all
but in mozilla it was perfect in the end he had to remove the doc type and then it worked fine
if someone ever finds out how to make vbxirc use the normal vB navbar / header and footer let me know.
I'm getting ++++ with the ones that are hardcoded in vbxirc.
Plus, i can't understand why vbxirc makes the /chat dir the default new root dir, cause my whole sidebar is forked with it, all links point to /chat/..... instead of to /. making them all useless (and preventing my rss feed to be loaded).
The basis of the hack is great, it just has too much hardcoded
if someone ever finds out how to make vbxirc use the normal vB navbar / header and footer let me know.
I'm getting ++++ with the ones that are hardcoded in vbxirc.
Plus, i can't understand why vbxirc makes the /chat dir the default new root dir, cause my whole sidebar is forked with it, all links point to /chat/..... instead of to /. making them all useless (and preventing my rss feed to be loaded).
The basis of the hack is great, it just has too much hardcoded
Actualy BarBeQue
Before 2.5.x everyone was linked from the original header and footer and i got alot of complaints during.
So instead of having everyone whine to me why it dint work i added new templates, which can be changed, and are not hard coded at all