Hi,
I'm likely to be responsible for the upgrade of a vBulletin 2 board (medium-size, a couple of hundred active members out of a few thousand registered) and was wondering if you could lay a few fears to rest.
1/
In vB2, private messages are presented in the user control panel—clicking on the link sends a read receipt, or users have the option of denying that receipt by clicking an alternate link.
From the forums I've used, vB3 seems to perform this with javascript. Users click to view the message, and then are presented with a javascript yes/no option (launching a popup) or (if that is dismissed or doesn't appear) a tickbox form to send a read receipt. Were javascript turned off, or a popup blocker, most users would therefore not bother to send read receipts. The system seems to have changed to 'opt-in' receipts rather than 'opt-out'.
Can the vB2 behaviour be implemented in vB2 without much hassle? (eg, Making default behaviour to automatically send receipts on viewing?) Ideally as a configurable option (or in templates at a push) and not through modification of the underlying code.
2/
Is there any configurable way to integrate the buddy list into a user control panels as with vB2, rather than as a popup? Many global variables (eg, forum list) seem not to be available to all templates, and none of the people working on this upgrade project has much idea about how to make them available. (Nor any desire to have to re-hack files when updates to the vBulletin core files are made available.)
We just want an assurance that we won't lose functionality users are familiar with by putting our eggs into the vB3 basket, and the popups and apparent extent of reliance on javascript are currently real concerns.
In recap: can read receipts be made automatic and opt-out, and can the buddy list be added to a normal page?
Fingers crossed, I'm hoping to have good news to tell the guy I'll be doing this for. If an approximation of the vB2 interface is no longer available and users will have to face changes whichever path we take, it might (relunctantly) be worth our while to consider other forum systems. (Which is why I'm posting this in Sales rather than Tech—please move the thread to the most appropriate forum if the sales team can't answer these questions.)
Thanks,
Stu.
I'm likely to be responsible for the upgrade of a vBulletin 2 board (medium-size, a couple of hundred active members out of a few thousand registered) and was wondering if you could lay a few fears to rest.
1/
In vB2, private messages are presented in the user control panel—clicking on the link sends a read receipt, or users have the option of denying that receipt by clicking an alternate link.
From the forums I've used, vB3 seems to perform this with javascript. Users click to view the message, and then are presented with a javascript yes/no option (launching a popup) or (if that is dismissed or doesn't appear) a tickbox form to send a read receipt. Were javascript turned off, or a popup blocker, most users would therefore not bother to send read receipts. The system seems to have changed to 'opt-in' receipts rather than 'opt-out'.
Can the vB2 behaviour be implemented in vB2 without much hassle? (eg, Making default behaviour to automatically send receipts on viewing?) Ideally as a configurable option (or in templates at a push) and not through modification of the underlying code.
2/
Is there any configurable way to integrate the buddy list into a user control panels as with vB2, rather than as a popup? Many global variables (eg, forum list) seem not to be available to all templates, and none of the people working on this upgrade project has much idea about how to make them available. (Nor any desire to have to re-hack files when updates to the vBulletin core files are made available.)
We just want an assurance that we won't lose functionality users are familiar with by putting our eggs into the vB3 basket, and the popups and apparent extent of reliance on javascript are currently real concerns.
In recap: can read receipts be made automatic and opt-out, and can the buddy list be added to a normal page?
Fingers crossed, I'm hoping to have good news to tell the guy I'll be doing this for. If an approximation of the vB2 interface is no longer available and users will have to face changes whichever path we take, it might (relunctantly) be worth our while to consider other forum systems. (Which is why I'm posting this in Sales rather than Tech—please move the thread to the most appropriate forum if the sales team can't answer these questions.)
Thanks,
Stu.
Comment