![]() |
How will licensed status change with vb's new pricing model?
I checked the FAQ and did not see this answered... so here goes.
Previously, vb.com used a running contract model.. you had to be licensed with vb.com to have access to d/l stuff from vb.org But with vb's new 'buy one release, and its yours' pricing model - the only running state is paying for technical support - we have a perpetual license for the major version we buy. What will vb.org follow for it's member access levels? What about vb3.x users who have a valid vb4.x license via their previous license, but did not buy vb4.0 explictly? Thx |
vb.org gets the license status from vb.com. If vb.com says you are licensed, then you show up as licensed here on vb.org. There are no different 'levels' of access for licensed users.
|
As long as you have a valid license to use vBulletin you will have access to all content on vBulletin.org.
|
All times are GMT. The time now is 10:30 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|