Redirects to WordPress Posts and PHP Memory

  • I’m in the process of converting a 10-year-old HTML site into a WordPress site. The old site has over 800 pages, most of which are product pages.

    I’m creating a .htaccess file with 301 redirects to each of the new WordPress posts/pages. The trouble is, with over 800 redirects, I’m worried that this method will be a heavy load on the server.

    Do you think it will be? I’ve never done this before.
    Would it be better if I put a redirect on each individual HTML page?

    I’m already having problems with server capacity, getting an occasional 500 error, which my web host says is due to the site running out of PHP memory. And, at present, customers aren’t using the site–only me.

    I created a custom phprc file with 128 MB limit as my web host suggested, but tonight I got the 500 error once as I worked on the site.

    I’d appreciate any suggestions.

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator James Huff

    (@macmanx)

    You won’t see too much load from excessive .htaccess redirects, unless they wind up looping, but I wouldn’t recommend keeping them around for too long, just to keep things tidy. Maybe 6 months to a year so search engines notice.

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter novelist99

    (@novelist99)

    Thank you for all of the suggestions. I really appreciate it. I will try what you suggested.

    I think one of the problems was likely infinite scroll, which I’ve disabled–unfortunately, because it’s cool.

    Also, the template I’m using has a built-in “builder” which adds various modules to pages, and I wonder if that could be causing problems. I’ll check to see if there’s an update.

    Here’s the site, which I soon plan to move to the main directory. https://www.butterflywebgraphics.com/wordpress/

    Since it’s a graphics site, it’s pretty server heavy to begin with.

    Thanks again!

    Moderator James Huff

    (@macmanx)

    It’s possible that Infinite Scroll and the builder were conflicting badly, essentially re-issuing the build for the built portions with every single new scrolled page.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Redirects to WordPress Posts and PHP Memory’ is closed to new replies.