vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   News and Announcements (https://vborg.vbsupport.ru/forumdisplay.php?f=2)
-   -   Discussions on vBulletin 4 and licensing (https://vborg.vbsupport.ru/showthread.php?t=225368)

Marco van Herwaarden 10-16-2009 11:31 AM

Discussions on vBulletin 4 and licensing
 
vBulletin 4 and Licensing Discussions

We acknowledge that many people have questions and concerns about the recently announced changes regarding vBulletin 4, licensing, and the costs to upgrade. vBulletin.org however is not the place where such questions can be answered.

In order to ensure that everyone's concerns and questions are heard by those who can give an official answers, we ask that everyone uses the official channels to raise those questions:
  1. The support ticket system for personal advice or answer to your questions.
  2. The vBulletin Pre-Sales Questions forum at vBulletin.com.
For general questions and remarks the vBulletin.com forums are also the place to do so.

The vBulletin team is working hard to read and summarize all the questions and issues raised. Due to the overwhelming number of questions and the fact that some questions will need to be decided upon by management, not all may be answered immediately, but if posted as described above, all questions will be answered as soon as is possible.

Many questions have already been answered and combined into a vBulletin 4 FAQ. We advise you to read these first before posting questions. Also please note that the FAQ pages will be updated as answers to questions are given, so please revisit to see if any of your new questions have been answered there.

It is in the best interest of both the vBulletin team and you as customers to limit these discussions to vBulletin.com and not to duplicate questions that already have been asked or been answered in the FAQ.

To avoid questions being unanswered, please do not post questions regarding the license changes or vBulletin 4 at vBulletin.org.

vBulletin 4 and vBulletin.org

Once vBulletin 4 reaches the beta stage, we will open a forum for discussions on modifications or styles in relation to vBulletin 4. At this time sections to host vBulletin 4 modifications and styles will also be made available.

Marco van Herwaarden 11-02-2009 08:49 AM

At vBulletin.org we have now opened our vBulletin 4.0 Alpha testers forums to members in the Beta testers team. To gain access to these vBulletin 4.0 forums please post a link to your vBulletin.org user profile in the following thread on vBulletin.com (only accessible to Alpha/Beta testers): Discussing modifications and styling.


All times are GMT. The time now is 05:25 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01016 seconds
  • Memory Usage 1,714KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (2)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete