I keep getting a 403 error on the pages I assign with Filebrowser. This is weird because I've given all the proper permissions in the Filebrowser module and the ftp side.
Anyone else have this problem?

CommentFileSizeAuthor
#2 filebrowser.jpg70.81 KBjudaz

Comments

blackbrd’s picture

blackbrd commented

Same problem here, all permissions are correct afaik. The admin side of this module sees all files in the assigned directory and displays the correct information (number of files and total kb).

judaz’s picture

judaz commented
StatusFileSize
new filebrowser.jpg70.81 KB

Could you people that actually got this module to work in that way that it actually shows up on/in your node
take a screenshot, of the filebrowser path settings page and post here ?

This is how mine looks, and i cant get it to work.. well it doesnt show up anywhere,
and YES, i have given permission to all roles to view this.

Susurrus’s picture

Susurrus commented
Status: Active » Postponed (maintainer needs more info)

This module doesn't create nodes! You can just specify any path you want that isn't already taken and Filebrowser will link that to the directory.

learninggone or blackbrd, can I get more details of the paths and locations you provided in the configuration page?

Susurrus’s picture

Susurrus commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

I recommend using the 6.x-2.x branch of Filebrowser. It switched to using nodes, which seems to be how people think this module works. You need to use the path module to provide the aliasing instead of Filebrowser, but it's much more flexible overall.

I'm closing this issue as an explanation is provided in #3. You need to provide an UNUSED path that is not 'node/*'.