Status
Not open for further replies.
This is a pretty unique problem...and not really a vbshout bug...it is specific to my current skin and a required custom field I have added. So I understand if you don't have a second to help...but very grateful if you do. :)

I have added a custom profile field that is required by members to be completed. However I noticed the mandatory pop up is having some sort of conflict with vbshout on the pages I am showing the shoutbox. For example here: Reef Tank Forums | Reef Aquarium Help & Information must be logged in to see the chat and of course not have the profile field filled in.

To describe it...it appears that each time the shoutbox is fetching the chats, the page is reloading inside of the chatbox...which of course is blowing up the page format and making it a confusing process for members.

I'm sure I have the notification pop up or something out of order? Any tips are appreciated.
 
Curiously after each time the shoutbox fetches shouts, another drop down arrow appears next to any vbmenu that shows the drop down indicator arrow.

Now if I refresh the page, it works like it should...shows the standard error message showing members to update their profile.

Something about logging in and not triggering the standard error is causing the problem.
 
Last edited:
No, it's not a vBShout bug. vBulletin prints that error page before vBShout code runs, and so vBShout is forced to display it in the frame.

There's no way to solve this, but it's a non-issue anyway since it only affects members who were viewing the shoutbox at the time. Any new users or subsequent page loads will see the error before the shoutbox :)
 
Hrmmm....while I see your point it seemed to confuse many of my members for days and they never tried to go any further and thus never really got the message about the need to update their profile field. I currently have countless members staring at a page that is flashing and growing wider with every auto refresh. We need to get them out of the "do loop". ;)

I think it still has to go in the bug department...whether it can be fixed or not is another question.

Can't you make a conditional that if the error is already printed, not to display the chatbox? Or if it is already printed for the chat to do a meta refresh and thus kick them over to the error message?
 
Last edited:
I can't make a check for that because vBShout's code never runs after the error has been printed.
 
I can't think of a way - that's not to say there is no way, but at this time I don't think so :(
 
Status
Not open for further replies.

Similar threads

Legacy vBShout

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