vBulletin is a very popular, commercial discussion forums application. Written in PHP, it is the system of choice for many of the biggest and most popular discussion forums on the Internet.
This book takes you step by step through setting up and running your own vBulletin website. In easy‑to‑follow language, it will show you how to select a vBulletin license, set up the site, and then customize and use it for maximum impact. You will learn how to use the powerful administration features of vBulletin, and even see how to alter the code to create your own 'hacks'.
Chapter 1 gives you a quick overview of vBulletin's key features and benefits and helps you choose the right vBulletin license for your community's needs.
Chapter 2 shows you how to go about installing and configuring a vBulletin installation.
Chapter 3 gives you a quick tour of vBulletin from both the user's perspective and the admin side.
Chapter 4 shows you how to go about customizing almost every aspect of a vBulletin installation.
Chapter 5 is a key chapter, which shows a vBulletin forum administrator how to go about administering every aspect of their forum.
Chapter 6 looks at the vBulletin upgrade process and guides you through the successful migration of all the important settings and customizations.
Chapter 7 shows you how to go about designing a new vBulletin template.
Chapter 8 shows you how to create and then distribute new vBulletin forum hacks.
Chapter 9 provides you with an important programmer's reference of information that will be handy to you when working with a vBulletin forum.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
There are three styles for code. Code words in text are shown as follows: "On most installations the database server is located on the same computer as the web server, in which case the address should be set to localhost."
A block of code will be set as follows:
<meta http-equiv="Cache-Control" content="no-cache" />
<!-- end no cache headers -->
<title><phrase 1="$vboptions[bbtitle]">$vbphrase [x_powered_by_vbulletin]</phrase></title>
$headinclude
When we wish to draw your attention to a particular part of a code block, the relevant lines or items will be made bold:
<meta http-equiv="Cache-Control" content="no-cache" />
<!-- end no cache headers -->
<title><phrase 1="$vboptions[bbtitle]">$vbphrase [x_powered_by_vbulletin]</phrase></title>
$headinclude
Any command-line input and output is written as follows:
GRANT ALL ON vb_database.* TO vb_user@localhost IDENTIFIED BY 'password';
New terms and important words are introduced in a bold-type font. Words that you see on the screen, in menus or dialog boxes for example, appear in our text like this: "clicking the Next button moves you to the next screen".
Feedback from our readers is always welcome. Let us know what you think about this book, what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply drop an email to [email protected], making sure to mention the book title in the subject of your message.
If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or email [email protected].
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Visit http://www.packtpub.com/support, and select this book from the list of titles to download any example code or extra resources for this book. The files available for download will then be displayed.
Although we have taken every care to ensure the accuracy of our contents, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in text or code—we would be grateful if you would report this to us. By doing this you can save other readers from frustration, and help to improve subsequent versions of this book. If you find any errata, report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the Submit Errata link, and entering the details of your errata. Once your errata have been verified, your submission will be accepted and the errata added to the list of existing errata. The existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
You can contact us at [email protected] if you are having a problem with some aspect of the book, and we will do our best to address it.