Evaluating vB; management questions 1st

[laverned]

Management wants to know, & I'm not sure (including where is appropriate to post, so I'll try here for now) on the following:

>>>>> Branding--What I've been able to find on "branding" pertains only to vB* branding-free (which, yes, is nice), not putting our own logo, etc on a product.
Is it legal to do our own branding? One post I stumbled on today implies yes but it doesn't come across as 100% sure. This could make or break a sale.

>>>>> SQL--store discussion in SQL: I see vBa is dependent on vBulletin, and vBu uses a flavor of SQL for a back-end repository.
But is there the ability, an API, to get one's own hands dirty? An API to the SQL part of the whole business (seems like a contradiction in terms). Is the way to make one's own extensions in functionality via bb code, php and the like, no API per se? Various forums (forae? :-) find zero when searching on "SQL" and "api", though today I came across mention of some form of API in 3.5. (API between what and what, BTW?)

>>>>> XML--can we export a discussion to XML?
It is implied in one post that XML output is a future possibility, but not present reality; not sure whether this applies to vBa or vBu in general or just to XML-output for [future] blog feature.

Strictly speaking management's questions were for vBadvanced specifically, but semi-technical questions are more often appropriate for vBu I believe.

TIA
dgl

[Steve Machol]

1. The 'branding free' license is available at a cost of $120 per license. You can purchase this in the 'Upgrade/Renew License' link in the Members Area.

Once you have purchased this option, you will have the right to remove the vBulletin/Jelsoft copyright info from the footer template (which displays at the bottom of every page.) You do not have to pay for the branding free option to remove the logo and replace it with your own. Note this is for one license only and is in addition to the cost of the license. If you ever transfer this license, the branding free option will transfer with it.

Also please note that you must retain all copyright notices within the actual product programming code (these notices do not affect any visible vBulletin pages). Note also this does *not* allow you to rebrand the software with another name. It only allows you to remove the Jelsoft/vBulletin copyright information.

2. You can view the full API here:

http://members.vbulletin.com/api/

3. This is currently not an option.

Also please note the vBAdvanced is a third-prty application that we do not provide or support.

[feldon23]

1. Every graphic in vBulletin can be changed without need for the branding free license. Only the copyright notice must remain. You can change all references to vBulletin in the templates/phrases and you can remove 'Powered by vBulletin' as well.

[laverned]

[quote=Steve Machol]<...snip...>
2. You can view the full API here:

http://members.vbulletin.com/api/

members.vbulletin.com behavior makes it evident that this is for paid customers. I can log into forums but not the above. I saw nowhere to register for //members... . Is there anywhere like the above for those of us who haven't bought yet?

Entering the above @ or clicking on "Members" at vBu Home gets a request for pw. Giving one's forum username and/or pw and/or going to "forgot your pw? Enter email" gets "not in database". And, no option at any point to register. Behavior says forum and Member logins are separate, not surprisingly.

dgl

[feldon23]

You must be a vBulletin customer to view the API. And even though there is a good unofficial API guide at vBulletin.org, it is also impossible to read unless you are a customer.

Can you tell us what you are trying to accomplish?

You can create bbCodes right from the control panel. You can create forums, users, usergroups, send private messages, etc. from basic API calls. There are over 500 places within the vBulletin code that you can 'hook' your own PHP code which uses vBulletin variables and existing SQL tables. Even with extensive modifications, it is rare that you should be talking directly to the database.

[Marco van Herwaarden]

The tutorial section at vbulletin.org is readable by non Customers i think. I suggest you have a look at vbulletin.org to see what community members are able to do with vB with the technigues currently available.

[feldon23]

All PHP code is blocked out until you are a customer.

[Marco van Herwaarden]

Yes the PHP code is blocked out, but you can read what can be done without seeing the exact code.

[ManagerJosh]

Just adding to the list of thoughts, there is an XML feature for RSS feeds. One of the options is just a regular XML.

http://www.vbulletin.com/forum/external.php?type=xml

[WisTex]

>>>>> SQL--store discussion in SQL: I see vBa is dependent on vBulletin, and vBu uses a flavor of SQL for a back-end repository.

But is there the ability, an API, to get one's own hands dirty? An API to the SQL part of the whole business (seems like a contradiction in terms). Is the way to make one's own extensions in functionality via bb code, php and the like, no API per se? Various forums (forae? :-) find zero when searching on "SQL" and "api", though today I came across mention of some form of API in 3.5. (API between what and what, BTW?) I don't have vBulletin (I am considering purchasing for a client's website), but I would assume, based on my experience many other forum software packages out there that uses a database that you can completely bypass the forum software if you want and write whatever you want to access and modify the forum database directly. You don't even have to use the same scripting language (PHP, ASP, etc.). I've built several sites that use the forum software as the base (i.e. handling member logins, security, etc.). The rest of the site has custom written code that accesses the same database and uses the same member list. No API required. Just direct coding. Although this API that vBulletin has sounds interesting.

And changing the functionality is typically done via making MODs to the forum itself. Perhaps this is what you mean by making your entensions in functionality.