This link has been bookmarked by 430 people . It was first bookmarked on 02 Jul 2010, by someone privately.
-
31 Dec 17
-
24 Jun 16
K Miura"when your domain name or URLs change"
-
13 Jun 16
-
WordPress allows you to install it into a subdirectory, but have your website served from the website root.
-
-
01 Apr 16
-
Many people want WordPress to power their website's root (e.g. http://example.com) but they don't want all of the WordPress files cluttering up their root directory. WordPress allows you to install it into a subdirectory, but have your website served from the website root.
-
As of Version 3.5, Multisite users may use all of the functionality listed below
-
Note to theme/plugin developers: this will not separate your code from WordPress. Themes and plugins will still reside under wp-content folder.
-
-
17 Feb 16
João SilvaMany people want WordPress to power their website's root (e.g. http://example.com) but they don't want all of the WordPress files cluttering up their root directory. WordPress allows you to install it into a subdirectory, but have your website serve…
-
18 Dec 15
-
01 Aug 15
-
daniela perezmover wordpress en subdirectorios en el dominio
-
12 Mar 15
-
02 Mar 15
-
16 Feb 15
-
29 Jan 15
-
13 Jan 15
-
08 Jan 15
-
Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress directory into the root directory
-
Using a pre-existing subdirectory install
-
If you already have WordPress installed in its own folder (e.g., http://example.com/wordpress),
-
Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress (wordpress in our example) directory into the root
-
-
05 Jan 15
-
29 Nov 14
-
03 Nov 14
sylvester roepstorffFølg denne beskrivelse for at flytte hjemmesiden til sin rod.
-
23 Oct 14
-
14 Oct 14
-
12 Sep 14
-
11 Sep 14
-
08 Sep 14
-
03 Sep 14
-
20 Aug 14
-
10 Aug 14
-
29 Jun 14
-
25 Jun 14
-
23 Jun 14
-
13 Jun 14
-
29 May 14
-
28 Apr 14
-
29 Mar 14
-
10 Mar 14
-
25 Feb 14
-
22 Jan 14
-
16 Jan 14
-
17 Nov 13
-
07 Nov 13
-
21 Oct 13
-
09 Oct 13
-
03 Oct 13
-
18 Aug 13
-
26 Jun 13
-
19 Jun 13
-
17 Jun 13
-
08 Jun 13
-
Pointing your home site's URL to a subdirectory
In some cases, you may have a WordPress site that changes significantly every year, such as with a conference website. If you want to install each year's version of the site in a subdirectory, such as /2010, /2011, and /2012, but have the root domain (yoursite.com) automatically redirect to a particular subdirectory (usually the latest), follow this technique:
-
-
16 May 13
-
09 May 13
-
03 May 13
-
30 Apr 13
-
18 Apr 13
-
15 Apr 13
Adrienne MichettiSelf-hosted Wordpress peeps: Is there an advantage to giving Wordpress its own directory? http://t.co/gF8OWQHE9y is it just abt clutter?
-
06 Mar 13
-
05 Mar 13
-
28 Feb 13
-
19 Feb 13
-
14 Feb 13
-
26 Jan 13
-
Go to the General panel.
-
In the box for Site address (URL): change the address to the root directory's URL. Example: http://example.com
-
Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress (wordpress in our example) directory into the root directory of your site
-
Move (DON'T COPY) the wp-config.php file to your root directory.
-
Edit your root directory's index.php.
-
-
06 Sep 12
arcojediMany people want WordPress to power their site's root (e.g. http://example.com) but they don't want all of the WordPress files cluttering up their root directory. WordPress allows you to install it into a subdirectory, but have your blog exist in the site root.
-
30 Aug 12
-
21 Jul 12
-
- Go to the General panel.
- In the box for Site address (URL): change the address to the root directory's URL. Example: http://example.com
- 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.)
- 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. As stated above, copy (don't move) the index.php file to your root directory, but MOVE (DON'T COPY) the web.config file to your root directory.
- Open your root directory's index.php file in a text editor
- 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'); - Login to your site. It should still be http://example.com/wordpress/wp-admin/
- 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.)
-
-
15 Jun 12
-
13 Jun 12
-
11 Jun 12
-
24 May 12
Martyn Whittaker"Using a pre-existing subdirectory install
If you already have WordPress installed in its own folder (i.e. http://example.com/wordpress) then the steps are as follows:
Go to the General panel.
In the box for Site address (URL): change the address to the root directory's URL. Example: http://example.com
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.)
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. As stated above, copy (don't move) the index.php file to your root directory, but MOVE (DON'T COPY) the web.config file to your root directory.
Open your root directory's index.php file in a text editor
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');
Login to your site. It should still be http://example.com/wordpress/wp-admin/
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.) " -
21 May 12
-
19 May 12
-
09 May 12
-
14 Apr 12
-
30 Mar 12
-
28 Mar 12
James Otto"Many people want WordPress to power their site's root (e.g. http://example.com) but they don't want all of the WordPress files cluttering up their root directory. WordPress allows you to install it into a subdirectory, but have your blog exist in the site root.
WARNING: Multisite Users - Please Read: This process is not applicable to and does not work if you have enabled MultiSite." -
27 Mar 12
-
25 Mar 12
-
21 Mar 12
-
03 Mar 12
-
21 Feb 12
-
20 Feb 12
christianacca"Many people want WordPress to power their site's root (e.g. http://example.com) but they don't want all of the WordPress files cluttering up their root directory. WordPress allows you to install it into a subdirectory, but have your blog exist in the site root. "
-
12 Feb 12
-
04 Feb 12
-
Using a pre-existing subdirectory install
-
Pointing your home site's URL to a subdirectory
-
-
21 Jan 12
-
Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress directory into the root directory of your site (Blog address).
-
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'); -
If you have set up Permalinks, go to the Permalinks panel and update your Permalink structure.
-
-
17 Jan 12
-
22 Dec 11
-
15 Dec 11
-
30 Oct 11
-
22 Oct 11
-
04 Oct 11
-
29 Sep 11
-
28 Sep 11
-
19 Sep 11
-
site's root (e.g. http://example.com)
-
to the root directory's URL
-
permalinks
-
-
15 Sep 11
-
29 Aug 11
-
03 Aug 11
-
20 Jul 11
-
11 Jul 11
-
09 Jul 11
-
11 Jun 11
Carl RempelThe process to move WordPress into its own directory is as follows:
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.)
Go to the General panel.
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
In the box for Site address (URL): change the address to the root directory's URL. Example: http://example.com
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.)
Move your WordPress core files to the new location (WordPress address).
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. As stated above, copy (don't move) the index.php file to your root directory, but MOVE (DON'T COPY) the web.config file to your root directory.
Open your root directory's index.php file in a text editor
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');
Login to the new location. It might now be http://example.com/wordpress/wp-admin/
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 y -
09 Jun 11
-
08 Jun 11
-
Giving WordPress Its Own Directory
-
While Leaving Your Blog in the Root Directory
-
WordPress allows you to install the WordPress files to a subdirectory, but have your blog exist in the site root
-
This process is not applicable to and does not work if you have enabled MultiSite
-
to move WordPress into its own directory is as follows:
-
- 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.)
-
Go to the General panel
-
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
-
In the box for Site address (URL): change the address to the root directory's URL. Example: http://example.com
-
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.)
-
Move your WordPress core files to the new location (WordPress address).
-
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. As stated above, copy (don't move) the index.php file to your root directory, but MOVE (DON'T COPY) the web.config file to your root directory.
-
Open your root directory's index.php file in a text editor
-
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'); -
Login to the new location. It might now be http://example.com/wordpress/wp-admin/
-
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.)
-
-
01 Jun 11
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.