UBB.Developers Forums UBB.threads 7 Development Addons and Modifications [7.x] [Pre-7.3] [Final] pJIRC Addon v0.5

And tested on riddledindarkness.com until Giz decided he was going to stalk my chat room waiting on 'payment'.

installed the chat on my site

http://a3.com/chat/pinwand

feel free to sign up

Problems:

I cannot shut of the /nick command, so the names can be faked

Even if I could, there probably is a back door to get in with another irc client. Again, no security for the nicknames, they can be faked

Can I get my own channel? to try? I might get 50 or more people in there if it works all right. If it works I might donate a little

But need unfakeable nicks

Oh and when I undock then I don't see the private chat buttons any more

oh and I need to have chat administrators that can be defined in the ubbthreads

So a moderator with rights to whatever forum should be chatadmin with special rights as soon as he logs in

Also need flood control, it is too easy to post 50 times the same long line

1. you can disable the /nick command by editing the language file; it has a section of commands you wish to disable.

2. Users can login with any IRC client to an irc server, this is simply an irc client.

3. You can register a channel on any of thousands (if not millions) of irc servers; there is a huge list at www.searchirc.com. I also operate my own at www.undergroundnews.com.

4. Not sure what you mean about undock...

5. chat admin's are simply users who have operator status in the channel, simply register the channel on an irc server and the users nickname to admin; as soon as they authenticate to their account (via /pass password or /nickserv identify password) they will be the channel operator (you can have any number of operators).

IRC chat's don't commonly have flood control, unless you configure a bot; most of them don't have bot's on them natively (however mine does when configured).

When I attempt to access Chat through the Breadcrumbs bar, I'm getting a syntax error: "Unexpected T-STRING" error in Line 50 of the chat.php file (the one in languages/english). I can't seem to locate the error - which line is "Line 50" according to the UBB software? And is this a common error - do you know what I might need to fix to get this to work?

Thanks!

What version of the UBB are you trying to run thison?

7.2.2

I just noticed on the portal page that it says 7.3 is now available, should I upgrade to that?

Also, I may not need help with this anymore, because I think the Naked Shoutbox is going to be a better option, but I'd still like to know if we can go ahead and upgrade. Thanks!

Line 50 of that file would be:

I don't see a syntax error in the above; you could try making sure that yours matches it, or remove the text between the ""'s completely.

Another option would be the naked shoutbox as mentioned, this script is for those who'd prefer relying on a 3rd party irc server.

Updated:
2526 - chatPre73v05.zip - Released: 05/12/2008 - Repaired a syntax error in the language file and preformed some minor code updates to go in line with the 7.3+ version.

Since this has to be reworked for 7.3 I'll be starting a new thread for that.

Ok I have it installed now as well (I even kept the fingers in place for you Gizmo :P)

My question is, I didn't have root access to the server to create folders SO I had to use an upload script to get my server in place which would allow me to add folders by name... my current directory is

/RoEForumPack/NewFeature1/;

where all do I have to change the links to match that? I changed the language file to point to that directory (as well as sounds and smilies) but I don't see it on my forums.. am I missing something?


EDIT: Oh and I changed the the default tpl file to point to that same place.


Dunny

http://forums.eventide.net/forums/ubbthreads.php

nevermind I found it Gizmo you really are a genious! Thanks

Dunny

http://forums.eventide.net/forums/ubbthreads.php

Lol was about to say "Edit the config file"

Will this work on 7.5.5 ?

Thanks,

-Graham

Graham, this won't work on anything remotely current (see the notice on post #1), instead use this