Okay
  Public Ticket #4536037
I can't use my license
Open

Comments

  • Dewey Hulsey started the conversation

    Our website was built and sold to us. Now our plugin is out of date and can't be used to edit existing sliders. We cannot update because it says we no longer have a license.

    We just purchased a license today and have the code.

    Now there is no way to enter it. Manually reinstalling from another source makes me anxious that our existing sliders will be deleted.

    Nowhere in the database or files to enter license. This is unacceptable, please help.

  • Dewey Hulsey replied

    Our license is updated now but we can't edit old sliders, it just spins forever as though it's loading.

    Attached files:  Screenshot 2026-01-21 103134.png

  •  167
    George replied

    Hi Dewey,

    Thanks for the update — if the license is already active but the editor “loads forever” when opening existing projects, it’s almost always caused by cached/optimized assets (plugin scripts, JSON data, REST/AJAX responses), either from a WordPress optimization plugin, a CDN, or even the browser cache.

    Could you please try these steps?

    1.Clear all caches

    • Clear your browser cache (or open the admin in an Incognito/Private window)

    • Purge any WordPress cache/optimization plugin caches (Autoptimize, WP Rocket, LiteSpeed, etc.)

    • Purge your CDN cache (Cloudflare / Bunny / etc.)

    • If your host has server-side caching, purge that too

    2.Temporarily disable optimization/minification

    Temporarily turn off:

    • JS/CSS minify / combine

    • Defer / delay JS

    • “Optimize delivery” / “remove unused CSS”

      Then try opening the same slider again.

    3.Hard refresh + test

    After purging caches, do a hard refresh of the WP admin page, then try editing an old slider.


    If it still keeps spinning, please send us the browser console errors (F12 → Console) and ideally the Network tab log for the request that keeps retrying/failing when you open a slider — that usually points straight to the exact cache/optimization rule causing it.

    Best Regards,
    George | Kreatura Dev Team