Vbulletin error handling & logging

vbulletin error handling & logging

Hi, After the EXT JS application is deployed on client's place how can we debug the JavaScript error's that might creep up, particularly if the client is. If you aren't seeing the actual error message I would guess the code Error Handling & Logging Options > Log Database Errors to a File. Log Database Errors to a File If you would like to log all database errors to a file, enter the path to the file here. · Log Failed Admin Control Panel Logins to.

watch the video

vBulletin 4.1.3 error . Need Help

Vbulletin error handling & logging - this

Edit your config.php file and make sure you have a valid email in this line:


Block Disabled:      (Update License Status) 
Suspended or Unlicensed Members Cannot View Code.

Then, go back to your site and produce the database error and let us know what it says in the email you get. We need to know the exact error that is emailed to you in order to help out. (Most likely, on a fresh install, you have some wrong information in the config.php file and vbulletin is unable to connect to your database.)
__________________

Former vBulletin.org Staff Member

Try a search before posting for help. Many users won't, and don't, help if the question has been answered several times before.
W3Schools - Online vBulletin Manual
If I post some CSS and don't say where it goes, put it in the additional.css template.
I will NOT help via PM(you will be directed to post in the forums for help.)

No members have liked this post.

Path to Error Handling and Logging options: Settings > Options > Error Handling and Logging


Log Database Errors to a File
To log all database errors to a file, enter the path to the file. The file will be saved as {filename}.log.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Log Failed Admin Control Panel Logins to a File
To log all failed Admin Control Panel login attempts to a file, enter the path to the file. The file will be saved as {filename}.log.
.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Log PHP Errors to a File
To log all PHP fatal errors to a file, enter the path to the file. The file will be saved as {filename}.log.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Log Emails to a File
To log all emails to a file, enter the path to the file here. The file will be saved as {filename}.log.

You should enable email logging only if you suspect problems with the email system within vBulletin.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Maximum File Size of Error Logs(default: 1048576)

1048576 bytes = 1 megabyte

If you want your vBulletin error logs to be rotated when they reach a certain size, enter the maximum file size in bytes.

When a log file reaches this size, it will be renamed as {filename}{unix timestamp}.logand a new file will be created.

Set this value to 0 to disable log rotation.


Disable Database Error Email Sending(yes/no)

To prevent vBulletin from sending email to the $config['Database']['technicalemail'] address you specified in config.php, set this value to Yes.

Error reports about database connection errors will still be sent.

We do not recommend that you set this value to Yes unless you are logging database errors to a file.

vBulletin 5x Remote Code Execution Vulnerability

Introduction
vBulletin is a global leader in forum and community software. Featuring strong security, robust management, good user experience, and the capability to serve more than 40,000 online communities, it is a very popular platform used by many major forums. Customers include well-known game company EA, game platform Steam, Sony, NASA, etc. It has many large customers in China including forums with tens of thousands of users such as Fengniao, 51 group buying, and OceanTribe.

Vulnerability Introduction
On August 11, 2020, Sangfor FarSight Labs followed a zero-day vBulletin 5.x remote code execution vulnerability identified by security researcher Amir Etemadieh (Zenofex). The zero-day vulnerability bypasses the released patch for CVE-2019-16759, a vBulletin vulnerability disclosed in 2019. The new zero-day does not have a CVE designation assigned yet, but the severity is identified as critical due to its simplicity and its ability to remotely execute commands on vulnerable vBulletin servers. Remote attackers can execute arbitrary code through specially crafted malicious parameters to control the target server or steal sensitive user information. This vulnerability affects all versions of vBulletin 5.x and exploit attacks have started to appear in the wild. vBulletin has recently released a fix for the vulnerability.

Vulnerability Reproduction
We reproduced this vulnerability in vBulletin 5.x by executing echo command, as shown in figures below:

Vulnerability Reproduction

Impacts
By searching from the Internet, we know that there are nearly 30,000 public-facing websites using vBulletin worldwide, and many of them are international community forums maintained by large international companies, so the vulnerability causes huge impact.

Affected versions:vBulletin 5.x

Timeline
Aug 11, 2020 Sangfor security team tracked a zero-day vulnerability, vBulletin 5.x remote code execution vulnerability.

Aug 12, 2020 Sangfor FarSight Labs reproduced this vulnerability successfully and released a vulnerability alert with remediation steps.

Remediation
1. vBulletin announced that patches were available for the 5.6.0, 5.6.1, and 5.6.2 versions of vBulletin Connect. The fixes remove the PHP Module. A full patch will be included in the next build of 5.6.3 and the PHP Module will be completely removed in vBulletin 5.6.4. For affected users, please follow its official website to obtain the latest patches: https://www.vbulletin.com/.

2. Sites running older versions of vBulletin need to be upgraded to vBulletin 5.6.2 as soon as possible according to vBulletin.

Temporary Remediation
vBulletin administrators can modify settings to prevent this vulnerability from being exploited by following these steps:

a) Log in to vBulletin Administrator Control Panel.

b) Click "Settings" on the left menu and click "Options" in the drop-down menu.

c) Select "General Settings" and click "Edit Settings".

d) Look for "Disable PHP, Static HTML, and Ad Module rending" and set to "YES", then Click Save.

Sangfor Solution

1. For Sangfor NGAF customers, update NGAF security protection.

2. Sangfor Cloud WAF has automatically updated its database in the cloud. These users are already protected from this vulnerability without needing to perform any additional operations.

3. Sangfor Cyber Command is capable of detecting attacks which exploit this vulnerability and can alert users in real-time. Users can correlate Cyber Command to Sangfor NGAF to block an attacker's IP address.

4. Sangfor SOC has Sangfor security specialists available 24/7 to help you resolve any security issues. For users with vulnerabilities, the SOC regularly reviews and updates device policies to ensure protection against this vulnerability.

Hi,

To cross populate you need someone who knows a little about databases. There are different ways but simplying exporting the usernames/passwords from the phpbb to a file then importing into Moodle (or vice versa) is a reasonble a way forward.

PhPBB is opensource and well tested. On many webhosts you can install directly from the control panel - it's provided for free. This way I would prefer if you've little experience because occasionally PhPBB needs a security patch which need to be installed. Its easy to do but if your webhost does it for free (or gives you notice that it needs to be done) its better. There are many "hacks" - alterations to the code that extend the functionality (see phpbbhacks.com)- I use these but really you shouldn't need them

Vbulletin needs a licence fee of over $100 and a support contract of about $30/year. It offers the same things really but a lot of webmasters I know use it simply because it takes the stress out of updates etc. VBulletin tends to have a little more functionality as a standard.

There are many free themes for both and many services which allow you to get a Corporate theme for your board. 'Skinning' a theme is not too difficult - slightly harder than making a theme for Moodle.

You can transfer data between phPBB and Vbulletin. So a reasonable way forward is to install PhPBB- use it to see if its what you want then make a decision at that point. You will also have a better understanding of how PHPBB works and that maybe enough to give you confidence to use it.

In use these boards have a lot of power.They have been forcably "evolved" through the internet (built by 16 year olds FOR 16 year olds) and are both easy to use and very complete in thier prowess.

e.g: Setting passwords to forums, even topics, mass emails to groups, advanced editing functions, banning (for time periods eg. a few hours to infinite) , creating stickies, activity logs of individuals, IM systems, poll creation, word filters, hiding areas from some groups, pre-authorisation of avatars, users, signatures, uploading of files in predefined formats etc etc.

Virtually every permutation of what you might want. This comes at a price of needing to learn how to use it. Moodle is a pushover in this respect.smile

There are very full forums offering advice on PhPBB and Vbulletin. These boards are the main stay of the Internet. You can often get a response about an issue in minutes... and of course if you use the search function your problem has almost certainly been covered before.

Most important of all these boards DEFAULT TO A NON-SUBSCRIPTION TO THREAD status.....

Let us know how it goes on...

tags in all browsers. With CSS the 'width' style attribute can be used to control the width more precisely, rendering these three replacement variables obsolete. With the information in this table, your transtion from the vBulletin 2 styles system to the vBulletin 3 system should be as painless as possible. Style Inheritance Back to Top Like so many other systems in vBulletin, the vBulletin Styles system works around the concept of inheritance. In essence, this means that you can create an unlimited number of styles in which your board can be viewed, and customizations made in one style will be inherited by all of its 'child' styles. Inheritance Example Back to Top The concept of inheritance as used by vBulletin 3 styles is best illustrated with an example of a common use for the system. Many site owners will want to customize the look of their vBulletin installation so that it fits in with the style of the rest of the site. This is normally done by editing the colors used by vBulletin, and by editing the header and footer templates. Let us imagine that we want to customize your header and footer templates, but we also want to offer three different color schemes for our visitors to choose between. For argument's sake, we'll call these the 'Red', 'Green' and 'Blue' styles. We could create three new styles, calling one 'Blue', one 'Green' and one 'Red', then customize the header and footer templates in each style. That would be a perfectly valid solution, but has one serious disadvantage, in that should we decide that we want to alter the HTML in the customized header template, we would need to go through and edit the template in each of our three styles individually. A much more manageable solution would be to create a single new style, which we will call 'Custom Header / Footer' and customize the header and footer templates within this style. Now in order to offer site visitors the three color variants we want, we create the 'Red', 'Green' and 'Blue' styles as child styles of the 'Custom Header / Footer' style. Each of these child styles will inherit the customized header and footer templates from the 'Custom Header / Footer' parent style, so we will not need to edit that template in the child styles, and if we choose to change the HTML of either the header or footer templates at some point in the future, we need only edit those templates in the parent style, and the changes will be automatically inherited by the three child styles. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 97/380 1/11/2018 vBulletin Manual While this is a very simple example, involving only the site color scheme and the header and footer templates, the vBulletin styles system allows you to individually customize every template and every CSS attribute of a style, and each of those customized attributes can be inherited by all child styles. In the next section we will look into the mechanics behind this system in order to gain a good understanding of how to use vBulletin styles most effectively. Inheritance Mechanics Back to Top In the vBulletin styles system, each element of a style can be customized from the vBulletin default value, and each customization will be inherited by any child styles of the style in which the customization was made, unless the value is further customized in the child style. In order to explain this in simple terms, let us assume that a vBulletin style consists of [x] individual elements, those being a background color, a text color, a font style and a few templates. For the purposes of this example, we will represent the contents of a style like this: Background Color Text Color Font Style Header Template Footer Template #FFFFFF #000000 10pt verdana, arial,

This is the default

