LinkStack icon indicating copy to clipboard operation
LinkStack copied to clipboard

Theme management page doesn't load and raises ErrorException

Open A-Printer opened this issue 8 months ago • 4 comments

LinkStack version

4.8.4

Description

On a brand new local install, when I visit the Themes page (https://linkstack-url/studio/theme) the bottom of the page for the Theme management fails to load and spins forever.

Image

In the Safari Console, I have this:

Image

and if I visit https://linkstack-url/theme-updater I get this:

Image

ErrorException: Undefined variable $hasSource

By the way, the https://linkstack.org/themes.php URL is a 404, the current URL is https://linkstack.org/themes/

Details about your system

MAMP PRO 6.9 on macOS 15.5, with Apache and PHP 8.2.13

How to reproduce

Install the project and once in the Dashboard, visit the Themes page.

Possible Solution

No response

Additional Context

I don't see anything in the Apache and PHP logs.

A-Printer avatar May 28 '25 13:05 A-Printer

Can you try a other browser ? :-( Unfortunately, I cannot reproduce this on my own instance

lastsamurai26 avatar May 28 '25 14:05 lastsamurai26

I see the exact same issue with the Chrome, Firefox and Vivaldi browsers, all on the latest version. I also tried to disable any content blockers.

What else can I do to help track down the issue?

A-Printer avatar May 30 '25 08:05 A-Printer

Just to be clear, the issue happens when no additional themes are installed, just the stock ones. If I add more themes that I downloaded from the official website, then the UI works as intended and presents a list of installed themes along with the version information and update status.

A-Printer avatar Jun 04 '25 12:06 A-Printer

@A-Printer thank you for the detailed description.

I can confirm that the error "Undefined variable $hasSource" is a bug and should be handled by the system. However, the way you describe to reproduce the error should never cause this error.

This error occurs in a catch that is supposed to handle incorrectly configured custom themes. This should never happen with the default themes.

This might be caused by incorrect file permissions or missing files. Make sure your themes contain the readme.md file and PHP can read these files properly.

JulianPrieber avatar Jun 04 '25 13:06 JulianPrieber