I have a test site on my workstation running Windows/XP, Apache, SQL5, and PHP5. I have the locale module switched on and 3 other languages installed, but English is default. I am upgrading from Drupal-5.1 to Drupal-6. I have switched off all the contrib modules, and switched to theme "Bluemarine". I have reloaded the database into the new database I will use for Drupal-6. The Drupal-6 code is in a new installation directory. When I run the update script I get this message before anything else (on the first page which tells me what to do and invites me to "continue" - I'm not using maintenance mode by the way because this is not a production site):
user warning: Unknown column 'language' in 'where clause' query: drupal_lookup_path SELECT dst FROM url_alias WHERE src = 'blogapi/rsd' AND language IN('en', '') ORDER BY language DESC in C:\Apache\Apache2\htdocs\drupal-6\includes\path.inc on line 68.
user warning: Unknown column 's.textgroup' in 'where clause' query: _locale_rebuild_js SELECT s.lid, s.source, t.plid, t.plural, t.translation FROM locales_source s LEFT JOIN locales_target t ON s.lid = t.lid AND t.language = 'en' WHERE s.location LIKE '%.js%' AND s.textgroup = 'default' ORDER BY t.plural DESC in C:\Apache\Apache2\htdocs\drupal-6\includes\locale.inc on line 2060.
I press "continue" and got to the Drupal database update page. I get this message again:
user warning: Unknown column 'language' in 'where clause' query: drupal_lookup_path SELECT dst FROM url_alias WHERE src = 'blogapi/rsd' AND language IN('en', '') ORDER BY language DESC in C:\Apache\Apache2\htdocs\drupal-6\includes\path.inc on line 68.
After running the upgrade procedure I get this error at the top of the page, all other DB commands seem to have worked:
user warning: Unknown column 'language' in 'where clause' query: drupal_lookup_path SELECT dst FROM url_alias WHERE src = 'blogapi/rsd' AND language IN('en', '') ORDER BY language DESC in C:\Apache\Apache2\htdocs\drupal-6\includes\path.inc on line 68.
user warning: Unknown column 'language' in 'where clause' query: drupal_lookup_path SELECT dst FROM url_alias WHERE src = 'blogapi/rsd' AND language IN('en', '') ORDER BY language DESC in C:\Apache\Apache2\htdocs\drupal-6\includes\path.inc on line 68.
I login to the admin pages, everything seems fine.
Locale module is switched on. I switch on content translation module.
I edit all the languages to include a local name and activate the Language switching block. I change the content type to accept translation - everything seems to work from here.
Comments
Comment #1
JirkaRybka commentedApart from the JavaScript rebuild, which seems to happen very early, this seems like a update-problem of the path module - the queries go into url_alias table. This certainly needs more examination.
Comment #2
gábor hojtsySeems like you have blogapi module enabled, which injects RSD (really simple discovery) links to the update pages (which are meant to help your client discover where to input blog posts). I am not sure why this goes to the update page, possibly because it uses Garland as a maintenance theme. This is an interesting side effect, and might uncover more issues.
The other one is similarly used to aggregate the JavaScript files used on the page, but that one is used in the update process (to nicely display progress bars and such), so the textgroup update should go to the update_fix_d6_requirements() probably.
I think this is critical to fix in the release.
Comment #3
JirkaRybka commentedUnfortunately, the textgroup column creation already IS inside update_fix_d6_requirements() - I've written that bit myself a while ago - so we need more research here. Update.php still executes quite a bit before that, and obviously there's a possibility that the JS rebuild fires earlier.
Comment #4
gábor hojtsyWell, the bug report was against beta-1, so let's get fresh testing results from joel_guesclin with the latest development snapshot then: http://drupal.org/node/97368
Comment #5
gábor hojtsyOh, now I see this is happening because of code in blogapi_init(), so it is basically the same problem of invoking hooks on the update page, which should not happen. This makes this issue a duplicate of http://drupal.org/node/179143 continue there.
Comment #6
gábor hojtsyDoh, the JS issue is not fixed elsewere, so reopening this to fix the JS building no update. (Although I did updates with even older databases and was unable to reproduce this).
Comment #7
JirkaRybka commentedOk, http://drupal.org/node/179143 (#37) now have a patch (my own - don't take it as a review!), which I tested successfully to fix the blogapi problem, and which might fix the JavaScript issue too. Unfortunately I'm unable to reproduce the problem, so further feedback is really welcome here.
Comment #8
catchjoel_guesclin: if you could test JirkaRyba's patch over on that issue, it'd be great. Marking this to 'needs more info' rather than duplicate for now in case it turns out to be unrelated.
Comment #9
gábor hojtsyWe know where _locale_rebuild_js() is called, so we know it is related. Continued at http://drupal.org/node/179143 then.
Comment #10
joel_guesclin commentedI'm really sorry not to have gotten back to you on this... I do this at work in my "spare" time, of which I have had none lately. I will try again as soon as I can