File downloads inaccessible after upgrading, various error messages

Addition: The "Metadata" tab still lists the (sub-) directories.

The files in the "audio" directory are owned by the webserver user.

Also, there is a descript.ion file in each subdirectory, but it's contents is not evaluated by the "Metadata" tab (the metadata textfields are empty).

Thanks, switching to "icon view", then saving, then switching back to "llist view" does the trick.

Now the previously uploaded files are listed again. But I'm getting the following warning:

warning: usort() [function.usort]: Invalid comparison function in /var/www/drupal/sites/all/modules/filebrowser/filebrowser.theme.inc on line 201.
warning: usort() [function.usort]: Invalid comparison function in /var/www/drupal/sites/all/modules/filebrowser/filebrowser.theme.inc on line 205.

Probably this causes that sorting by Display name does not work. Edit: #841372: usort() Invalid comparison function - Upgrading to dev version.

Also, the texts from the descript.ion files still do not appear in the "Metadata" tab (not sure if they should).

And, last but not least, the listed files can not be downloaded (404, file not found error).

Thanks & greetings, -asb

6.x-2.x-dev deliver additional errors:

Parse error: syntax error, unexpected '}' in /var/www/drupal/sites/all/modules/filebrowser/filebrowser.theme.inc(218) : runtime-created function on line 1
Parse error: syntax error, unexpected '}' in /var/www/drupal/sites/all/modules/filebrowser/filebrowser.theme.inc(223) : runtime-created function on line 1

The "Display name" error is nox fixed in the dev version.

Also, it breaks the theme. Great.

> What is the field you are sorting (in the URL sort parameter) ?

http://.../node/218?sort=desc&order=Display+name

> Which php version are you using ?

PHP 5.2.6-1+lenny8

Magic quotes GPC	Off
Magic quotes runtime	Off
Max execution time	30
Max input time	60
Memory limit	200M
Post max size	30M
Register globals	Off
Safe mode	Off
Session cache limiter	none
Session save handler	user
Upload max filesize	30M

PHP extensionscURL version	7.18.2
GD version	2.0 or higher
FreeType support	Enabled
JPG support	Enabled
PNG support	Enabled
Multibyte support	Enabled
XML support	Enabled
Zip support	Enabled
Zlib support	Enabled

> Is it possible for you to insert an "error_log($code)" just before the erroneous line and giving to me what you have ?

The error was:

Parse error: syntax error, unexpected '}' in /var/www/drupal/sites/all/modules/filebrowser/filebrowser.theme.inc(218) : runtime-created function on line 1
Parse error: syntax error, unexpected '}' in /var/www/drupal/sites/all/modules/filebrowser/filebrowser.theme.inc(223) : runtime-created function on line 1

If 218 and 223 are the line numbers, I'm getting this after inserting error_log($code) at the two locations referenced:

Parse error: syntax error, unexpected T_VARIABLE in /var/www/drupal/sites/all/modules/filebrowser/filebrowser.theme.inc on line 219

Inserting error_log($code) before line 1 makes no sense because line 1 is: <?php.

Regarding storing the data: I'm putting the files into /audio (in the root of the Drupal installation); however, there's also a directory at ./sites/default/files/filebrowser that I haven't created (with two subdirectories: archives and obscurity_links). I have no idea what archives is, and I can't find a setting to configure/remove these obscurity_links in the current -dev release. This is a bit confusing but no major issue (some documentation what to expect would help)

Thanks & greetings, -asb

Changing description and status (the module does not work at all in the current state)

Any updates on this issue?

Sorry, in filebrowser 6.x-2.x-dev from 2010-Sep-07 this issue isn't fixed completely.

E.g. downloads are still completely impossible.

As well if the file includes whitespace characters which aren't handled at all, as it seems, as with filenames like "saudade_cd_2nd-cut_14.mp3" (watchdog logs: "file not found", but the path is correct).

As far as I can see, the latest dev release isn't operational at all, except that it creates directory listings (which can't be used for anything since downloads are impossible).

> Are you sure you are using the right download manager ("private" if you folder in under drupal root, "public" else case ? ).

Yes, the "downloads" folder is under Drupal root. And no, I wasn't aware that the "private" download method would be a requirement. I've changed this, but the behaviour doesn't change.

Thanks for the clarification. I upgraded to the current dev release, cleared all caches (through drush), but the behaviour didn't change.

Any other ideas?

@Yoran: Yes, downloads circumventing the filebrowser mechanism do work fine. The OS is Debian "Lenny", the PHP version - well, would you please have a look at #6 from July 2, 2010?

