Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I had problems with our testbed as there was no way I could get simpletest to install drupal HEAD and I could install it through browser w/o problems so I took away the only diff between normal browser and simpletest which is JS. After disabling JS in FF install is stuck on 'Installing Drupal' page. Refreshing does not work and there are no link or buttons I could click to push it to next step. DB tables are generated and populated its just UI that is 'stuck'.
Comment | File | Size | Author |
---|---|---|---|
#5 | Picture 5.png | 44.85 KB | Rok Žlender |
Comments
Comment #1
Amazon CreditAttribution: Amazon commentedThis is the testbed: http://testing.drupal.org/
Comment #2
Gábor HojtsyI just did a quick install without JavaScript in Firefox (the fieldsets were not collapsible, so this verified I am not using JS), and all worked fine for me. So I am unable to reproduce.
Comment #3
vjordan CreditAttribution: vjordan commentedI successfully installed without JS enabled. I cannot reproduce this issue.
Comment #4
yched CreditAttribution: yched commented"Simply" disabling JS in FF to test non-JS install is borched, because your browser still has the 'has_js' cookie, so it still gets served the 'JS' version of the batch processing page. This of course doesn't happen if JS is 'really' disabled, not just from 30 secs ago for the sake of testing. You need to disable JS *and* clean the cookie - or restart your browser, since has_js is a (browser-)session cookie.
The initial problem is probably that the batch engine (which is now used even for non localized installs since http://drupal.org/node/176003) relies on the fact it is facing a *browser* : the successive HTTP requests are triggered through AHAH (JS) or http-equiv="Refresh" (non-JS).
Same reason why you can't batch in cron...
Comment #5
Rok Žlender CreditAttribution: Rok Žlender commentedHow to reproduce:
To my big surprise installation went over fine in Safari 3 on same install.
Comment #6
Gábor HojtsyHm, since we cannot reproduce this so far, maybe you can look into whether the refresh meta tag is missing or what happens for you? Maybe you have a broken theme file, which you modified and badly merged with cvs update?
Comment #7
keith.smith CreditAttribution: keith.smith commentedI just tried to reproduce this problem with a web server running Apache/2.0.54 (Fedora), with PHP 5.0.4, MySQL 4.1.20, using FF 2.0.0.11 on a Vista system. I disabled JS in Firefox, and deleted all cookies for my test site (including the has_js cookie). Created a new database, and checked out a new version of HEAD. Granted write permissions to sites/default. Closed and restarted my browser. Checked that Javascript was disabled, and it was.
Ran the installation routine, had no JS elements during that process (no clean urls, no collapsible fieldsets, no automatic email addresses or time zone detection.) But, the installation completed normally, and I ended up on the "Visit your new site" screen, and the new site seems to work fine.
Comment #8
yched CreditAttribution: yched commentedLooks like Rok and I crossposted in #4 - #5.
Thus, resetting the title : install is definitely *not* JS only.
The problem with the testbed is most probably that the install currently has to be performed through a browser - or, at least, something capable of executing the refresh meta tag.
Dunno whether this still qualifies as critical.
Comment #9
Gábor HojtsyRok reproduced this issue in two of his browsers, so the title change was deliberate IMHO.
Rok: you should test with firebug's http sniffer, and see what happens actually.
Comment #10
yched CreditAttribution: yched commented"Rok reproduced this issue in two of his browsers, so the title change was deliberate IMHO."
Since we crossposted in #4-#5, my bet is that what Rok reports is caused by the 'has_js' cookie not being cleaned. We'll see :-)
So, Rok, could you confirm you get a broken non-JS install *after* cleaning your cookies ?
Comment #11
Rok Žlender CreditAttribution: Rok Žlender commentedNo I cannot. This seemed to be old cookie issue. I successfully installed drupal without JS on few browsers (FF, Safari, Opera). This is no longer critical. Problem I'm having is that simpletest does not support meta redirects. I can go around this by manually reloading proper pages. Not sure if this is worth fixing but I'll leave the issue open.
Comment #12
cburschka1.) The bug in normal browsers is caused by this: #229825: backport "$_COOKIE['has_js'] must die" patch to 7.x
2.) The bug in simpletest, lynx and other clients without meta-refresh is caused by this: #229905: Batch API assumes client's support of meta refresh.
That covers both problems described here.
Comment #13
acrollet CreditAttribution: acrollet commentedThe patch in #23 at http://drupal.org/node/210752 fixed this issue for me. (needing to use curl for install.php)