Packages Stuck on “Loading Packages…”

On some older LEAP installs, the package listing page may occasionally get stuck showing:


Loading Packages…


This happens when the VueJS package listing app encounters invalid data and cannot finish loading.


The good news is this is usually very quick to fix.


Step 1: Check the Browser Console

First, open the affected Packages page and inspect the browser console for errors.

Chrome / Edge

  • Right click → Inspect
  • Open the Console tab

Safari

  • Develop → Show JavaScript Console

The console error will normally point to one of the two issues below.


Issue 1: Package Segment Slug Contains Hyphens

Older installs can fail to load the generated JSON file if the Package Segment category slug contains hyphens (- ).


Example Problem Slug

reserved-seat

Correct Slug

reservedseat


How to Fix

  1. Go to Categories
  2. Open the relevant Package Segment category
  3. Remove any hyphens from the slug
  4. Save the category
  5. Refresh the Packages page

Once saved, the JSON endpoint will regenerate correctly and the listing should load again.


Issue 2: Missing Yearly Price

Another common cause is a package missing its Yearly Price value.

Older VueJS templates attempt to format the yearly price and can fail if the field is empty.

How to Fix

  1. Go to Entries → Packages
  2. Review package entries
  3. Look for a package missing the Yearly Price field
  4. Enter a value and save the entry

Once all packages contain a yearly price, the listing page should load normally again.


Why This Happens

These issues only affect some older LEAP installs.

Newer platform versions include protections that prevent:

  • Invalid slugs breaking JSON loading
  • Empty pricing fields crashing the listing app

Summary

If packages are stuck loading:

  1. Check the browser console
  2. Remove hyphens from Package Segment slugs
  3. Ensure all packages have a Yearly Price entered

In most cases, the issue is resolved immediately after saving the corrected content.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us