WP 1.5 How to install into subdirectory?

I’ll tell you how I’m testing.

I have 1.2.2 in my root.

1. I cloned my database.
2. Created /wordpress/
3. Installed 1.5 in /wordpress/ and pointed it to new database
4. Ran /wordpress/wp-admin/upgrade.php

Done

EDIT:

Be sure to edit cloned db to reflect that it’s in /subdir/

Dmitri, many thanks for the clear instructions. I have a slightly different problem using luxSCI for hosting. MySQL dbms is located in a non-user accessible area. Thus I cannot clone the DBMS itself.

If I’m to make this work, I’ll need to switch the DBMS between the 1.2.2 and 1.5 WP installs.

No doubt it could be done by the Competent. I’m just starting, so my troubleshooting skills are weak – if I break it I”m in trouble ??

Related question. When I originally tried to install WP 1.2.2 into root/wp subdirectory, the install.php failed because it couldn’t find one of it’s setup files [config.php or /wp-admin/post.php, I forget]. My brute-force fix was to move the whole WP install into the root of my domain. When I tried a test install of 1.5 into a subdirectory yesterday, the same thing happened. Since I don’t want to take seekerblog.com off the air, I stopped.

I’ve seen a comment or two in the forums indicating that you must tell WP to change the “WordPress address (URI)” before you do the new subdirectory install. Does that make sense?

Steve

Actually, I’m quite confused about what you’re trying to do.

If you’re trying to install your blog files in one place (/blog/, for example) and have you index.php somewhere else (the root directory, for example) please read this: https://www.ads-software.com/docs/installation/different-address/

If you’re just trying to normally install WordPress, please please read this: https://codex.www.ads-software.com/Installing_WordPress

If you don’t want to disrupt your v1.2.2 install, you need to make a new database for the v1.5 install and place it in a different directory.

>Actually, I’m quite confused about what you’re trying to do.

No doubt because I explained it poorly. And large thanks for instant and detailed reply.

>If you don’t want to disrupt your v1.2.2 install, you need to make a new >database for the v1.5 install and place it in a different directory.

That may be the Key insight I needed – I was trying to work around the inability to have two DBMS instances. I’ll try a more coherent explanation:

1. Objective

Test a WP1.5/Mallow-theme blog without disrupting service to existing WP1.2.2 blog at seekerblog.com.

Once (if) I’m satisfied the WP1.5 version is ‘stable’ I will replace/upgrade the still running WP 1.2.2 install.

My desire is that the DBMS continue updating with WP 1.2.2 activity. When ready to make the switch I want to attach that instance of MySQL to the new WP1.5.

2. Problems

a) my host doesn’t allow access to the DBMS directories, so I cannot just clone a separate test-instance. HOWEVER, I just realized they will most likely create a new instance for my [prob just a few $$]. That should solve prob (a). I’m contacting LuxSCI support now to make the new instance.

b) to isolate WP1.5 from WP1.2.2 I need to install into a subdirectory. As it is a test install index.php does NOT need to be at root.

Both times I’ve tried to install WP in a subdirectory, install.php failed due to file referencing problems. I didn’t troubleshoot, I just bypassed the problem by moving the install to the root. The first attempt was ‘clean’, the second attempt yesterday was after WP1.2.2 was configured and running at root.

Is there is a tip I should know before again try to install WP1.5 into root/wp?

Thanx, Steve

Progressing thanks to your help. Cloned new DBMS instance, installed WP1.5 into root/wp_mallow. Then,

Run https://seekerblog.com/wp_mallow/wp-admin/upgrade.php

Result: Invalid argument supplied for foreach() in /xd1/homes/hash/41/a2141/90/05/u20590/seekerblog.com/www/wp_mallow/wp-settings.phpon line 103

And here is line 103: foreach ($current_plugins as $plugin) {

Any suggestions appreciated, Steve

Two things strike me as wrong:

1. https://seekerblog.com/wp_mallow/wp-admin/upgrade.php
That looks like you either have a blog called “wp_mallow” OR you are somehow putting WP files under a theme ?

2. /–path–/seekerblog.com/www/wp_mallow/wp-settings.php
That seems a curious path … the /www/ looks to be wrong.

More opinions needed I think.

Podz – thanx for the feedback.

I named the wp_mallow directory to identify it as the new WP1.5 install.

The path “/–path–/seekerblog.com/www/wp_mallow” in the error results (I think) because my host luxSCI requires that site files be in the /root/www directory, and it resolves https://seekerblog.com to https://seekerblog.com/www. I.e., that’s where my WP1.2.2 index.php sits.

As I posted above, everytime I’ve attempted a subdirectory install at this hosting service I get path referencing errors.

Try just /mallow/. The _ could be conflicting with your server setup.

/mallow/ OK – will change it to /wp/ ??

Right now I’m trying the wintel/linux-only app called MySQL Query Browser on my never-used XP box. I’ve figured out how to make it connect, and have just changed wp_options:site_url and :home to point to seekerblog.com/wp_mallow, and cleared the wp_options:active_plugins (which was set to markdown.php)

I’ll see if that clears my problem before I change the subdirectory.

>just changed wp_options:site_url and :home to point to seekerblog.com/wp_mallow,
>and cleared the wp_options:active_plugins

Yike, that fixed it! Successfully accessed upgrade.php, upgrade worked, now looking at the WP1.5 test site, default install.

So the wp_mallow subdirectory is OK. What killed it was the old install pointers. Maybe the WP install/upgrade should offer user the ability to fix pre-existing settings?

I would think that potential upgraders would typically have the same challenge I’m facing. How to do upgrade, then validate, without disrupting a “production” site?

Thanks guys!!

Steve