/blog

  • Hello,

    I have run into a strange issue. I manage a website called grillpartssearch.com which has an X-Cart framework (like Shopify). We currently have a wordpress blog installed at https://grillpartssearch.com/blog/. The problem is we’re using an old module that let’s us use wordpress with X-Cart it is out of date and no longer supported (and I cannot update wordpress without crashing the site) so I wanted to do a separate wordpress install. We changed to a hosting company where I do not have cPanel access and I would have to install wordpress manually using FTP (I also have access to phpMyadmin). But I need the address to be /blog/ and I’m not sure the right steps on how. I believe I must:

    1. Download a backup of the old wordpress blog
    2. Do a fresh install of wordpress
    3. Somehow make it /blog/ or /blog2/
    4. Transfer the backup to the new wordpress install.
    5. If I had to make the new wordpress /blog2/ delete the old site and use phpmyadmin to change /blog2/ to /blog/
    6. Any advice on this would be great. This is a unique situation that would need a unique solution. Thank you in advance.

    Best Regards,

    Kelly

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)

  • What is your expected result? Why do you want to do a separate WordPress install? Why change hosting company?

    For WordPress site migration, I recommend All-in-one WP migrate

    1. Install migration plugin on Source site
    2. Download Source site backup
    3. Install WordPress on new hosting account (Destination)
    4. Install migration plugin on Destination
    5. Upload and restore backup

    Note: If you want to use the same domain name on Destination, then you will need to edit your localhost file to manually change the IP address that resolve to the domain name. So that the domain goes to the new hosting account (not the old hosting), on your computer.

    Moderator bcworkz

    (@bcworkz)

    Somehow make it /blog/

    You would have done that by installing WP in public_html/blog/ instead of the usual public_html/ (assuming public_html/ is the public root for your domain name, YMMV)

    All-in-one WP migrate is a good recommendation, but TBH I’ve never used it. I assume it’ll properly update all domain/path references based on the destination location. Even if it did not, you can update the data to reflect the correct domain/path using the Better Search and Replace plugin. Do not try to do this directly through phpMyAdmin because it’s difficult to correctly update serialized data. The plugin knows how to handle serialized data. It’s OK to use phpMyAdmin to update the siteurl and home option values so you can gain proper access to the site, but don’t try to do global updates.

    If All-in-one WP migrate does what I think it does, none of the search and replace or phpMyAdmin actions will be necessary.

    I assume this new site has a different domain name, so Liew’s comments on localhost wouldn’t apply. While what he suggests will work for you, it doesn’t help any other site visitors, so I don’t think it’s a very useful solution.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘/blog’ is closed to new replies.