Skip to main content
Start with the exact exception and failing request. Avoid replacing core Paymenter files to work around a theme or extension packaging problem.

​
First checks

Then inspect the latest Laravel log entries:
Confirm public/lucentui/manifest.json exists at the Paymenter root. Republish the prebuilt bundle from themes/lucentui/public/lucentui, clear caches, and hard-refresh.
Upload LucentUIEditor-3.0.0-upload.zip, not the theme archive or a combined bundle. The Editor ZIP must contain LucentUIEditor.php directly at its root.
Upload and installation are separate steps. Return to Ready to Install / Upload, click Install beside LucentUI Editor, enable it on the edit page, and save.
This normally indicates mixed files from different releases or a disabled/outdated Editor. Replace both theme and Editor from the same release, ensure the Editor is enabled, and clear compiled views. Do not add the helper to Paymenter core.
Republish the complete bundled public directory. Check the browser Network panel to confirm filenames match public/lucentui/manifest.json, then hard-refresh.
Republish the current public/lucentui assets and hard-refresh the browser. The progress arc uses the active semantic primary color in both light and dark mode; seeing only the neutral track usually means an older compiled stylesheet is cached.
Update the theme and republish its bundled assets. In the current release, the eye button reveals the value without navigation, while the rest of the card remains a link to Credits. Test the active Cards, Strip, or Minimal dashboard variant after clearing cached views.
Confirm lucentui is Paymenter’s active theme and that you selected Save Changes. Presets only change the form until saved. Clear application caches and test outside the private preview.
Verify Paymenter’s public storage link, file permissions, and that opacity is above zero. For external URLs, test the direct image in a signed-out browser.
Confirm the locale is enabled in Paymenter’s Allowed Languages and its translated value is non-empty. Reload the Editor after changing the allowed language list.
Replace an ambiguous global numeric mapping with option:{parent ID}, checkout:{field}, or plan scope. Save, clear caches, and test every product type that reused the ID.
Reproduce the action with Paymenter’s default theme. If both fail, inspect the extension’s request and Laravel log. If only LucentUI fails, capture the console and failed network request and report the extension/version pair.
Remove the most recent snippet, especially duplicate listeners, intervals, and DOM observers that survive Livewire navigation. Restore a known-good Editor export if the form is no longer usable.

​
Collect a useful support report

Include:
  • Paymenter, PHP, LucentUI, and LucentUI Editor versions.
  • The failing URL and whether it affects guests, clients, or administrators.
  • Light/dark and Lucent/Flat mode combination.
  • Exact exception, relevant Laravel log lines, console errors, and failed request status.
  • Installed extension name and version when the problem occurs in an integration.
  • Whether the same action works with Paymenter’s default theme.
Remove tokens, cookies, passwords, customer data, and private infrastructure addresses before posting logs or screenshots publicly.
Last modified on September 10, 2026