This is the default helvetica, sans-serif 'header' template!'footer' template!
Using the example of the customized header and footer templates we used in our first look at style inheritance, we can imagine that we could represent the 'Custom Header / Footer' style like this: vBulletin Default Background Color vBulletin Default Text Color Font Style #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif Header Template Footer Template

This is the default 'header' template!

This is the default 'footer' template!

#FFFFFF #000000 10pt verdana, arial,

This is my custom

This is my custom helvetica, sans-serif 'header' template!'footer' template!
In this example, items that have been customized in a style are shown in red. You can see that the background color, text color and font style values are all shown in black, meaning that they are unchanged from the default values, while both the header and footer templates are shown in red, meaning that they have been customized, and therefore override their default contents. Custom Header / Footer We will now add the final branch of the style tree from our previous example, namely the 'Blue' style. Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is my custom 'footer' template!

#0000FF #FFFFFF 10pt verdana, arial,

This is my custom

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Here we can see that both the background and text color values have been customized, and are therefore shown in red, while the font style value has not been changed and therefore is being inherited from the vBulletin default values. However, both the header and footer templates have been customized in the parent 'Custom Header / Footer' style, and so those custom versions are inherited by the 'Blue' style. This inheritance is shown as an orange value. Blue Furthermore, if we now decided to customize the header template in the 'Blue' style, we would have something like this: Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is my custom 'footer' template!

#0000FF #FFFF00 10pt verdana, arial,

This is my special BLUE

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Here we can see that the customized (red) header template in the 'Blue' style overrides not only the default vBulletin header template, but also the customized header template from its parent 'Custom Header / Footer' style, while the Footer template is still inherited from its parent. Blue To illustrate the ability of vBulletin's style system to allow a theoretically infinte level of parent/child relationships between styles, we will now add a child style to the 'Blue' style, in which we will set the font size to be extra large. We will call this style 'Big Font Blue'. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 98/380 1/11/2018 vBulletin Manual In this style, we will customize the font size attribute to be larger than normal, which will result in a style inheritance diagram like this: Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is my custom 'footer' template!

Blue #0000FF #FFFF00 10pt verdana, arial, helvetica, sans-serif

This is my special BLUE

This is my custom 'header' template!'footer' template!
#0000FF #FFFF00 14pt verdana, arial,

This is my special BLUE

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Here you can see that the vBulletin default font style is inherited by the 'Custom Header / Footer' style and the 'Blue' style, but is overridden by the customized version in the 'Big Font Blue' style. Big Font Blue Were we to now customize the font style in the 'Custom Header / Footer' style, the change would automatically be inherited by the 'Blue' style, but would not be inherited by the 'Big Font Blue' style, as it has its own customized version. Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 12pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is my custom 'footer' template!

Blue #0000FF #FFFF00 12pt verdana, arial, helvetica, sans-serif

This is my special BLUE

This is my custom 'header' template!'footer' template!
#0000FF #FFFF00 14pt verdana, arial,

This is my special BLUE

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Additionally, were we now to revert the customized footer template in the 'Custom Header / Footer' style, its child styles would automatically inherit the vBulletin default value. Big Font Blue Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 12pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is the default 'footer' template!

Blue #0000FF #FFFF00 12pt verdana, arial, helvetica, sans-serif

This is my special BLUE

This is the default 'header' template!'footer' template!
#0000FF #FFFF00 14pt verdana, arial,

This is my special BLUE

