Verified environment
- Modern PHP 8.3-class runtime
- MySQL 8-class database server
- PHP-capable web server
- HTTPS for production use
- A final public hostname or domain
Installation
Install Clistor 3.1 cleanly.
A beginner-friendly production installation path that keeps configuration, database state, license state, and server details specific to the target environment.
1. Prepare the hosting environment
Before you begin
- Prepare a dedicated database and database user.
- Have the intended public Application URL ready.
- Use an administrator password unique to Clistor.
- Keep secrets out of screenshots and public tickets.
Hosting note: PHP modules and web-server configuration vary between hosting providers. If your host uses a control panel, use its PHP/MySQL tools or ask the host to provide an equivalent PHP 8.3/MySQL 8 environment.
2. Use the clean release package
Upload or extract the Clistor 3.1 installable package into the web root or subdirectory where the application will remain.
Clistor_3.1_Installable_V2_Final.zip
Keep the original directory structure intact. Do not copy a live config.php from another installation and do not move an existing installation's runtime license-state file into a new server.
| Path | Purpose |
|---|---|
/index.php | Root compatibility entry point. |
/admin/ | Main Clistor administration application. |
/includes/ | Public styles, JavaScript, images, and supporting resources used by the installed application. |
3. Prepare the database
Create a database reserved for this Clistor installation and a dedicated database user. Keep database access private to the application host or a trusted network whenever possible.
| Installer field | What to enter |
|---|---|
| Database Hostname | The MySQL hostname reachable from the web server. |
| Database Name | The database created for Clistor. |
| Database User | The dedicated MySQL account Clistor will use. |
| Database Password | The password for that MySQL account. |
| Table Prefix | An installation-specific prefix when your setup uses one. |
4. Extract the files into the final site path
Place the files where Clistor will actually run. Installing in the final path avoids unnecessary URL and permission changes later.
Permissions: give the web server write access only where Clistor needs runtime storage, temporary data, or session storage. Do not make the entire application world-writable.
5. Set the Application URL correctly
The Application URL is the base address Clistor uses when it builds links back into the product. Enter the exact public scheme, hostname, and base path.
Domain-root example
https://mail.example.com
Subdirectory example
https://example.com/clistor
- Use https:// for production once TLS is configured.
- Include the subdirectory if Clistor is not installed at the domain root.
- Do not leave localhost, a development hostname, or an old migration path in production.
6. Complete setup and license activation
Enter the requested administrator and license details in the installer. Production activation is intended for the real deployment hostname; localhost or direct IP testing may not be suitable for a production license.
Keep credentials separate: do not reuse the database password as the Clistor administrator password.
7. Verify the first login
After the installer completes, sign in and confirm that the main product surfaces load before doing any production work.
A healthy first login exposes the normal Clistor workspace and navigation.
- Home dashboard loads without errors.
- Contact Lists and Contacts open normally.
- Email Campaigns can be created and edited.
- Built-in Email Templates open and previews work.
- Forms and Statistics load.
- Settings, Help, and the version/status view open correctly.
8. Configure the installation before real use
Application setup
- Review sender and sending-related settings for your environment.
- Configure branding, support, and updates links.
- Create only the user accounts your team needs.
- Review permissions before sharing access.
Operational setup
- Verify HTTPS and database privacy.
- Configure scheduled tasks/cron used by your workflow.
- Back up the database and application files.
- Confirm that installer/setup routes no longer expose the setup UI.
9. Test before a real campaign
Create a small controlled test list, add a test contact, create a campaign, select a built-in template, preview the message, and confirm the workflow behaves as expected.
Go live only after: links, sender details, sending configuration, scheduled tasks, unsubscribe behavior, and reporting surfaces have been reviewed in your own environment.