🐛 custom themes are not working

[kobalteule]

Input data (markdown source)

# Acme Corporation
## Introduction

---

Expected Behavior

Custom css being used and rendered

Current behaviour

just plain white background and black font, without any formatting

Steps to reproduce

1. use any slide and add a custom css

Which Operating Systems are you using?

• [ ] Android
• [ ] iPhone/iPad
• [ ] Linux
• [ ] macOS
• [x] Windows

Obsidian Version

1.8.3

Slides Extended Plugin Version

2.1.8

Checks

• [x] I have tried it in the sandbox vault with only this plugin enabled

Possible solution

I am using the demo-vault "custom slideshow" from the discussions. the slides are show, however, when I add my css which was working with advanced slides, it seems as if it is not used. I created a separate folder theme, where I put the css and pointed to this folder in the plugin settings. as my css is being proposed in the default theme field, I guess, it is found.

Any ideas on how to get custom themes running?

[ebullient]

I use them all the time, and all appears to function.

Can you try again w/ the dev console open and let me know what it says? The paths it tries to resolve should be shown

[kobalteule]

Sorry, could have tried that first. However, while it is searching for other resources here: http://localhost:3080/css/slides-extended.css my css file cannot by found at this path: http://localhost:3080/C:/Users/MyUser/Downloads/Custom.Slideshow/Custom%20Slideshow/theme/my.css

which seems wrong to me as a webserver path. However: C:/Users/MyUser/Downloads/Custom.Slideshow/Custom%20Slideshow/theme/my.css is the right path in the filesystem.

in the options I set just "theme" (I also tried with mytheme, in case theme was a reserved word)

[ebullient]

the custom theme setting (and these custom themes) should also be in your vault. Not randomly elsewhere..

[kobalteule]

sure, but it is all in the vault at C:/Users/MyUser/Downloads/Custom.Slideshow/Custom%20Slideshow/

here is the data.json: { "port": "3080", "autoReload": true, "autoStart": true, "exportDirectory": "/export", "enableChalkboard": false, "enableOverview": true, "enableMenu": true, "enablePointer": false, "enableTimeBar": false, "theme": "my.css", "highlightTheme": "zenburn", "transition": "slide", "transitionSpeed": "default", "controls": true, "progress": true, "slideNumber": false, "showGrid": false, "autoComplete": "inPreview", "paneMode": "split", "themeDirectory": "mytheme", "center": true }

this is the structure of my vault:

. ├── Decks │   └── Meat Delivery - John Doe.md ├── export │   └── Meat Delivery - John Doe │   ├── css │   ├── dist │   ├── index.html │   └── plugin ├── mytheme │   ├── my.css │   ├── my-white.css │   └── my-white.scss ├── .obsidian │   ├── appearance.json │   ├── app.json │   ├── community-plugins.json │   ├── core-plugins.json │   ├── core-plugins-migration.json │   ├── graph.json │   ├── plugins │   │   ├── obsidian42-brat │   │   └── slides-extended │   └── workspace.json └── Stacks ├── Company Intro.md ├── Products │   └── Meat Delivery.md └── Representatives └── John Doe.md

[kobalteule]

btw. when I point the browser to http://localhost:3080/mytheme/my.css, the css-code is displayed. but why is the plugin not pointing to this path?

[ebullient]

There is some old magic code here related to composition of css folders. Out of curiosity, what happens if you rename "mytheme" to "css"

[kobalteule]

unfortunatly no difference: http://localhost:3080/C:/Users/MyUser/Downloads/Custom.Slideshow/Custom%20Slideshow/css/my.css

I also removed the space in the directory name.. still the same, 404 error

[kobalteule]

are there any news regarding this bug? How are you using custom themes then?

[ebullient]

I am at a conference and launching a foundation. I'll get there.

In settings, assets/css is the theme directory.

In slides/presentations, I still use css in the path (this is leftover magic + revealjs expectation I haven't had time to unravel):

assets is root in my vault, and has a css directory:

[JamesWiresmith]

I just wanted to add that I've seen the same problem:

• Obsidian: v1.8.10
• Slides Extended: v2.1.13
• OS: Windows 11

It could be unrelated, but I do see built in themes working in the preview although not once I start the presentation