This is the default helvetica, sans-serif 'header' template!'footer' template!
The system does not allow you to alter the vBulletin default value for any item, so you can revert any of your customizations at any time to their original contents. Big Font Blue This diagram illustrates the decision system used by vBulletin when loading each element from a style. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 99/380 1/11/2018 vBulletin Manual The Style Manager Back to Top The Style Manager is the central hub for editing and creating vBulletin styles and their constituents. From here you can control every aspect of the way your vBulletin installation appears to your visitors, from simple color and font changes right through to fundamentally altering the layout of the board by editing templates. The image above shows the Style Manager as it would appear immediately after a new vBulletin installation. Looking at the Style Manager from left to right, various controls are visible. The 'Allow User Selection' Checkbox This checkbox controls whether or not the style will be available for non-administrators to use. If the checkbox for a style is cleared, only administrators will be able to use that style. The Style Title Hyperlink The style title is also a hyperlink. Clicking it will open a new window and show the public area of your vBulletin using the style you clicked, even if the public are not able to use that particular style. The Display Order Text Box The small text box containing a number controls the display order of a style. Higher numbers will be displayed later in the listing. This value makes absolutely no difference to the content of the style, and is used soley for convenience of display. The Style Options Menu This popup menu contains links to make alterations to the style such as changing its title, downloading the style as a style.xml file etc. The Expand/Collapse Templates List Button Clicking the [« »] button will open or close the list of templates for the current style. Note: Examples of (modified) vBulletin boards: http://www.vBulletin.com/links.php Examples of vBulletin style and template modifications here: http://www.vBulletin.org/forum/ Creating New Styles To create a new style, click the [Add New Style] link underneath the main body of the Style Manager. Back to Top This will bring up the Add New Style interface. The controls on this form are as follows: Parent This menu controls the way that this new style will inherit attributes from other styles that you may have Style defined. For a complete discussion of vBulletin 3 style inheritance principles, see Style Inheritance. Title Here you should enter the name you have chosen for your new style Allow This Yes/No choice corresponds to the checkbox next to each style on the main Style Manager interface, User and affects whether or not your visitors will be able to use this style to view the board. Selection Display This text box expects you to enter a whole number (0, 15, 99, 1007 etc) to affect the position at which https://www.vbulletin.com/docs/onepage/?manualversion=40205500 100/380 1/11/2018 vBulletin Manual Order this style will appear in any style lists. It corresponds to the display order text box on the main Style Manager interface. When you have filled in the forum, hit the [Save] and you will be returned to the Style Manager, where your new style will be shown. Creating Child Styles Back to Top To create a child style of an existing style, click on the style options menu for the style of which the new style will be a child, and pick Add Child Style from the popup menu. This will take you to the Add New Style interface, with the correct parent style already selected in the form. You may continue to add further child styles to child styles in order to satisfy any inheritance critera you may require. The image above illustrates the style layout as described in the reference guide to Style Inheritance. Editing Style Settings Back to Top If you decide at any time that you need to rename a style, alter its display order or perhaps even change its parent/inheritance arrangement, you will need to select Edit Settings from the style options menu for the style you want to edit. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 101/380 1/11/2018 vBulletin Manual This will load the Edit Style Settings interface, which appears almost identical to the Add New Style form previously described. Using this form you can easily rename the selected style, change its display order or change the ability of users to choose this style. Note: If you choose to change the parent style, you should bear in mind the changes to your styles that this alteration will make. For example, if we were to change the parent of the 'Red' style to 'No Parent', any templates, CSS or StyleVars currently being inherited from the 'Custom Header / Footer' style would no longer be inherited. In practice, this would mean that the customized header and footer templates defined by the 'Custom Header / Footer' style would no longer be used by the 'Red' style. Consider changes such as this before changing the parent of an existing style. Deleting a Style To delete a style, click on the style options menu in the Style Manager and choose Delete Style. Back to Top Note: When you delete a style, any customized templates, CSS, StyleVars or replacement variables belonging to that style will be deleted along with the style. If the style you choose to delete has no child styles, a confirmation dialog will be displayed, informing you of exactly what is to be deleted and asking if you are sure. If you confirm the deletion, the style will be irrevokable deleted, along with any customizations made within it. On the other hand, if the style you choose to delete has one or more child styles, an extra step will be added into the deletion process should you choose to continue with the deletion. Any child styles of the style you delete will not be deleted, but rather they will be attached to the parent style of the style you have deleted. For example, if you have a style arrangement of Custom Header / Footer -- Red -- Green -- Blue ---- Big Font Blue ... and you chose to delete the 'Blue' style, then the child style of 'Blue' will be attached to the parent style of 'Blue', resulting in this: Custom Header / Footer -- Red -- Green -- Big Font Blue Note: When deleting styles that have child styles, be aware that any customizations made in the style to be deleted will no longer appear in the child styles after the style has been deleted. Editing the Templates https://www.vbulletin.com/docs/onepage/?manualversion=40205500 Back to Top 102/380 1/11/2018 vBulletin Manual To edit any of vBulletin’s templates directly, select [Edit Templates] from the style options dropdown or click the [« »] button. Other template related options in the drop down include: Add New Template – this takes you to the form to add a new template not based on any existing template. Revert all Templates – this will automatically remove all templates that have been customized in this style. The templates in this style will become equivalent to the templates of its parent style. The template list will look similar to this: On the left, you will see a list of templates (white background) and template groups (black background). On the right, you will see 5 buttons. Any buttons you cannot use will be grayed out. Customize – if a template has yet to be edited in this style, click this button to edit it. Expand/Collapse – this button expands or collapses a specific template group. Edit – if a template has already been edited in this style, click this button to edit it further. This is effectively the same action as Customize. View Original – if the selected template has been edited in this style, clicking this button will show you the original version of the template. Revert – this button allows you to revert a template to the version that is being used in the parent style (or the original if there is no parent style). If the template being reverted is a custom template with no corresponding original/default then it will be deleted. You may also double click the template or template group name on the left and the appropriate action will be executed; templates will be Customized or Edited and template groups will be Expanded/Collapsed. Templates are color coded as follows: Black – this template is unmodified in this style or any parent styles. The version included with vBulletin will be used. Orange – this template has been modified in a parent style, but not in this style. The modified template will be used. Red – this template has been modified in this style. The customized version will be used. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 103/380 1/11/2018 vBulletin Manual You may modify this color scheme by editing your control panel styles. Note: The template manager will look significantly different in browsers other than Internet Explorer. However, the functionality is the same. Adding or Editing a Single Template Back to Top Editing a template is simply like editing regular HTML. Each template represents XHTML bits with PHP-style ($varname) variable names. For more information on what you can use in the templates, see the Templates Introduction. Product - the name of the product which introduced this template. By default this will be vBulletin. Style – the name of the style that this template is in or will be inserted into. Title – the title of the template. This is what is used to identify a template, so it must be unique. Generally, only a-z, A-Z, 0-9, and _ are used. If there is more than one template revision stored an additional link of [View History] will be shown. This link will allow you to compare the current template with previous versions. Template – this is the actual body of the template. The [Show Default] link will show you the unmodified version of the template. Search in Template – the text box and [Find] allow you to search within the template text. Please note that this is not available in all browsers. This row also contains several additional options: Copy – this automatically copies the context of the Template box to your clipboard. View QuickRef – this displays the language quick reference. Save in Template History - This row allows you to save your template revision for future comparison if needed. You can add a comment to help you remember what was changed. Comparing Templates Back to Top vBulletin allows you to store multiple historical versions of a template. You can use these to compare template changes across versions and to keep track of your edits. The feature lets you quickly and easily see the differences between two versions of the template. This feature is accessed by clicking the [View History] in the template editor. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 104/380 1/11/2018 vBulletin Manual When you first enter it will give you a list of all the template revisions stored. Each row will give you the following information: Status - This will tell you if the template is the currently active template, a historical revision or the current default. Last Modified - When the template was last modified and who edited it. Version - The version of vBulletin in which the template was modified. View - Simply allows you to view the template by itself. Old/New - Allows you to select the template revisions for comparison. Old is showed on the left side of the resulting screen and New is shown on the right. Each historical revision will also provide a delete checkbox so that you can remove it from the database if you wish. Once you select two templates to compare, click on the Compare Versions button. The result will be similar to the image below and show where differences between the two versions occur using color highlights and using View SideBy-Side mode The default mode is a diff format (or View Inline mode) which will look similar to the image below Mobile Style https://www.vbulletin.com/docs/onepage/?manualversion=40205500 Back to Top 105/380 1/11/2018 vBulletin Manual In vBulletin 4.1.2, a mobile style was introduced. This is a streamlined style that allows easier browsing on smartphones and other small screen devices. The Mobile Style is meant to be complementary to your vBulletin installation and simplify access for your users. Installing the vBulletin Mobile Style Back to Top Mobile Style Install If you're doing a new install, or are upgrading an existing install that didn't have a mobile style, a "Default Mobile Style" will be created in the mobile style list, and it will be automatically set as both 'Default Style for Old Mobile Browsers' and 'Default Style for Modern Mobile Browsers' (in Admin CP -> Settings -> Options -> Style & Language Settings). Mobile Style Upgrade If you're upgrading an existing install, that had a mobile style, from 4.1.10 (or lower) to 4.1.11 (or higher), a "Default Mobile Style" will be created in the mobile style list, and any style that was set as either Default Style for Old Mobile Browsers or Default Style for Modern Mobile Browsers (in Admin CP -> Settings -> Options -> Style & Language Settings) will be moved to the mobile style list, effectively becoming a mobile style. Note: that if you were previously using the normal Mobile Style provided by vBulletin, you need to revert all its templates after it is moved to the mobile style list, or they will all show as customized and never be updated automatically during upgrades. Rather than the above, you may also just delete the Mobile Style you had since before the upgrade, and use instead the "Default Mobile Style" added by the upgrade (also setting it as 'Default Style for Old Mobile Browsers' and 'Default Style for Modern Mobile Browsers'), but it is not recommended to do so as it may cause some oddities to your mobile users until they clear their cookies. Any upgrade from 4.1.11 to an higher version will not require any intervention on your part for the mobile style upgrade. Disabling the Mobile Style If you do not wish to use the mobile style, you can disable it following these steps: Back to Top 1. Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Old Mobile Browsers. Set 'None'. 2. Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Modern Mobile Browsers. Set 'None'. 3. Admin CP -> Styles & Templates -> Style Manager. Edit any style in the mobile style list and set "Allow User Selection" to No. Admins will always be able to use the mobile style, as they can always use any existing style and because it is not possible to delete the last mobile style. Enabling the Mobile Style If you do wish to use the mobile style, you can enable it following these steps: Back to Top Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Old Mobile Browsers. Select 'None' from the Dropdown menu. Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Modern Mobile Browsers. Set 'Default Mobile Style' from the dropdown menu. Admin CP -> Styles & Templates -> Style Manager. Edit any style in the mobile style list and set "Allow User Selection" to Yes. Note: Note: Not all Old Mobile Browsers will be able to use the Default Mobile Style. For the purposes of these older browsers, you may be able to find a style available at www.vbulletin.org. Frequently Asked Questions Why does the Mobile Style have its own Style Manager? This is because it is based off a secondary Master Style. Back to Top What are the benefits of basing the Mobile Style off a secondary Master Style? It allows the Mobile Style to work like the Default Style. This helps with installation, upgrades and customizations. Plus you can create multiple mobile styles and save customization between versions and upgrades. My users are saying the Mobile Style doesn't work properly The Mobile Style is based on the jQuery Mobile Module. As such it requires that Javascript and Cookies are enabled on the device. If they are using an iOS Device, they will either need to turn off Private Browsing or delete their cache due to issues with the Safari Browser. What devices are supported by the Mobile Browser? The vBulletin Mobile Browser is based on the jQuery Mobile module. It should support all devices that jQuery Mobile supports. You can see a list of devices here: http://jquerymobile.com/demos/1.1.0-rc.1/docs/about/platforms.html Are you going to add more devices? We do not intend to add devices not on the above list at this time. Does the mobile browser support RTL languages like Hebrew or Arabic? No, it does not at this time. Search in Templates Back to Top The Styles & Templates > Search in Templates group lets you search for strings in templates from the style(s). Additionally you can run a "find and replace" search which allows you to replace all instances of a certain string with another string. Back to Top https://www.vbulletin.com/docs/onepage/?manualversion=40205500 106/380 1/11/2018 vBulletin Manual Search Templates When you do not know which template resides in which style, or which template to modify, than use the Styles & Templates > Search in Templates > Search Templates system to find the template in one or more styles. Search in Style Select the style in which you want to search. You can select to search in all the styles or just one. Search for Text Enter the string of text you want to search for. This search string is case sensitive. The search will find any words / phrases containing the string you enter here. For example, if you search for "bullet" the search will find "vbulletin", "bullets", etc. Additionally you could select the [Large Edit Box] if you have a chunk of text which you would like to have an overview on while entering. Search Titles Only Select yes if you want to search only through the template titles and not through the actual content of the templates. Note: Use the Styles & Templates > Search in Templates > Find and Replace in Templates feature if you have a lot of templates in one or more styles that has text that you wish to have replaced. This could save you quite some time. Find and Replace in Templates Back to Top Use the Styles & Templates > Search in Templates > Find and Replace in Templates feature if you have a lot of templates in one or more styles that has text that you wish to have replaced. This could save you quite some time. Warning: Replacing strings in templates could result in errors if you do not know what you are doing. This is an action that can not be undone, so please be aware that you should look twice before applying a find and replace on templates. Adviced is to run a test first. Search in Style Select the style in which you want to search. You can select to search in all the styles or just one. Search for Text Enter the string of text you want to search for. This search string is case sensitive. The search will find any words / phrases containing the string you enter here. For example, if you search for "bullet" the search will find "vbulletin", "bullets", etc. Replace with Text Enter a replacement string here. This string will be substituted in for all instances of the search string above. For example, if you search for "bullet" and your replacement string is "carrot" then "vbulletin" would become "vcarrotin". Test Replacement Only Select no if you are really sure you wish to replace found strings in a template. It is adviced to run a test replacement first. Running a test replacement first will show the result of doing this find/replace, without actually updating the templates. Use Regular Expressions The regular expression option is for advanced users only! Setting this option to 'yes' will use preg_replace() instead of str_replace() for your find/replace operation. Do not use this option if you are not sure how to use PCRE regular expressions! https://www.vbulletin.com/docs/onepage/?manualversion=40205500 107/380 1/11/2018 Replacement Variable Manager vBulletin Manual Back to Top Replacement variables are useful in representing commonly used values in templates. Use the Styles & Templates > Replacement Variable Manager group to add / modify / delete replacement variables. Note: To learn more about Replacement Variables, please read the Replacement Variables Introduction The Replacement Variable Manager lists all of your styles, together with any replacement variables defined within them. This allows you to see at a glance the way in which any replacement variables you have defined are being inherited by child styles. Refer to the Color Key at the top of the Replacement Variable Manager page to see how colors are used to indicate whether a replacement variable is customized in a particular style, or inherited from a parent style. Add New Replacement Variable Back to Top To add a new replacement variable, click the [Add New Replacement Variable] link next to any style listed on the Replacement Variable Manager main page. On the Add New Replacement Variable page, you will find a form in which you can specify the style to which you want to add a new replacement variable, along with two text fields. The first text field is for the text you want the replacement variable to find, and the second field should contain the text with which to replace the find text. Note: The find text is not case sensitive, meaning that dog will match DOG, DoG, dOG etc. When you click the [Save] button, any child styles of the style to which you added the new replacement variable will automatically inherit the new variable, while parent styles will be unaffected. This is the principle of inheritance in action. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 108/380 1/11/2018 vBulletin Manual Customizing a Replacement Variable When a replacement variable is inherited by a style, you may customize it in that style and have the changes automatically appear in any of its child styles. Back to Top To customize a replacement variable, simply click the [Customize] link next to any replacement variable on the main page. This will load the Replacement Variable Customization form, which looks almost identical to the Add New Replacement Variable interface, and works in exactly the same way. After making your changes, the new value will be automatically inherited by any child styles. Download / Upload Styles This section covers how to download and upload styles. Back to Top Downloading styles is handy when you want to make a backup of your templates and options, or share your work with other forum administrators. Uploading styles is handy to revert to a backup or applying the same style to several boards. You can use this option to import a style that someone has given you. Make sure you read and understand all the options to avoid incomplete style downloads / uploads. Note: When you upload or download a style, the process will not transfer any image files. Your image files should be managed with an FTP client. Downloading a Style Back to Top If you have created a style of which you are proud, you may want to share it with other vBulletin administrators. Alternatively, you may simply want to back up all your templates and style settings to a file on your computer. Both of these actions are catered for by the Style Download system, which allows you to download all the customized StyleVars, CSS, Replacement Variables and Templates into a single XML file. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 109/380 1/11/2018 vBulletin Manual The Style Download form is relatively simple, with only a few controls to manipulate. Style Use this menu to pick the style you want to download Title By default, the downloaded XML file will contain the title of the style as it exists on your web server. If you would like the XML file to store a different name for the style you are downloading, enter it here. Filename This field allows you to specify the name of the XML file vBulletin will send to your web browser when you click the [Download] button. However, most browsers allow you to rename a file as you download it, so this field may be irrelevant to you. Options The options give you a choice of two types of style download. If you choose to Get customizations made only in this style, then the style XML file you download will contain only items that are customized specifically in the style you are downloading. Items that are inherited from parent styles will not be included. On the other hand, if you choose to Get customizations made in this style and all parent styles, the style XML file will contain not only items customized specifically in the style you are downloading, but also any items that have been customized in a parent style. Clicking the [Download] button will instruct vBulletin to package your style up into an XML file and start downloading it to your web browser. Note: The XML file you download can not contain any image files. If your style includes custom images, you should download these separately using an FTP client. Uploading a Style Back to Top If you have downloaded a vBulletin 3 XML style file from another vBulletin installation, or if you want to restore a style backup that you made yourself, you will have need of the vBulletin 3 Style Importer. This system will read an XML file, convert the data inside it into StyleVars, CSS, Replacement Variables and Templates and write the data into your database. Either If the XML style file you want to import is located on your own computer, use this control to find the file Upload and upload it. XML File from your computer Or If the XML style file you want to import is located on your web server, enter the file path to the file here. Import XML file from your server Merge Into Style If you are restoring a style backup, you will probably want to import the XML file over the top of the style of which it is a backup. To do this, select the style you want to merge into from the list provided. If no style is chosen from the list, a new style will be created and the data in the XML file will be imported into this style. Ignore Style Version When a style file is downloaded from vBulletin, the version number of the vBulletin exporting the file is included. If the version number included in the style file you are importing does not match the version number of the vBulletin doing the import a warning will be shown to alert you to possible incompatabilities. If you are confident that no errors will occur as a result of importing a style from a different version of vBulletin, use this control to force vBulletin to accept the file regardless of the stored version number. Title for If you chose to create a new style rather than overwrite an existing style, vBulletin will use the style title https://www.vbulletin.com/docs/onepage/?manualversion=40205500 110/380 1/11/2018 vBulletin Manual Uploaded included in the XML file as the title for the new style unless you specify an alternative title using this Style control. Parent These controls are only applicable when creating a new style rather than overwriting an existing style. Style / Their function is identical to that described in the section dealing with adding a new style. Display Order / Allow User Selection Note: XML style files can not contain image files, so no images will be imported when using this system. If the style you are importing requires special images, you will need to upload them to your web server using an FTP client. Find Updated Templates Back to Top vBulletin's default templates are often updated during upgrades. This page shows you what customized templates may need to be reverted and recustomized as a result of the default templates changing. If the page displays no modified templates then all your templates are up to date. You can choose to modify or revert a template if it is listed. Note: The Find Updated Templates system is primarily of use to check for modified templates after running an upgrade script. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 111/380 1/11/2018 vBulletin Manual Languages and Phrases In vBulletin 3, any language-dependent text is kept separately from the HTML layout code. Back to Top This enables you the administrator to create (or download) versions of the user interface translated into multiple languages other than US English, making your board truly multinational and language-independent. An Introduction to Languages and Phrases Back to Top vBulletin 3 has introduced the ability to translate your board or modify the text displayed via the control panel, all without having to delve into the templates and HTML. This section will cover everything you need to know to translate your board, edit existing phrases, and add new phrases Languages vs. Phrases Back to Top A language contains a collection of phrases. Specifically, a language contains all the phrases that vBulletin has, broken down into various groups of phrases. For example, there is a Polls group that only contains phrases dealing with polls. You can specify the default language that guests will see; once a user is registered, he or she may change the language the board is displayed in. Note: Language settings apply to both the front-end and the control panels. A phrase represents a single string containing text that could be translated. This may vary from a single word used on a button to an entire error message or email. Significant effort has been made to make phrases as gender-independent as possible, but there are still some problem areas. If you are trying to translate a phrase and having problems because of a language difference (such as a gender conflict), you may report it to us. Note: Some gender issues may not be addressable because vBulletin does not include a method to determine if a user is male or female. We recommend working around this by including both translations simultaneously. This is similar to saying him or her’ or forum(s)’ in English. The 'Master Language' and 'Custom Master Language' Back to Top Beyond any user-created languages, there are 2 that always exist. These are master languages and are generally hidden from being directly edited. The Master Language is where all of vBulletin’s untranslated, default phrases exist. This allows an original copy of a phrase to exist at all times for reference purposes. You will never be able to edit this language directly. The Custom Master Language is similar to the Master Language. However, the only phrases that will be inserted here are any custom phrases that you have created. This allows every language to have access to the phrase as if it were in the Master Language. Phrase Syntax Back to Top When editing phrases, you will notice strings such as {1} or {2}. These represent variables, and will be replaced with specific examples at runtime. Let’s consider an example. Suppose you are working with phrase showing_avatars_x_to_y_of_z. By default, its text is: Showing Avatars {1} to {2} of {3} At run time, this may take on a value such as: Showing Avatars 10 to 20 of 24 Notice that {1}, {2}, and {3} have been replaced with specific values. Now, suppose you wanted the output to look like this: 24 Avatars Total. Displaying 10 – 20. You could accomplish this by changing the phrase text to: {3} Avatars Total. Displaying {1} – {2}. The order of the numbers does not matter. All that matters is that you reference the correct number for what you want. Using Phrases in Templates Back to Top Phrases are generally straightforward to use in templates. Simple phrases (without any variable portions) can be referenced like regular $variables; complex phrases are referenced similarly to template conditionals. When referencing a phrase in a template, there are two things you have to know. 1. The phrase name (phrase_name) – this is what uniquely identifies a phrase and how phrases are referenced. Generally, the phrase name reflects the phrase text directly; for example, the phrase with variable name poll_timeout has the text of Poll Timeout. 2. The phrase group – if the phrase is in a group, you will only be able to access it on pages that load that group. For example, the Polls group is only loaded in poll.php, so if you try to reference poll_timeout in a template that’s loaded on another page, you won’t get any output. To use a phrase in a template, you need to use the following constructs phrase {vb:phrase phrase_name[, arguments for phrase...]} Inserts the specified phrase. If arguments are provided, they will be run through htmlspecialchars. Example: {vb:phrase welcome} https://www.vbulletin.com/docs/onepage/?manualversion=40205500 112/380 1/11/2018 vBulletin Manual rawphrase {vb:rawphrase phrase_name[, arguments for phrase...]} As above, though arguments bypass htmlspecialchars. Example: {vb:rawphrase message_by_x_on_y_at_z, {vb:link member, {vb:raw postinfo}}, {vb:raw postinfo.username}, {vb:raw postinfo.postdate}, {vb:raw postinfo.posttime}} For more information on the template syntax please see: Template Syntax Managing Languages Back to Top To manage your languages, go to Languages & Phrases > Language Manager in the admin control panel. You will be presented with this: Here you can add or edit existing languages, change the default language, view a language quick reference, or rebuild all languages. Adding or Editing a Language Back to Top To reach this page, visit Languages & Phrases > Language Manager > click [Add New Language] or [Edit Settings]. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 113/380 1/11/2018 vBulletin Manual The form to add or edit a language contains many settings that are specific to a locale. For example, some people might prefer the mm/dd/yy date format, while others prefer dd/mm/yy. General Settings Title – the name of your language. This will be displayed to users when they are selecting a language. Allow User Selection – determines whether users can select the language. If this is set to no, the language is effectively disabled. Text Direction – direction of the text in the language. English is left to right, while Hebrew is right to left. Language Code – the abbreviation for the language. This will not have any effect on the displayed text, but it may be used by programs such as screen readers. HTML Character Set – this indicates the encoding of the characters that are displayed on the page. Setting this to an incorrect value may prevent some characters from being displayed. If you are unsure what to put here, enter UTF-8, as it will likely contain the characters you need. Image Folder Override – this allows you to specify the path to button images, relative to the main forum directory, that contains translated text. This will replace the button images folder, which defaults to images/buttons. If you wish to specify a specific button directory for each style, you may use <#>. At runtime, this will be replaced with the ID number of the style that the user is using. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 114/380 1/11/2018 vBulletin Manual Date / Time Formatting This section allows you to specify specific date and time options. Locale represents a special code that allows dates and times to be automatically translated into a specific language. All the other settings in this group allow you to override the default date and time formatting with one that is more appropriate for your language. For example, English (US) would use the mm/dd/yy format, while English (UK) would use the dd/mm/yy format. These formats are represented by %m/%d/%y and %d/%m/%y, respectively. Number Formatting Decimal Separator – represents the character that separates the integer and decimal parts of a number. Thousands Separator – represents the character that separates and groups thousands in a number. Translating a Language Back to Top To begin translating a language, click Languages & Phrases > Language Manager > click [Edit / Translate

