Home
zeroShop
Support

Ticket Assistance

Get fast, reliable help for any issue related to your products. Our support team guides you with clear answers and efficient solutions.

Log in to your account to access ticket assistance

FAQ

Frequently asked questions

Everything you need to know about zeroShop. Can't find the answer here? Contact our support team.

The full documentation is included in the zeroShop application — available to all users after activation.

Your hosting must have: PHP 8.2 or newer, and the following PHP extensions: mysqli, cURL, GD, mbstring, intl, JSON, OpenSSL, zip. The mod_rewrite Apache module must be enabled.

Installation runs in 3 screens and takes about 10 minutes. Unzip the package to your web root, then access https://your-domain.com/zeroshop/installation/ in your browser.
- Step 1: Verifies your Purchase Code (Order ID).
- Step 2: Configures your database and administrator account.
- Step 3: Confirms success.

Yes. The installer does not create the database — it only imports the tables. Create it in cPanel (MySQL Databases) or phpMyAdmin before running the installer. Use collation utf8mb4_unicode_ci. Then create a database user and add the user to the database with ALL privileges.

The zeroshop/backups/ directory must be set to 777. The installer checks three writable paths:
- zeroshop/installation/,
- zeroshop/writable/,
- zeroshop/app/Config/Database.php.
If any of these are not writable, the installation will be blocked.

After installation do the following (not mandatory, but strongly recommended):
- Delete the installation folder,
- Rename the admin,
- Rename zeroshop application folders to unique names (Admin > Configuration > Rename folders),
- Remove the default admin@admin.com account,
- Enable htaccess protection on the admin directory (Admin > Configuration > Back-office protection).

Yes. zeroShop works on both Apache and Nginx.
A sample Nginx configuration file is included in the documentation to set up URL rewriting, security headers, and static file caching.

- CSRF protection,
- HTTPS enforcement,
- honeypot anti-bot + rate limiting,
- systematic output escaping (esc(), purify_html()),
- granular permissions per page/action,
- filtered uploads,
- .htaccess blocking access to app/, system/, writable/,
- and HTTP security headers (X-Content-Type-Options, X-Frame-Options).

Still have questions?

Can't find the answer you're looking for? Our support team is here to help.

Get in touch and we'll respond as quickly as possible.