Updated zip, you can re-import the new XML file :)


Fillip

Now I get this error when trying to update the instance:

It also can't display at the footer when I change it to that option. Only below the navbar. Any assistance would be most welcome!

Also prune seems to remove all the messages. Is there a way to remove just one?
And I tried to mention someone with the @____; method (I have user tagging set for @ AND ;) but it didn't do the link. Any assistance would be greatly appreciated.

I appreciate this contribution as, when it works, it should greatly increase participation at my forums.

That will be fixed in the upcoming 5.4.1 :)

That function is not possible on vB3, unfortunately :(
I will remove that option from vB3's admincp.

Double-click it.

That is not an advertised or supported feature in the Shoutbox - the mention integration is from posts themselves.


Fillip

v5.4.1

• Reworked Instance Management in an attempt to work around Suhosin limitations (feedback requested!)
• Added a notice in the Instance Management to admins running Suhosin informing them of recommended changes to .htaccess
• Alternating Shout Colours will now work as intended on vB3
• Multiple conflicts with other jQuery-based products that prevented the Shoutbox from loading has been fixed
• The uninstaller has been updated to the new installer format so it will now function correctly
• The Sticky Note is now properly manageable from the AdminCP
• The context menu entries now once again work properly
• Leaving a chatroom will now work as intended
• Inviting someone to a chat room will now work as intended
• PHP error on instance management fixed

Fillip

Due to an exploit discovered by one of DBTech's members we would like to announce the immediate availability of vBShout v5.4.2:

• It is no longer possible to break the display of vBShout by using %message% or any other % % template variable in user names.
• The CMS tab will once again light up as intended when browsing the vBCMS page
• Editing a shout will now correctly display the old shout in the Command Log

In addition, the following fixes were previously applied to v5.4.1 after its release, and are included in this version:

• The "Max Characters Per Shout" setting is now properly ignored when your Usergroup is a Shoutbox Manager
• You can now properly delete shouts that, for whatever reason, have an instance id set to 0 and show up in your name
• The Shoutbox should no longer interfere with other mods adding themselves to the navbar in vB3

Finally, we have received word from one of our Suhosin users that the workaround did not fully comply with Suhosin's restrictions.

Sadly there's nothing further we can do. Due to the sheer number of features included in vBShout, allowing you to configure them all causes Suhosin to believe that vBShout is a malicious script.

That being siad, we have included a notice for Suhosin users that, if followed, should allow the Instance Management to work as intended. Feedback on whether the tips in the notice worked would be welcome.


Fillip

After upgrading i'm getting "Internal Server Error" when trying to post

Any ideas?

Thanks in advance

UPDATE:

I'm getting blank pages on showthread after upgrade so i'd to disable it

Try removing all the .txt files from /dbtech/vbshout/aop and ensure the folder is set to CHMOD 0777.

Fillip

Yes, it's CHMOD 777. After removing all txt files i'm getting the same blank pages with new vbshout enabled

Thanks Filip

Thanks to your diligence in reporting vBShout issues, we've seen it fit to release v5.4.3.

It fixes the following issues:

• Suhosin users should no longer find the Permissions and BBCode Permissions erased upon saving the Instance Options form.
  Please note that it is still required to submit the 3 forms separately, the top form will simply not erase any previous changes you have made to the bottom ones anymore.
• The Shoutbox can now once again be placed on the vB CMS on vB4
• It is now once again possible to determine if you have been flagged Idle if the Shout Order is set to Oldest First
• If you had more than one instance per page, it was possible for the Shoutbox to be stuck on Loading. This has now been corrected.
• The Shoutbox will now properly display times for shouts made in a global chatroom
• Deleting or posting a shout in a chat room will no longer show the contents of the "Shoutbox" tab until the shouts refresh again
• BBCode parsing for notifications should now once again work as intended
• The Auto-Idle function should now function correctly

Thanks for your patience and assistance in tracking down these issues :)


Fillip