vBulletin Fix

HostGator is committed to making it easy to transfer your site to your new hosting account. We can transfer website files, databases, scripts, and one free domain registration transfer.

What qualifies me for a free transfer?

HostGator provides free transfers for new accounts within 30 days of sign-up, and to newly upgraded accounts. For upgraded accounts it must be an inter-server upgrade to qualify. Please note that downgraded accounts do not qualify for free transfers.

Depending on which type of account you sign up for, we offer differing numbers of free transfers. Please refer to the chart below to see what we include for new packages.

Full cPanel Transfers is the number of cPanel to cPanel transfers that are included.

Max. Manual Transfers is the maximum number of Manual Transfers that are included with your account.

Total Free Transfers is the total number websites that we will move for you.

Account TypeTotal Free TransfersFull cPanel TransfersMax. Manual Transfers
?Shared1121
?Reseller3030230
?VPSUnlimited1Unlimited210 per VPS level
?Dedicated (Basic)Unlimited1Unlimited275
?Dedicated (Standard, Elite, Pro)Unlimited1Unlimited2100

1While we can do unlimited cPanel to cPanel transfers for you, depending on your account, you will have a limited number of Manual Transfers.

2Full cPanel transfers include all domains, Addon Domains, Subdomains, and cPanel settings. This will also include your emails and email accounts. Please note that this does require that your old host's cPanel backup generator to be active.

A few examples: An Aluminium Reseller account includes up to 30 free transfers. Out of this 30, you can have 20 cPanel to cPanel transfers and 10 Manual Transfers, or any combination of the two that totals 30 or less websites. Another example: A Pro Dedicated server includes unlimited cPanel to cPanel transfers, this means you can have 150 sites (or even more) moved. Also since there is an unlimited total number of transfers, you can utilize up to 100 Manual Transfers.

For more information please see ourTransfers Support Article, contact our transfers department at [email protected], or call 866.96.GATOR

Path to Error Handling and Logging options: Settings > Options > Error Handling and Logging


