![]() |
I installed a new skin on my site and the chat box is stretching the skin too wide. How can i fix it so that the chat box will align with the current skin?
|
hmmm then perhaps our problem is just the channels not showing, but they are still now showing after the <if> statement was deleted.
|
Quote:
What image are you talking about ? Quote:
Quote:
Quote:
|
Quote:
On a side note when I as an admin type /team TESTTESTTEST it shows no where but if I look at the team archives then i can see the message. Seriously any help would be appreciated. |
Sorry but that is not helping... The input field is small but the chat box is still stretched
|
Ok I figured it out... I had to move the chat images to the new skin folder
|
The advantage is that users without javascript simply won't see the channel. The channel is hidden by default (style=display:none) and then shown via javascript.
Or does the channel work without javascript as well? I tested it and it just showed a "loading..." message but I forgot to check if I could post stuff on it. Maybe there should be a fallback with iframe that refreshes every x seconds instead of ajax. Ofcourse that won't be able to use the new functionality you are hopefully going to incorporate (json :)) but I think only a small part of the usrs will have javascript disabled. Maybe you should also do a check to see if ajax is enabled (and put that value in a cookie so as not to check on every page) and if not use the iframe fallback. Btw, this message: "Error : you can't send a private chat to this user as he doesn't have the necessary permissions to use this feature. " should be "he/she", not just "he" |
Btw are you supposed to get a notification when a message is posted in another channel?
I would love if this worked more like facebook; 1 public channel, then for each private chat another channel (or tab) which would be better at the bottom instead of the side. That way, users also won't make any mistakes by inadvertedly forgetting to type /pm first or mistyping it and thus releasing sensitive information on the public channel. Another benefit would be that you could possibly cache the user permissions and would not have to check the user table on every /pm command + if user is allowed to use the command, etc |
Quote:
|
Quote:
|
All times are GMT. The time now is 01:36 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|