General questions
1. When and where can I download the Quickstart packages?
Quickstart packages
The Quickstart packages are activated after receipt of payment and are then available as a download in your account. In the case of PayPal payment, the download can be made directly after the order. In the case of prepayment / bank transfer, the process is delayed accordingly. You will be informed of the status of your order by email..
Individual Quickstart packages (configurator)
The creation of an individual Quickstart package takes place after receipt of payment. In the case of PayPal payment, the creation can be started immediately after the order has been placed. In the case of prepayment / bank transfer, the process is delayed accordingly. You will be informed of the status of your order as well as the activation of the Quickstart package by email. To download the Quickstart package, please log into your account! There you will find the download link.
2. Are there recommendations for the hoster?
100% joomla-compatible web space and database
- FTP access and a database are required
- Auf den Webspace muss mittels Domain zugegriffen werden können
- The web space must be accessible via a domain
- PHP should have strict security settings by default
- The wwwrun problem must not exist (otherwise you have to work with insecure rights)
- Server with firewall to protect against typical attack scenarios
- Web space and databases must be backed up regularly and automatically
3. What is a Quickstart package?
A Quickstart package is a package which, in addition to the CMS, can also contain components, modules, plugins, languages and templates from third parties. Settings and configurations are usually already implied. The installation is similar to a normal Joomla installation.
Using a Quickstart package can save you a lot of time! The individual extensions do not have to be laboriously found and installed.
Questions about the J3 QS installation
4. Recommended tech. requirements for J3 Quickstart packages?
PHP:
PHP 7.3 +
Supported databases:
MySQL (Inno DB support): 5.5.3 +
Supported web servers:
Apache (with mod_mysql, mod_xml, mod_zlib, mod_rewrite): 2.4 +
Nginx: 1.8 +
Microsoft IIS: 7
PHP settings:
- memory_limit: 128M or higher (minimum: 64M)
- max_execution_time: 30
- upload_max_filesize: minimum 32M
- post_max_size: minimum 32M
Important: "post_max_size" must be greater or equal to "upload_max_filesize"!
Depending on the hoster, the PHP settings can be set in php.ini, user.ini or directly in the hoster's account.
5. How do I install a J3 Quickstart package?
The installation of the J3 Quickstart packages is almost exactly the same as a normal J3 installation.You can find detailed instructions here:
J3 INSTALLATION
Questions about the J4 QS installation
6. Recommended tech. requirements for J4 Quickstart packages?
PHP:
7.4 (at least PHP 7.2.5)
Supported databases:
MySQL (Inno DB support): 5.6+
Supported webservers:
Apache (with mod_mysql, mod_xml, mod_zlib, mod_rewrite): 2.4+
Nginx: 1.10+
Microsoft IIS: 8
PHP settings:
- memory_limit: 128M or higher (Minimum: 64M)
- max_execution_time: 30
- upload_max_filesize: minimum 32M
- post_max_size: minimum 32M
Important: "post_max_size" must be greater or equal to "upload_max_filesize"!
Depending on the hoster, the PHP settings can be set in php.ini, user.ini or directly in the hoster's account.
7. How do I install a J4 Quickstart package?
The installation of the J3 Quickstart packages is almost exactly the same as a normal J3 installation.You can find detailed instructions here:
J4 INSTALLATION
Technical questions
8. How do I unzip a Quickstart package directly on a web server?
The conventional method of unpacking a Quickstart package on the computer and then uploading all files and directories individually is very time-consuming and error-prone. After all, several thousand files have to be transferred.It is faster if you first load the Quickstart package onto the server and then unpack it there. There are different methods for unpacking:
- unzip.php (own script)
- kickstart.php
You can find detailed instructions for the different methods here:
Unpacking ZIP
9. What is the additional password protection (Apache Server)?
Password protection for a website can be useful if a website or directory should only be available to certain users. You can also hide the website from search engine bots, for example if the website is still in the development phase. At Joomla, this password protection is also recommended as additional protection for the administrator directory (backend). This increases the security against hack attacks.
As soon as the password protection has been set up, the Apache server requests the additional access data (user name and password) within a small window. If these are entered correctly, the directory is released. In the case of backend protection, the login mask for the backend is displayed.
The following instructions explain how you can set up this protection very easily:
Password protection
