Javascript error in installation: Location.toString() cannot be called

That sometimes happens if you visit a page other than install.php before/during the process or similar.

Could you post up the rest of that page? Do you still get the form there?

Are you using IIS?

OK well I know nothing about IIS, but since it's listed at /requirements I'm bumping back up to critical to get some more eyes on this. Please reply with IIS, php and mysql versions and whether you clean urls enabled or not.

Looks like the bug is not reproducable by the reporter either. Sending emails is a different problem, you should set up your Microsoft Windows server / PHP instance to use an SMTP service which can send email.

I get the same problem while using the latest XAMPP 1.6.5 on WindowsXP professional:
- Apache HTTPD 2.2.6 + Openssl 0.9.8g
- MySQL 5.0.51
- PHP 5.2.5
- PHP 4.4.7
- phpMyAdmin 2.11.3
- FileZilla FTP Server 0.9.24
- Mercury Mail Transport System 4.52

I tried redownloading, reinstalling with first deleting all the files.. the error remains. When I go to the main page I get this error:

Fatal error: Call to undefined function user_access() in C:\Program Files\xampp\htdocs\drupal\includes\theme.inc on line 1651

Also dropped all database tables before reinstalling..

can you guys check your php error logs and report here?
I note here a code style inconsistency:
implode (',', $placeholders)
(space after implode in menu.inc, 316) but it can't be that.

impahz: did you reproduce that with RC2 or HEAD?

little time now... I'm trying to install RC2

boydjd: what's a documentation issue here? what needs to be documented?

I have the same issue on:
Drupal 6.0-rc2
MySQL 4.1.16
Apache Linux
PHP Version 5.0.4

Reporting the very same issue.
Drupal 6RC2 on LAMPP (PHP5.2.4, Apache/2.2.6 (Unix) DAV/2 mod_ssl/2.2.6 OpenSSL/0.9.8e PHP/5.2.4 mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.7, linux 2.6.22-14-generic).

Cleaning tables and files allows me to retry, yet I still get the very same error message.

I finally found a windows machine and some time to try to reproduce this, but I cannot reproduce this on XAMPP 1.6.5 with the same configuration as impahz (Windows XP Pro). We need more info to be able to reproduce this bug.

check your php error file, on my machine it's C:\temp\xampp\apache\logs\phperror.log
edit C:\temp\xampp\apache\bin\php.ini first, make sure log_errors = On and uncomment the line error_log =..., then restart XAMPP.

and Akral reported the same problem on a linux machine. can anyone post her php_info settings?

Here is my phpinfo().

thanks akral. can you reproduce this bug again with latest HEAD snapshot: http://drupal.org/node/97368 ?

People can't install Drupal, bumping up to a critical

I haven't reproduced the issue, but could this patch be enough to avoid the error? Can someone who's having this problem try it out? At a minimum, the patch didn't break the install process for me (linux, lighttpd, postgres).

This a good patch, I like it.

If anybody comes up with steps to reproduce please post. I just tested several installs with cvs on OS X, Apache 2, PHP 5.2.5 and tried visiting other pages at each step of the install but am so far unable to reproduce.

@HorsePunchKid: Can you explain why you thought the patch #23 could fix this?

So, if you visit a page when Drupal is not yet installed then the menu placeholders will come back empty handed and that's a problem. It does seem that "Install site" somehow runs the full page and I really have no idea what goes on. If I could get file level access to a place where this can be reproduced , that would be tremendously helpful.

its not an IIS issue - i just installed cleanly with IIS 5.1 / PHP 5.2.5 ISAPI / DRUPAL-6 as of now.

however, i can reproduce the error - when i disable javascript. install creates the db tables and goes until "> 4. Install site" - and then it stops, doesn't redirect any further. it clearly isn't finished. going from there to the start page yields the

PHP Fatal error: Call to undefined function user_access() in includes\theme.inc on line 1671

as reported above.

hope that helps.

1. please give us the list of tables installed. It seems you do not have all tables. I have 45.
2. please tell us the exact size of your drupal files.
3. how did you copied the files to your server?
4. @potowotoumi why do you use port 8888?

please provide the exact steps you are making at install process.
5. do you click on back or forward buttons in your browser at install process?
6. do you open new pages at install process?
7. do you use phpadmin to set up the database?
8. do you create a new database user, or you are using root?
9. do you clean up your browser cache before install? if not, please try.
10. which browser do you use? can you try it with other browser(s)?
11. do you use a clean drupal, or do you overwrite your previous drupal directory?

