The eLumine Exit: Replacing a Discontinued LearnDash Theme with a Custom Theme You Own

Earlier this year, LearnDash quietly retired eLumine — for years the go-to WordPress theme for LearnDash course sites. If you run a course site on it, you have probably already noticed the signs: the theme stopped evolving, the Unyson framework it depends on was abandoned long ago, and LearnDash now points eLumine users toward a generic page-builder theme instead.

This month we walked a client through the exit. Their entire training academy moved from eLumine to a lean custom theme they now own outright — in one working day, with zero downtime and nothing broken for their learners. Here is how an eLumine exit actually works, and why “just switch themes” is the one piece of advice you should not follow.

The situation: a live academy on a dead theme

Our client is a nonprofit education foundation that runs an online teacher-training academy — LearnDash courses, WooCommerce checkout for program registration, Gravity Forms, and an active cohort of teachers logging in every day. The site ran on eLumine plus a child theme, with the Unyson framework underneath.

Three problems were stacking up:

• The subscription treadmill. An annual theme fee kept billing for a product that was no longer meaningfully updated.
• An abandoned foundation. Unyson — the framework eLumine is built on — has been discontinued for years. Every WordPress and PHP upgrade became a small gamble.
• A layout that was never really theirs. Like many eLumine sites, the homepage had grown out of the theme vendor’s demo content. The organization wanted a site it fully owned, right down to the layout.

The client cancelled the subscription. Our job was to make sure that decision cost them nothing.

Step 1: find out what your theme is secretly doing

This is the step that generic “best eLumine alternatives” articles skip entirely — and it is where theme swaps go wrong.

A course site that has been running for years almost never keeps its business logic in a plugin where it belongs. It accumulates in the child theme. Our audit of this site’s child theme found four pieces of real functionality hiding in functions.php and the template files:

• Auto-completion: lessons and topics were marked complete when a teacher viewed them — a deliberate simplification of the LearnDash flow for this audience.
• Cohort gating: teachers could only access the weeks of material the program had unlocked so far; everything else redirected to a friendly “not yet” page.
• A custom registration shortcode that the login and signup pages depended on.
• Seven page templates — login, contact, certificate printing, cohort-week pages — each with logic the academy relied on every session.

Switch this site to an off-the-shelf theme and every one of those quietly dies. No error message — the cohort gate simply stops gating, and every enrolled teacher can see the whole program on day one. If you take nothing else from this case study: audit your child theme before you touch anything.

Step 2: back up like you mean it

Before changing a single file we took three separate backups: a full account snapshot (4.1 GB), a database export, and an archive of the old eLumine parent and child themes with their settings. Total cost: a few minutes. It is the difference between “we can undo this in an hour” and “we hope this works.” (This is a standing rule on every project we take on — backups before changes, always.)

Step 3: rebuild as a small custom theme — with continuity tricks

We built a replacement theme from scratch: a few thousand lines, no framework, no builder dependency for the core pages, no license key. The interesting part is not the code — it is the continuity details that made the swap invisible to users:

• Same template filenames. WordPress stores each page’s template choice by filename. By giving our new templates the exact names of the old ones, every page kept its template assignment automatically — no re-editing dozens of pages.
• Same sidebar IDs. Widget areas were registered under the old theme’s identifiers, so years of configured widgets survived the switch untouched.
• Same brand tokens. The organization’s blue, orange, and amber palette and logo carried over exactly. Learners saw a cleaner site, not a different one.
• Ported logic, documented. The auto-completion, cohort gating, and registration shortcode were rewritten into the new theme — and the settings the staff change every session now live in one documented place instead of being scattered.

We also rebuilt the homepage natively in the theme rather than keeping the old demo-derived builder layout — same copy, same colors, new structure the client owns. As a bonus, the audit caught two registration buttons that had been pointing nowhere; they now link to the actual checkout products.

What changed for the client

• Recurring theme cost: gone. The cancelled subscription now costs them nothing in lost functionality.
• One less abandoned dependency. The Unyson framework was deleted from the site entirely.
• Full ownership. The theme is theirs — no license, no renewal, no vendor risk. When WordPress 8 arrives, updating is our (small) problem, not a vendor lottery.
• Nothing broke. Same look, same logins, same widgets, same URLs. The migration was live the same day it started.

If your site is still on eLumine

You have three realistic options. You can stay put and accept slowly compounding risk on an abandoned framework. You can swap to a generic theme and rebuild your layouts in a page builder — fine for a simple site, dangerous for one with years of accumulated child-theme logic. Or you can treat the retirement as the push to finally own your theme: audit what the site really does, port it into a small custom theme, and step off the subscription treadmill for good.

We think the third option is almost always the right one for a working course site — it is the same philosophy behind why we replaced a scheduling subscription with a small system our client owns: recurring fees for software you depend on are a fine trade only while the vendor holds up their end.

Running a course site on eLumine — or any discontinued theme — and not sure what is buried in your child theme? We now offer this migration as a fixed-price service — see the eLumine Exit ($1,500, all-inclusive) — or book a free consultation and we will tell you exactly what an exit would involve for your site. No pressure, no jargon.