Log Database Errors to a File
To log all database errors to a file, enter the path to the file. The file will be saved as {filename}.log.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Log Failed Admin Control Panel Logins to a File
To log all failed Admin Control Panel login attempts to a file, enter the path to the file. The file will be saved as {filename}.log.
.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Log PHP Errors to a File
To log all PHP fatal errors to a file, enter the path to the file. The file will be saved as {filename}.log.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Log Emails to a File
To log all emails to a file, enter the path to the file here. The file will be saved as {filename}.log.

You should enable email logging only if you suspect problems with the email system within vBulletin.

The directory in which this file is to be created must be writeable (chmod 777) by the web server.

Maximum File Size of Error Logs(default: 1048576)

1048576 bytes = 1 megabyte

If you want your vBulletin error logs to be rotated when they reach a certain size, enter the maximum file size in bytes.

When a log file reaches this size, it will be renamed as {filename}{unix timestamp}.logand a new file will be created.

Set this value to 0 to disable log rotation.


Disable Database Error Email Sending(yes/no)

To prevent vBulletin from sending email to the $config['Database']['technicalemail'] address you specified in config.php, set this value to Yes.

Error reports about database connection errors will still be sent.

We do not recommend that you set this value to Yes unless you are logging database errors to a file.
tags in all browsers. With CSS the 'width' style attribute can be used to control the width more precisely, rendering these three replacement variables obsolete. With the information in this table, your transtion from the vBulletin 2 styles system to the vBulletin 3 system should be as painless as possible. Style Inheritance Back to Top Like so many other systems in vBulletin, the vBulletin Styles system works around the concept of inheritance. In essence, this means that you can create an unlimited number of styles in which your board can be viewed, and customizations made in one style will be inherited by all of its 'child' styles. Inheritance Example Back to Top The concept of inheritance as used by vBulletin 3 styles is best illustrated with an example of a common use for the system. Many site owners will want to customize the look of their vBulletin installation so that it fits in with the style of the rest of the site. This is normally done by editing the colors used by vBulletin, and by editing the header and footer templates, vbulletin error handling & logging. Let us imagine that we want to customize your header and footer templates, but we also want to offer three different color schemes for our visitors to choose between. For argument's sake, we'll call these the 'Red', 'Green' and 'Blue' styles. We could create three new styles, calling one 'Blue', one 'Green' and one 'Red', then customize the header and footer templates in each style. That would be a perfectly valid solution, but has one serious disadvantage, in that should we decide that we want to alter the HTML in the customized header template, we would need to go vbulletin error handling & logging and edit the template in each of our three styles individually. A much more manageable solution would be to create a single new style, which we will call 'Custom Header / Footer' and customize the header and footer templates within this style. Now in order to offer site visitors the three color variants we want, we create the 'Red', 'Green' and 'Blue' styles as child styles of the 'Custom Header / Footer' style. Each of these child styles will inherit the customized header and footer templates from the 'Custom Header / Footer' parent style, so we will not need to edit that template in the child styles, and if we choose to change the HTML of either the header or footer templates at some point in the future, we need only edit those templates in the parent style, and the changes will be automatically inherited by the three child styles. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 97/380 1/11/2018 vBulletin Manual While this is a very simple example, involving only the site color scheme and the header and footer templates, the vBulletin styles system allows you to individually customize every template and every CSS attribute of a style, and each of those customized attributes can be inherited by all child styles. In the next section we will look into the mechanics behind this system in order to gain a good understanding of how to use vBulletin styles most effectively. Inheritance Mechanics Back to Top In the vBulletin styles system, each element of a style can be customized from the vBulletin default value, and each customization will be inherited by any child styles of the style in which the customization was made, unless the value is further customized in the child style. In order to explain this in simple terms, let us assume that a vBulletin style consists of [x] individual elements, those being a background color, a text color, a font style and a few templates. For the purposes of this example, we will represent the contents of a style like this: Background Color Text Color Font Style Header Template Footer Template #FFFFFF #000000 10pt verdana, arial,

This vbulletin error handling & logging the default

This is the default helvetica, vbulletin error handling & logging, sans-serif 'header' template!'footer' template!
Using the example of the customized header and footer templates we used in our first look at style inheritance, we can imagine that we could represent the 'Custom Header / Footer' style like this: vBulletin Default Background Color vbulletin error handling & logging Default Text Color Font Style #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif Header Template Footer Template

This is the default 'header' template!

This is the default 'footer' template!

#FFFFFF #000000 10pt verdana, arial,

This is my custom

This is my custom helvetica, sans-serif 'header' template!'footer' template!
In this example, items that have been customized in a style are shown in red. You can see that the background color, vbulletin error handling & logging, text color and font style values are all shown in black, meaning that they are unchanged from the default values, while both the header and footer templates are shown in red, meaning that they have been customized, and therefore override their default contents. Custom Header / Footer We will now add the final branch of the style tree from our previous example, namely the 'Blue' style. Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is error cannot find libmysqlclient_r under /usr/local/mysql custom 'header' template!

This is my custom 'footer' template!

#0000FF #FFFFFF 10pt verdana, arial,

This is my custom

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Here we can see that both the background and text color values have been customized, vbulletin error handling & logging, and are therefore shown in red, while the font style value has not been changed and therefore is being inherited from the vBulletin default values, vbulletin error handling & logging. However, both the header and footer templates have been customized in the parent 'Custom Header / Footer' style, and so those custom versions are inherited by the 'Blue' style. This inheritance is shown as an orange value. Blue Furthermore, if we now decided to customize the header template in the 'Blue' style, we would have something like this: Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is my custom 'footer' template!

#0000FF #FFFF00 10pt vbulletin error handling & logging, arial,

This is my special BLUE

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Here we can see that the customized (red) header template in the 'Blue' style overrides not only the default vBulletin header template, but also the customized header template from its parent 'Custom Header / Footer' style, while the Footer template is still inherited from its parent. Blue To illustrate the ability of vBulletin's style system to allow a theoretically infinte level of parent/child relationships between styles, we will now add a child style to the 'Blue' style, in which we will set the font size to be extra large. We will call this style 'Big Font Blue'. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 98/380 1/11/2018 vBulletin Manual In this style, we will customize the font size attribute to be larger than normal, which will result in a style inheritance diagram like this: Background Color Text Color Font Style Header Template Footer Template vBulletin Image i/o error internal error 3ds max #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is my custom 'footer' template!

Blue #0000FF #FFFF00 10pt verdana, arial, helvetica, sans-serif

This is my special BLUE

This is my custom 'header' template!'footer' template!
#0000FF #FFFF00 14pt verdana, arial,

This is my special BLUE

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Here you can see that the vBulletin default font style is inherited by the 'Custom Header / Footer' style and the 'Blue' style, but is overridden by the customized version in the 'Big Font Blue' style. Big Font Blue Were we to now customize the font style in the 'Custom Header / Footer' style, the change would automatically be inherited by the 'Blue' style, but would not be inherited by the 'Big Font Blue' style, as it has its own customized version. Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 12pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is my custom 'footer' template!

Blue #0000FF #FFFF00 12pt verdana, arial, helvetica, sans-serif

This is my special BLUE

This is my custom 'header' template!'footer' template!
#0000FF #FFFF00 14pt verdana, arial,

This is my special BLUE

This is my custom helvetica, sans-serif 'header' template!'footer' template!
Additionally, were we now to revert the customized footer template in the 'Custom Header / Footer' style, vbulletin error handling & logging, its child styles would automatically inherit the vBulletin default value. Big Font Blue Background Color Text Color Font Style Header Template Footer Template vBulletin Default #FFFFFF #000000 10pt verdana, arial, helvetica, sans-serif

This is the default 'header' template!

This is the default 'footer' template!

Custom Header / Footer #FFFFFF #000000 12pt verdana, arial, helvetica, sans-serif

This is my custom 'header' template!

This is the default 'footer' template!

Blue #0000FF #FFFF00 12pt verdana, vbulletin error handling & logging, arial, helvetica, sans-serif

This is my special BLUE

This is the default 'header' template!'footer' template!
#0000FF #FFFF00 14pt vbulletin error handling & logging, arial,

This is my special BLUE

