We believe one of the coolest additions we’ve made to our WordPress Twitter Bootstrap plugin is one that was released with version 2.0.2.1 of the plugin.

Why is this a big deal?

Because while WordPress is a fantastic platform in many respects, there is as-yet no standardised options interface for WordPress themes and plugins in the backend.

I’m not a huge fan of the boxy WordPress admin interface components. It works in some areas, like on the Dashboard, but for many plugins that use these dull grey boxes, it just doesn’t work.

So, we decided to put our money where our mouth is and use Twitter Bootstrap styling in the admin interface for the plugin itself.

And if we can make it available to ourselves, why not make it available to all?

There was just one little problem with that…

How to use Twitter Bootstrap CSS on the WordPress admin backend

If we were to include the Twitter Bootstrap CSS library in the WordPress backend, we’d quickly screw-up the styles for the whole admin interface.

Clearly this is not an option.

The only way around this is to make the Twitter Bootstrap CSS apply only to targeted areas, or ‘divs‘.

Our solution: we took the latest Twitter Bootstrap CSS library and prefixed all defined styles with our own custom class name, namely:

.bootstrap-wpadmin

So simply put, if you want to apply Twitter Bootstrap styles to your admin interface, you need to wrap it all up in a single <div> with the class detailed above.

For example:

<div class="bootstrap-wpadmin">
 All my original WordPress Admin plugin/theme interface code
</div>

This allows you to be specific about the sections of your admin interface that take on the bootstrap styles while protecting the rest of the WordPress admin interface.

2 important points to note for those with concerns/questions:

1. The backend bootstrap library is the latest bootstrap library available when the plugin version you’re currently using was released.  This library doesn’t automatically update as it is a custom library that we created based off the original. Don’t worry, it is exactly the same as the original, but as outlined already, we just prefixed all the elements with our custom class.
2. If you look at the source code of your WordPress Administration pages, you’ll find a CSS link called “bootstrap-wpadmin-fixes.css“. This is because the CSS styles in the WordPress admin section contain some funky definitions that break the Twitter Bootstrap – we created a few manual fixes for this in a separate file.

And that’s it.

With version 2.0.2.1+ of the WordPress Twitter Bootstrap CSS plugin, you can now (as a plugin or theme developer) include the Bootstrap library in the WordPress backend and take full advantage of it to create a nice options/configuration interface for the users.

We hope you got hold of the update we released last week for the Twitter Bootstrap plugin for WordPress v2.0.2

This week we’re introducing quite a few changes to the plugin, the first of which I’ll address in the post.

Before you look at that however, if you have a few minutes, we think you should consider taking a quick look at our new WordPress backup solution – it’s going to change the world of WordPress website backup and recovery protection. Check it out…

You can learn more about the bootstrap badges here. They’re a simple concept and one that you can use quite easily on your site.

How to use the Twitter Bootstrap Badge shortcode for WordPress

To use the badges, the process is much the same as with buttons and labels. Let’s take the following simple example:

[TBS_BADGE]my 1st twitter bootstrap badge[/TBS_BADGE]

will result in the following badge with default styling and colouring etc:

my 1st twitter bootstrap badge

As with all our Twitter Bootstrap shortcodes for WordPress, provided with this plugin, you can add the following fields for the corresponding HTML parameters:

• id
• class
• style

Twitter Bootstrap Badge Options

Similar to bootstrap labels, you can style the badges with different colours using the classes provided. Here is a breakdown of all the classes, the names of which you must use with the “class” parameter

• class=”success”
• class=”warning”
• class=”error”
• class=”info”
• class=”inverse”

The following is one example where I also add some custom CSS styling (small-caps) into the badge text:

[TBS_BADGE class="info" style="font-variant: small-caps;"]custom styled badge[/TBS_BADGE]

will give you:

custom styled badge

As you can see, with the TBS_BADGE shortcode, it’s easy to add bootstrap badges to your WordPress posts and your theme.

