Enthusiast Bridge

When to Use the Enthusiast Bridge

The Enthusiast Bridge is for fanlisting owners who have already imported their data into Luster but have not yet updated their fanlisting page code. It lets your old Enthusiast show_*.php includes keep working by routing them through Luster instead.

Use the bridge when:

• You have imported your Enthusiast data into Luster and want your existing pages to keep working immediately.
• You plan to migrate your pages to Luster’s embed system gradually, one fanlisting at a time, rather than all at once.
• You want a zero-downtime transition — visitors see working forms the entire time.

Setup

1. Download the Bridge

   In the Luster admin panel, go to Admin → Collective → Migration & Bridges and click Enthusiast Bridge. This downloads a ZIP file.

2. Unzip into Your Enthusiast Folder

   The ZIP contains luster-bridge.php and all of the wrapper files (show_join.php, show_members.php, etc.). Extract them into your Enthusiast installation folder, replacing the original show_*.php files.

3. Set the Luster Path

   Open luster-bridge.php and set the LUSTER_PATH constant to the absolute server path of your Luster installation. The download pre-fills this for you, but verify it is correct.

   PHP

   define('LUSTER_PATH', '/home/username/public_html/luster');

4. Done

   Your existing fanlisting pages will now render forms through Luster instead of Enthusiast. No other changes are needed.

How It Works

When a visitor loads one of your fanlisting pages, the following happens:

1. Your page loads config.php

   Your existing fanlisting page includes its config.php, which sets a $listing variable. This is either a numeric listing ID or a dbtable string (e.g. "huntrix").

2. The page includes a show_*.php file

   Your page includes a file like show_join.php. Because you replaced the originals with bridge wrappers, it now loads the Luster bridge version instead of the old Enthusiast code.

3. The bridge resolves the listing

   The bridge reads $listing and finds the matching Luster listing. If $listing is numeric, it uses it directly as the listing ID. If it is a string, it looks up the dbtable name in the owned table to find the listing ID.

4. Luster renders the output

   The bridge passes the resolved listing ID to the corresponding Luster embed file (e.g. embed/join.php), which renders the form and outputs the HTML.

Supported Wrappers

The bridge includes replacement wrappers for all Enthusiast show_*.php files. Each wrapper routes to the equivalent Luster embed.

Manual Override

If the bridge cannot auto-detect your listing from the $listing variable, or if you want to skip auto-detection entirely, you can set the Luster listing ID manually before the include.

$luster_listing_id = 5;
include '/path/to/enthusiast/show_join.php';

When $luster_listing_id (or $luster_fanlisting_id) is set before the include, the bridge uses it directly and skips the $listing lookup.

Styling

The bridge renders forms using Luster’s HTML output, which means the output uses Luster’s CSS classes (fl-form, fl-field, fl-input, etc.) instead of Enthusiast’s old classes (show_join_name_field, etc.).

To style the output, you have two options:

• Add Luster’s public stylesheet to your fanlisting pages. The stylesheet is at public/assets/css/default/style.css in your Luster installation. This gives you sensible defaults immediately.
• Write your own CSS targeting the fl-* classes. See the CSS Class Migration Reference for the full mapping of old Enthusiast class names to Luster equivalents.

Troubleshooting