Hello,
After upgrading to 6.2.18 all notifications in the shoutbox return the below example. The link to the thread/post is not displayed correctly.
*{ } used in replace of bbcode bracket for example.
I have reinstalled 6.2.18 with a fresh download and problem has not resolved.
Thank you.
Hi guys, it's me again :)
How do I (can I) censor words or part words for shoutbox lite 5.4.4 please?
I have some words censored in the forum but I assume this does not carry over to the shoutbox.
Thanks.
Thank you that has fixed the problem!
I know it was a user (me) issue, can I make a suggestion please. In the Readme file point 3. explains install and upgrade process. However it omits the steps in the Upgrade notes. Ill take full responsibility for not resolving the problem with the...
Yes I did delete the XML files. In fact when I uninstall I use the plug in manager then I ftp and remove all the files and folders that were created by the shoutbox install process. I was very careful to check each file.
Thanks I will try. I gave it a shot earlier today and it killed the site and returned a general server 500 error :(
Maybe a call to the host is in order!
Thanks Ozzy you've been a great and patient help! I'd really like to break through this one hurdle as my forum users are not net savvy and tend to rely on the Shoutbox notifications for posting updates.
This is what I have;
This is the Notification Page.
Couple more things.
Spelling error Editing Instance>
Enable Context Menu
This will allow you to globally disable the advanecd...
I have downloaded the package again and did a full uninstall, remove and reinstall.
Set Context menu on and I now have PM's working and the error message has gone...
Thanks Ozzy! I will make these changes to htaccess later today thank you very much for picking that up.
Currently when accessing the Notification page, nothing is displayed in the Notification 'window'. Would this be a symptom of Suhosin restriction?
Fillip H. thanks for you help but I am still getting errors and limited function on the lite version.
vBulletin is 4.1.4
Shoutbox Lite is 5.4.4 (as downloaded in the last 30 minutes of this post).
User installer is SuperAdmin
Disabled forum and disabled Shoutbox
Uninstalled Shoutbox Lite...
Thanks I had checked that already, still have error
Warning: dl() [function.dl]: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/suhosin.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/suhosin.so: cannot open shared object file: No such file...
Thanks I have done that, but now I do not have a dbyte box in the lefthand banner of my AdminCP
I only have the DByte Tech:vBShout - General Options in the main drop down box.
Well I have upgraded Vbulletin to 4.1.4 all working great in the past week. Upgraded Lite Shoutbox 5.4.4 and there is no PM feature anymore. Also I now have an error at the top of my CP when viewing Instance Management > Editing Instance.
Error reads;
Warning: dl() [function.dl]: Unable to...
I use Chrome or Firefox and until recently was advised that in IE my forum drop down tabs are being hidden behind the shoutbox.
Link here;
http://www.mysandman.com.au/forums/forum.php
Also is there a method in reducing the width of the shoutbox so there is no horizontal scroll bar?
Thanks.
Thanks for the great Lite product, it installs easily and works very well.
I would like to know how (as an admin or user) can one edit and/or delete a shout.
I have checked the cp and Admin, Mods and registered users are checked to delete and edit. But I cannot find how to delete a shout...
Yes I did, and have again to make sure. No change to the ACP.
I'm going to drink beer, it may provide a solution... not THE solution but one none the less.
It's ok I know it can be frustrating doing 'tech' support for free products and this problem seems to be user related not application.
This is my ACP menu;
I do not have that option within the ACP. After installing I was assuming an additional tab would appear, but not for me. I am at a loss...
I will disable all plug ins and reinstall DB Activity again to see if fixes.