Hey Stephen,

The team has just released a patch version of ThemeBuilder that resolves the issue we discussed. You can reload your project and re-use the "Export All" option to generate an SCSS theme with the corrected references. Please don't hesitate to contact me if you need any further assistance!

Regards,
Nick Iliev
Progress Telerik

Hello Stephen,

It seems that the ticket closes automatically after 7 days of inactivity, even though my colleague Nick has tried to find a workaround for this problem. I will take the initiative to reopen it manually each time this occurs until the problem is resolved.

Just as a side note, the team has made progress and opened a PR to resolve the Sass compilation issue. Please note that it may take some time for the fix to be fully tested and released. We will keep you updated with any progress we have on this.

Regards,
Petar
Progress Telerik

Hello Stephen,

I've marked this ticket as pending and set the need to add an additional answer so that it won't be closed automatically. Once we have the fix published live I will immediately update the thread. Currently, I can provide a fixed date, but we expect the patch to be released in the weeks after the New Year's holidays.

Regards,
Nick Iliev
Progress Telerik

Hi Stephen,

I wanted to inform you that our support system may automatically close a ticket after a period of inactivity. Of course, you can reopen a ticket at any time. Additionally, I am monitoring all discussions, and I will update this thread even if it has been automatically closed, once the fix is ready and goes live.

Regards,
Nick Iliev
Progress Telerik

Hello Stephen,

While I can provide a specific date the team works with higher priority on resolving the issue. As we spoke, we uncovered an additional issue related to the same scenario while using the latest patch version of TB from the 12th of December (yesterday). The issue is publicly available from the following GitHub thread, which you can use as a reference and for tracking purposes:

https://github.com/telerik/themebuilder/issues/134 (threat also contains a temporary workaround for recently generated themes)

Once we have a stable fix I will immediately update this ticket and the linked thread.

Regards,
Nick Iliev
Progress Telerik

Hello Stephen,

Thank you for providing the demo; it was incredibly helpful in reproducing and identifying the issue!

Our investigation confirmed that there is indeed a legitimate bug in ThemeBuilder. The SCSS files generated do not properly reference some internal Kendo theme files. As a result, the k-color mixin is not successfully loaded when using SASS; however, this issue does not occur when using precompiled CSS.

We have identified this as a high-priority bug, and our team is actively working on a fix through a patch version. Once the fix is released, I will update this ticket, allowing you to re-export the new ThemeBuilder theme.

Meanwhile, as a temporary workaround, you can manually patch the generated theme through the following approach:

- Open the following line in <your-theme>/dist/scss/_overrides.scss file

https://github.com/TheCodingWaffle/kendo-them-builder-requested-demo/blob/main/mpp-v18-theme-builder/dist/scss/_overrides.scss#L3 

- Below the third line (after the tokens import), add the following line:

@use '@progress/kendo-theme-bootstrap/scss/all.scss' as *;

After the modification, the file should look like the one below.

Then re-run your Angular application, and you should see the expected results as they are styled in ThemeBuilder.

Regards,
Nick Iliev
Progress Telerik

Hello Stephen,

Based on the screenshot, it looks like the k-color mixin function is not present in the imported theme, which might be related to using the old version of the theme in the Angular project (where the k-color mixin is not yet present) or having a misconfiguration during the installation of the new theme.

Could you please share your ThemeBuilder project (share it with themebuilder@progress.com while using the Share option within the ThemeBuilder app) alongside an Angular demo reproducing the issue you are observing? Providing the Angular demo that reproduces your use case and the observed issue will allow us to investigate further and suggest a tailored solution.

Regards,
Nick Iliev
Progress Telerik