Quote:
Originally Posted by alessai
]
ive put yes for "Can see MGC Chatbox?" (for unregistered) and the others no is that right?
|
Yes yes that's right, but with those options the unregistered still can't see ?
Humm I thought I had tested it, I'll put in the possible bugs list so that I can test it and correct in case I made a mistake.
Quote:
Originally Posted by Sykko
dont worry about it... the truth is I think I was biting off more than I could chew with it, was a bit more than I knew how to do.
your box had better features but the other one seems to work ok too and the members are ok...
eventually we may try again after we get better at doing installs like this one  it would be a nice little upgrade 
|
Ok
Quote:
Originally Posted by Rukas
Is it possible to have the box show up on one forum only, or alternately have it work with one style only so I can then assign one forum with that template.
Ive tried the whole # $search_text = '$forumhome_markread_script';
replace with $search_text = '$chatbox_forumhome'; but it still displays on all styles.
|
If you do so and put $chatbox_forumhome on one style, it shall not be seen on other styles (only for forumhome as you seem to do the modification for the forumhome template only).
Quote:
Originally Posted by NeutralizeR
I upgraded to the 1.3 version, edited my chatbox templates, changed the settings, tested it for a while... and suddenly it stopped working. It says "Loading..." but nothing happens and when i enter a message it redirects me to the archives. The buttons are also inactive and IE gives me a javascript error message:
"Error: 'auto_refresh'" undefined.
I fully uninstalled the product, reverted the templates (a few times) and made a fresh insallation but still no luck. I'm stuck here.
I even dropped all of the chatbox tables via phpmyadmin, installed the earlier versions, cleaned my browser caches (both in IE and FF). Help needed 
|
Did you revert templates ?
Did you uploaded the js files correctly in the clientscript directory ?
This is possible errors when the javascript is firing such errors.