> did you check you have a table called node_dir_listing_content ...

I have one table node_dir_listing_content and another one called node_dir_listing

mysql> describe node_dir_listing;
+-------------+------------------+------+-----+---------+-------+
| Field       | Type             | Null | Key | Default | Extra |
+-------------+------------------+------+-----+---------+-------+
| nid         | int(10) unsigned | NO   | PRI | NULL    |       | 
| folder_path | varchar(255)     | NO   |     | NULL    |       | 
| properties  | longtext         | NO   |     | NULL    |       | 
+-------------+------------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

mysql> describe node_dir_listing_content;
+-------+------------------+------+-----+---------+----------------+
| Field | Type             | Null | Key | Default | Extra          |
+-------+------------------+------+-----+---------+----------------+
| nid   | int(10) unsigned | NO   | MUL | NULL    |                | 
| fid   | int(10) unsigned | NO   | PRI | NULL    | auto_increment | 
| root  | varchar(255)     | NO   |     | NULL    |                | 
| path  | varchar(255)     | NO   |     | NULL    |                | 
+-------+------------------+------+-----+---------+----------------+
4 rows in set (0.00 sec)

The first one indeed contains the data from the filebrowser listing; sample excerpt:

mysql> select * from node_dir_listing_content;
+-----+-----+---------------------+----------------------------------------------------------------+
| nid | fid | root                | path                                                           |
+-----+-----+---------------------+----------------------------------------------------------------+
| 218 | 301 | /Saudade            | /Saudade/saudade_cd_2nd-cut_09.mp3                             | 
| 218 | 277 | /Saudade            | /Saudade                                                       | 
| 218 | 275 | /                   | /Saudade                                                       | 
| 218 | 274 | /                   | /                                                              | 
...
+-----+-----+---------------------+----------------------------------------------------------------+
38 rows in set (0.00 sec)

I never fully understood the mechanics of the Filebrowser module, but this looks strange to me: Two different file ids are pointing to the same "path", but are coming from a different "root". However, other directories have the same "structure" in this database table, so probably this is how it is supposed to be?

> and can you find the file you try to download with the right path and nid in it?
> when you found this file, the fid column value should be the same as XX in filebrowser/download/XXX link.

Sorry, the that part I do not understand. What would be the "right path"?

@Osik: I'm running Apache, so at least it's not an issue with those incomplete Lighty rewrite rules ;) you're still on FreeBSD?

If I'm hovering over the link on saudade_cd_2nd-cut_09.mp3 (physically stored in the folder /var/www/mysite/audio/Saudade) when being on http://mysite.tld/node/218/275, I'm getting the URL http://mysite.tld/filebrowser/download/301. The URL http://mysite.tld/filebrowser/download/301 results in a 404 "not found", while http://mysite.tld/audio/Saudade/saudade_cd_2nd-cut_09.mp3 immediately downloads the file.

Node node/218 is configured as follows:

• The system file path to the directory: /var/www/aem/audio
• Download manager: Direct download
• Allow subdirectory listings (checked)
• Folder Upload: (unchecked)
• FileSystem encoding: UTF-8

> You use an absolute path instead of a relative one, for a apache served directory.
> "normally" if in your case drupal root is /var/www/aem, path definition should be just "audio".

Hm, the description of this setting seems to be pretty clear: "The system file path to the directory. This can be an absolute path or should be relative to the Drupal root directory.. However, if I use a path relative to the Drupal root directory, downloads start to work. So correcting the description ("...must be a path relative to the Drupal root directory") would suffice, but a proper fix is even better, of course. Changing the status to "fixed".

Thank you!

Re #23 - I had filebrowser-6.x-2.x-dev from 2010-Sep-19 running for a while with a relative path (relative to Drupal's root on the webserver). As reported in September, this worked.

Without changing the configuration, it suddenly stopped working again. The behaviour went back exactly to the status described in #11 (no files can be downloaded because of "file not found" errors).

Next I changed the "system file path to the directory" from relative to absolute (this is the configuration that used to not work). Now files can be downloaded again, at least there are no "file not found errors" anymore at the moment. I absolutely don't understand what is happening here.

Furthermore, when clicking on an audio file, the file is not being downloaded by default, but a audio player opens in the web browser; I believe that the "Filebrowser" module serves a wrong mime type.

Last but not least, the audio file is not being played, but the browser stopps responding (checked with Opera and Chromium under Ubuntu "Maverick"). Windows users could do a right mouse click on the file and choose "Save as", however this doesn't work for Apple users.

Reopening.