The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
vBulletin Mail System Details »» | |||||||||||||||||||||||||
[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:
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:
What can and can't I do with an open-source vBMS in terms of licensing? You can:
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. Show Your Support
|
Comments |
#162
|
|||
|
|||
This is just what I was looking for... tagging for updates!
|
#163
|
|||
|
|||
Any news? All this progress makes me quite hopeful! :knockedout:
|
#164
|
|||
|
|||
The X-Mailer-Info might be what you're talking about:
PHP Code:
That should describe what was used to send the message, and it's accurate that it points to the vBMS product URL. |
#165
|
|||
|
|||
you tell me. You have most of my files already and whatever problems you reported, I believe was fixed.
|
#166
|
|||
|
|||
Quote:
(Or perhaps i just missunderstood something.) But i just tested the version at your forum again. The mail sent from there arrived twice again at my client. |
#167
|
|||
|
|||
OK, then it was someone else. I get the double emails, you get the double emails, 2 other guys don't.
So all that is left is the double email and email not being html on site, when received from an alias. It might help to know which php version everyone uses so I could narrow down that double emails issue. Problem is I get help only once, then everyone disappears. |
#168
|
|||
|
|||
Quote:
Quote:
|
#169
|
||||
|
||||
Quote:
|
#170
|
|||
|
|||
Later on or tomorrow, I'll look at that double emails issue.
|
#171
|
||||
|
||||
I did some test driving on the VBMS and it looks like we're almost there for a working VBMS. I want to extend a big CONGRATS to all that have worked on this. It will be a very welcomed addition to vBulletin. A HUGE thankyou to Lionel for spending so much time on this and to Filburt for helping and releasing the product as open source. Way to go guys!
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|