Viewing 4 replies - 1 through 4 (of 4 total)
  • How did you move it – exactly what steps did you take?

    Thread Starter pasad50

    (@pasad50)

    I didin’t change anything in /store/ instance.
    I chnaged WordPress in root folder url setting to https://www.mydomain.com/blog/. I move all files from root to blog folder. I created an index file in the root

    */
    define(‘WP_USE_THEMES’, true);

    /** Loads the WordPress Environment and Template */
    require( dirname( __FILE__ ) . ‘/blog/wp-blog-header.php’ );

    You are going to have to give me more details of when and were you are encountering the 404 errors and exactly how you moved it.

    Are you saying that you moved one blog and the other blog is now having problems?

    You said

    I chnaged WordPress in root folder url setting to https://www.mydomain.com/blog/. I move all files from root to blog folder. I created an index file in the root

    I don’t know what you are referring to as the “root folder url” unless you you mean the “WordPress Address (URL)” or “Site Address (URL)” In the Admin Dashboard under Settings -> General

    Before you changed anything, did you make a backup of the entire WP site you moved? Did you backup your database?

    Always have a backup of both before you make any changes – large or small.

    A backup is a way to undo changes which cause problems and get back to a known condition of the code and or database.

    A simple way to make a backup is to use the Duplicator plugin. It was originall written to provide a way to move a WP installation (like you are doing) but it also is a quick way to make a backup of the entire site, including the database.

    If you have a backup, it would be easiest to restore it and then use Duplicator to make the move you want.

    If there is not backup, just give me as much detail as you can of each step you took in moving the WP installation, settings you changed and where and how you changed them, directories created, what new files did you create and where did you create them, etc.

    Details as to the 404 errors – what sort of posts or pages are you trying to get to when you get a 404? Are you saying that the changes to one blog have caused problems on the other blog? etc. etc

    You showed the following:

    */
    define(‘WP_USE_THEMES’, true);

    /** Loads the WordPress Environment and Template */
    require( dirname( __FILE__ ) . ‘/blog/wp-blog-header.php’ );

    Is that from wp-config.php? Is that code you changed? ??

    Bob

    I should have added:

    If you can get the WP installation back to where it was before you moved it and it was working properly, install the Duplicator plugin and use it to move WP to the other directory.

    It can be a tad contusing the first time you use it,let me know if there is anything you don’t understand before you that step or enter a particular value.

    I highly recommend you use Duplicator to make backups of all WP installations before you make any changes – including move it – so that you have a way to go back to a stable situation.

    I’ve been in Data Processing since 1973 and us ol’ timers won’t change anything without a backup – we learned, early on, and probably the hard way, that a backup can save your butt when you make a change and screw things up.

    Backups are not some waste of time – backups can make the difference between a broken program, or web site, and one that works.

    Knowing that you can go right back to where you started from gives you a profount sense of security.

    All ways back things up before making any changes.

    Also, make changes and test them somewhere other than on a “production” site. You can setup a sever/PHP/MySQL package on your own computer – too complicated to go into here – or you can simply create another directory on your hosting server and move WP to that directory before making changes. You then test the changes there and when you’ve got it working, you make the changes to the production system.

    If you put no links, anywhere, to the test directory, it will be private and no one else can get to it. That makes it safe to test things out before implementing them on the production site.

    When I say “If you put no links, anywhere,” – I also mean that you don’t give out a link to that directory to ANYONE – even on a forum like this. Once you give out a link you can almost count on it becoming more widely known.

    I’ve had WP installations in “unknown” directories for months at a time and no one has ever found them.

    Be wary if you want to post an error message from the test site, change the URL to hide the actual location.

    Bob

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Move wordpress to it's own directory – Redirect Rule’ is closed to new replies.