question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Themes not working in Lektor 3.1.1

See original GitHub issue

lektor --version Lektor, version 3.1.1

Documentation implies Lektor now has theme support, but installing a new theme and setting it with the themes variable in .lektorproject results in the following:

Some of the files from the new theme get included in the new build.
But, the css file from the default quickstart project seems to stick around In the end it looks like the themes support is simply broken and that it fails silently.

The documentation should either be updated to reflect this reality, or the themes feature should be completed.

I tried to read the source code to see if I could fix it, but it’s way too complicated!

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
nixjdmcommented, Jul 14, 2018

This sounds like you have conflicting files in your project as you do in your theme. When that happens your existing project files are used instead of the theme’s files. This is on purpose to allow the themes to be flexibly overridden.

Can you check this? Compare ls themes/[theme-name]/templates/ to ls templates/, for instance. Models would work the same way.

I do have a site using themes that works with 3.1.1 / master. I’m betting this what’s going on.

0reactions
nixjdmcommented, Aug 13, 2018

I agree that the documentation should be made more clear. Theming does work though, so since this is mainly a documentation issue I’m opening https://github.com/lektor/lektor-website/issues/240 and closing this issue.

Briefly, that workflow is not the end of the story. After your step 3 you’d need to modify your project to actually use the installed theme, and how precisely to do that depends on the theme (and your existing project, but in your example’s case it’s simply the quickstart).

like removing the default theme that quickstart created

At this time the quickstart does not use a theme. It is a normal, theme-less Lektor project. #535 would change that and hopefully make adopting a theme from the quikstart state a little easier. For now though, the expectation is that there are manual steps to use a newly installed theme after it’s installation.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Creating a Theme | Documentation
HI, I updated from 3.0.1 to lektor 3.1, the problem still exists. I think it is not a problem of the theme but...
Read more >
lektor/lektor
I've been working on two themes (turtle's steps, admittedly) and the more examples to take a ... Not a ton of change, but...
Read more >
Known Bugs & Issues - Documentation - OceanWP
Solution: Make sure ALL scripts are enabled via Theme Panel > Scripts & Styles. Afterwards, purge website caching on all levels (browser, ...
Read more >
CHANGES · 038ea4a60bf777528d105283785118bac2ee9a3a ...
Lektor Debian package used for Jenkins builds. ... work in all situations yet (in particular thumbnailing does not actually. 172. do anything for...
Read more >
Lektor CMS (@getlektor) / Twitter
Is it Pyramid running on top of MongoDB with a Redis cache? ... GitHub - Andrew-Shay/lektor-theme-simple-strap: A clean, simple, black and white theme...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found