we can't reproduce it, please give us more details..

confirmed

install on xampp with disable javascript does not work
no error, but the install stops at "Install site", (and 43 tables are created)

missing tables:
cache_update
menu_custom

Confirmed on Mac OSX on installing with javascript off.

I ran a diff on the two databases and the unexpected tables missing are menu_custom and watchdog. I'm not familiar with menu_custom yet and I'm not sure when watchdog gets created. The other table differences are cache tables and things like openid and contact which are both on in my good install.

debugging a little with javascript disabled shows that $_COOKIE['has_js'] is 1 - with javascript disabled! -, letting _batch_start() go into _batch_progress_page_js() - which clearly isn't advisable without javascript. here the install stops. debugging further ...

if you delete your cookies the install works with disabled javascript

guess install.php should take care of this ...

now the question is if this is the root of all evil. can anyone experiencing this bug please clean his cookies and try installing again?

A clean (no cookies) install with javascript off does indeed work.

Wondering if this is really critical at this point since there is a workaround (delete cookies on a re-install) and while it should be fixed doing re-installations with JS on first time and then off the second time is a bit of an edge case. I convinced myself it's not.

Install.php should check for this and unset the cookie if JS is no longer on... maybe I'll get to look at that this evening if somebody hasn't fixed it yet.

Although I was about to complain that the automatic timezone configuration didn't work either until I remembered JS was off!

Hmmm. So this ends up being a bit of a pickle to solve.

In batch.inc Drupal install/update checks to see if the user has the has_js cookie set:

 function _batch_start() {
  // Choose between the JS and non-JS version.
  // JS-enabled users are identified through the 'has_js' cookie set in drupal.js.
  // If the user did not visit any JS enabled page during his browser session,
  // he gets the non-JS version...
  if (isset($_COOKIE['has_js']) && $_COOKIE['has_js']) {
    return _batch_progress_page_js();
  }
  else {
    return _batch_progress_page_nojs();
  }
} 

The problem is that the cookie is set in drupal.js as follows:

if (Drupal.jsEnabled) {
  // Global Killswitch on the <html> element
  document.documentElement.className = 'js';
  // 'js enabled' cookie
  document.cookie = 'has_js=1; path=/';
  // Attach all behaviors.
  $(document).ready(function() {
    Drupal.attachBehaviors(this);
  });
}

Of course drupal.js isn't called once JavaScript is off so unsetting the cookie will have to be done elsewhere.

Now come on, if you install once with JS then you have JS. Don't play evil games with poor Drupal.

But we still do not know, if this solved the problem for everyone. Who had problem with install please report back.

No. Drupal and the install process does not require javascript. The only problem is with the install, if you have an older drupal cookie with "has_js=1" in it and you install drupal with disabled javascript.

some kind of documentation to delete cookies when the install does not work, would be good..

Added to installation troubleshooting page.

I had this issue crop up today with a fresh checkout of HEAD. Drupal told me the db already exists, and would I please clear it. I fired up phpmyadmin, emptied the database, and switched immediately back to Firefox to continue the installation. At that point, I refreshed the page, clicked on the "Install Drupal in English", and got this error.

I'd say that this issue is not fixed at all. It should be explored further and a solution crafted for it.

@Pasqualle in #46, I may indeed have had an old cookie during my install, but I most certainly *did* have javascript enabled and running. FYI.

My system is Ubuntu 7 + Firefox 2 + a stock LAMP installation with apt_get.

1. do you have menu_custom table in database?
2. can you install drupal if you delete the cookies from your browser?

Hmm, a reinstall after dropping all tables again and clearing both session and domain cookies via the Web Developer Toolbar results in a proper installation. I don't really know how to reproduce this bug.

