Step 1: Replace WordPress files

1. Get the latest WordPress zip (or tar.gz) file.
2. Unpack the zip file that you downloaded.
3. Deactivate plugins.
4. Delete the old wp-includes and wp-admin directories on your web host (through your FTP or shell access).
5. Using FTP or your shell access, upload the new wp-includes and wp-admin directories to your web host, in place of the previously deleted directories.
6. Upload the individual files from the new wp-content folder to your existing wp-content folder, overwriting existing files. Do NOT delete your existing wp-content folder. Do NOT delete any files or folders in your existing wp-content directory (except for the one being overwritten by new files).
7. Upload all new loose files from the root directory of the new version to your existing wordpress root directory.

NOTE – you should replace all the old WordPress files with the new ones in the wp-includes and wp-admin directories and sub-directories, and in the root directory (such as index.php, wp-login.php and so on). Don’t worry – your wp-config.php will be safe.

Be careful when you come to copying the wp-content directory. You should make sure that you only copy the files from inside this directory, rather than replacing your entire wp-content directory. This is where your themes and plugins live, so you will want to keep them. If you have customized the default or classic themes without renaming them, make sure not to overwrite those files, otherwise you will lose your changes. (Though you might want to compare them for new features or fixes..)

Lastly you should take a look at the wp-config-sample.php file, to see if any new settings have been introduced that you might want to add to your own wp-config.php.

Step 2: Update your installation

Visit your main WordPress admin page at /wp-admin. You may be asked to login again. If a database upgrade is necessary at this point, WordPress will detect it and give you a link to a URL like http://example.com/wordpress/wp-admin/upgrade.php. Follow that link and follow the instructions. This will update your database to be compatible with the latest code. You should do this as soon as possible after step 1.

Don’t forget to reactivate plugins!

Step 3: Do something nice for yourself

If you have caching enabled, clear the cache at this point so the changes will go live immediately. Otherwise, visitors to your site (including you) will continue to see the old version (until the cache updates).

Your WordPress installation is successfully updated. That’s as simple as we can make it without Updating WordPress Using Subversion.

Consider rewarding yourself with a blog post about the update, reading that book or article you’ve been putting off, or simply sitting back for a few moments and letting the world pass you by.

Final Steps

Your update is now complete, so you can go in and enable your Plugins again.
If you have issues with logging in, try clearing cookies in your browser.

Troubleshooting

If anything has gone wrong, then the first thing to do is go through all the steps in our extended upgrade instructions. That page also has information about some of the most common problems we see.

If you run into a request for FTP credentials with trying to update WP on a IIS server automatically, it may well be a matter of rights. Go into the IIS Management Console, and there to the application pool of your blog. In its advanced settings, change the Process Model Id into LocalSystem. Then on Sites, choose your blog, right click, click on Edit permissions and on security tab add authenticated users. That should do it.

If you experience problems after the upgrade, you can always restore your backup and replace the files with ones from your previous version from the release archive.

When Your Domain Name and URLs Do Not Change

Moving your domain without changing the Home and Site URLs of your WordPress site is very simple, and in most cases can be done by moving the files.

• If database and URL remains the same, you can move by just copying your files and database.
• If database name or user changes, edit wp-config.php to have the correct values.
• If you want to test before you switch, you must temporarily change “siteurl” and “home” in the database table “wp_options” (through phpMyAdmin or similar).
  If you had any kind of rewrites (permalinks) setup you must disable .htaccess and reconfigure permalinks when it goes live.

If you are changing to a new server but same domain, all you need to do is edit wp-config.php with your new database/user information and upload everything as it is to your new server.

When Your Domain Name or URLs Change

When your domain name or URLs change – i.e. from http://example.com/blog to http://example.com, or http://example.com to http://example.net – there are additional concerns. The files and database can be moved, however references to the old domain name or location will remain in the database, and that can cause issues with links or theme display.

