vBulletin Mail System

[high]BEFORE YOU READ FURTHER, DO NOT INSTALL THIS MODIFICATION IN ITS PRESENT STATE. READ THE RELEVANT SECTIONS OF THIS POST FIRST IF YOU WISH TO INSTALL VBMS. I AM NOT OFFICIALLY SUPPORTING THIS MODIFICATION.[/high]

Note: For now, this thread will serve for all support questions. Obviously, the thread is going to get very long, very soon, and quickly lose any manageability. I hope to have a Premum Modification forum set up for vBMS, depending on whether the administration here supports it.

The vBulletin Mail System is now a free modification, instead of $40 to $48 (depending on the license). All features of the developer license (notes, etc.) are public as well. These files will be released shortly; they are not available yet.

For product information: http://www.webdesignforums.net/vbms/ .

What's attached to this thread?

The latest development version of vBMS, designed for 3.5 (incompatible with 3.0 in many ways, incompatible with 3.6 in a handful of ways). It is not to be installed in a live environment under any conditions.

What does this mean?

The forum at http://www.webdesignforums.net/vbms/forum/ will no longer serve as a support forum. If you have questions, you should do one of two things:

• Post in this thread ONLY. All technical, historical, and nearly all other threads should be posted here. In all likelyhood, I will not response to technical questions in this thread, and I will not respond to such requests via private messages or other means. By posting in this thread, tens of thousands of other users can help you in addition to me (provided they don't get there first and I have the time).
• If the question is personal for me only--no development questions--then send me a private message. Send the private message only through my site (http://www.webdesignforums.net/), not this site, so I can easily look up your customer history. Effectively, this involves billing only, or other licensing questions.

What about those who purchased the product?

When you bought vBMS, you were paying for the stable 3.0 release that has been around for over a year, and a 2.3.x release that has been around for much longer (since 2003). You still have access to those products (they will be released in the new forum). However, your license has been inherited to a standard open-source license: you may now install vBMS on as many domains and forums as you like, as well as freely distribute it.

Your input has also allowed a stable 3.5 version to be very close to completion. The expertise of the tens of thousands of coders who are now exposed to vBMS--which includes the developers of vBulletin themselves--will further improve the product to create a stable and full-featured product for vBulletin 3.5, 3.6, and beyond.

If your intention was to buy a 3.5 release, please note that it was clearly and repeatedly mentioned that a 3.5 version was only under development, not readily available, and that the version available was specifically not suitable for live use. I apologize if you thought this was different as I attempted to make it abundantly clear, including specifically telling people not to buy vBMS if they are running vBulletin 3.5 or later.

However, with this transition to open source, you will still get what you paid for, and faster: a stable 3.5/3.6 release.

Why go open-source?

To be honest, it is not fair to those who bought a vBMS license but have upgraded their installation of vBulletin to beyond 3.0. This will allow a much faster development cycle with support from many vBulletin modification developers. There are secondary reasons as well:

• Time. vBMS is well over 16,000 lines of code. Managing a product of that scope is simply beyond the several hours free I have each week to develop the product. Also, with Jelsoft churning out the vBulletin versions, developing a product that is dependent on frequent changes is extremely difficult. That is not to say that frequent new versions of vBulletin is a bad thing; it simply makes development difficult.
• Product scale. As mentioned above, vBMS is huge--far bigger than the majority of vBMS additions and even bigger than some of the version transitions of vBulletin itself.
• Reverse engineering vBulletin. As a factor of the two above, I am finding it increasingly difficult to develop for vBulletin. While I applaud Jelsoft for offering a product and specifically not mangling, encrypting, or otherwise prohibiting the viewing of its source (obviously, for customers only), there is still much to be done to favor strongly to developers who build products exclusively for their product. Others who feel catoring towards developers can help Jelsoft can see my request for a "developer license" of vBulletin.
• Fraud. As many people know, online software vendors are among the worst hit for credit card fraud, and it's extremely damaging: even if a thousand copies of a piece of software are sold, it only takes one single fraudulent order to leak the product, voiding, in all honesty, the majority of future orders. After putting a great deal of time into vBMS to see it stolen so brazenly, it demoralized me.
• Bad experiences. I have appealed several times to the community to hire additional developers, but the developers I hand-picked did not work out on these occasions. So far, none of the experiences has sped up development time, so paid outside help has not worked out.
• Personal reasons. I have changed jobs, taken on part-time work (I'm still poor), and even had a death in the family break up my work.

But the ultimate reason: I want vBMS to be available for all current versions of vBulletin so those who paid good money do not feel cheated.

What can and can't I do with an open-source vBMS in terms of licensing?

You can:

• Distribute vBMS to anybody you like.
• Modify vBMS to do whatever you like (excluding changing copyright notices), and then claim the changes as your own.
• Remove mentions of vBMS, the "vBulletin Mail System", or other branding.
• Develop special distributions of vBMS that you have extensively modified, and distribute those changes as a package
• Sell any components of vBMS that you have directly created (this is allowed, but discouraged). Only the components themselves may be sold, not the entire package with your modifications included.

You cannot:

• Advertise any of your modifications that you may be selling at vBulletin.org.
• Use vBMS for any illegal purposes, including use vBMS on a forum without an active vBulletin license.
• Modify vBMS to do whatever you like, and then claim the entire product as your own.
• Remove mentions of vBMS, the "vBulletin Mail System", or other branding, and replace them with others that imply you exclusively developed the product.
• Sell any components of vBMS that the product originally contained or others have freely developed.
• Sell the product as a whole, including a modified product.

What technical skills do I need to understand how vBMS works?

You need the usual vBulletin skills in general. This means PHP, MySQL, HTML, and CSS. You also should have a working knowledge of XML.

You'll also need to familiarize yourself with how MIME headers in e-mails work. If you want to modify how vBMS receives and routes mail, you'll need to understand the beast that is the imap library: http://www.php.net/imap . The imap library is only used to receive messages; sending messages has no dependency on imap.

Will you help with development?

I'll offer simple assistance in whatever free time I have--and I'll only do it publicly in the new forum. I will not write extensive parts of code for you or talk to you privately about vBMS. I will enjoy answering questions about how vBMS works at a high-level, and then you can see the inner workings to see how it's actually implemented.

So can vBMS actually be installed?

The version of vBMS that has been uploaded is the latest development version. It can be installed on a test forum, but there are several critical bugs that need to be resolved. You can browse the old support forums (http://www.webdesignforums.net/vbms/) for an overview of those bugs. I have a suspicion that they are simple fixes to you, the community with experience with vBulletin.

What is the first goal of those movement to open-source?

I wish to have a stable version of vBMS with little to no known bugs available for vBulletin 3.5 and 3.6 as soon as possible to appease past and present customers. Feature additions should come later; compatibility and bug fixes should be the utmost priority. When the stable version for 3.5 and 3.6 is available, then new features can be added. At the old forums, there is a list of feature requests, many of which have been addressed.

What will be my role in this?

As a user experienced with vBulletin development, both you and others will benefit from a stable 3.5/3.6 version of vBMS. That should be the priority. Feature additions, visual tweaks, etc. come later. Compatibility and just making it work completely with the features already present is the most important.

What remains to be done for a transition to open-source?

The version of vBMS attached to this thread is the latest one to which customers had access. It is still littered with copyright information and warnings about piracy. While the copyright information is still valid and will perpetually be valid, you can obviously ignore the piracy warnings. A proper version will be uploaded within several days that is fully suitable for open-source use.

Remember, this means that the piracy warning is no longer applicable, but the copyright information is applicable and must never, under any circumstances, be removed.

Any last thoughts?

As with any modification, back up your site files, but more importantly, your database, before proceeding. vBMS makes a significant number of alterations and new tables.

[dodgeboard.com]

okay- you made some real progress today! Thanks for all your efforts. Email me if you need anything webmaster at dodgeboard.com

[Lionel]

Thanks, you've been a tremendous help.

[filburt1]

I must say, it's pretty damned impressive what you guys have done with it, especially figuring it out so quickly. I'd like to think it's because I coded it with some high-level concepts in mind, but more likely, you're PHP gods.

The installer's a +++++. What specific problems is it causing?

BTW, header duplication and problems will occur within the vbms_mail_message class. The API function you posted is just a wrapper to provide safe arguments for the class and to easily say "just send the message" without all the extra code.

[dodgeboard.com]

post 127:

The problem is the phrasetype table structure is not the same from 3.54 to 3.60
I had xml error from the very first line of the install. So what I did, I opened the xml and ran the queries one by one in php admin, simply changing {tp} with my prefix. Once all the tables were created and the inserts done (a matter of minutes), I imported the templates xml from the upload styles input.

Did the same for the phrases. That took a couple of minutes.

The biggest headache is the settings. I had to do them one by one, but it's only 14 of them. You need also to set the settinggroup (1 entry with phpadmin)

Then the fun begins. I replaced all $DB_Site with $db (just a search and replace for all the files).

Filburt,

Can you package these changes so that the queries are properly executed?

Then use the files posted by Lionel on post 197 to put together a 3.6.0 beta release.

[filburt1]

I have no idea how the phrasing works in vB 3.6, so I don't know even how to start fixing that one. The table prefixes should automagically be replaced when queries are run. It should add the settings and create the group as well.

If the whole process changed in 3.6 versus 3.5, then I don't know what to do. I have near-zero experience with 3.6.

(also don't have <oXygen/> installed right now)

[Lionel]

You need to deal with that single line for phrasetype (database has changed from 3.54 to 3.60)

And need to make sure all settings are there (15 of them). Here are 3 screenshots of what the complete settings should be. Some of them, I 'borrowed' from the 3.07 version to manually install.

I also borrowed the code below navbar to display new emails from the 3.07 version

[Lionel]

Originally Posted by filburt1

I have no idea how the phrasing works in vB 3.6, so I don't know even how to start fixing that one. The table prefixes should automagically be replaced when queries are run. It should add the settings and create the group as well.

If the whole process changed in 3.6 versus 3.5, then I don't know what to do. I have near-zero experience with 3.6.

(also don't have <oXygen/> installed right now)

OK here is what I did

1-Imported the phrases directly from Filburt xml into english language

2-Did same thing for templates

replace new_ with your prefix

for settings you are on your own. My sql files have my autoincrements

working 3.60 version here

[DaNIEL MeNTED]

I think you mean "replace WDF_ with your own prefix"

[dodgeboard.com]

Originally Posted by DaNIEL MeNTED

I think you mean "replace WDF_ with your own prefix"

If you look at the text files Lionel uploaded, you'll see:

PHP Code:

INSERT INTO new_product VALUES ('wdf_vbms', 'Vbulletin Mail System', 'Vbulletin Mail System', '2.52', 1, '', ''); 


I think he means to replace the new_product table line with your own prefix. Same with new_settinggroup and new_phrasetype in the corresponding files

[DaNIEL MeNTED]

Doh! Thats what I get for working on 2 things at once...