Avacweb Chat - Bug Report Thread

Please post detailed descriptions of bugs in AWC that need fixing in this thread


When Im starting the next version of Avacweb Chat and it's been a while since the last version there will be quite a few bugs that I will have forgotten about...

So please use this thread to post problems that you believe are bugs in AWC and need fixed in the next update so I can find them all in one place, thanks!

I'll allow myself to start a chronological list of bugs, starting with the one I found as #1:

Bug Index: #1
Bug description: Bypassing avacweb_chat_config.commands
Observation: When replying using a command after entering an arbitrary amount of spaces before the "/", the command will not be properly parsed if there was one defined in the config, or the command will be parsed by forumotion if the config was used to disable it.
Possible fix (optional for reports, only if you know what you are doing): When parsing lines with RegExp add "^\s?"

EDIT BY LG:
this bug has been fixed in 1.9.1 silent update.

Bug Index: #2
Bug description: If emoticon has ', then it bugs in chat.

Bug Index: #3
Bug description: You can see all Public /me messages in private messages.

Bug Index: #4
Bug description: When you open the chatbox, then it often doesn't scroll to the last message (stays on top).

Bug Index: #5
Bug description: Since the last update forumotion, the cat still to chat: 0 even if people are above

@Tonight bug#3 is fixed in 2.0. I wanted to ask about the bug#2 you posted. Do you see this happening in the FM chatbox too? Or just AWC?

Just tested, and yes, bug#2 happens in default chatbox too.

Okay then the bug is with FM so I can't do much to fix it I'm sorry to say! You should post it on the the support forum since they're probably looking for chatbox related bugs at the moment.

Actually they locked up their bug report topic claiming they got them all.

I've got 2 bugs to report:

1. Although my CSS and JS applies for FireFox, Safari and Google Chrome, unfortunately it does not so for IE: http://prntscr.com/6dzib0 Roxanne just advised me.
2. When resizing the window, the SEND button doesn't stay on the bottom bar but shifts out of view as well as the header (whereas I expected the rightbox to be resized first as well as the sendbox): http://prntscr.com/6e08zg .

there is a bug when i try create a private convertation

http://prntscr.com/6ef8v0

Samantha, your first bug is more a browser problem. IE being daft... Putting '!important' back into your css once again should appease IE... Sorry to undo that hard work.

Your second bug I can fix in a silent update.

Thanks @Chall Valdez, is the bug preventing you from starting private conversations or is it only when you click the button from the menu? Can you use the /pm command to starts private conversations?

@LGforum : Done and it looks way better now. I'm still left with the white gap at the bottom of the page I PMed you about. In all browsers by the way. Here's the new CSS:

Code:

[panda=css].custom_placement #avacweb_chat {bottom:0px!important;width: 100%!important;margin: 0px auto!important;margin-right: -10px!important;height: 113%!important;}