This is the default helvetica, sans-serif 'header' template!'footer' template!
The system does not allow you to alter the vBulletin default value for any item, so you can revert any of your customizations at any time to their original contents. Big Font Blue This diagram illustrates the decision system used by vBulletin when loading each element from a style. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 99/380 1/11/2018 vBulletin Manual The Style Manager Back to Top The Style Manager is the central hub for editing and creating vBulletin styles and their constituents. From here you can control every aspect of the way your vBulletin installation appears to your visitors, from simple color and font changes right through to fundamentally altering the layout of the board by editing templates. The image above shows the Style Manager as it would appear immediately after a new vBulletin installation. Looking at the Style Manager from left to right, various controls are visible. The 'Allow User Selection' Checkbox This checkbox controls whether or not the style will be available for non-administrators to use. If the checkbox for a style is cleared, only administrators will be able to use that style. The Style Title Hyperlink The style title is also a hyperlink. Clicking it will open a new window and show the public area of your vBulletin using the style you clicked, even if the public are not able to use that particular style. The Display Order Text Box The small text box containing a number controls the display order of a style. Higher numbers will be displayed later in the listing. This value makes absolutely no difference to the content of the style, and is used soley for convenience of display. The Style Options Menu This popup menu contains links to make alterations to the style such as changing its title, vbulletin error handling & logging, downloading the style as a style.xml file etc. The Expand/Collapse Templates List Button Clicking the [« »] button will open or close the list error 0xc800 1007 templates for the current style. Note: Examples of (modified) vBulletin boards: http://www.vBulletin.com/links.php Examples of vBulletin style and template modifications here: http://www.vBulletin.org/forum/ Creating New Styles To create a new style, click the [Add New Style] link underneath the main body of the Style Manager. Back to Top This will bring up the Add New Style interface. The controls on this form are as follows: Parent This menu controls the vbulletin error handling & logging that this new style will inherit attributes from other styles that you may have Style defined. For a complete discussion of vBulletin 3 style inheritance principles, see Style Inheritance. Title Here you should enter the name you have wsasend error muonline for your new style Allow This Yes/No choice corresponds to the checkbox next to each style on the main Style Manager interface, User and affects whether or not your visitors will be able to use this style to view the board. Selection Display This text box expects you to enter a whole number (0, 15, 99, 1007 etc) to affect the position at which https://www.vbulletin.com/docs/onepage/?manualversion=40205500 100/380 1/11/2018 vBulletin Manual Order this style will appear in any style lists. It corresponds to the display order text box on the main Style Manager interface. When you have filled in the forum, hit the [Save] and you will be returned to the Style Manager, where your new style will be shown. Creating Child Styles Back to Top To create a child style of an existing style, click on the style options menu for the style of which the new style will be a child, and pick Add Child Style from the popup menu. This will take you to the Add New Style interface, with the correct parent style already selected in the form. You may continue to add further child styles to child styles in order to satisfy any inheritance critera you may require. The image above illustrates the style layout as described in the reference guide to Style Inheritance. Editing Style Settings Back to Top If you decide at any time that you need to rename a style, alter its display order or perhaps even change its parent/inheritance arrangement, you will need to select Edit Settings from the style options menu for the style you want to edit. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 101/380 1/11/2018 vBulletin Manual This will load the Edit Style Settings interface, which appears almost identical to the Add New Style form previously described. Using this form you can easily rename the selected style, change its display order or change the ability of users to choose this style. Note: If you choose to change the parent style, you should bear in mind the changes to your styles that this alteration will make. For example, if we were to error-incorrect bios ide the parent of the 'Red' style to 'No Parent', any templates, CSS or StyleVars currently being inherited from the 'Custom Header / Footer' style would no longer be inherited. In practice, this would mean that the customized header and footer templates defined by the 'Custom Header / Footer' style would no longer be used by the 'Red' style. Consider changes such as this before changing the parent of an existing style. Deleting a Style To delete a style, click on the style options menu in the Style Manager and choose Delete Style. Back to Top Note: When you delete a style, any customized templates, CSS, StyleVars or replacement variables belonging to that style will be deleted along with the style, vbulletin error handling & logging. If the style you choose to delete has no child styles, a confirmation dialog will be displayed, informing you of exactly what is to be deleted and asking if you are sure. If you confirm the deletion, the style will be irrevokable deleted, along with any customizations made within it. On the other hand, if the style you choose to delete has one or more child styles, an extra step will be added into the deletion process should you choose to continue with the deletion. Any child styles of the style you delete will not be deleted, but rather they will be attached to the parent style of the style you have deleted. For example, if you have a style arrangement of Custom Header / Footer -- Red -- Green -- Blue ---- Big Font Blue . and you chose to delete the 'Blue' style, then the vbulletin error handling & logging style of 'Blue' will be attached to the parent style of 'Blue', resulting in this: Custom Header / Footer -- Red -- Green -- Big Font Blue Note: When deleting styles that have child styles, be aware that any customizations made in the style to be deleted will no longer appear in the child styles after the style has been deleted. Editing the Templates https://www.vbulletin.com/docs/onepage/?manualversion=40205500 Back to Top 102/380 1/11/2018 vBulletin Manual To edit any of vBulletin’s templates directly, select [Edit Templates] from the style options dropdown or click the [« »] button. Other template related options in the drop down include: Vbulletin error handling & logging New Template – this takes you to the form to add a new template not based on any existing template. Revert all Templates – this will automatically remove all templates that have been customized in this style. The templates in this style will become equivalent to the templates of its parent style. The template list will look similar to this: On the left, you will see a list of templates (white background) and template groups (black background). On the right, you will see 5 buttons. Any essbase error code 1012704 you cannot use will be grayed out. Customize – if a template has yet to be edited in this style, click this button to edit it, vbulletin error handling & logging. Expand/Collapse – this button expands or collapses a specific template group. Edit – if a template has already been edited in this style, click this button to edit it further. This is effectively the same action as Customize. View Original – if the selected template has been edited in this style, clicking this button will show you the original version of the template. Revert – this button allows you to revert a template to the version that is being used in the parent style (or the original if there is no parent style). If the template being reverted is a custom template with no corresponding original/default then it will be deleted. You may also double click the template or template group name on the left and the appropriate action will be executed; templates will be Customized error curl maximum redirects followed Edited and template groups will be Expanded/Collapsed. Templates are color coded as follows: Black – this template is unmodified in this style or any parent styles. The version included with vBulletin will be used. Orange – this vbulletin error handling & logging has been modified in a parent style, but not in this style. The modified template will be used. Red – this template has been modified in this style. The customized version will be used. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 103/380 1/11/2018 vBulletin Manual You may modify this color scheme by editing your control panel styles. Note: The template vbulletin error handling & logging will look significantly different in browsers other than Internet Explorer. However, the functionality is the same. Adding or Editing a Single Template Back to Top Editing a template is simply like editing regular HTML. Each template represents XHTML bits with PHP-style ($varname) variable names. For more information on what you can use in the templates, see the Templates Introduction. Product - the name of the product which introduced this template. By default this will be vBulletin. Style – the name of the style that this template is in or will be inserted into. Title – the title of the template. This is what is used to identify a template, so it must be unique. Generally, only a-z, A-Z, 0-9, and _ are used. If there is more than one template revision stored an additional link of [View History] will be shown. This link will allow you to compare the current template with previous versions. Template – farcry antiterror cheats is the selftest hp error code body of the template. The [Show Default] link will show you the unmodified version of the template. Search in Template – the text box and [Find] allow you to search within the template text. Please note that this is not available in all browsers. This row also contains several additional options: Copy – this automatically copies the context of the Template box to your clipboard, vbulletin error handling & logging. View QuickRef – this displays the language quick reference. Save in Template History - This row allows you to save your template revision for future comparison if needed, vbulletin error handling & logging. You can add a comment to help you remember vbulletin error handling & logging was changed. Comparing Templates Back to Top vBulletin allows you to store multiple historical versions of a template. You can use these to compare template changes across versions and to keep track of your edits. The feature lets you quickly and easily see the differences between two versions of the template. This feature is accessed by clicking the [View History] in the template editor. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 104/380 1/11/2018 vBulletin Manual When you first enter it will give you a list of all the template revisions stored. Each row will give you the following information: Status - This will tell you if the template is the currently active template, a historical revision or the current default. Last Modified - When the template was last modified and who edited it. Version - The version of vBulletin in which the template was modified. View - Simply allows you to view the template by itself. Old/New - Allows you to select the template revisions for comparison. Old is showed on the left side of the resulting screen and New is shown on the right. Each historical revision will also provide a delete checkbox so that you can remove it from the database if you wish. Once you select two templates to compare, click on the Compare Versions button. The result will be similar to the image below and show where differences between the two versions occur using color highlights and using View SideBy-Side mode The default mode is a diff format (or View Inline mode) which will look similar to the image below Mobile Style https://www.vbulletin.com/docs/onepage/?manualversion=40205500 Back to Top 105/380 1/11/2018 vBulletin Manual In vBulletin 4.1.2, a mobile style was introduced. This is a streamlined style that allows easier browsing on smartphones and other small screen devices. The Mobile Style is meant to be complementary to your vBulletin installation and simplify access for your users. Installing the vBulletin Mobile Style Back to Top Mobile Style Install If you're doing a new install, or are upgrading an existing install that didn't have a mobile style, vbulletin error handling & logging, a "Default Mobile Style" will be created in the mobile vbulletin error handling & logging list, and it will be automatically set as both 'Default Style for Old Mobile Browsers' and 'Default Style for Modern Mobile Browsers' (in Admin CP -> Settings -> Options -> Style & Language Settings). Mobile Style Upgrade If you're upgrading an existing install, that had a mobile style, from 4.1.10 (or lower) to 4.1.11 (or higher), a "Default Mobile Style" will be created in the mobile style list, and any style that was set as either Default Style for Old Mobile Browsers or Default Style vbulletin error handling & logging Modern Mobile Browsers (in Admin CP -> Settings -> Options -> Style & Language Settings) will be moved to 1c 8 runtime error mobile style list, effectively becoming a mobile style. Note: that if you were previously using the normal Mobile Style provided by vBulletin, you need to revert all its templates after it is moved to the mobile style list, or they will all show as customized and never be updated automatically during upgrades. Rather than the above, you may also just delete the Mobile Style you had since before the upgrade, and use instead the "Default Mobile Style" added by the upgrade (also setting it as 'Default Style for Old Mobile Browsers' and 'Default Style for Modern Mobile Browsers'), vbulletin error handling & logging, but it is not recommended to do so as it may cause some oddities to your mobile users until they clear their cookies, vbulletin error handling & logging. Any upgrade from 4.1.11 to an higher version will not require any intervention on your part for the mobile style upgrade. Disabling the Mobile Style If you do not wish to use the mobile style, you can disable it following these steps: Back to Top 1. Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Old Mobile Browsers. Set 'None'. 2. Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Modern Error sim only 3/4 metadata areas found Browsers. Set 'None'. 3. Admin CP -> Styles & Templates -> Style Manager. Edit any style in the mobile style list and set "Allow User Selection" to No. Admins will always be able to use the mobile style, as they can always use any existing style and because it is not possible to delete the last mobile style. Enabling the Mobile Style If you do wish to use the mobile style, you can enable it following these steps: Back to Top Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Old Mobile Browsers. Select 'None' from the Dropdown menu. Admin CP -> Settings -> Options -> Style & Language Settings -> Default Style for Modern Mobile Browsers. Set 'Default Mobile Style' from the dropdown menu. Admin CP -> Styles & Templates -> Style Manager. Edit any style in the mobile style list and set "Allow User Selection" to Yes. Note: Note: Not all Old Mobile Browsers will be able to use the Default Mobile Style. For the purposes of these older browsers, you may be vbulletin error handling & logging to find a style available at www.vbulletin.org. Frequently Asked Questions Why does the Mobile Style have its own Style Manager? This is because it is based off a secondary Master Style. Back to Top What are the benefits of basing the Mobile Style off a secondary Master Style? It allows the Mobile Style to work like the Default Style. This helps with installation, upgrades and customizations, vbulletin error handling & logging. Plus you can create multiple mobile styles and save customization between versions and upgrades. My users are dsl error micro_httpd the Mobile Style doesn't work properly The Mobile Style is based on the jQuery Mobile Module. As such it requires that Javascript and Cookies are enabled on the device. If they are using an iOS Device, they will either need to turn off Private Browsing or delete their cache due to issues with the Safari Browser. What devices are supported by the Mobile Browser? The vBulletin Mobile Browser is based on the jQuery Mobile module. It should support all devices that jQuery Mobile supports. You can see a list vbulletin error handling & logging devices here: http://jquerymobile.com/demos/1.1.0-rc.1/docs/about/platforms.html Are you going to add more devices? We do not intend to add devices not on the above list at this time. Does the mobile browser support RTL languages like Hebrew or Arabic? No, it does not at this time. Search in Templates Back to Top The Styles & Templates > Search in Templates group lets you search for strings in templates from the style(s). Additionally you can run a "find scsistatusx02 winerror0 neroerror-1093 replace" search which allows you to replace all instances of a certain string with another string, vbulletin error handling & logging. Back to Top https://www.vbulletin.com/docs/onepage/?manualversion=40205500 106/380 1/11/2018 vBulletin Manual Search Templates When you do not know which template resides in which style, or which template to modify, than use the Styles & Templates > Search in Templates > Search Templates system to find the template in one or more styles. Search in Style Select the style in which you want to search. You can select to search in all the styles or just one. Search for Text Enter the string of text you want to search for. This search string is case sensitive. The search will find any words / phrases containing the string you enter here. For example, if you search for "bullet" the search will find "vbulletin", vbulletin error handling & logging, "bullets", etc. Additionally you could select the [Large Edit Box] if you have a chunk of text which you would like to have an overview on while entering. Search Titles Only Select yes if you want to search only through the template titles and not through the actual content of the templates, vbulletin error handling & logging. Note: Use the Styles & Templates > Search in Templates > Find and Replace in Templates feature if you have a lot of templates in one or more styles that has text that you wish to have replaced. This could save you quite some time. Find and Replace in Templates Back to Top Vbulletin error handling & logging the Styles & Templates > Search in Templates > Find and Replace in Templates feature if you have a lot of templates vbulletin error handling & logging one or more styles that has text that you wish to have replaced. This could save you quite some time. Warning: Replacing strings in templates could result in errors if you do not know what you are doing. This is an action that can not be undone, so please be aware that you should look twice before applying a find and replace on templates. Adviced is to run a test first. Search in Style Select the style in which you want to search. You can select to search in all the styles or just one. Search for Text Enter the string of text you want to search for. This search string is case sensitive. The search will find any words / phrases containing the string you enter here. For example, if you search for "bullet" the search will find "vbulletin", "bullets", etc. Replace with Text Enter a replacement string here. This string will be substituted in for all instances of the search string above. For example, if you search for "bullet" and your replacement string is "carrot" then "vbulletin" would become "vcarrotin". Test Replacement Only Select no if you are really sure you wish to replace found strings in a template. It is adviced to run a test replacement first. Running a dsdt error 4061 replacement first will show the result of doing this find/replace, without actually updating the templates. Use Regular Expressions The regular expression option is for advanced users only! Setting this option to 'yes' will use preg_replace() instead of str_replace() for your find/replace operation. Do not use this option if you are not sure how to use PCRE regular expressions! https://www.vbulletin.com/docs/onepage/?manualversion=40205500 107/380 1/11/2018 Replacement Variable Manager vBulletin Manual Back to Top Replacement variables are useful in representing commonly used values in templates, vbulletin error handling & logging. Use the Styles & Templates > Replacement Variable Manager group to add / modify / delete replacement variables. Note: To learn more about Replacement Variables, please read the Replacement Variables Introduction The Replacement Variable Manager lists all of your styles, together with any replacement variables defined within them. This allows you to see at a glance the way in which any replacement variables you have defined are being inherited by child styles. Refer to the Color Key at the top of the Replacement Variable Manager page to see how colors are used to indicate whether a replacement variable is customized in a particular style, or inherited from a parent style. Add New Replacement Variable Back to Top To add a new replacement variable, click the [Add New Replacement Variable] link next to any style listed on the Replacement Variable Manager main page. On the Add New Replacement Variable page, you will find a form in which you can specify the style to which you want to add a new replacement variable, along with two text fields, vbulletin error handling & logging. The first text field is for the text you want the replacement variable to find, and the second field should contain the text with which to replace the find text. Note: The find text is not case sensitive, bios error code ffff that dog will match DOG, DoG, dOG etc. When you click the [Save] button, any child styles of the style to which you added the new replacement variable will automatically inherit the new variable, while parent styles will be unaffected. This is the principle of inheritance in action. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 108/380 1/11/2018 vBulletin Manual Customizing a Replacement Variable When a replacement variable is inherited by a style, you may customize it in that style and have the changes automatically appear in any of its child styles. Back to Top To customize a replacement variable, simply click the [Customize] link next to any replacement variable on the main page. This will load the Replacement Variable Customization form, which looks almost identical to the Add New Replacement Variable interface, and works in exactly the same way. After making your changes, the new value will be automatically inherited by any child styles. Download / Upload Styles This section covers how to download and upload styles. Back to Top Downloading styles is handy vbulletin error handling & logging you want to make a backup of your templates and options, or share your work with other forum administrators. Uploading styles is handy to revert to a backup or applying the same style to several boards. You can use this option to import a style that someone has given you. Make sure you read and understand all the options to avoid incomplete style downloads / uploads. Note: When you upload or download error 400 aim style, the process will not transfer any image files. Your image files should be managed with an FTP client. Downloading a Style Back to Top If you have created a style of which you are proud, you may want to share it with other vBulletin administrators. Alternatively, you may simply want to back up all your templates and style settings to a file on your computer. Both of these actions are catered for by the Style Download system, which allows you to download all the customized StyleVars, CSS, Replacement Variables and Templates into a single XML file. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 109/380 1/11/2018 vBulletin Manual The Style Download form is relatively simple, with only a few controls to manipulate. Style Use this menu to pick the style you want to download Title By default, the downloaded XML file will contain the title of the style as it exists on your web server. If you would like the XML file to store a different name for the style you are downloading, enter it here. Filename This field allows you to specify the name of the XML file vBulletin will send to your web browser when you click the [Download] button. However, most browsers allow you to rename a file as you download it, so this field may be irrelevant to you. Options The options give you a choice of two types of style download. If you choose to Get customizations made only in this style, then the style XML file you download will contain only items that are customized specifically in the style you are downloading. Items that are inherited from parent styles will not be included. On the other hand, if you choose to Get customizations made in this style and all parent styles, the style XML file will contain not only items customized specifically in the style you are downloading, but also any items that have been customized in a parent style. Clicking the [Download] button will instruct vBulletin to package your style up into an XML file and start downloading it to your web browser. Note: The XML file you download can not contain any image files. If your style includes custom images, you should download these separately using an FTP client. Uploading a Style Back to Top If you have downloaded a vBulletin 3 XML style file from another vBulletin installation, or if you want to restore a style backup that you made yourself, you will have need of the vBulletin 3 Style Importer. This system will read an XML file, convert the data inside it into StyleVars, CSS, Replacement Variables and Templates and write the data into your database. Either If the XML style file you want to import is located on your own computer, use this control to find the file Upload and upload it. XML File from your computer Or If the XML style vbulletin error handling & logging you error_noaccess loadlibrary masm32 to import is located on your web server, enter the file path to the file here. Import XML file from your server Merge Into Style If you are restoring a style backup, you will probably want to import vbulletin error handling & logging XML file over the top of the style of which it is a backup. To do this, select the style you want to merge into from the list provided. If no style is chosen from the list, a new style will be created and the data in the XML file will be imported into this style. Ignore Style Version When a style file is downloaded from vbulletin error handling & logging, the version number of the vBulletin exporting the file is included. If the version number included in the style file you vbulletin error handling & logging importing does not match the version number of the vBulletin doing the import a warning will be shown to alert you to possible incompatabilities. If you are confident that no errors will occur as a result of importing a style from a different version of vBulletin, use this control to force vBulletin to accept the file regardless of the stored version number. Title for If you chose to create a new style rather than overwrite an existing style, vBulletin will use the style title https://www.vbulletin.com/docs/onepage/?manualversion=40205500 110/380 1/11/2018 vBulletin Manual Uploaded included in the XML file as the title for the new style unless you specify an alternative title using this Style control. Parent These controls are only applicable when creating a new style rather than overwriting an existing style. Style / Their function is identical to that described in the section dealing with adding a new style. Display Order / Allow User Selection Note: XML style files can not contain image files, so no images will be imported when using this system. If the style you are importing requires special images, you will need to upload them to vbulletin error handling & logging web server using an FTP client. Find Updated Templates Back to Top vBulletin's default templates are often updated vbulletin error handling & logging upgrades. This page shows you what customized templates may need to be reverted and recustomized as a result of the default templates changing. If the page displays no modified templates then all your templates are up to date. You can choose to modify or revert a template if it is vnode_pager_putpages i/o error 28. Note: The Find Updated Templates system is primarily of use to check for modified templates after running an upgrade script, vbulletin error handling & logging. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 111/380 1/11/2018 vBulletin Manual Languages and Phrases In vBulletin 3, any language-dependent text is kept separately from the HTML layout code. Back to Top This enables you the administrator to create (or download) versions windows 7 install uxstyle error 2203 the user interface translated into multiple languages other than US English, making your board truly multinational and language-independent. An Introduction to Languages and Phrases Back to Top vBulletin 3 has introduced the ability to translate your board or modify the text displayed via the control panel, all without having to delve into the templates and HTML. This section will cover everything you need to know to translate your board, edit existing phrases, and add new phrases Languages vs. Phrases Back to Top A language contains a collection of phrases. Specifically, a language contains all the phrases that vBulletin has, broken down into various groups of phrases. For example, there is a Polls group that only contains phrases dealing with polls. You can specify the default language that guests will see; once a user is registered, he or she may change the language the board is displayed in. Note: Language settings apply to both the front-end and the control panels. A phrase represents a single string containing text that could be translated. This may vary from a single word used on a button to an entire error message or email. Significant effort has been made to make phrases as gender-independent as possible, but there are still some problem areas. If you are trying to translate a phrase and having problems because of a language difference (such as a vbulletin error handling & logging conflict), you may report it to us. Note: Some gender issues may not be addressable because vBulletin does not include a method to determine if a user is male or female. We recommend working excel 2010 ole error 800a03ec this by including both translations simultaneously. This is similar to saying him or her’ or forum(s)’ in English. The 'Master Language' and 'Custom Master Language' Back to Top Beyond any user-created languages, there are 2 that always exist. These are master languages and are generally hidden from being directly edited. The Master Language is where all of vBulletin’s untranslated, default phrases exist. This allows an original copy of a phrase to exist at all times for reference purposes. You will never be able to cd key chernobyl terrorist this language directly. The Custom Master Language is similar to the Master Language. However, the only phrases that will be inserted here are any custom phrases that you have created. This allows every language to have access to the phrase as if it were in the Master Language. Phrase Syntax Back to Top vbulletin error handling & logging When editing phrases, you will notice strings such as {1} or {2}. These represent variables, and will be replaced with specific errors remount ro at runtime. Let’s consider an example. Suppose you are working with phrase showing_avatars_x_to_y_of_z. By default, its text is: Showing Avatars {1} to {2} of {3} At run time, this may take on a value such as: Showing Avatars 10 to 20 of 24 Notice that {1}, {2}, and {3} have been replaced with specific vbulletin error handling & logging. Now, suppose you wanted the output to look like this: 24 Avatars Total. Displaying 10 – 20. You could accomplish this by changing the phrase text to: {3} Avatars Total. Displaying {1} – {2}. The order of the numbers does not matter. All that matters is that you reference the correct number for what you want. Using Phrases in Templates Back to Top Phrases are generally straightforward to use in templates. Simple phrases (without any variable portions) can be referenced like regular $variables; complex phrases are referenced similarly to template conditionals. When referencing a phrase in a template, there are two things you have to know. 1. The phrase name (phrase_name) – this is what uniquely identifies a phrase and how phrases are referenced. Generally, the phrase name reflects the phrase text directly; for example, the phrase with variable name poll_timeout has the text of Poll Timeout. 2. The phrase group – if the phrase is in a group, you will only be able to access it on pages that load that vbulletin error handling & logging. For example, the Polls group is only loaded in poll.php, so if you try to reference poll_timeout in a template that’s loaded on another page, you won’t get any output. To use a phrase in a template, you need to use the following constructs phrase {vb:phrase phrase_name[, arguments for phrase.]} Inserts the specified phrase. If arguments are provided, they will be run through htmlspecialchars. Example: {vb:phrase welcome} https://www.vbulletin.com/docs/onepage/?manualversion=40205500 112/380 1/11/2018 vBulletin Manual rawphrase {vb:rawphrase phrase_name[, arguments for phrase.]} As above, though arguments bypass htmlspecialchars. Example: {vb:rawphrase message_by_x_on_y_at_z, {vb:link member, {vb:raw postinfo}}, {vb:raw postinfo.username}, {vb:raw postinfo.postdate}, {vb:raw postinfo.posttime}} For more information on the template syntax please see: Template Syntax Managing Languages Back to Top To manage your languages, go to Languages & Phrases > Language Manager in the admin control panel. You will be presented with this: Here you can add or edit existing languages, change the default language, view a language quick reference, or rebuild all languages. Adding or Editing a Language Back to Top To reach this page, visit Languages & Phrases > Language Manager > click [Add New Language] or [Edit Settings]. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 113/380 1/11/2018 vBulletin Manual The form to add or edit a language contains many settings that are specific to a locale. For example, some people might prefer the mm/dd/yy date format, while others prefer dd/mm/yy. General Settings Title – the name of your language. This will be displayed to users when they are selecting a language, vbulletin error handling & logging. Allow User Selection – determines whether users can select the language. If this is set to no, the language is effectively disabled. Text Direction – direction of the text in the language. English is left to right, while Hebrew is right to left. Language Code – the abbreviation for the language. This will not have any effect on the displayed text, but it may be used by programs such as screen readers. HTML Character Set – this indicates the encoding of the characters that are displayed on the page, vbulletin error handling & logging. Setting this to an incorrect value may prevent some characters from being displayed. If you are unsure what to put here, enter UTF-8, as it will likely contain the characters you need. Image Folder Override socket write error outlook this allows you to specify the vbulletin error handling & logging to button images, relative to the main forum directory, that contains translated text. This will replace the button images folder, which defaults to images/buttons. If you wish to specify a specific button directory for each style, you may use <#>. At runtime, this will be replaced with the ID number of the style that the user is using. https://www.vbulletin.com/docs/onepage/?manualversion=40205500 114/380 1/11/2018 vBulletin Manual Date / Time Formatting This section allows you to specify specific date and time options. Locale represents a special code that allows dates and times to be automatically translated into a specific language. All the other settings in this group allow you to override the default date and time formatting with one that is more appropriate for your language. For example, English (US) would use the mm/dd/yy format, while English (UK) would use the dd/mm/yy format. These formats are represented by %m/%d/%y and %d/%m/%y, respectively. Number Formatting Decimal Separator – represents the character that separates the integer and decimal parts of a number. Thousands Separator – represents the character that separates and groups thousands in a number. Translating a Language Back to Top To begin translating a language, click Languages & Phrases > Language Manager > click [Edit / Translate