If you have any questions or feedback on this or any other aspect of our Twitter Bootstrap plugin, please don’t hesitate to contact us, or post a comment below.

Thanks!

A couple of weeks back, Twitter Bootstrap was updated to version 2.0.2.

To reflect this update on the Twitter Bootstrap library we’ve recently released an update to our WordPress plugin: WordPress Twitter Bootstrap CSS

To see what’s new with Twitter Bootstrap v2.0.2, you can check out the changelog here.

As for the plugin, the following changes have been made:

• UPDATED: Updated Twitter Bootstrap library to v2.0.2
• ADDED: Ability to include Responsive CSS stylesheet that comes with Twitter Bootstrap version 2.0+
• ADDED: Reorg’d some of the interface to be a little more logical
• FIXED: serious oversight with including individual Javascript libraries.

So as you can see the plugin hasn’t changed a lot, but one important addition is the ability to include the responsive CSS stylesheet that ships with Twitter Bootstrap v2.0+

We hope you’re all finding this plugin useful and it’s helping you make the most of Twitter Bootstrap. Feedback has been great so far, thank you!

If you have any questions or comments, please feel free to post them below or contact us.

A few days ago I outlined how to make full use of the WordPress shortcode provided for making full use of Twitter Bootstrap Buttons.

Today, I’m going to outline how you can use our new shortcode for creating Twitter Bootstrap Button Groups.

Button Groups are easy! Here’s goes…

What are Twitter Bootstrap Button Groups?

Button groups are collections of Buttons that are related in some way and you want to illustrate this relationship visually to the user.

It doesn’t matter why you think they’re related, if they’re related you can display this by using the Button Group feature provided in Twitter Bootstrap.

The WordPress shortcode to use in this case is:

[TBS_BUTTONGROUP]

This shortcode alone has no use. It needs to be used in conjunction with buttons.

So to do this you simply place Twitter buttons within the Button Group shortcode as shown in the following example:

[TBS_BUTTONGROUP] .. [TBS_BUTTON] .. [TBS_BUTTON].. [TBS_BUTTON]..[/TBS_BUTTONGROUP]

Some Twitter Bootstrap Button Group Examples

Let’s try some examples.

First, if you’re not too familiar the buttons, check out our complete guide on using Twitter Bootstrap Buttons here.

With the following code:

[TBS_BUTTONGROUP style="margin:20px"][TBS_BUTTON text="button 1"/][TBS_BUTTON text="button 2"/][TBS_BUTTON text="button 3"/][/TBS_BUTTONGROUP]

you will get the 3 buttons grouped together as seen below:

There are 2 things to note from this example.

1. As with all our components, we offer the option to include in-line CSS styling either through “style”, and also with “class” and “id” definitions. Here I added a margin of 20px to the DIV that will hold the button group so it looks ok on the page.
2. the [TBS_BUTTONGROUP] shortcode must have a corresponding closing tag ([/TBS_BUTTONGROUP]) to indicate the completion of the button group definition.

Twitter Bootstrap Button Groups Toggle Functionality

With Twitter Bootstrap version 2.0, a new toggle functionality has been included with the Buttons components.

For button groups, there are currently 2 types of toggle functions:

1. Checkbox
2. Radio

Specifying these options on the shortcode is easy using the toggle parameter. Currently the ways to specify the type of toggle button group you want are as follows:

1. For Checkbox button group: toggle="buttons-checkbox"
2. For Radio button group: toggle="buttons-radio"

And it’s as easy as that.

As outlined in the TBS_BUTTON how-to article, currently our plugin does not supply the necessary javascript to activate the toggle buttons because we haven’t yet been able to create it. We hope with a bit more time this will be over come soon.

Taking the above example button group, this is how you would create a checkbox toggle group:

[TBS_BUTTONGROUP toggle="buttons-checkbox" style="margin:20px"][TBS_BUTTON text="button 1"/][TBS_BUTTON text="button 2"/][TBS_BUTTON text="button 3"/][/TBS_BUTTONGROUP]

And with the right Javascript to activate it, you’ll have a nice toggle button group.

As you can see, Twitter Bootstrap Buttons Groups are easy with the WordPress Twitter Bootstrap CSS plugin.

Any questions or feedback, please drop them to us in the comments section below.

Thanks!

We’ve talked already about the [TBS_ICON] shortcode that came with the latest release (v2.0.1b).

In this article I’m going to break down all the options available to you with our [TBS_BUTTON] shortcode.

Some of the uses of these buttons are to simply create slightly more elaborate links within your posts.

Twitter Bootstrap Button Basics

Buttons are primarily of 2 types:

1. (Hyper)Links
2. Actions

Their respective HTML elements are:

1. a
2. button

In general, you should use links for objects, such as links to image, videos, or other web pages. Buttons are typically actions.

So let’s say I want to create a link to a web page; let’s call it Google (http://www.google.com)

I can create a link button to Google using the following code:

[TBS_BUTTON element="a" link="http://www.google.com" title="Google Search Engine"]The text in my button[/TBS_BUTTON]

Here is how the button would look: The text in my button

Important TBS_BUTTON shorcode notes:

• You don’t have to use a closing tag. I.e. You don’t need both [TBS_BUTTON] & [/TBS_BUTTON]. Instead you can pass the parameter text as in the following example which will give you exactly the same button as that above. “text” parameter takes priority for button text so don’t specify it if you want to use the alternative method.

[TBS_BUTTON element="a" link="http://www.google.com" title="Google Search Engine" text="The text in my button"]

• If you use multiple buttons on the one page, and you do not use the closing tag, then you should indicate this by using a forward slash / at the end of the shortcode, as follows: [TBS_BUTTON ..my parameters.. /]
• In previous versions of the shortcode, the parameter to add a title to a link was “link_title“. Now it’s just “title“.
• If you don’t include the “element” parameter, it defaults to a hyper-link button and outputs an anchor tag <a>.  But if you also don’t specify a “link“, it defaults to a <button>
• There is a “type” parameter which by default is unused in the case of <a> elements, and defaults to “button” for all other elements. Of course you can set what you want for type at any time
• If you create a “button” and don’t specify the value parameter, value defaults to 0.
• As with all our shortcodes, you have the options to specify component class, id, and style parameters to the buttons. Simply use them exactly as you would when specifying them on normal HTML components – see below for more on available Twitter Bootstrap button classes.

Twitter Bootstrap Button Styles

Twitter Bootstrap comes with a number of default buttons styles which are accessed within the shortcode using the “class” paramenter.

Here are most of the classes you can include in their respective groups (i.e. you cannot use 2 codes from the same group). The class name to use for each style is the text within each button shown below…

Twitter Bootstrap Button Sizes

• btn-large
• default size- when you don't specify one
• btn-small
• btn-mini

Twitter Bootstrap Button Colours

• default: when you don't specify a class
• btn-primary
• btn-info
• btn-success
• btn-warning
• btn-danger
• btn-inverse

It shouldn’t come as too much of a surprise that you can mix these two groups of classes just by specifying more than 1 class, separated by a space.

For example, with the following shortcode specified:

[TBS_BUTTON class="btn-large btn-danger" text="My large danger button"/]

You will get this button:

My large danger button

Twitter Bootstrap Button options: Toggle and Disabled

You have the option to load a disabled button or create a “toggle” button.

Currently our plugin doesn’t supply the JavaScript necessary to activate Twitter toggle buttons, but we hope to in a later release. For now, the code simply adds the necessary toggle data parameter to the button.

Here is an example of a disabled twitter button:

[TBS_BUTTON class="btn-large btn-info" disabled="y" id="my-lovely-button" style="color: yellow; font-family:monospace;" text="My monospace, yellow-text, disabled info Twitter Button"/]

providing the following button

My monospace, yellow-text, disabled info Twitter Button

producing the following HTML code:

<button style="color: yellow; font-family:monospace;" id="my-lovely-button" type="button" class="btn btn-large btn-info disabled" value="0" disabled="disabled">My monospace, yellow-text, disabled info Twitter Button</button>

How to get Twitter Bootstrap for your WordPress site

If you haven’t installed it already, you can do so by going to your “Add New” Plugins page in the admin section of your WordPress site and search for “WordPress Twitter Bootstrap”.

Simply install and activate the plugin and then go to the “Bootstrap CSS” page under the new menu “Host Like Toast” that appears on the WordPress Admin screen.

Select to add Twitter Bootstrap, and then in order to use shortcodes make sure to check to option to enable them. We provide this option as a performance optimization for those who have no wish to use the shortcodes.

In writing this guide I discovered a bug with the button shortcode code and have released an update to address this. The plugin at the time of writing is v2.0.1c.

Please let us know how you get on with the plugin and of course if you have any suggestions or feedback for us.

We released WordPress Twitter Boostrap CSS plugin today, at version 2.0.1b

This release saw a whole heap of internal changes and improvement, most of which I’ll cover in the coming week so you can take full advantage of the features on offer.

In this article I’m going to explain quickly how to start using the Glyphicons to spruce up your posts, pages and your whole WordPress website.

Before you look at that however, if you have a few minutes, we think you should consider taking a quick look at our new WordPress backup solution – it’s going to change the world of WordPress website backup and recovery protection. Check it out…

New Twitter Bootstrap WordPress Shortcode: [TBS_ICON]

First take a look at the Glyphicons available from the Twitter Bootstrap library.

As you’ll see, there are many icons available in the library and each icon has its unique name.

To put any one of these icons in your WordPress posts, you simply need to enter the following text anywhere in your WordPress post/page editor:

[TBS_ICON class="icon-my-lovely-horse"]

You then replace the text “icon-my-lovely-horse” with the name of the icon you want (use the Glyphicons section on the Twitter Bootstrap site as a reference).

Twitter Bootstrap Glyphicons WordPress Shortcode Examples

I had to choose a default icon to show in case you didn’t specify the “class”. I decided upon “icon-star-empty” but please, if you want to use this icon specify it explicitly as I may change or remove the default in future releases for whatever reason.

Example 1: Default

So, the following shortcode :

[TBS_ICON]

will give you:

Example 2: Zoom In and Zoom out Glyphicons

The following shortcodes text:

[TBS_ICON class="icon-zoom-in"] and [TBS_ICON class="icon-zoom-out"]

will give you:

and

Example 3: Custom Glyphicon Styling

With all our shortcodes we offer full support for adding custom CSS styles and element IDs so you can style them directly.

You use the parameters “style” and “id” to achieve this and enter values exactly as you would in HTML.

The following shortcode:

[TBS_ICON class="icon-off" style="border: 1px solid green; background-color: yellow" id="my-icon"]

will yield:

with an HTML element ID of “my-icon” so you can refer to it anywhere in your CSS/Javascript definitions.

Example 4: Combining with other Bootstrap elements, e.g. Twitter Buttons

In this example, I’ll create a Twitter Bootstrap Button and embed a Twitter Glyphicon within it using our shortcodes.

The following shortcodes:

[TBS_BUTTON][TBS_ICON class="icon-trash" style="margin-right: 5px"]This is a rubbish button[/TBS_BUTTON]

will give you:

This is a rubbish button

If you look closely at the code, I included a style of “margin-right: 5px” making the layout inside the button nicer. Without it the image and the text wouldn’t be as neat.

This highlights the power of customization that is available to you with our Twitter Bootstrap WordPress shortcodes. With only a little effort you can spice up your links, add funky icons to your text, and if you’re feeling bold start modifying whole sections of your WordPress theme.

Instant access to the power of Twitter Bootstrap in WordPress

Our WordPress Twitter Bootstrap CSS plugin gives you instant access to the power made available to us all with the Twitter Bootstrap library.

We hope that this new shortcode helps and you find it useful.

As always, we welcome feedback and suggestions about this and anything else that may be on your mind concerning our hosting and Managed WordPress Hosting service.

We reported last week that Twitter Bootstrap version 2.0 was released.

This was a huge update that brought many changes and required extensive work on the WordPress Bootstrap CSS plugin.

We released an updated version of the plugin into beta a week ago and we’re quite happy that in its existing state, it’s good for prime time.

That said though, there are a few things you need to take into consideration before upgrading.

Upgrading from pre-2.0.0 WordPress Twitter Bootstrap plugin

You should know there are 2 versions of the Twitter Bootstrap libraries now available within the admin section of the WordPress plugin:

1. Twitter Legacy
2. Twitter

1. Twitter Legacy

This is the original version (1.4.x) of Twitter Bootstrap. We appreciate that people need time to migrate when there are big changes in a library such as this.

If you want the option to stay up to date with the plugin’s latest features, while giving you time to migrate your site to Twitter Bootstrap version 2.0, you’re covered!

If, when you upgrade to version 2.0 of the WordPress Twitter Bootstrap CSS plugin, you’re configured to us “Twitter” bootstrap, you will automatically be converted to “Twitter Legacy”.

Bugs notwithstanding, there should be absolutely no change in your website appearance and functionality – you can upgrade this plugin with confidence!

2. Twitter

“Twitter” represents the latest public, stable version of Twitter Bootstrap. At the time of writing that’s version 2.0.0.

Certain features and libraries are only available with “Twitter” that are not available with “Twitter Legacy”.

We have been diligent in making the admin interface reflect these differences so there should be minimal confusion.

Hot-Linking option is removed (permanently) from version 2.0.0 onwards

Hot-linking resources on your website comes with its own issues, and maintaining the plugin to support hot-linking was proving more work that the possible benefits.

Apologies to anyone who prefers hot-linking. The migration/upgrade from previous versions will be seamless and shouldn’t present any problems.

WordPress shortcodes support for Twitter Bootstrap elements

Since there were serious changes to the Twitter Bootstrap elements, the plugin shortcodes have changed a lot also.

Where possible we’ve tried to maintain backward compatibility with the “Twitter Legacy” configuration, but this wasn’t always possible.

And, as Twitter Bootstrap continues to evolve, we cannot guarantee long-term support for legacy users. So, please upgrade your site to use the latest version as soon as you can.

The following is a short list of the most important notes to take on the shortcodes system:

• [TBS_BUTTON] supports the classes: default | primary | info | success | danger. But, whichever you choose, this must be the first class defined in the “class” parameter.
• [TBS_LABEL] supports the classes: default | warning | info | success | important. But, whichever you choose, this must be the first class defined in the “class” parameter.
• [TBS_BLOCK] is no longer supported. Twitter Bootstrap 2.0+ does not have “blocks” and instead uses “alerts” with specific classes. If you use [TBS_BLOCK] with “Twitter Legacy” you should still get blocks, but they are actually alerts with a legacy class defined. You should change all your [TBS_BLOCK] instances to [TBS_ALERT] and use the alert-block class.
• [TBS_ALERT] shortcode has a “class” parameter which can remain undefined (for the default setting), or can use: alert-block with alert-success | alert-info | alert-error. To use alert-block with alert-success, for example, just separate them in the parameter with space, e.g.: class="alert-block alert-success"
• [TBS_TWIPSY] is no longer supported. Please use [TBS_TOOLTIP] going forward with the same parameters as twipsy. For now, in version 2.0.0 the old shortcode should still work, but we will not be guaranteeing this as versions progress.
• [TBS_TOOLTIP] is unlike TWIPSY with regards the “placement” parameter. The options are now: top | bottom | left | right
• [TBS_POPOVER] is unchanged and works as with Twitter Legacy 1.4.0

• [TBS_ICON] allows you to add Twitter Bootstrap Glyphicons to your WordPress site.
• [TBS_BUTTONGROUP] allows you to create Twitter Bootstrap Button Groups

At the time of writing, the other shortcodes are currently untested with version 2.0 and are unlikely to work. If you really need them, stick with Twitter Legacy for now.

In the future, I’ll be posting more detailed how-to on the site to use the newest and latest Twitter Bootstrap shortcodes as they become available and updated.

Stay tuned!

Last week DIY Themes released Thesis Framework 1.8.3.

Fun. Not really.

I wrote a guide some time ago about creating Thesis Child Themes. One of the advantages I tout about child themes is the smooth upgrade path from one version of the parent theme to the next.

Unfortunately this latest release of Thesis 1.8.3 caused me a little bit of a headache because he changed the way he includes the theme’s CSS stylesheets.

In this quick post I’m going to show you what you can do to quickly offset any problems associated with Thesis Child Themes and stylesheets.

What changed in Thesis 1.8.3 with regards CSS stylesheets?

Honestly, I don’t know the exact answer to that because I haven’t delved into the code too deeply.

But, we know he changed things because he tells us he did, and also because I’ve reviewed a little bit of the code enough to see some significant changes for myself.

The best thing I can do is describe the problem as I see it, and how I went about fixing it.

Before we even download Thesis 1.8.3, let’s start with the child theme you have already created and are presumably running on your site.

If you’ll remember from the how to article on Thesis child themes, we created the critical styles.css in the root of the child theme folder.

This styles.css should have a single import line and will look something like this:

@import url("../thesis/style.css");

Pretty innocent huh? Well it is this line that fried my site.

You see it uses a relative path to find the parent Thesis theme – the “../” means “go up 1 directory level”.

However, with Thesis 1.8.3, with the way it is being included into the site, this relative path is failing and it’s not finding the parent thesis theme folder.

Not good.

The simple solution here is to create a full path to the CSS stylesheet file. The following line now replaces the line above:

@import url("//www.hostliketoast.com/wp/wp-content/themes/thesis/style.css");

As you can see, not too complicated. You just have to replace it with your URL and if you have WordPress files in a sub-folder, as I do with (‘wp/‘), then you need to include that also.

This wont break your Thesis 1.8.2 and prepares you nicely for Thesis 1.8.3.

Remember, when performing upgrades of your site, you should always create a backup of your website files in case you toast them.

Upgrading to Thesis Framework 1.8.3 for your WordPress child theme

Assuming you’ve created the backup of your theme files and WordPress database, download the new Thesis 1.8.3 and copy them into your parent thesis theme folder, overwriting all files when prompted.

Navigate to the thesis admin section of your WordPress site and run the database upgrade when you’re prompted.

All being well, your website should be seamlessly upgraded to run Thesis Framework 1.8.3.

If you hit a glitch, and your WordPress site isn’t showing the styles as you would expect, the only suggestion I have is to “rebuild” your CSS files.

Thesis 1.8.3 has a new “Design Mode” – I don’t care much for it because I use other means of optimizing my websites.

But it’s there and we have to work with it…

• Go to Thesis ‘Site Options’
• Expand the ‘Stylesheet Options’ section
• Uncheck the box ‘Use Design Mode’
• Save.
• Re-Check the box ‘Use Design Mode’
• Save

Now try reloading the site.

Other issues with Thesis Framework 1.8.3

I’m not the only person that has experienced problems with the latest Thesis upgrade, but I was able to work my way through it eventually. It was nothing too serious in the end.

If you do have more serious issues, you’re best to go back to 1.8.2 and sit tight. Or go to the Thesis Forums and ask for help from the great number of superb folks out there.

Or, you can write to me in the comments sections below, or contact us directly and I’ll see what I can do to assist you.

Remember to completely clear any website caches, and your browser cache if the site doesn’t look as you expected.

If you host your website using CPanel, we have provided a free, fully customizable script for backing up your full web hosting site.

We have received a couple of questions about security recently so we decided to simply highlight clearly that you can configure the CPanel backup script to transfer your backup files over SCP.

SCP is not SFTP, though it is often confused. The backup script uses native CPanel API calls and is therefore only as powerful or as limited as the base-CPanel implementation.

How to enable Secure SCP transfer of CPanel backup files

To see the demonstration on how to backup your web hosting using our CPanel script, please see our original article and video on automating CPanel backups.

If you want to see where to enable SCP, look at the 1:20 mark on the video. The item you need to edit is

ftp_method

where it reads

passiveftp

change this to

scp

Next, change the item:

ftp_port

from 21, to

22

Now it should be noted at this stage that 22 is the default port normally used for SCP. You must check with your server which port SCP services are configured to use – and of course that your server even supports SCP!

If in doubt, check with the service provider.

Now all that is left is to download the CPanel backup script

If you’re not already a member of the Host Like Toast Developer Channel, you can do so for free today using the form below.

If you’re a reseller hosting provider and you need a script to backup all your clients hosting, you can purchase our premium reseller backup script here.

If you have any questions or comments, please feel free to drop them in the area below!

We wrote yesterday that Twitter Bootstrap 2.0 was released to public.

We’ve been hard at work preparing our WordPress Twitter Bootstrap CSS plugin so that you can take advantage of the latest Twitter Bootstrap as soon as possible.

Today we’ve released the first beta of the plugin for those that want it now.

95% of the implementation and testing has been done, but there are a couple of outstanding issues that still need to be addressed.

Outstanding issues for WordPress Twitter Bootstrap v2.0 beta

As with any new major release, there will be a couple of issues.

We have finalised the code necessary for you to include all the new v2.0 Twitter Bootstrap features. However, some functionality available in v1.4.0 of the Twitter Bootstrap library may not function correctly in v2.0.0.

It is for this reason we have released it as v2.0.0-beta1 and the following are some points you should note before upgrading:

• There are 2 versions of Twitter on the plugin now: “Twitter” and “Twitter Legacy”
• With “Twitter Legacy” selected, you run on Twitter Bootstrap version 1.4.0
• With “Twitter” selected, you run on Twitter Bootstrap version 2.0.0
• WordPress Twitter Bootstrap CSS plugin versions number: are now aligned with the latest stable release of Twitter Bootstrap, starting with version 2.0.0
• If you’re upgrading from pre-2.0 version of the plugin, and you were using “Twitter”, you will automatically be switched to “Twitter Legacy” so as to retain your existing configuration.
• Twitter Bootstrap shortcodes that were released with version 0.8+ of the plugin may not work with “Twitter” version 2.0.0 on the plugin
• It should be noted that because of a change of wording on Twitter Bootstrap, “twipsy” has been replaced by “tooltip” throughout
• Shortcode [TBS_TWIPSY] only works with “Twitter Legacy” and has been replaced with “[TBS_TOOLTIP]” when using “Twitter”
• Support for hotlinking CSS and Javascript files from Github (the Twitter Bootstrap repository) has been removed with this version.

Get the WordPress Twitter Bootstrap CSS plugin today!

The plugin is of course free, and you can grab it from the WordPress.org repository here.

Your best bet is to add it from within your WordPress website by searching for “WordPress Twitter Bootstrap CSS”. Of course, if you already have it installed your website will notify you of the latest update in the next 24hrs.

Please feel free to offer feedback on our contact page, or better yet comment below so everyone can follow along.

Hope you love it!