| FAQ General |
 |
 |
 |
|
Read also the FAQ Troubleshooting page. Close All | Open All Yes, you can use the monitoring script in combination with cron jobs to get this. The following instructions comes from the jDownloads User: rblackman. Many thanks that he share it with us. "Like many users here I upload files via FTP and have been trying to find a solution for running the scan.php file automatically. So it updates without having to log into the site and go the control panel each time I have a new file. I have found something that works so I'm sharing this here in the hope that it will help others. I am running Joomla on a local server within our LAN for our Intranet. I use a Turnkey installation of Joomla 2.5 but I think it should work for other installations even if you can't get to the server controls to add a traditional cron job. The answer is in another Joomla extension: JPrc Cronjobs.
When you will not, that this message is viewed in a empty category, you can remove it in this way:
The developers from www.joomace.net have created a special search addon for Joomla: AceSearch. You can get it (also for free) for Joomla 1.5.x and Joomla 2.5.x. When you has installed the newest release from AceSearch, you must download here a special extension file for jDownloads and install it with the AceSearch extension installer. Afterwards can you configure the settings (see screenshot) from this special extension to get your best search results from jDownloads.  Note: We can not give support for this addon in the jDownloads forum. Please contact the developer for it. When you will restore a jDownloads backup file, you must observe this:
When you will move your jDownloads download area from Joomla 1.5 to Joomla 2.5, here is a short howto: Old Joomla 1.5.x website
Extremely rarely is viewed by the jDownloads installation at the top this message:  You can try to fix it in this way:
The most hosters has the option: Indexes deactivated as default. But sometimes it is activated so visitors can browse to the download folders and seen the files. Then you can stop it in two ways.
 1. Erstelle eine php.ini mit dem Texteditor. 2. Schreibe folgenden Text in die Datei: upload_max_filesize = 200M
post_max_size = 500M memory_limit = 1G max_execution_time = 10800 max_input_time = 10800 session.gc_maxlifetime = 10800 3. Lade die Datei in beide der folgenden Verzeichnisse hoch: joomlahauptverzeichnis/ joomlahauptverzeichnis/administrator Wenn man nur über das Backend große Dateien hochladen möchte, reicht es aus wenn man die Datei in das Administratorverzeichnis hochlädt. Wenn man das ganze aber auch im Frontend nutzen möchte, muss die Datei in beide Verzeichnisse hochgeladen werden. 4. Anschließend noch ins Backend gehen und unter "jDownloads > Konfiguration > Uploads > Maximale Dateigrösse in KB:" 204800 eintragen. Alle genannten Werte sind lediglich Beispiele. Dieser Tipp wurde eingereicht von mawo. When you has this problem, you must check the configuration from your activated Editor. Here is as example the TinyMCE Editor used.
 Generally can you use all language packages from this download category (for Joomla 1.5) or here for Joomla 2.5.