(Sorry, Pasqualle, I didn't see your comment before I dropped all my old tables, so I couldn't tell ya. I do remember that there were 46 of 'em though.)

repro steps I know of:
1. clear cookies
2. install drupal with enabled javascript
3. drop tables
4. reinstall drupal with disabled javascript

This method is considered as "playing evil games with poor Drupal"

If someone can provide other repro steps then we need to fix something, otherwise this issue can be closed..

I had this same problem. I have javascript enabled and DID NOT change that during the install process. I had to delete the "has_js" cookie to continue through the installation. once the cookie was deleted everything seemed to work fine.

I think I'm getting the same thing:

* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM menu_router WHERE path IN () ORDER BY fit DESC LIMIT 0, 1 in /home/burlingt/public_html/includes/menu.inc on line 315.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM menu_router WHERE path IN () ORDER BY fit DESC LIMIT 0, 1 in /home/burlingt/public_html/includes/menu.inc on line 315.

This was a fresh install on a previously unused domain. I had javascript enabled from the start and deleting the has_js cookie did not help.

Help appreciated.

mbond and AgentD please post any details about what steps you are taking and getting this error. What versions of PHP/Apache/MySQL browser and OS are you using? The more detail the better the chances somebody can replicate the problem so it can be fixed.

Redhat ES5
php 5.2.3
Apache 2.2.3-11 (el5)
mysql 5.0.22-2.2 (el5)

Firefox 2.0.0.12

Did a clean install to a new database. Followed the directions, got the above error. Deleted everything (including tables from mysql), cleared my cookies, did a clean install again, same thing.

Deleted everything from the server again, deleted cookies, cleared cache, restarted firefox, did a clean install again and got the same error message. Deleted just the has_js cookie for my server, hit the refresh button and it took off and finished the install.

I did NOT turn javascript off while installing, or change any other firefox preference.

An interesting thing to note is that I installed it on a second server.

CentOS 4
apache 1.3.41
PHP 4.4.8
mysql 5.0.45

Installed from the same firefox as above, and it went right through without any problems.

I've also noticed some additional problems with the first install, like pathauto not working properly that is working fine on the second install.

re: #56
JBrauer

Hi and thanks.

Server Info:
Operating system Linux
Linux kernel version 2.6.9-67.0.1.ELsmp
Apache version 1.3.39 (Unix)
Perl version 5.8.8
PHP version PHP/4.4.6
MySQL version 4.1.22-standard-log

Using Firefox 2.0.0.11

The error appears in the install process at step 4. I select choose language, verify requirements, set up database, then at Install Site that error appears and I can't get any further.

Thanks for any help.
Dan

------------------------
UPDATE:

I dropped the database, rebuilt it and install went through no problem.

Thanks.

Hi, I'm running

Debian stable
Apache-2.2
Mysql-5
PHP-5.2
Drupal-6.1
Galeon and Iceweasel

I'm getting the "ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM menu_router WHERE path IN () ORDER BY fit DESC LIMIT 0, 1" on line 316 error consistently in the install step 4

I edited line 316 from "DESC' " to "DESC LIMIT"
Then it gave me : "Parse error: syntax error, unexpected T_STRING in /var/www/a/drupal-6.1/includes/menu.inc on line 321"
line 321 : if ($router_item['access']) {

and then a bit further again, something about [' together perhaps, I don't code at all yet. Does this kind of stuff help ?

thanks

I'm experiencing the same original problem (ie, line 315 in menu.inc) at step "Install site". Tried reinstall a few times, including deleting cookies, clear db, clear settings.php, and using the patch. The patch clears the error, but I don't go any further. Below are the db tables created so far.

Linux
Apache 1.3x
Drupal 6.1
PHP 5.2.5
MySQL 4.1.10
Mozilla 1.7.3, Seamonkey 1.1

+-------------------------+
| Tables_in_drupal61 |
+-------------------------+
| access |
| actions |
| actions_aid |
| authmap |
| batch |
| blocks |
| blocks_roles |
| boxes |
| cache |
| cache_block |
| cache_filter |
| cache_form |
| cache_menu |
| cache_page |
| comments |
| files |
| filter_formats |
| filters |
| flood |
| history |
| menu_links |
| menu_router |
| node |
| node_access |
| node_comment_statistics |
| node_counter |
| node_revisions |
| node_type |
| permission |
| role |
| sessions |
| system |
| term_data |
| term_hierarchy |
| term_node |
| term_relation |
| term_synonym |
| url_alias |
| users |
| users_roles |
| variable |
| vocabulary |
| vocabulary_node_types |
+-------------------------+
43 rows in set (0.00 sec)

It appears that the installer sometimes forgets to build the menu routers? Why does it do that? I've seen this bug reported multiple times, but never been able to reproduce it.

Has anyone who has experienced this issue tried installing with Javascript enabled?

If that fixes the problem, this bug is a duplicate of #229825: backport "$_COOKIE['has_js'] must die" patch to 7.x.

The only time i get this error message is when installing with Javascript enabled.

I get the same error even when I disable javascript and clear all cookies.

The only time i get this error message is when installing with Javascript enabled.

Could you open the Error Console in Firefox, clear it, then run the installation with Javascript and see if any error message appears in the Console?

Hi,
Maybe it can help : I'm used to use Konqueror as a navigator ; with it, I've got this error either with Javascript or without it (not matter the cookie has_js exists or not). Each time I tried, the database of drupal has only 43 tables.
I tried the same installation with Firefox ; and it works with or without Javascript : the 45 tables are created and the installation process goes on. The only problem I've got is when I disabled Javascript but before removing has_js cookie : the process stall at 'install drupal' but without any error message. I'd just had to delete the cookie and the new installation goes on without problem.
I must precise that each time, I've delete all the tables in database, and the complete directory in my system (clean the install in fact).

The non-cleared cookie is a known issue.

But the other one seems to be a platform-specific Javascript bug.

Does Konqueror have a Javascript error log/console whose output you could post here?

Subscribe.

I'm sorry, but I can't find a way to display a sort of Javascript console for Konqueror. I've googled and find that there is a way using DCOP, but I'm not used with this tool and haven't manage to get things work.
Does anybody here know how to use DCOP in that way ?

Hi,
Due to a failure in Gallery2 installation module, I've been obliged to reinstall all Drupal ; from another computer with Firefox, I've got the error again ! The Error console shows :
Error : uncaught exception: Permission refused to call method Location.toString (translation from my own).

I am updating the title as this diagnosis (out of the numerous causes that have led to the symptoms described in this issue) is the only reproducible one that hasn't got its own issue yet.

Javascript, especially its security features, are beyond my ability, so I can't contribute any further.

I just got this same mySQL error again while re-installing a 7.x-dev instance for testing patch http://drupal.org/node/241086. I have a Mac running the latest Xampp. I have JS enabled for this localhost site, and always have. I shall post more details when I figure this out, but for now, it appears the problem is still happening.

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM menu_router WHERE path IN () ORDER BY fit DESC LIMIT 0, 1 in /www/drupalhead/includes/menu.inc on line 315.

Oh, BTW, this issue only cropped up when I dropped all tables to restore my sandbox to it's virgin state, and then proceeded straight to the install.php file without clearing my cookies. More info to follow as I find it.

The patch in #23 is exactly what I used to solve the issue for my version of Drupal. A similar solution could have been brought about by putting the placeholders into strings:
SELECT * FROM {menu_router} WHERE path IN ('. implode (',', $placeholders) .')
becomes
SELECT * FROM {menu_router} WHERE path IN ("'. implode ('","', $placeholders) .'")

I know the issue was caused by trying to reference the path for "node" too early in the system so that placeholders comes back empty, so it solves the issue, but I can't guarantee that it's really solving the root problem, just avoiding utter failure.

----
The way that I originally managed to recreate this issue was by consistently reinstalling to the same domain. Dropping the db, resetting the settings.php, and then re-installing.

about the "menu_router .. IN()" warnings - could someone clarify - patch #23 (or #74) should be submitted, or does someone know that an empty $placeholders shouldn't happen? A comment #179143-6: Do not fire bootstrap hooks during update says that it shouldn't be applied, but the issue is marked as fixed (it was about some errors, not these warnings) and it didn't fix the warnings. Either way the warnings should be fixed, cause they're reappering in several posts and aren't connected to any of the problems, they're just confusing. Not critical though.

Another thing that might be confusing - if you have some kind of strong onscreen error reporting (I had XDebug on), warnings may stop drupal from installing (not sure why, disabling javascript and cookies didn't help). After applying #23 I had the same problem as #25 (installation stopped, but no errors showing); after removing lines "CREATE DOMAIN int_unsigned ..." from system.install (which, already defined, was the cause of the blocking hidden warnings in my case, with #23 applied or not) everything worked fine; after disabling XDebug there was no problem at all.

As for the konqueror error/javascript console, it's still in development I think, but running konqueror in the console (I mean bash, Konsole) should show js errors.

This db error happened to me on a clean install when I cloned my settings.php file from another site. I had left the $cookie_domain set to another domain, so the install failed.

FWIW: Applying the patch in #23 solved the issue I was having with trying to run install.php via a curl script. (So as to automate the install process)

See also: http://drupal.org/node/204374

I don't know if the patch would have any other bad effects, but it seems pretty harmless - any way we could get this committed?

* Now come on, if you install once with JS then you have JS. Don't play evil games with poor Drupal.

How about adding a simple noscript area during the install "Javascript is disabled, allthough you can use Drupal without javascript it is highly reccomended to enable javascript for improved usability."

patch in #23 no longer applies.

error: menu.inc: No such file or directory

This issue has gone pretty quiet though, it's been over 3 years with no activity. Not sure if this is still an issue?