News:

Dear forum visitors, if the support forum is not available, please try again a few minutes later. Thanks!

Main Menu
Support-Forum

Configuring the root directory for uploading files in jDownloads

Started by ghicar, 02.01.2024 20:59:45

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ghicar

This is a minor irritation on the excellent jDownloads package but thought I would ask anyway.  I see there is a mandatory configuration settings under options in the "Path Settings"  tab  with the label: "Upload directory path". The notes state that this must be the full path on the server.

I have a website with three environments live, test & dev, and I regularly take backups of Live into Test and/or Dev when I want to try something risky before implementing on Live.

This setting means I have to remember to go and edit this path in case I later attempt to upload files.  If you don't make this edit then uploads fail with HTTP 500  "Internal Server Error".

It would be good to have an option to specify this path relative to the JROOT so you don't need to remember to edit the setting when I take a fresh backup to dev/test.

BTW, Using jDownloads 4.0.38 on J!5.0.1 and PHP 8.2. All works fine for me, many thanks.
  •  

Arno

Hi,
In very old versions I had this setting with a relative path.
But at some point I had to change this, but I can't remember the reasons for this at the moment.
I would have to see if this option could be created as an alternative.  :-\
Best Regards / Gruß
Arno
Please make a Donation for jDownloads and/or write a review on the Joomla! Extensions directory!
  •  

ghicar

Had a bit of a look around and made it marginally (arguably) better for my use case of copying live websites into lower environments.  I edited ~administrator/components/com_jdownloads/config.xml to make the "Upload directory path" parameter an optional field. This allowed you to empty the field and save the options. At first I thought this had done the trick but then realised that jdownloads processing of the form puts the correct default value in place when it is empty, so I would still need to edit the options to blank out the field and save whenever I copy the website somewhere else.  I did not think the benefit was worth moving away from the std 4.0.38 version, so I reverted the change I had made.
  •