You can sell download files in many ways.
You can also post your questions about this in the support forum. When you will use Joomfish to translate data from jDownloads, you must do this:
First of all, you must install the AlphaUserPoints component. When you has done this, go to the plugin installer from this component and install this three plugins:
Note: when you has problems to install the plugins as zip file, please unzip it first and use only the .xml file for the installation. Go to the AlphaUserPoint rules manager and configure the jDownloads plugins. See pic as sample:  Go now to the jDownloads configuration tab: Specials. You see in the middle from the site this options for the AlphaUserPoint support in jDownloads: 
Your points: 22 Needed Points: 25
By the way, make sure that you has all download categories access rights set to (minimum): Public view but only registered user can download. You must also use the summary page, when you will use the AlphaUserPoint rules. Important: The above tutorial is for Joomla 1.5 and for Joomla 1.6/1.7. But make sure, that you has installed AlphaUserPoints 1.6.4 stable (or newer) when you will use it in Joomla 1.6/1.7. The most users used a menu link like: Downloads and used the same name for the jDownloads upload root folder. Normally it is not a problem. But when you will use a specially sef/seo component, it is better to change the folder name (as sample to jdownloads). Please check also, whether for your installed sef/seo component a special plugin is required. So exists (as sample) for sh405sef a few different jDownloads plugins. Make also sure, that your installed plugin is also for your installed jDonloads version. What i must mind, when i will use a sef (search engine friendly URLs) option in Joomla? Joomla comes with a few specially options to create search engine friendly URLs (sef). You can activate this in the Global Configuration. When you has activated this option, sometimes you see in the frontend a 404 error message: 'The Page cannot be found' or alternatively a Joomla error message. Please try this to resolve it:
This function monitored the download folder from jDownloads, when it is activated in the jDownloads configuration. Whensoever you go to the jDownloads Control panel, all folders and files are scanned from this function. Is this option deactivated, you can run it manually with a click on: Check downloadarea now. Exactly, the function does this:
Important: When you will add automaticly many files or folders (> 500), it is recommended to add it in more as one step. A sample:
Tip:
When you install jDownloads as default is used this star graphic:  But you can also use this star graphic for your ratings:  When you will change it, you must do this:
Yes, this is possible. You must do this:
PAD is the Portable Application Description, and it helps authors provide product descriptions and specifications to online sources in a standard way, using a standard data format that will allow webmasters and program librarians to automate program listings. PAD saves time for both authors and webmasters. For more, see the PAD FAQ on www.asp-shareware.org. One of the problems, you can run into with Joomla (or other CMS or PHP Scripts) is a thing called "wwwrun" problem. This is caused when your server is running PHP as an Apache module and not as CGI. In bad cases you will not be able to change your Joomla files with an ftp client or upload anything new. In most cases can help the Joomla extension: JoomlaXplorer. Please read this article on www.sigsiu.net when you will looks a little bit deeper into this problem. As many users continue to have difficulties related to file size while uploading files with jDownloads, I decided to try to shed some light on the difference between the upload settings in your jDownloads backend and the global configuration settings of the webserver where your site is hosted. In a nutshell, the settings you make in your jDownloads backend always obey those of the webserver. This means, for example, that you won't be able to set a maximum file size for uploads that is larger than the value for maximum file size in your webservers global settings. Like most other Joomla! components, most jDownloads code was written in PHP. PHP is a server side application, which means that all functions of a PHP script are executed on the server where your web pages are located. This works quite differently from a client side Java applet, which excutes on your machine after it was is downloaded together with the page you requested to view. Hence, you may easily influence the behavior of Java based script, for example by enabling or disabling options in the configuration of your web browser. This isn't at all the case with PHP: As everything runs on the webserver, PHP configuration settings can only be changed there, and only so if you have administrative access to that server. Please note, by the way, that this has nothing to do with your Joomla! backend, nor with your access to the control panel of your hosting account. Administrative access, or root access, to the global configuration settings of a webserver is reserved to the people who own and/or professionally administer it (= in most cases, your webhost). PHP configuration settings are within a file called php.ini, which is located on the webserver. The exact location of this file is displayed under System >> System Info >> PHP Info >> Configuration File php.ini path. As I said earlier, you can only lay your hands upon this file if you have administrative access. In practice, this means that it's entirely out of reach for you. You may, however, view the current settings made within php.ini. If you have Joomla!, a quick way to do this is to look them up in your backend under System >> System Info >> PHP Info. Alternatively, you may also create a simple text file, call it info.php (or the likes), and place the following lines into it: <?php phpinfo(); ?> Then, upload this file to your server and point your browser to it. The result is only slightly different from the info displayed in your Joomla! backend. In both cases, you'll be able to examine the specific settings made by the system administrator in regard to PHP.... .... which brings us back to jDownloads: No matter which upload setting you chose in your jDownloads configuration panel, all will be executed by PHP and hence ultimately obey the global settings PHP settings made by the system administrator. Many of such general settings exist, and they often influence one another as well. Before I go into detail on the particular parameters related to file upload, another important note: The jDownloads configuration manager provides you with an option to determine user rights in regard to the size and the amount of files they may upload. Please note that these settings exclusively regard the jDownloads frontend-upload, and their only purpose is to allow you to place limitations on whatever is allowed in your servers php.ini. Hence, you won't be able to expect a setting for a a very large file size you make in your jDownloads backend to have an effect unless the settings inside php.ini allow for it. If the settings within your servers php.ini determine a maximum file size for uploads which is smaller than the one you entered in your jDownloads backend, the setting in php.ini is the one that counts. Now, the php-ini settings regarding upload:
Their relation should always be as such: memory_limit >> post_max_size > upload_max_filesize If upload_max_filesize was set to 2 MB, a batch upload of 4MB zip file for example would simply be bound to fail. These 3 settings, however, are not the only ones that determine a smooth functioning of your file uploads. Another important setting, well capable of ruining your uploads even if correct values were set for upload_max_files, post_max_size and memory_limit, is this:
Add a slow internet connection to this, and the end is in sight rather quickly. jDownloads will go throught the tasks until it hits the time limit set in php.ini and then stops. This is why sometimes only a part of zip file is processed during a batch upload with jDownloads: The time limit has been reached and the parser has halted the execution of script. We are currently looking for ways to avoid such undesired interruptions, but the matter isn't a trivial one.
It's worth noting here that host related issues of that sort would be of a rather general nature, and would cause problems not with one particular PHP script but many others as well. I hope this text helped to add some clarity regardiing the the processes involved in the upload functionality of jDownloads. Unfortunately, many factors are at play, and not all -hardly any, infact- lie within the reach or the responsibility of jDownloads. When you run into problems, keep in mind that you can also upload your files via FTP. With the jDownloads auto monitoring function, you can add easy the new uploaded folders or files in the jDownloads database tables. Of course there are yet other factors out there that may create problems, such as wwwrun, but we'll talk about these another time. Source by arrangement with: www.joomgallery.net When you will not use the summary page for your downloads, you must do this:
Please read informations here!
Since jDownloads 1.8.x is it possible to edit a download also in the frontend. But you must set the configuration correct:
 Note: It is not possible to change all data fields in the frontend. But for the most situations is it enough. With jDownload can you set only the access rights to a category:
 Note: It is not possible to set user permissions directly to a single download You can see a sample in the layouts administration
When you activate the htaccess protection, only the jDownload PHP script can send the download file. All direct accesses to the download folder, view a 404 Forbidden message. Important:
When you will update to a version 1.7.x or older:
Important: It is not possible to update directly from a very old version to the last release. When you has as example installed the jDownloads v1.4, you must update it step by step. This meant, that you must update v1.4 to v1.5, then v1.5 to v1.6 and so on.
When you will remove the jDownloads component complete, here is a how-to:
System Requirements
Installing jDownloads is pretty straight forward:
After installing continue with the initial configuration:
|
