The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
LOL... ohh yeah, updating now & thanks for the "reminder"
|
#12
|
||||
|
||||
Yes it is.
Quote:
Yes, I tend to agree, its simply always been a text field, and no one has ever suggested otherwise (until now). Not sure off the top of my head how easy it would be to change it now (or even if its worth it). |
#13
|
||||
|
||||
Quote:
I don't see anyone in this thread with their vBulletin version in their postbit |
#14
|
||||
|
||||
vbulletin is constantly changing - new versions are out more frequently
IMO it's not needed. most people will ignore option or never update it |
#15
|
||||
|
||||
The confusion here would seem to be because of a difference between the postbit and postbit legacy templates - apparently its only in the legacy version now, I wasnt aware it had been removed from the other template.
|
#16
|
||||
|
||||
TBH, at this moment, the only logical reason I can think of offhand to use it is for modification purposes (to keep from having to ask the user which version of vbulletin they are using) and even that is prone to error due to not updating or an incorrect setting.
|
#17
|
||||
|
||||
You could prompt users once a fortnight to update the field?
|
#18
|
||||
|
||||
Or prompt a couple of weeks after a new vBulletin release. Could get annoying though.
|
#19
|
||||
|
||||
Well, if you only did it after a release you'd get many people who have to plan an upgrade etc. who wouldn't upgrade straight away.
|
#20
|
||||
|
||||
Hence the waiting of a couple of weeks.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|