Скачать или смотреть Giving WordPress Its Own Directory

This is a tutorial of how to give wordpress its own directory instead in the root directory.

Giving WordPress Its Own Directory

https://codex.wordpress.org/Giving_Wo...

Contents

1 Moving a Root install to its own directory
2 Using a pre-existing subdirectory install
3 Pointing your home site's URL to a subdirectory
4 Moving Specific WordPress Folders
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. If you are running a version of WordPress older than 3.5, please update before installing a Multisite WordPress install on a subdirectory.

Note to theme/plugin developers: this will not separate your code from WordPress. Themes and plugins will still reside under wp-content folder.

Moving a Root install to its own directory
The 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. 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 than the .htaccess file so you must 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( dirname( _FILE_ ) . '/wp-blog-header.php' );
to the following, using your directory name for the WordPress core files:
require( dirname( _FILE_ ) . '/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.)

   • Giving WordPress Its Own Directory