Moving an old site to a sb directory so it functions

Started by Ryar, Jun 20, 2022, 02:32 AM

Previous topic - Next topic

RyarTopic starter

Hey everyone,

I'm assisting with the installation and configuration of a new WordPress website. The challenge is that the client wants to keep their existing website active in an archive subdirectory, which is a mixture of PHP and HTML with includes. The old website has been modified over time to work with the latest PHP version but retains its 1995 look.

While moving the WordPress site to the root directory poses no issues, I'm unsure if there's an easy way to move the old website to the archive and have it function properly. Alternatively, it may be necessary to modify file pathways manually.

It's essential to note that the client does not want to import the old website into the new WordPress site. Any recommendations on how to proceed would be highly appreciated.
  •  

inaevrodom

While I'm aware that this response may come a bit late, I'd like to offer some help to those who may have similar questions (and to you, if this issue is still unresolved).

The solution largely depends on how the initial website was scripted. If it used absolute paths, modifying each file manually would be necessary. However, if relative paths were used, copying and pasting should be a straightforward process.
  •  

albert_Cage

To address this, you can start by ensuring that the server configuration allows for the coexistence of different technologies. Since the old website consists of a mixture of PHP and HTML with includes, it's important to confirm that the server supports these technologies and that there are no conflicts with the WordPress installation.

Moving the WordPress site to the root directory can be straightforward, but relocating the old website to the archive subdirectory may require careful planning. You may need to create specific configurations in the server settings to ensure that both the new WordPress site and the old website can function without interfering with each other.

If the old website has been modified to work with the latest PHP version, it's crucial to verify that these modifications will continue to function in the new server environment. You may need to review the codebase of the old website and make adjustments to file pathways to accommodate the move to the archive subdirectory.

As the client does not want to import the old website into the new WordPress site, it's essential to maintain clear separation between the two. This may involve setting up redirects or reconfiguring the server to handle requests for the old website within the archive subdirectory.

Communication with the client is key throughout this process. It's important to manage their expectations and provide regular updates on the progress of the migration. Explaining the technical considerations in a language they understand will help them appreciate the complexity of the task and the efforts involved in achieving their desired outcome.
Handling the installation and configuration of the new WordPress site alongside the preservation of the old website requires a meticulous approach to server configuration, code review, and client communication. By carefully addressing these aspects, you can ensure a seamless transition while maintaining the distinct identity of each website.
  •