View Issue Details

This issue affects 1 person(s).
 0
IDProjectCategoryView StatusLast Update
20630Bug reportsTheme editorpublic2026-08-04 15:33
ReporterFreda Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status ready for code reviewResolutionopen 
Product Version7.0.x 
Summary20630: Renaming a parent custom theme breaks child theme inheritance and leaves stale parent references
Description

When a custom theme that serves as the parent of another custom theme is renamed, any child themes that extend it continue to reference the original parent theme internally, even though the Theme Editor overview displays the parent's new name.

As a result, the child theme can no longer resolve inherited assets and becomes unusable in the Theme Editor. Attempting to edit, duplicate, extend, or reinstall the child theme results in errors indicating that inherited files or the parent theme cannot be found, even though the parent theme still exists under its new name.

Steps To Reproduce

Steps to reproduce

  1. Create a custom theme (ParentTheme) extending fruity_twentythree.
  2. Create a second custom theme (ChildTheme) extending ParentTheme.
  3. Rename ParentTheme using the Theme Editor.
  4. Attempt to edit, duplicate, extend, or reinstall ChildTheme.

Expected result

Renaming a parent theme should either:

update the parent (extends) references of all dependent child themes automatically, or
prevent renaming while dependent themes exist, or
present a clear validation message indicating that renaming the parent theme will invalidate dependent themes.

Actual result

The child theme cannot resolve its parent and errors such as the following are displayed:

Theme 'ChildTheme' was not found, can't find file: ./css/variations/theme_apple.css

TagsNo tags attached.
Attached Files
Bug heat0
Complete LimeSurvey version number (& build).
I will donate to the project if issue is resolvedNo
Story point estimate0
Browser.
Database type & version.
Server OS (if known)
Webserver software & version (if known)
PHP Version.

Users monitoring this issue

There are no users monitoring this issue.

Activities

Issue History

Date Modified Username Field Change
2026-08-04 14:54 Freda New Issue
2026-08-04 14:54 Freda File Added: Screenshot 2026-08-04 at 12.11.32.png
2026-08-04 15:16 tibor.pacalat Assigned To => DenisChenu
2026-08-04 15:16 tibor.pacalat Status new => assigned
2026-08-04 15:32 c_schmitz Assigned To DenisChenu => c_schmitz
2026-08-04 15:33 c_schmitz Status assigned => ready for code review