Using latest HEAD, the upload module's attach button simply hangs. Using Konqueror 3.4.3. I've tested Firefox, and it seems to work.

I'm pretty sure it used to work on Konqueror. I'd debug this myself but frankly I don't know where to begin with this ajax stuff. Not sure if the problem lies with upload.module, upload.js, common.inc...

Comments

Dave Cohen’s picture

I got konqueror to show me an error message. It was in parseJson in drupal.js. Apparently the data passed in there is an object, and there is no code to handle that case.

I added code:

function parseJson(data) {
  if (typeof data == 'object') {
    return { status: 0, data: 'Unspecified error' };
  }
  if (data.substring(0,1) != '{') {
    return { status: 0, data: data.length ? data : 'Unspecified error' };
  }
  return eval('(' + data + ');');
}

And the result was an alert box with Unspecified error. After I close it, however, konqueror crashed.

I think I've exhausted my tolerance for javascript for a while. I hope someone more knowledgeble can investigate.

Bèr Kessels’s picture

I can confirm this.

No error is reported, but that is most prolly due to the use of the iframe.

konq 3.5 has no issues. So it makes me thing konq 3.4 hasa bug wrt to json parsing.

Can we please just switch off JS for konq 3.4 then?

Bèr Kessels’s picture

bumping this issue. It is annoying. And untill SuSE and kubuntu come with KDE3.5 majority of KDE users are running 3.4

It is a SHAME that Drupal cannot run flawless on an OSS system. The amount of ppl using that OSS system might be a minority, but when did we no longer care about minorities?

killes@www.drop.org’s picture

Ber, I had asked you shortly before the 4.7 release if there were any leftover problems with Konqueror and you said there werent any. ...
Can you roll a patch for excluding Konq 3.4 from JS?

Bèr Kessels’s picture

My answer was: not on 3.5. In 3.5 it is all fine. not in 3.4.
My JS skills are even worse then yours, killes, :) But ill see what we can do.

magico’s picture

Someone with JS skills and Konqueror 3.4 can provide a patch so this can work flawless?

Bèr Kessels’s picture

Version: x.y.z » 4.7.x-dev
ztyx’s picture

Version: 4.6.x-dev » 6.x-dev

Version: x.y.z » 4.7.x-dev

Hmm, this bug was filed for HEAD. Should the version really be set to 4.7.x-dev then?

Since I have to set a version to make this comment I set it to 6.x-dev. Once again, what version of Drupal was this bug applicable to?

EDIT: I looked at the wrong date. Setting it to 4.6.x-dev. Is this bug applicable to Drupal 5.x or Drupal 6.x?

ztyx’s picture

Version: 4.7.x-dev » 4.6.x-dev
dutler’s picture

Version: 6.x-dev » 6.6
Priority: Normal » Critical

confirmed with konqueror 3.5.10
Drupal 6.6
Access to update.php Protected
Configuration file Protected
Database updates Up to date
Drupal core update status Up to date
File system Writable (public download method)
Module and theme update status Up to date
MySQL database 5.0.45
PHP 5.2.5
PHP memory limit 96M
PHP register globals Disabled
"PHP settings limit the maximum file size per upload to 24 MB"
Unicode library PHP Mbstring Extension
Web server
Apache/1.3.37 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a PHP-CGI/0.4mm

gábor hojtsy’s picture

How did it work for Bèr then? Was it fixed for some time in Konqueror 3.5.x?

dddave’s picture

Status: Active » Closed (fixed)

Konqueror? D6.6? No feedback to #11 so my educated guess is that this is obsolete.