vBulletin 5x Remote Code Execution Vulnerability

Introduction
vBulletin is a global leader in forum and community software. Featuring strong security, robust management, good user experience, and the capability to serve more than 40,000 online communities, it is a very popular platform used by many major forums. Customers include well-known game company EA, vbulletin error handling & logging, game platform Steam, Sony, NASA, etc. It has many large customers in China including forums with tens of thousands of users such as Fengniao, 51 group buying, and OceanTribe.

Vulnerability Introduction
On August 11, 2020, Sangfor FarSight Labs followed a zero-day vBulletin 5.x remote code execution vulnerability identified by security researcher Amir Etemadieh (Zenofex). The zero-day vulnerability bypasses the released patch for CVE-2019-16759, a vBulletin vulnerability disclosed in 2019. The new zero-day does not have a CVE designation assigned yet, but the severity is identified as critical due to its simplicity and its ability to remotely execute commands on vulnerable vBulletin servers. Remote attackers can execute arbitrary code through specially crafted malicious parameters to control the target server or steal sensitive user information. This vulnerability affects all versions of vBulletin 5.x and exploit attacks have started to vbulletin error handling & logging in the wild. vBulletin has recently released a fix for the vulnerability.

Vulnerability Reproduction
We reproduced this vulnerability in vBulletin 5.x by executing echo command, as shown in figures below:

Vulnerability Reproduction

Impacts
By searching from the Vbulletin error handling & logging, we know that there are nearly 30,000 public-facing websites using vBulletin worldwide, and many of them are international community forums maintained by large international companies, so the vulnerability causes huge impact.

Affected versions:vBulletin 5.x

Timeline
Aug 11, 2020 Sangfor security team tracked a zero-day vulnerability, vBulletin 5.x remote code execution vulnerability.

Aug 12, 2020 Sangfor FarSight Labs reproduced this vulnerability successfully and released a vulnerability alert with remediation steps.

Remediation
1. vBulletin announced that patches were available for the 5.6.0, 5.6.1, vbulletin error handling & logging, and 5.6.2 versions of vBulletin Connect. The fixes remove the PHP Module. A full patch will be included in the next build vbulletin error handling & logging 5.6.3 sony serious error the PHP Module will be completely removed in vBulletin 5.6.4. For affected users, please follow its official website to obtain the latest patches: https://www.vbulletin.com/.

2. Sites running older versions vbulletin error handling & logging vBulletin need to be upgraded to vBulletin 5.6.2 as soon as possible according to vBulletin.

Temporary Remediation
vBulletin administrators can modify settings to prevent this vulnerability from being exploited by following these steps:

a) Log in to vBulletin Administrator Control Panel.

b) Click "Settings" on the left menu and click "Options" in the drop-down menu.

c) Select "General Settings" and click "Edit Settings".

d) Look for "Disable PHP, vbulletin error handling & logging, Static HTML, and Ad Module rending" and set to "YES", then Click Save.

Sangfor Solution

1. For Sangfor NGAF customers, update NGAF security protection.

2. Sangfor Cloud WAF has automatically updated its database in the cloud, vbulletin error handling & logging. These users are already protected from this vulnerability without needing to perform any additional operations.

3. Sangfor Cyber Command is capable of detecting attacks which exploit this vulnerability and can alert users in real-time. Users can correlate Cyber Command to Sangfor NGAF to block an attacker's IP address.

4. Sangfor SOC has Sangfor security specialists available 24/7 to help you resolve any security issues. For users with vulnerabilities, the SOC regularly reviews and updates device policies to ensure protection against this vulnerability.

Edit your config.php file and make sure you have a valid email in this line:


Block Disabled:      (Update License Status) 
Suspended or Unlicensed Members Cannot View Code.

Then, go back to your site and produce the database error and let us know what it says in the email you get. We need to know the exact error that is emailed to you in order to help out. (Most likely, on a fresh install, you have some wrong information in the config.php file and vbulletin is unable to connect to your database.)
__________________

Former vBulletin.org Staff Member

Try a search before posting for help. Many users won't, and don't, help if the question has been answered several times before.
W3Schools - Online vBulletin Manual
If I post some CSS and don't say where it goes, put it in the additional.css template.
I will NOT help via PM(you will be directed to post in the forums for help.)

No members have liked this post.

Hi,

To cross populate you need someone who knows a little about databases. There are different ways but simplying exporting the usernames/passwords from the phpbb to a file then importing into Moodle (or vice versa) is a reasonble a way forward.

PhPBB is opensource and well tested. On many webhosts you can install directly from the control panel - it's provided for free, vbulletin error handling & logging. This way I would prefer if you've little experience because occasionally PhPBB needs a security patch which need to be installed. Its easy to do but if your webhost does it for free (or gives you notice that it needs error given 32512 be done) its better. There are many "hacks" - alterations to the code that extend the functionality (see phpbbhacks.com)- I use these but really you shouldn't need them

Vbulletin needs a licence fee of over $100 and a support contract of about $30/year. It offers the same things really but a lot of webmasters I know use it simply because it takes the stress out of updates etc. VBulletin tends to have a little more functionality as a standard.

There are many free themes for both and many services which allow you to get a Corporate theme for your board. 'Skinning' a theme is not too difficult - slightly harder than making a theme for Moodle.

You can transfer data between phPBB and Vbulletin. So a reasonable way forward is to install PhPBB- use it to see if its what you want then make a decision at that point. You will also have a better understanding of how PHPBB works and that maybe enough to give you confidence to use it.

In use these boards have a lot of power.They have been forcably "evolved" through the internet (built by 16 year olds FOR 16 year olds) and are both easy to use and very complete in thier prowess.

e.g: Setting passwords to forums, even topics, mass emails to groups, advanced editing functions, banning (for time periods eg. a few hours to infinite)creating stickies, activity hallows eve tales of terror wav of individuals, IM systems, poll creation, word filters, hiding areas from some groups, pre-authorisation of avatars, users, signatures, uploading of files in predefined formats etc etc.

Virtually every permutation of what you might want. This comes at a price of needing to learn how to use it. Moodle is a pushover in this respect.smile

There are very full forums offering advice on PhPBB and Vbulletin. These boards are the main stay of the Internet. You vbulletin error handling & logging often get a response about an issue in minutes. and of course if you use the search function your problem has almost certainly been covered before.

Most important of all these boards DEFAULT TO A NON-SUBSCRIPTION TO THREAD status.

Let us know how it goes on.

0 Comments

Leave a Comment