.a_chat_pm tr, .a_chat_pm td, .a_chat_tab tr, .a_chat_tab td, .a_chat_cmd tr, .a_chat_cmd td {display:none!important;}
.a_chat_pm:before, .a_chat_tab:before, .a_chat_cmd:before {content: 'Hidden Content';font-style: italic;}
#achat_login {font-size: 1em!important;}
.user {font-weight: bold!important;}
#awc_header, #awc_footer {background: #FF5100!important;}
#chatbox_header {color: #FFF!important;}
#awc_title {font-size: 1.2em!important;color: #FFF!important;font-weight: 700!important;margin: 2px!important;}
#awc_rightbox {width: 85%!important;background-position: center!important;background-image:url('http://i.imgur.com/1EcLzk3.png')!important;background-repeat:no-repeat!important;}
#awc_userlist {width: 15%!important;background-image:none!important;}
#awc_userlist h4.member-title {margin-top: 3px!important;padding: 3px!important;font-weight: 700!important;font-size: 12px!important;color: #FFF!important;border-radius: 0px!important;-moz-border-radius: 2px!important;-webkit-border-radius: 2px!important;box-shadow: inset 0 3px 5px #EEE!important;-moz-box-shadow: inset 0 3px 5px #EEE!important;-webkit-box-shadow: inset 0 3px 5px #EEE!important;background: #FF5100!important;}
#awc_userlist li {font-size: 11px!important;font-weight:700!important;}
.achat_button {text-shadow:none!important;border: none!important;border-radius: 0px!important;-moz-border-radius: 2px!important;-webkit-border-radius: 2px!important;box-shadow: inset 0 3px 5px #EEE!important;-moz-box-shadow: inset 0 3px 5px #EEE!important;-webkit-box-shadow: inset 0 3px 5px #EEE!important;background: #2D68D1!important;color: #FFF!important;font-weight: 700!important;font-size: 12px!important;}
.achat_button:hover {color: #FFF!important;border: 0px!important;}
#awc_buttons {margin-right: 25px!important;}
/#achat_update {display:none!important;}/
#awc_message {width: 85%!important;margin-left: -10px!important;padding: 2px 5px!important;}
#achat_user_prefs, #achat_smilies, #achat_colors, #achat_popup {bottom: 17%!important;font-weight: bold!important;font-size: 12px!important;}
.achat_row {background:none!important;min-height: 14px!important;line-height: 13px!important;font-size: 11px!important;border-top: 0px!important;border-bottom: 0px!important;}
.achat_row.my_message {background:none!important;}
#awc_tabs {border-bottom: 0px!important;border-left: 2px solid #ECF3F7!important;border-top: 3px solid #ECF3F7!important;border-right: 1px solid #ECF3F7!important;text-shadow: none!important;border-radius: 0px!important;-moz-border-radius: 2px!important;-webkit-border-radius: 2px!important;box-shadow: inset 0 3px 5px #EEE!important;-moz-box-shadow: inset 0 3px 5px #EEE!important;-webkit-box-shadow: inset 0 3px 5px #EEE!important;background: #2D68D1!important;color: #FFF!important;font-weight: 700!important;font-size: 12px!important;}
.achat_tab {text-shadow:none!important;font-size: 12px!important;padding: 3px 15px!important;border-radius: 0px!important;-moz-border-radius: 2px!important;-webkit-border-radius: 2px!important;box-shadow: inset 0 3px 5px #EEE!important;-moz-box-shadow: inset 0 3px 5px #EEE!important;-webkit-box-shadow: inset 0 3px 5px #EEE!important;background: #2D68D1!important;color: #FFF!important;font-weight: 700!important;font-size: 12px!important;}
.achat_tab.selected {text-shadow:none!important;font-size: 12px!important;border-radius: 0px!important;-moz-border-radius: 2px!important;-webkit-border-radius: 2px!important;box-shadow: inset 0 3px 5px #EEE!important;-moz-box-shadow: inset 0 3px 5px #EEE!important;-webkit-box-shadow: inset 0 3px 5px #EEE!important;background: #FF5100!important;color: #FFF!important;font-weight: 700!important;font-size: 12px!important;}


@LGforum

when i try to send pm

@LGforum : I've got an update for you about hiding the default FM chatbox (forumURL/chatbox) with custom placement (maybe even without custom placement but I can't test that) and when logged in. The default chatbox will not be totally hidden: http://prntscr.com/6eibej (scroll down to the bottom of the picture) until this little bit of CSS is added:

Code:

[panda=css]#message {display:none}
.right-box {display:none}

I even think this is a FM bug when "Do not display" is selected from the ACP. Can you please confirm this and confirm what I did is right? If so, you may wanna add it to the default AWC CSS Thanks.

@LGforum : Upon clicking on user's name and typing a message and pressing enter, nothing happens at all.

Okay so there's a bug with the PM system, thanks for spotting this guys.
I'll have it fixed in a silent update.

@Samantha [ic]body.chatbox { display:none }[/ic] would be a better solution Id say. (As long as they've kepy this element).

LGforum wrote:[quotelink="http://www.avacweb.com/t2236p15-avacweb-chat-bug-report-thread#22683"]Okay so there's a bug with the PM system, thanks for spotting this guys.
I'll have it fixed in a silent update.

@Samantha [ic]body.chatbox { display:none }[/ic] would be a better solution Id say. (As long as they've kepy this element).

OK, thanks. That seems to be working too, so yes, they still do. Then the total CSS to hide the default FM chatbox would be like this, right?

Code:

[panda=css]body.chatbox {display:none}
p.page-bottom + .h3, p.page-bottom + .h3 + div.page-bottom, #chatbox_popup {display: none;}

Or can I purge the second line now as well? I hope you're gonna integrate it in the default AWC CSS so we can discard of those line(s). Thank you!

I won't integrate it since some people prefer to have the main chatbox available still.
You'll still need the second line for now. Unless you look in the index_body template and remove the chatbox link on the home page via templates.

Thanks for for giving clarity on that, LG! Nah, I won't yk. I just like to keep things crystal clear and be 100% on that, thanks. Sweet. Hope ur good.

@LGforum : Roxanne is here with us and she said the chatbox isn't loading at all on her 4G mobile, it just seems to be stuck in a loading state but nothing shows. Well, that's kind of a shock to me now. I really need this fixed real fast! I forgot all about testing mobile connection to the cb up until now because I hardly ever visit the internet from my mobile (I've got a 3G connection), but to me it doesn't show either, not through WiFi connection straight up through this router connecting to broadband internet we got at home and not when connected to the mobile internet provider... Now, as you know I've got custom placement, I never thought about adjusting CSS for mobile devices, but I shouldn't have to, right? This seems to be a big letdown to us because over 70% of our members do use mobile devices. So, what's wrong? Whatever we try, nothing seems to show regarding the mobile version of the cb on my ws. I'm lost!

Please, help!


And..., one other thing: I still need to get rid of that huge ugly white gap at the bottom of the page. Any word on that yet?


Thank you in advance for investing some of your time into this.


Regards,

Samantha

I'm on my mobile now and chat is fine and much better to use now
I can only assume it is down to the custom placement you have. What we can do is maybe a few css tweaks or simply remove the mobile version on yours since your chat is full page anyway.

The big white gap, inspect the element and find what it's coming from

LGforum wrote:[quotelink="http://www.avacweb.com/t2236p15-avacweb-chat-bug-report-thread#22702"]I'm on my mobile now and chat is fine and much better to use now
I can only assume it is down to the custom placement you have. What we can do is maybe a few css tweaks or simply remove the mobile version on yours since your chat is full page anyway.

The big white gap, inspect the element and find what it's coming from

LG, it had been working before in v1.9.1 and I had custom placement back then as well. I just don't understand how it shouldn't be working now. I don't want to get rid of the mobile version since more than half of the users do use mobile devices to connect to my website, so to me that's not something I'd do very lightly and as a last resort. Since nothing is showing, maybe it IS already disabled, but how can I check that?

I've inspected the element before and that's why I thought it was chat itself. Here's the result: http://prntscr.com/6fcmjj (http://fcnl.actieforum.com/h1-friendcodes-chatbox ) And it doesn't matter what percentage in height or margins, top or bottom I use in CSS, the gap will always be there.

Well, I've tried everything in my power to get to a solution. I'm out of ideas.

EDIT: Is it because of this line maybe? There's nothing in there for mobile users....

Code:

[panda=js]  // LGFORUM EDITS:     
      if(window.avacweb_chat) {
   avacweb_chat.init(avacweb_chat.tid, _userdata);
      }
  //END LGFORUM EDITS

The 1.9.1 mobile version majorly sucked. The mobile version isn't disabled - that's imposible unless you've actually disabled it lol.
What I mean by disable it, is on a mobile device your users will still see the full page chat, which would surely be alright?
If that's not an option then we'll have to look at disabling the custom placement while on mobiles, so that the mobile version can work properly.
I'll have to actually have a look at it rather than just speculating.

I tested it on my mobile (Huawei) and it worked fine. But in an iPad there is a problem.. you cannot see the content of the chat and.. each time you send a message (I'm in known than it is sent..) you cannot see it, plus the "Public" tab multiplied itself each time you send a message..so one more Public tab per each message..

And another thing, the sound option.. it works, but when you refreshed page or anything it is deselected again. And I am not sure if you are aware of those options for the new chat on FM: http://help.forumotion.com/t139284-codes-to-personalize-your-chatbox

they are compatible with the AWC chat?

Ty!

Str0ng wrote:[quotelink="http://www.avacweb.com/t2236p15-avacweb-chat-bug-report-thread#22707"]I tested it on my mobile (Huawei) and it worked fine. But in an iPad there is a problem.. you cannot see the content of the chat and.. each time you send a message (I'm in known than it is sent..) you cannot see it, plus the "Public" tab multiplied itself each time you send a message..so one more Public tab per each message..

And another thing, the sound option.. it works, but when you refreshed page or anything it is deselected again. And I am not sure if you are aware of those options for the new chat on FM: http://help.forumotion.com/t139284-codes-to-personalize-your-chatbox

they are compatible with the AWC chat?

Ty!

Nice. Thanks for the update. So, my bosom friend and I are not the only ones having trouble with the mobile version. Are cookies set to 'Accept all' on your iPad? They should be set to be accepted.