bamerrell

I was afraid that I might have to start over. I do still have a full install in the root, but the copy has its own DB, etc.

Can you elaborate on the possibility of a .htcacess conflict? What comes to mind that might be amiss in the wp-config? And why would these prevent the script from being recognized?

I don’t want to take up too much of your time, but I would love to at least figure out what is wrong so I can learn from this headache.

Thanks!

So I’ve been really busy and I haven’t had the time to try the steps listed above, but I think I figured out what is going on here.

When I created this development site ‘www.example.com/dev’, I must have done something wrong. It looks like all the image links on the dev site are still pointing to the original site ‘www.example.com/wp-content/uploads…’. I tried my best to follow documentation when I made the dev site, but it was a long time ago so I don’t remember exactly what I did. I remember that I copied the original site and moved it over, but I don’t know the steps I took.

I think if I can manage to fix the image anchors on the dev site to point to ‘wwww.example.com/dev/wp-content…’, it will be smooth sailing when I delete the original site and transition to the dev site.

Does anyone know how I can fix these links? I tried running the Velvet Blues Update URLs plugin to no avail:

Results
9 Content Items (Posts, Pages, Custom Post Types, Revisions)
0 Links
10 Attachments
34 Custom Fields

A little more info: I’ve tried running the plug-in with the following values:

Old URL: http://www.example.com
New URL: http://www.example.com/dev

and

Old URL: http://www.example.com/dev
New URL: http://www.example.com

I tried both just in case I had the two mixed up. Same result with both input sets.