Loading...
 
Skip to main content

On Windows, generating custom theme files with npm produces generated output in two places

Status
Closed
Subject
On Windows, generating custom theme files with npm produces generated output in two places
Version
27.x
master
Category
  • Usability
Feature
New feature (not an enhancement to a current one)
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Theme: Look & feel, Styles, CSS, Theme Control Center
Resolution status
New
Submitted by
Gary Cunningham-Lee
Volunteered to solve
Bruno Kambere
Lastmod by
Gary Cunningham-Lee
Rating
(0)
Description

In Windows 11, when running npm to produce content from _custom/shared/themes/MyTheme, two paths are created in public/generated/shared. The directory /public/generated/shared contains two subdirectories, /laragon and /shared. laragon is directly under C: directory here, and contains the WAMP stack. The directory path in laragon reflects the path to the Tiki instance I'm testing with, and so also contains a /custom/shared/themes directory.

The problem seems to be that this longer path to the themes contains the image directories (one having images), and the other set of /shared/themes contains the CSS files, so the images can't be found, as specified by the CSS.

Please see this conversation: https://matrix.to/#/!SLEgqpTNTlGYAhzNvK:gitter.im/$h6R2W_KSy-wxq7EDullkNWSotkH8HEJRKdzhW-ABPKI?via=gitter.im&via=matrix.org&via=sans-nuage.frQuestion, which includes screenshots of the directory structure.

A workaround is to manually copy the missing theme subdirectories from _custom/shared/themes to public/generated/custom/shared/themes, but it would be better if this worked automatically.

Solution
I don't know what was done, but this issue seems to be fixed now.
Workaround
Importance
7
Easy to solve?
3
Priority
21
Demonstrate Bug on Tiki 19+
Demonstrate Bug (older Tiki versions)
Ticket ID
8625
Created
Friday 26 April, 2024 09:34:54 UTC
by Gary Cunningham-Lee
LastModif
Sunday 07 December, 2025 11:23:13 UTC


Show PHP error messages