Bug New bugs post-fix (performed by Fillip H.)

Status
Not open for further replies.

Mangahav

Customer
Fillip H.,
Same site as previous.

There have been some new bugs that came up after your fix.

They are:

- when I type a message on the shoutbox, it appears blank for a few seconds and then appears.

- When we go into threads we get the following new error (which was not present before this fix):
Code:
Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../includes/class_bbcode.php on line 2958

- Now no one can edit their posts anymore (gets stuck on loading when I press edit)

Please assist.
 
These issues are not related to vBShout. I've responded to your PM, but for completeness' sake I'll copy it here:

The reason for those issues is either that you have old, outdated modifications installed on your forum that are not updated for PHP 5.4, or that you have not upgraded to vB 4.2.3.

You can re-disable error output in config.php, but this is strongly not recommended. I would strongly recommend you upgrade to vB 4.2.3 and if the issues persist, find the old modifications and de-activate them.

Hiding error output is like rolling down your sleeve when you're bleeding, the problem might be out of sight but it's still there.
 
Yes, I can confirm this is the case.

All products I am personally responsible for are developed on PHP 5.6 (will be moved to PHP 7 as soon as vB3 and vB4 are updated to support PHP 7, should this happen).

DBTech runs PHP 5.6 as well.
 
I have successsfully upgraded my vB version to 4.2.3. Do I need to reupload/reinstall vB Shout?

However, a new bug seemed to have arisen that might be usergroup related, or not. I am not sure.

What happenes when I change font/B/U/I: Screenshot by Lightshot

What others see.
IPD8Kzn.png





The version upgrade seems to have resolved the previous bugs with the line of code at the top, shout being blank after posting a message, and the edit issue.
 
Last edited:
No, that is not needed :)

Are you still experiencing PHP errors? If so, they will be the cause of a product, and you will need to disable each individual product and re-enable them one by one until you find the culprit.
 
No, that is not needed :)

Are you still experiencing PHP errors? If so, they will be the cause of a product, and you will need to disable each individual product and re-enable them one by one until you find the culprit.

I do not believe I am experiencing any PHP errors.
 
I do not believe I am experiencing any PHP errors.

The version upgrade seems to have resolved the previous bugs with the line of code at the top, shout being blank after posting a message, and the edit issue.
Your website errors seem to have been fixed.
This confirms that it was due to vBulletin 4.2.2.

Which means DB Tech Shout is not compatible for some hosts, who use vBulletin 4.2.2 or below.

Which in turn means the 'fix' Fillip H. provided was the root issue for your PHP errors on vBulletin 4.2.2.
 
Last edited:
Fillip H.;
http://www.dragonbyte-tech.com/f46/formatting-options-not-appearing-certain-usergroups-19804/
That was rather rude of you to just close the thread, without even letting me reply whether or not the bug was fixed.
I'm sorry, it wasn't my intention to be rude :(

I was trying to keep my list of open tickets trimmed, since I had already fixed the issue. The majority of our customers do not respond back saying whether the issue has been fixed, so when I've confirmed a fix first-hand I'll close the ticket to ensure my list of open tickets are only true open tickets.

Again, it was not my intention to be rude and I apologise.
 
What happenes when I change font/B/U/I:
8o8EdMc.png


What others see.
IPD8Kzn.png
Odd, I don't have that issue anymore.

I'm sorry, it wasn't my intention to be rude :(

I was trying to keep my list of open tickets trimmed, since I had already fixed the issue. The majority of our customers do not respond back saying whether the issue has been fixed, so when I've confirmed a fix first-hand I'll close the ticket to ensure my list of open tickets are only true open tickets.

Again, it was not my intention to be rude and I apologise.
Thank you for apologising.

Suggestion: Give the user at least 24 hours to confirm whether the bug has been fixed or not :)
 
Last edited:
Odd, I don't have that issue anymore.
That's not a bug, it's a Lite version limitation. It's intended that the Lite version only displays your own formatting options when you change yours, even on others' shouts.

There may be a quirk in the system where if you have not saved your B/I/U settings at some point, you see the "true" styles, but if you have, you see your own.

I don't have the time or resources to investigate that further, it's not an issue that affects the functionality of the mod in any way.
 
I reuploaded and reinstalled the plugin myself just now. FOr now it seems to be resolved, please allow 72 hours to see if it remains resolved.
 
Hello Mangahav,

This ticket has now been closed with the status Not A Bug.

We hope your issue or question has been addressed to your satisfaction. If not, please feel free to re-open it by clicking this link.

If you have any further issues or questions, please feel free to start a new support ticket via the button at the top of every page.

Thank you!
 
Status
Not open for further replies.

Legacy vBShout

vBulletin 3.8.x vBulletin 4.x.x
Seller
DragonByte Technologies
Release date
Last update
Total downloads
3,167
Customer rating
5.00 star(s) 1 ratings
Back
Top