Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By vizechef on
"Test site, always start with a test site" - imho a really good advice !
So I downloaded the complete MySQL database from production an put it into a test environment, that I prepared before. settings.php has correct entries and - voila - I get the front page !!
Wow, I was happy and tried to login as admin, but it didn't work.
I played around truncating the tables 'sessions, cache, watchdog, accesslog' which I thought were possible reasons for that problem.
After that I was able to call pages (i.e. admin/settings) directly and navigate to others, but when submitting changes I was thrown out with the 'Access denied' message.
There are many other things I tried out, but - no success !
Somebody having an idea ??
Comments
did you update?
If you are testing with 4.7 and the production site is from 4.6 you have to run update.php first.
White Paper Designs
I have 4.7 beta 4 in
I have 4.7 beta 4 in production and built my second test environment completely new by transferring all folders from production to test. Then I made the required changes in settings.php and installed the database.
Btw, it has another name but I do not expect this to be a problem. Am I right ?
Does your webserver know
Does your webserver know it's name, have you made any changes to .htaccess (or do you need to), does the system you are using to access the test site know the name (hosts file, etc).
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
My webserver
Hi Steven, is it you I quoted ? :-)
I've seen your comments in numerous topics and I totally agree.
My webserver is a XAMPP (Apache 2.0.54, PHP 4.4, MySQL 4.1.14) running under Win XP.
I neither made any changes to hosts file nor defined a virtual host in apache configs.
I deleted the htaccess file that I downloaded from production, because my first test environment runs fine without it ( or better - it only runs WITHOUT htaccess ;-))
Do you think it is a session-based problem ?
clean urls
Do you have clean urls turned on?
If you do, you have to have .htaccess working.
White Paper Designs
No
No, I have not.
Hm ...
It's kinda strange ...
To my biggest surprise I was able to login today !?
I have DEFINITELY done NOTHING except shut down my pc and gone to bed !
I wish all problems could be solved this way ...;-)
Somebody having an idea what could have been the reason for that phenomena ?
Is there a session-based maximum time frame which ran out ?
Help setting up prod site from test site.
Help. I just copied my test site to my prod site. Everything is working fine but one thing.
When I try and access my prod site by http://mysite.com, nothing will load. If I access http://www.mysite.com it loads fine.
I can access my test site with http://mysite.com/sandbox . It redirects/shows this url as http://www.mysite.com/sandbox (on the test site, but not on the prod site).
Both the prod site and the sandbox site have the same .htaccess files. There is no .htaccess in root. The only rewriterules that are active are:
# Rewrite current-style URLs of the form 'index.php?q=x'.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
I’m sure this will be obvious to most of you, but it is driving me crazy. I’ve tried to use other rewrite rules in the prod site .htaccess, but I just don’t “get it”.
Sounds like you may be
Sounds like you may be having this problem
http://drupal.org/node/59243
http://drupal.org/node/61124
For example, right now I am locked out of my subdomained site, but when I access it via the file tree off the normal site I can actually get in. The subdomain is just printing
<html><body></body></html>At least on firefox, can't see any source code via IE
Same issue?