By r.smith on

Wanting to upgrade, I have followed the steps here for creating a test site which will go in mysite.com/test_site. I have tried this both with the GUI methods and the command line methods.

[My situation: running Drupal 6.3 installed with Fantastico, MySQL 5.0.67, php 5.2.6, using theme Framework -- I did try switching to core themes with same result, clean URLs enabled, using URL aliases. I did clear my cache table after importing to testsitedb, I did clear brower cache, I did make the changes in the instructions to settings.php.]

What I find is that my Admin buttons don't work on the test site. When I navigate through the test site admin page to something, for example, mysite.com/test_site/admin/build/block, there is no problem, but when I change something on that page and click "Save Blocks", the page refreshes to mysite.com/admin/build/block (not the test site!) This happens in all such cases, like editing and then saving a view, logging in, running cron manually, etc. What is causing this, and how do I fix it?

Thank you so much in advance for your help.

⋅ Categories: Drupal 6.x

Comments

r.smith’s picture

r.smith commented

I thought perhaps the Pathological module would help this problem, but it doesn't seem to have solved it. Any one else have any ideas?

jstarek’s picture

jstarek commented

I just had the same problem. Check your .htaccess (it's easy to miss it when copying your files over on a Unix console as it's hidden) for your mod_rewrite configuration: When moving from domain.invalid to domain.invalid/testsite , you have to modify your RewriteBase accordingly. In the example:

RewriteBase /testsite

Hope that helps!

Jürgen

r.smith’s picture

r.smith commented

Jürgen,

Thanks for your comment. I tried it, made the RewriteBase /test_site change the .htaccess file in the test_site directory, and ran cron on the test site. No luck. I am missing a step that you can see?

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

If you're using the locale module, and you have it configured to use a domain for language negotiation, you'll have this problem.

For example if your English website is the default language and is set to http://en.website.com, when you move the database to another test site, it will exhibit the problems you show.

To fix this problem, you have to access the database and edit the languages table.

update languages set domain="http://en.testsite.com" where language="en"

did the job for me. You could also disable languages with 

update languages set enabled=0

to turn off all the languages while you get into your test site.

Anonymous’s picture

Anonymous (not verified) commented

Did you point the test site to the test database? if you forgot to edit your settings you will be using the live database

r.smith’s picture

r.smith commented

Had given up and am trying to create a test site again. I am not using the Locale module, and I did change the settings.php to point to the new database
$db_url = mysql://user:pass@localhost/test_site_db';
as outlined on the page http://drupal.org/upgrade/copying-your-site-via-GUI

One strange thing I've just noticed: When I'm on my test site, if I hover over a link, mozilla will tell me the link goes to www.blah.com/test_site/blah, but when I actually click on the link, it is my live site, not the test site ... Not sure what that means :(