Add-on Modules

• Overview
• Installing an Add-on
• Uploading a Module
• Selling Add-ons to Your Businesses
• Managing Modules
• How Slotara Stays Safe
• Emergency: Safe Mode
• Troubleshooting

Overview

Add-on modules add new features to Slotara without changing its code, for example invoicing. Manage them at Admin → System → Modules (/admin/modules).

Every change asks for your password. In demo mode nothing can be installed, changed or removed.

{info} Add-ons need an activated license. See License Activation.

Installing an Add-on

1. Open Admin → System → Modules.
2. Under Available add-ons, click Install next to the add-on.
3. For a paid add-on, paste its purchase code. Enter your password and confirm.
4. A progress bar shows each step (download, signature check, files, database). Keep the page open; it takes a few seconds.

The add-on is switched on as soon as it's installed. Its pages appear in the business panel for the businesses that may use it (see Selling Add-ons).

New versions of installed add-ons show an Update to x.y.z button on their row. Use More → Check for updates to check right away (Slotara also checks once a day).

Uploading a Module

Upload module installs a module from a file instead of the store:

Any other file is refused with an explanation.

{warning} Developer mode loads code that hasn't been checked. Use it on a development copy, not your live site.

Selling Add-ons to Your Businesses

Most add-ons can be included per subscription plan, so you can offer them on your higher plans:

1. Admin → Subscription Plans → Edit plan → Modules included: tick the add-ons this plan includes.
2. For one business, Admin → Tenants → Edit → Extra modules grants an add-on its plan doesn't include.

Businesses without the add-on don't see its pages in their panel, and its public pages show "Your plan does not include this feature". Add-ons that aren't sold per plan (marked so by their author, e.g. Invoices) are available to every business.

Managing Modules

Every action is recorded in storage/logs/licentra-modules.log (who, what, when).

From the command line:

php artisan module:list
php artisan module:install slotara-invoices
php artisan module:enable slotara-invoices
php artisan module:disable slotara-invoices
php artisan module:uninstall slotara-invoices            # --delete-data to drop its tables

How Slotara Stays Safe

• Only signed modules install. Store downloads and uploaded packages are checked against the author's digital signature; a module folder copied onto the server is never loaded.

• A broken module only breaks itself. Slotara switches a module off, and shows why on the Modules page, when it:

  • throws an error while starting,
  • causes 3 crashes within 10 minutes,
  • causes 3 errors on Slotara's own pages, or
  • causes 10 errors within 10 minutes on its own pages or background tasks.

  Bookings, the booking page and all other pages keep working.

• Bookings always save. When a module reacts to a new booking and fails, the booking is still saved.

• Modules can't replace Slotara's pages. Each module lives under its own address (e.g. /slotara-invoices/...).

• Updates and installs never overlap. A Slotara update never touches modules or their data, and a module that doesn't support the new Slotara version is switched off instead of breaking the site.

• Before installing, each module lists what it adds (tables, outside services it contacts, scheduled tasks) on its row.

Emergency: Safe Mode

If the site misbehaves after installing a module and you can't reach the admin panel:

# in .env
LICENTRA_MODULES_SAFE=true

then run php artisan config:clear (or delete bootstrap/cache/config.php). No modules load until you remove the line again. Or switch them all off:

php artisan module:disable --all

Troubleshooting