If you do a search and replace on your entire database to change the URLs, you can cause issues with data serialization, due to the fact that some themes and widgets store values with the length of your URL marked. When this changes, things break. To avoid that serialization issue, you have two options:

1. Only perform a search and replace on the wp_posts table.
2. Use the Search and Replace for WordPress Databases Script to safely change all instances. ( If you are a developer, use this option. It is a one step process as opposed to the 15-step procedure below )

As of Version 3.5, Multisite users may use all of the functionality listed below. If you are running a version of WordPress older than 3.5, please update before installing a Multisite WordPress install on a subdirectory.

Moving a Root install to its own directory

The process to move WordPress into its own directory is as follows:

1. Create the new location for the core WordPress files to be stored (we will use /wordpress in our examples). (On linux, use mkdir wordpress from your www directory. You’ll probably want to use “chown apache:apache” on the wordpress directory you created.)
2. Go to the General panel.
3. In the box for WordPress address (URL): change the address to the new location of your main WordPress core files. Example: http://example.com/wordpress
4. In the box for Site address (URL): change the address to the root directory’s URL. Example: http://example.com
5. Click Save Changes. (Do not worry about the error message and do not try to see your blog at this point! You will probably get a message about file not found.)
6. Move your WordPress core files to the new location (WordPress address).
7. Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress directory into the root directory of your site (Blog address). The .htaccess file is invisible, so you may have to set your FTP client to show hidden files. If you are not using pretty permalinks, then you may not have a .htaccess file.

• If you are running WordPress on a Windows (IIS) server and are using pretty permalinks, you’ll have a web.config rather than a .htaccess file in your WordPress directory. For the index.php file the instructions remain the same, copy (don’t move) the index.php file to your root directory. The web.config file, must be treated differently then the .htaccess file so you must MOVE (DON’T COPY) the web.config file to your root directory.

1. Open your root directory’s index.php file in a text editor
2. Change the following and save the file. Change the line that says:
   require(‘./wp-blog-header.php’);
   to the following, using your directory name for the WordPress core files:
   require(‘./wordpress/wp-blog-header.php’);
3. Login to the new location. It might now be http://example.com/wordpress/wp-admin/
4. If you have set up Permalinks, go to the Permalinks panel and update your Permalink structure. WordPress will automatically update your .htaccess file if it has the appropriate file permissions. If WordPress can’t write to your .htaccess file, it will display the new rewrite rules to you, which you should manually copy into your .htaccess file (in the same directory as the main index.php file.)

Using a pre-existing subdirectory install

