jDownloads Support Forum

Older Versions => jDownloads 3.2 (Support ended) => Bugs => Topic started by: fm on 05.02.2015 15:42:36

Title: [PATCH] wrong path used for flowplayer
Post by: fm on 05.02.2015 15:42:36
Hi there,

jdownloads: 3.2.24 beta
Joomla!: 3.3.6

I had the same problem as described here:
Quote from: whitemike on 06.06.2014 09:02:38
Hi
is there a possibility to change to path to the download file when using the media player

we have the download-files outside the normal url hierarchy and the module is always telling me file not found and showing url hierarchy path

The reason (for me) was that the upload directory needed to be the full path starting from the webserver's filesystem root plus the folder for the downloads:
/mnt/..../userfolder/joomla/jdownloads/downloads

The plugin inserted a path in flowplayer that was created by using basename($jlistConfigM['files.uploaddir']). In my case this was meant to fail, since the stream path started with downloads instead of joomla/jdownloads/downloads.

I fixed it by adding two new variables to the config, namely 'files.uploaddir_base' and 'files.uploaddir_dir', where the former is the path starting from the filesystem root down to the webserver root and the later is the relative path to the downloads.
Both variables will be joined together and written to 'files.uploaddir' after hitting save in the configuration. Therefore, everything else will remain unchanged.
But I also modified the insertion of flowplayer so that it is now using 'files.uploaddir_dir'.

I added the (hopefully) complete patch below.
It also adds the required variables to the database and adds the description.


For those who don't know how to use this patch and still want it:

(on Linux...)
patch -p1 < file_path.patch
Florian

[gelöscht durch Administrator]
Title: Re: [PATCH] wrong path used for flowplayer
Post by: Arno on 14.02.2015 01:38:40
Hi Florian,
why have you posted this as bug?
Title: Re: [PATCH] wrong path used for flowplayer
Post by: fm on 14.02.2015 12:19:30
Hi,

I posted it here since the original problem actually was a bug and there is no section it would, imho, fit in better ;)

Florian