The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
DJ's "How To Install Modifications (Mods/Hacks)" for Beginners
This article is intended to help out new vBulletin owners who are just starting out modifying their forum, but are very new to vBulletin and new or alien to coding in general. This guide will cover the basics, and tell you the things you need to know before, during, and after "installing" something you see here on vBulletin.org. Let's get a couple of terms out of the way first. "Mod" or "Hack": By now you probably have guessed that mod is just short for modification, and you'll see it frequently used here and on other vB sites (not to be confused with the shortened form of moderator). The other term often used is hack, which is just another nickname for modification. "Install": You'll also notice that above I put installing in quotation marks. The reason I did that is because not every modification actually installs anything. Some things are simple template edits, while some use the core features already built into vBulletin. We use the term "install" for all of these, even though technically your not installing anything, nor are you making any actual modifications to your board. Disclaimers All sites that offer third party plugins to existing software come with the warning that you use these products at your own risk. If you install a modification from here and it doesn't work, or your forum becomes unusable, who's fault is that? The coders? vBulletin.org? Or you? The answer to that question falls squarely on the individual who chose to install the modification to begin with. So proceed with caution and don't blame anyone but yourself if things go wrong. One important way to remain cautious is to do a backup of your database prior to installing your modification. This will ensure that you can restore your forum back to a state when it was fully functional. If you don't know how to do that, here are a couple of good tutorials: Downloading Modifications You may notice that an author has attached several different types of files to his/her modification thread. This could be a PHP file , an XML file , TXT files or a ZIP folder . ZIP folders are the most common type of files attached to threads because they can contain file types that the forum ordinarily would not allow you to upload, but more importantly they're compressed, so an author can add lots of content in one file. In most cases, this is where your install instructions and other important documentation will be located along with whatever else the modification requires to run. You will need to download this file and extract the contents using some kind of decompression software. Your computer should already have this ability built in, but in the event it doesn't or you need a better manager, you can get an excellent free version from ZipGenius. Install Instructions Can Have Different Steps Now that we've got that out of the way, lets get to the reason why you called. Installing modifications is not as hard as it sounds, and coding skill is generally not required in most cases. Sometimes you may need to use a little common sense, and you should always follow your steps carefully and without distraction. The vast majority of problems that develop when installing modifications come from the user not following the directions carefully or completely. Then they want to blame the author if their forum looks funny afterwards, when all that's happened is they're missing a quotation mark, or they forgot to upload a file. There is no one way to install modifications. They all work differently, and their application will invariable be different. However, if you were to take all the steps from every modification on vBulletin.org and break the steps down into their basic type, you'd only end up with six basic methods: Template Edits, File Edits, Upload Files, Import Product/Plugin, Use Core Content and Use External Content. Sometimes you'll have to do just one of these. Sometimes you'll have to do a combination of more. Highly unlikely you'd ever have to do all six, but I digress. Let's look at the steps you will no doubt be asked to do and address what they mean and what they accomplish.
In most cases, uninstalling a product is the same thing as installing a product, only in reverse. In your Product Manager, you'll find a list of installed modifications. Most of the time, uninstalling is as simple as clicking uninstall. Usually anything more complex than that will come with it's own set of uninstall instructions. Either way, check the documentation that came with the product. You would be surprised how many mistakes can be avoided just be re-reading the original thread information or reading "READ ME" files included in the ZIP file. Common Terms and Phrases Here are a few common instructions you may run into that you may not readily know what they mean.
I Need HELP???!!!111?!! (Forum Etiquette 101) Believe it or not, there are some things you need to do if you want to get help with a certain modification. First and foremost, you should check to see if your question hasn't already been asked, possibly many times before. No, you don't have to search the whole forum, nor do you have to read every post in a 120 page thread. Use the Search this Mod feature in the top right corner of every modification thread. Remember that you can use quotation marks " " to search for phrases that have words that fall under the allowed character limit. When that fails, your best bet on getting help will be from the original thread where you downloaded the mod. It doesn't matter that the thread is 3 years old, starting a new thread about a mod that already has one will just result in you being redirected back to the original. Also, REMEMBER TO MARK AS INSTALLED. Why? Because a great many mod authors will not give support to people who have not marked a thread as installed, or will list them as low priority. Plus, clicking that little box will help you in the long run, as you will be notified of important updates and bug fixes to the modification. Keep in mind that just because a thread is marked "Supported" doesn't mean that the author is going to get back to you in a timely manner. The author could be on vacation, working, sick, dealing with the loss of a loved one or a host of other possibilities. Also keep in mind that no one gets paid for their work here. All mods here are submitted for free and are developed in the author's spare time. So showing the same indignant attitude that you would for, say, a paid product, is not likely to get you a lot of help, as the danger of loosing your buisness is kind of a moot point. Sometimes, not often, but sometimes, no one knows the answer to your question. It's unfortunate, and we all do our best to keep that from happening. But when it does, repeatedly bumping the thread with the same question over and over again is not going to help. Now, if quite a bit of time has passed and you notice that other's have been getting support in the interim, then give the thread a friendly bump. But keep in mind that no response is often tantamount to "I don't know", and not "I don't care". Remember the old saying that you'll catch more flies with honey then you will with vinegar? Keep that in mind, because no one here at vB.org gets paid for their efforts and they are helping just because they can. That means they can choose to NOT help you just because they can. So don't give them any more reason not to, then they already have. Be patient, use common sense, check and double check your work carefully and be courteous when seeking help, and your experience on this site will be productive, enjoyable and you'll likely be able to work out any problems you may encounter. |
#2
|
||||
|
||||
Fantastic! Great, well written article. A lot of people will find this most useful.
Thank you for taking the time to put it together. I do have one question though...it's concerning the removal of a mod that made changes to the database. Some authors include a executable removal file. However, some do not. In most cases is it ok or common practice to un-install the product, remove the files and leave the db as is? |
#3
|
||||
|
||||
Quote:
But in the event the explanations are not that explicit, your best bet is to check with the developer or other people in the modification thread. In most cases, the tables will probably be sitting there doing nothing and doing no harm and dropping them is as simple as logging into phpMyAdmin and removing them. But since databases are extremely delicate, you should make absolutely sure of what your doing before you do it. And that means checking within the modification thread as thoroughly as possible, and doing your research before proceeding. |
#4
|
||||
|
||||
Very nice DJ!!! This will help so many w/ the basics and very well done!
|
#5
|
||||
|
||||
DJ, what a great article! Where was this when I started out a few months ago?!
Thanks again for all of the contributions that you make to this community and for helping others as you always do! :up: |
#6
|
|||
|
|||
THANKS SO MUCH FOR THIS DIG! IT IS VERY MUCH APPRECIATED!m I printed it for reference
Gabby |
#7
|
|||
|
|||
Thanks for this. I was at sea without it.
|
#8
|
||||
|
||||
Updated the article to include Markup Validation to Common Terms and Phrases.
|
#9
|
||||
|
||||
Updated the article to include a little bit about uninstalling. Sadly, I ran out of character count so I could include more.
|
#10
|
|||
|
|||
thanks for the great article;
including tips on how to upgrade would be great |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|