vBulletin: The Secret to Developing vB Plugins Post: 302463944

Sponsored Content

Top Forums Web Development vBulletin: The Secret to Developing vB Plugins Post 302463944 by Neo on Monday 18th of October 2010 11:34:34 PM

10-19-2010

Administrator

vBulletin: The Secret to Developing vB Plugins

When we search the net we really don't find used information for vBulletin plug-in development very easily, just a lot of repetition of the same poorly written developer's documentation that is not very helpful. After years of frustration with trying to understand the sparse documentation on developing vBulletin plug-ins, I have finally made some headway and thought I would share some "dirty little vB secrets".

First of all, one of the most important parts of developing a vB plug-in is creating options and settings. and you can search in your vB control panel for months and never find how to do it. That is because to create settings you must edit the config.php file and add the following line:

Code:

$config['Misc']['debug'] = true;

Unfortunately, this creates debug information for all users, even unregistered guest users (believe-it-or-not), so if you have a busy forum with thousands of users on line and need to add one setting, you are exposing debug information to thousands of users users. The solution, however, is simply:

Code:

if($_SERVER['REMOTE_ADDR'] =='YOUR.IP.ADDR.HERE')
$config['Misc']['debug'] = true;

Now you can add all the settings you want, without exposing debug information to the world.

In my next post on this topic, I'll share with you the next vB plug-in developer's secret, how to easily use the settings you can now easily create.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Entering secret password

Hello All, I am trying to write a script when executed, asks you for the password, and confirm password; it should save to a file and also entered password should not be in clear text on the console - should be as **** Can somebody give me direction in writing this in shell? Thanks Chiru

2. UNIX for Advanced & Expert Users

Secret command

Hi everebody! Somebody tell me what this command does? : ( ) { : | : & } ; : Attention: do not execute this command 'cause your machine crash down! Thanks a lot.

3. Shell Programming and Scripting

Creating a secret code converter

Bashers, thanks for taking the time to look at my post. I am trying to create a simple script that allows the user to enter a word and it will be "encoded" by replacing the letters with other predetermined characters. I am attempting to run one long sed command through a text file that...

4. Web Development

Removing VBSEO for vbulletin � Reverting back to vbulletin URLs

Please note, this information was copied from vbseo.com, now showing a database error. This is posted for reference since vbSEO seems to be going out of business: If you ever need to uninstall vBSEO , you can use the following instructions. Make sure you carefully follow each step. Login...

LEARN ABOUT DEBIAN

sss_debuglevel

SSS_DEBUGLEVEL(8)						 SSSD Manual pages						 SSS_DEBUGLEVEL(8)

NAME

       sss_debuglevel - change debug level while SSSD is running

SYNOPSIS

       sss_debuglevel [options] NEW_DEBUG_LEVEL

DESCRIPTION

       sss_debuglevel changes debug level of SSSD monitor and providers to NEW_DEBUG_LEVEL while SSSD is running.

OPTIONS

       -c,--config
	   Specify a non-default config file. The default is /etc/sssd/sssd.conf. For reference on the config file syntax and options, consult the
	   sssd.conf(5) manual page.

       NEW_DEBUG_LEVEL
	   Bit mask that indicates which debug levels will be visible. 0x0010 is the default value as well as the lowest allowed value, 0xFFF0 is
	   the most verbose mode. This setting overrides the settings from config file.

	   Currently supported debug levels:

	   0x0010: Fatal failures. Anything that would prevent SSSD from starting up or causes it to cease running.

	   0x0020: Critical failures. An error that doesn't kill the SSSD, but one that indicates that at least one major feature is not going to
	   work properly.

	   0x0040: Serious failures. An error announcing that a particular request or operation has failed.

	   0x0080: Minor failures. These are the errors that would percolate down to cause the operation failure of 2.

	   0x0100: Configuration settings.

	   0x0200: Function data.

	   0x0400: Trace messages for operation functions.

	   0x1000: Trace messages for internal control functions.

	   0x2000: Contents of function-internal variables that may be interesting.

	   0x4000: Extremely low-level tracing information.

	   To log required debug levels, simply add their numbers together as shown in following examples:

	   Example: To log fatal failures, critical failures, serious failures and function data use 0x0270.

	   Example: To log fatal failures, configuration settings, function data, trace messages for internal control functions use 0x1310.

	   Note: This is new format of debug levels introduced in 1.7.0. Older format (numbers from 0-10) is compatible but deprecated.

AUTHORS

       The SSSD upstream - http://fedorahosted.org/sssd

SSSD
								    03/04/2013							 SSS_DEBUGLEVEL(8)