Creo que esto puede responder tu pregunta mejor que todo lo que te podamos decir:
Publicado Originalmente por Kier en vBulletin.com
==================================================
vBulletin 3.0.0 Beta 7
In order to fix several bugs found in previous releases, and to prepare the ground for the first Release Candidate, we have decided to release a seventh beta version for vBulletin 3.
Images Folder Reorganization
One of the primary things new in Beta 7 is the reorganization of the images folder.
In previous versions of vBulletin, a single variable controlled the location of the directory containing all images used in vBulletin templates. In vB2, this was {imagesfolder} and in vB3 Betas 1-6, this was $stylevar['imagesfolder'].
This system, while functional, did not lend itself well to boards using multiple similar styles. For example, if the only difference between StyleOne and StyleTwo on BoardX is that they have different colored buttons, you would have to create a complete duplicate of the 'images' folder, one version containing the buttons for StyleOne and the other containing the buttons for StyleTwo. This would mean that you would also need to duplicate all the other images, such as the folder icons, the attachment type icons, the poll counter bars etc.
In order to prevent this necessity, we have reorganized the images folder into logical directories and assigned each image type its own $stylevar. For example, all button images are now held in images/buttons and are referenced with $stylevar['imgdir_button'], while all attachment icons are stored in images/attach and are referenced with $stylevar['imgdir_attach'].
This means that you can now share groups of images between styles, without having to make and duplication or symbolic links on your server.
A complete description of the reorganization is available later in this thread.
New CSS Class for WYSIWYG Text Area
.wysiwyg (WYSIWYG Editor)
This new class is used to control the WYSIWYG text area. As some board owners like to have the WYSIWYG area appear like any other textarea, and others like it to appear like the first alternating color, this class allows you to choose between them - or to define something totally new if you want to do so.
[more details]
PM Popup Changes
Some changes in Beta 7 have necessitated a change in the way that we handle the New Private Message popup. To cut a long story short, pmpopup is now handled by the pm_popup_script template, which is
appended to the footer when a PM popup is to be shown. Therefore, you can remove the confirm_newpm() function from your headinclude, although leaving it in place will not break anything.
[more details]
BBCode Changes
With Beta 7, we have decided to hard-code the [
quote] and [
email] bbcode definitions (including the [
quote=username] and [
email=emailaddress] bbcodes). However, this does not mean that your customized [
quote] bbcode will be lost. If you have customized your [
quote] and [
quote=username] bbcodes, you should go to the bbcode manager and copy the 'Replacement' HTML into a text file for safe keeping
before you upload the new Beta 7 files to your server. After the upgrade is complete, you can edit the new bbcode_quote to appear in the same way as your old bbcode replacements did. Note that the bbcode_quote template uses a conditional to show either the [
quote] or the [
quote=username] HTML.
[more details]
Renamed Templates
A few templates have been renamed for Beta 7 in order to make a more organized template manager. The following templates have been renamed:
- postbit_bbcode_code => bbcode_code
- postbit_bbcode_html => bbcode_html
- postbit_bbcode_php => bbcode_php
- bbcode => help_bbcodes
- bbcodebit => help_bbcodes_bbcode
- SMILIELIST => help_smilies
- smilielistbit => help_smilies_smilie
- smilielist_category => help_smilies_category
- avatarlist => help_avatars
- avatarlist_avatar => help_avatars_avatar
- avatarlist_category => help_avatars_category
- avatarlist_row => help_avatars_row
Version-Based Template Comparison
The "Find Updated Template" option in the admin control panel now does its comparison based on the version of the master template and your custom template. If your custom template was edited in an earlier version, it will appear on this list. This is similar to the existing function of this feature, but it should now work in all cases (there were several cases where the old implementation wouldn't show a template as needing to be updated).
Note this will not show you
what needs to be updated; only that the template has changed.
Right-to-Left Language Support
With Beta 7, we have finally implemented proper support for right-to-left languages. In order to maintain this support, you should bear the following in mind:
In a right-to-left layout, all 'align="left"' attributes need to be reversed to say 'align="right"' and vice versa. This is achieved by
not putting the words 'left' and 'right' into the templates, but rather you should use $stylevar['left'] and $stylevar['right']. These variables will automatically be replaced with 'left' or 'right' depending on the language direction.
Therefore, the following template changes have taken place:
- align="left" => align="$stylevar
"
[*]
text-align: left =>
text-align: $stylevar
[*]
float: left =>
float: $stylevar
[*]
border-left: 2px =>
border-$stylevar: 2px
[*]
padding-left: 2px =>
padding-$stylevar: 2px
[*]
margin-left: 2px =>
margin-$stylevar: 2px
(The following is also true for
align="right" =>
align="$stylevar"
etc.)
[more details]
Content Type Stylevar Becomes Language Setting
In previous versions of vBulletin, one of the stylevars contained the content type for a <meta> tag. This is no longer the case. The content type is now hard-coded as
text/html and the character set (charset) is now defined as part of the language settings. The default charset is
ISO-8859-1.
To make this work on your forums, you should edit your headinclude template if you have customized it, find this text:
Code:<meta http-equiv="Content-Type" content="$stylevar[contenttype]" />
and replace it with this:
Code:<meta http-equiv="Content-Type" content="text/html; charset=$stylevar[charset]" />
[more details]
Popup Smilie Window in WYSIWYG Mode
... now works.
[more details]
Forum Manager under IE with Win95 / Win98 / WinME
We have had reports of the forum manager eating system resources under Internet Explorer on Win9x, so a new admin setting allows you to change the behavior of the forum manager to use an expand/collapse system rather like the style manager, in order to prevent those operating systems from falling over. This setting is disabled by default, but can be enabled via the 'Admin Control Panel Options' section of the main vBulletin Options page.
