FAQ

What are the requirements?

PHP 8.4+, MySQL 8.0+ (or MariaDB 10.6+), a web server with URL rewriting, and the document root pointing to /public.

Do I need to run composer install?

No. The installer package already includes vendor dependencies. If you downloaded the source package, run composer install --no-dev.

There is no system crontab. What should I do?

Add a URL cron job in your hosting panel hitting /cron/{CRON_TOKEN} every 1–5 minutes. It drives scheduled publishing and the queue.

Can one installation run multiple websites?

Yes. WinnaCMS supports multi-site: add a site and bind a domain in Site Management; themes, settings and content are isolated per site.

How do licensing and updates work?

Production use requires a commercial license bound to your domain. Updates use a signed channel with version history, security patches and rollback. Request a trial at sales@winna-group.com.

Can I remove the footer attribution link?

No. The “Powered by WinnaCMS” link must remain visible. Removing, modifying or hiding it is reported to the license service by the copyright guard.

Which languages are supported?

Simplified Chinese and English are built in. Additional languages can be enabled in Language Management; menus, content and site names are maintained per language.

What is reported after installation?

Only the domain, CMS/PHP/database versions, server environment, admin email and install time, used for licensing follow-up and update services. Passwords, keys and site content are never sent. Set INSTALL_REPORT_ENABLED=false in .env to opt out.

What should I do before upgrading?

Back up the database and uploads first: click “Back up database now” on the Update page and back up public/media and public/uploads yourself. Core upgrades back up the database automatically, but database migrations from module/theme upgrades are not rolled back automatically. You cannot submit an upgrade without ticking “I have backed up”.