If you already have WordPress installed in its own folder (e.g., http://example.com/wordpress), then the steps are as follows:

1. Go to the General panel.
2. In the box for Site address (URL): change the address to the root directory’s URL. Example: http://example.com
3. Click Save Changes. (Do not worry about the error message and do not try to see your blog at this point! You will probably get a message about file not found.)
4. Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress (wordpress in our example) directory into the root directory of your site—the latter is probably named something like www or public_html. The .htaccess file is invisible, so you may have to set your FTP client to show hidden files. If you are not using pretty permalinks, then you may not have a .htaccess file. If you are running WordPress on a Windows (IIS) server and are using pretty permalinks, you’ll have a web.config rather than a .htaccess file in your WordPress directory.
5. Edit your root directory’s index.php.
   1. Open your root directory’s index.php file in a text editor
   2. Change the line that says:
      require(‘./wp-blog-header.php’);
      to the following, using your directory name for the WordPress core files:
      require(‘./wordpress/wp-blog-header.php’);
   3. Save the file.
6. Login to your site (if you aren’t still already). The URL should still be http://example.com/wordpress/wp-admin/
7. If you have set up Permalinks, go to the Permalinks panel and update your Permalink structure. WordPress will automatically update your .htaccess file if it has the appropriate file permissions. If WordPress can’t write to your .htaccess file, it will display the new rewrite rules to you, which you should manually copy into your .htaccess file (in the same directory as the main index.php file.)

Since the site is not working for some of these steps, it is best to make this change at a time of low activity, e.g., the middle of the night.

If you already have content in your site, see when your domain name or URLs change for how to deal with references to the old URL that will remain in the database.

• .btn-default
• .btn-primary
• .btn-success
• .btn-info
• .btn-warning
• .btn-danger
• .btn-link

Large button

Default button

Small button

Extra small button

Default Primary Success Info Warning Danger Link

Large button Large button

Default button Default button

Small button Small button

Extra small button Extra small button

1. Copy the entire font-awesome directory into your project.
2. In the <head> of your html, reference the location to your font-awesome.min.css.

   <link rel="stylesheet" href="path/to/font-awesome/css/font-awesome.min.css">

    

Includes 200 glyphs in font format from the Font Awesome set. Glyphicons Halflings are normally not available for free, but their creator has made them available for Bootstrap free of cost.

hey-kids.3/
assets/
├── about/
│    ├── index-2.php
│    └── index.php
├── announcement/
│    └── index.php
├── assets/
│    ├── css/
│    ├── font-awesome/
│    ├── fonts/
│    ├── html-components/
│    ├── html-components-js/
│    ├── html-dark-bg/
│    ├── html-light-bg/
│    ├── html-page-elements/
│    ├── html-parallax-bg/
│    └── images/
│        ├── background/
│        ├── fractionslider/
│        ├── logo/
│        ├── shop/
│        └── slideshow/
│    ├── js/
│    └── index.php
├── contact/
│    ├── index-2.php
│    └── index.php
├── cover/
│    ├── index-2.php
│    └── index.php
├── discography/
│    ├── discography-detail.php
│    └── index.php
├── doc/
│    ├── images/
│    └── index.php
├── error/
│    ├── index-2.php
│    └── index.php
├── event/
│    └── index.php
├── gallery/
│    ├── detail.php
│    ├── index-2.php
│    └── index.php
├── home/
│    └── index.php
├── landing/
│    ├── index-3.php
│    ├── index-2.php
│    └── index.php
├── login/
│    ├── index-2.php
│    └── index.php
├── news/
│    ├── index-3.php
│    ├── index-2.php
│    ├── index.php
│    ├── news-detail-2.php
│    └── news-detail.php
├── register/
│    ├── index-2.php
│    └── index.php
├── search/
│    └── index.php
└── shop/
├── detail.php
└── index.php


This is a paragraph. It should not have any alignment of any kind. It should just flow like you would normally expect. Nothing fancy. Just straight up text, free flowing, with love. Completely neutral and not picking a side or sitting on the fence. It just is. It just freaking is. It likes where it is. It does not feel compelled to pick a side. Leave him be. It will just be better that way. Trust me.

Left Align

This is a paragraph. It is left aligned. Because of this, it is a bit more liberal in it’s views. It’s favorite color is green. Left align tends to be more eco-friendly, but it provides no concrete evidence that it really is. Even though it likes share the wealth evenly, it leaves the equal distribution up to justified alignment.

Center Align

This is a paragraph. It is center aligned. Center is, but nature, a fence sitter. A flip flopper. It has a difficult time making up its mind. It wants to pick a side. Really, it does. It has the best intentions, but it tends to complicate matters more than help. The best you can do is try to win it over and hope for the best. I hear center align does take bribes.

Right Align

This is a paragraph. It is right aligned. It is a bit more conservative in it’s views. It’s prefers to not be told what to do or how to do it. Right align totally owns a slew of guns and loves to head to the range for some practice. Which is cool and all. I mean, it’s a pretty good shot from at least four or five football fields away. Dead on. So boss.

Justify Align

This is a paragraph. It is justify aligned. It gets really mad when people associate it with Justin Timberlake. Typically, justified is pretty straight laced. It likes everything to be in it’s place and not all cattywampus like the rest of the aligns. I am not saying that makes it better than the rest of the aligns, but it does tend to put off more of an elitist attitude.