Under most circumstances, installing WordPress is a very simple process and takes less than five minutes to complete. Many web hosts offer tools to automatically install WordPress for you. If you prefer a manual installation you can take a look at the Installation Guide.
Any host that supports the requirements for WordPress can be used for hosting your website. If you’re not sure if your host can run WordPress the best thing to do would be to contact them and ask if they meet the requirements for running WordPress. You can find a list with some good hosts here.
If you want to perform a manual installation using cPanel you can follow the guide on using cPanel.
The wp-config.php file is one of the most important files of your website. It’s located in the root of your WordPress installation and contains most of the website’s configuration details. Editing this file can be done in any plain-text editor. Usually this isn’t necessary unless you’re installing WordPress manually.
The current requirements for running WordPress can be found on the requirements page at WordPress.org.
If you want to change the language that WordPress is using, you can select your preferred language in the Administration Screen. To do this you can go the Settings > General, and choose your preferred language from Site Language dropdown menu.
Yes. WordPress requires access to a MySQL or MariaDB database to store information. So you’ll need a database.
You should create a new database if:
- You have not already created one on the server
- Your generous host offers you more than one database, and you wish to have a separate database for the website you are setting up.
It is not essential to create a new database for each WordPress installation.
- If you are using the same database for multiple WordPress installations, take care to edit the wp-config.php file ensuring that each installation has a unique database prefix.
- If you are setting up a new database for a new website, edit wp-config.php, and be sure to get the database name, and other details correct.
If the following (or similar) message appears after uploading your website a couple of things can be happening:
You are not authorized to view this page. You might not have permission to view this directory or page using the credentials you supplied. If you believe you should be able to view this directory or page, please try to contact the Web site by using any e-mail address or phone number that may be listed on the personal.fredsmith.com home page. You can click Search to look for information on the Internet. HTTP Error 403 – Forbidden
If your account is hosted on a Apache based server the following things can be happening:
- server permissions aren’t allowing the request from being executed
- your index.php isn’t configured to be an allowed directory index
- the underlying filesystem isn’t allowing Apache access to the files requested
If you have checked all these settings and everything seems to be set up correctly you’d best contact your hosting provider for support.
If you have not already installed WordPress, you can rename the folder with the WordPress files, before, or even after uploading the files.
- WordPress Address (URL):
- Site Address (URL):
Once you have done this, you can rename the directory or folder with the WordPress files in it.
When you specified the upload path, you used backslashes.
Use forward slashes “/” to specify the path to the directory.
Yes you can! As long as you have PHP installed you shouldn’t have any trouble getting started with WordPress. Both Apache and Microsoft IIS are capable of serving your WordPress website.
This also answers the questions:
- How can I have my blog in one folder but my index at root?
- How can I have people see my blog at www.example.com but keep all the files in
- How do I install WordPress in a different directory than where the index.php resides?
- Giving WordPress Its Own Directory
- Moving WordPress
Whether you are testing a new version of WordPress, setting up a new blog or have some other reason to limit access, the following information may help you keep unwanted visitors out.
There is no guaranteed way to do this. You can use the .htaccess file (which also contains your permalink code) to check for certain IP addresses and prevent them from viewing your site. This will only stop the IP address, not the person, so if they have access to an allowed IP address, they can get to your page. One tutorial for this is located at Clockwatchers.com
An .htaccess file can also be used to prevent others from “hot-linking” to your images (bandwidth theft) or to set up a password protected blog.
Apache Basic Authentication
To require a password to access your site using .htaccess and .htpasswd.
Tools that help you create the files necessary to password protect your site: Htpasswd generator, htaccess Tools and Clockwatchers.com .htaccess And .htpasswd Tools
Note: When your site is accessed the password is encoded weakly using Base64 and can be easily intercepted and decoded.
Search Engines: Spiders and Bots
Search Engines will index your site and cache your content. If you do not want this to happen, you can go to the Settings > Reading from Administration Screen, and Click Check the ‘Discourage search engines from indexing this site’ box to ask search engines not to index this site.
Note: It is up to search engines to honor your request.
You may use a file called robots.txt. More details can be found at Affilorama.com and elsewhere on the web.
In some setups, it’s necessary to use something other than the HTTP_HOST header to generate URLs. Reverse proxies take the original request and send it to one of a group of servers. To do so, it overwrites the HTTP_HOST with the internal server’s domain. When that domain is not publicly accessible, at best your images might not load correctly, at worst, you’ll be stuck in a redirect loop. To fix this, figure out which header has the right domain name and add a line to your wp-config.php file that overwrites HTTP_HOST with the correct hostname.
If you need to use SERVER_NAME, add this line to wp-config.php:
If you need to use HTTP_X_FORWARDED_HOST, add this line to wp-config.php:
No. Other databases are not supported at the moment.
There are several other excellent database storage engines, such as PostgreSQL and SQLite that WordPress is interested in supporting in the future. Supporting multiple databases is trickier than it sounds and is not under active development, although there are plenty of architectural discussions about the best approach to take. Approaches for increasing the number of supported databases are discussed at Using Alternative Databases.
MySQL and MariaDB are extremely fast. It is also the most widely available database server in the world. Open-source and free, MySQL and MariaDB are supported by thousands of low-cost Linux (and Windows!) hosts, which means a very low barrier to entry for anyone wanting to start a WordPress (or database-driven) website. MySQL’s documentation is useful, cogent and thorough. (Note: it may be intimidating if you are new to all this.) Add to all that the fact that users are able to directly manipulate MySQL and MariaDB with phpMyAdmin, developed expressly for that purpose, and it is obvious that MySQL and MariaDB are the best choice.
ministration of MySQL/MariaDB over the Web.
No. The only time you would modify your WordPress blog with PHP would be when integrating some of the plugins. In most cases clear instructions are given within a text file that accompanies the plugin. Other than that, you will not be changing any of the PHP files.
Most definitely! There are no known issues with any version of WordPress when PHP is running in Safe Mode.
Yes. You certainly need PHP to power your WordPress blog. PHP is the scripting language that drives all of WordPress, and without PHP, your server will not be able to interpret the pages that create your weblog. For supported PHP version, refer Requirements for WordPress.
How can I import posts from my current weblog which uses a different blogging tool such as b2, Movable Type MT, Blogger, etc.?
- Importing Content