Manuals

Installation and usage for every script here. Requirements first, then the steps, then what to do when a step does not work.

The best manual ships inside the script. Every file here carries its own documentation in its header — what it does, what changed in each version, and how to install it. That copy always matches the code you actually have, which a web page cannot promise. Open the file in a text editor and read the top.

By script

  • Rilato Redirect Manager — manual being written; the documentation in the file header is complete in the meantime
  • Rilato Short Link Maker — manual being written; the documentation in the file header is complete in the meantime
  • Rilato Autoresponder — manual being written; the documentation in the file header is complete in the meantime
  • Rilato Affiliate Manager — manual being written; the documentation in the file header is complete in the meantime
  • Rilato Split Tester — manual being written; the documentation in the file header is complete in the meantime
  • Rilato Page Editor — manual being written; the documentation in the file header is complete in the meantime
  • Rilato Shopping Cart — manual being written; the documentation in the file header is complete in the meantime (script not released yet)
  • Rilato Host Manager — manual being written; the documentation in the file header is complete in the meantime (script not released yet)

Things common to all of them

PHP version

Everything here targets PHP 8.1 or newer, and is developed against 8.4. They use typed properties, match, and named arguments in places, so PHP 7 will not run them.

Databases on Linux

MariaDB database names are case sensitive on Linux and not on Windows. A script developed on WAMP and moved to a live server fails here more often than anywhere else. Type the name into the config block exactly as you created it.

Where to put config secrets

Each script has a config block at the top of the file, or a separate config file above the web root. Whichever it uses, that file should never be readable over HTTP. The included .htaccess rules take care of this on Apache; on Nginx you will need the equivalent location block.

Running on WAMP first

Every one of these runs locally. Set it up on WAMP, break it there, and only then put it on the live host. It is much easier to read an error message on a machine you control.

Something missing or wrong in a manual? Tell us and we will fix it.