Also you can ask for help at:
How to make the right sidebar displaying everywhere? Not only the homepage and categories.
It doesn’t work for the "add topic“ button
Hmm… works fine for me when previewing on Theme Creator.
If you want to specifically target the New Topic button, try:
button#create-topic {
// add stuff here...
}
When having
- a private message
- with a tag
- viewing without sidebar
The width becomes very small
Cause:
.navigation-topics,
.categories-list,
body[class*="tag-"]:not(.archetype-regular):not(.archetype-banner),
body[class*="category-"]:not(.archetype-regular):not(.archetype-banner):not(.archetype-banner):not(.archetype-private_message) {
in fkb-d-topic-list.scss is being applied, and it shouldn’t.
I suspect it needs :not(.archetype-private_message)
However, I wonder why it is targeting these archetypes so specifically at all? Is it just trying to see whether it’s on a topic list (vs topic view?)
2 Likes
I’m loving this theme but I’m either encountering a bug or I broke something.
For some reason there doesn’t seem to be any padding above topics so the rounded corners sort of disappear and there’s no visible separation between each topic.
Looks like something with the new modern foundation experimental change is causing this behaviour. Turning that off seems to set the padding back to normal.
Title:
[Bug] Theme crashes on Discourse 2026.4.0-latest — Could not find module 'ember-this-fallback/js-component'
Description:
After updating Discourse to v2026.4.0-latest (commit 19374472fd), the FKB Pro theme causes a fatal frontend crash, making the forum partially unusable. Discourse shows the orange banner:
“由于主题/组件有错误，您的站点可能无法正常运行。由 ‘FKB Pro theme’ 引起。”
(Translation: “Due to an error in the theme/component, your site may not work properly. Caused by ‘FKB Pro theme’.”)
Root Cause:
The theme (or one of its components) still references the ember-this-fallback/js-component module, which has been removed from Discourse core in recent versions. This module was a compatibility shim for the deprecated Ember this-property-fallback pattern, which allowed templates to use {{foo}} instead of {{this.foo}}. Discourse officially announced the removal of this shim and required all themes/plugins to migrate to explicit this. bindings.
Error from browser console:
Failed to load theme 4 from https://www.sitetalk.net/...
Error: Could not find module 'ember-this-fallback/js-component' imported from (require)
[THEME 4 'FKB Pro theme'] Error: Could not find module 'ember-this-fallback/js-component' imported from (require)
at vendor.js
at requireModule (vendor.js)
at Object.lookup (chunk.js)
...
at reportThemeError (chunk.js)
(Discourse version shown in console: v2026.4.0-latest, Ember v6.10.1)
Environment:
| Item | Value |
|---|---|
| Discourse version | v2026.4.0-latest (commit 19374472fd) |
| Ember version | v6.10.1 |
| Theme | FKB Pro (default install from this repo) |
| Reproduction | 100% reproducible after upgrading Discourse |
We hope that the developers can fix this issue. Thanks!!!
4 Likes
Hello, after updating Discourse to v2026.4.0-latest — Ember v6.10.1, an error occurred, making the forum unusable:
client-error-handler.js:109 [THEME 28 ‘FKB Pro theme’] Error: Could not find module ember-this-fallback/this-fallback-helper imported from (require)
at loader.js:247:1
at a (loader.js:258:1)
at requireModule (loader.js:24:1)
at Object.lookup (app.js:36:12)
We hope this can be fixed.
4 Likes
Any news on getting this fixed yet?
Any news on getting this fixed yet?
I have a report that GitHub - literatecomputing/fkb-pro-theme: FKB Pro is a highly modified, detailed, professional social theme, but still user-friendly. · GitHub is working. I made a pull request.
4 Likes
Hi Don,
First of all, absolutely stunning theme! I recently deployed FKB Pro for my local education community, Jiwa.now, and the card-based UI looks gorgeous and highly professional.
While testing on mobile, I noticed a UX issue regarding the clickable areas on the topic cards. Currently, the clickable zones feel inconsistent. For example, users can click on the very edges of the card to enter a topic, but clicking on other blank areas (like on the right of the avatar row or in the middle of footer) does nothing.
This “hit-or-miss” interaction makes users feel confused, and it often leads to accidental clicks when they are simply trying to swipe and scroll through the feed.
A Suggestion for Future Updates: It would be a UX improvement if the theme could refine this by default—making only the core content (Title, Image, and Excerpt) clickable to enter the topic, while disabling the card’s background to prevent swipe misclicks.
In the meantime, to make the mobile touch experience 100% reliable for my users, I wrote a CSS snippet using a pointer-events “whitelist” approach. It neutralizes the background click entirely and specifically re-enables clicks only on the actual interactive elements.
I thought I’d share it here for anyone looking to refine their touch targets, and perhaps it could be a useful reference for developers:
/* Fix for mobile card click/touch conflicts (Smart Whitelist Approach) */
/* 1. Neutralize the entire card background to prevent swipe-clicks */
.topic-list-item {
pointer-events: none !important;
}
/* 2. Re-enable all native links and buttons (Avatars, Tags, Titles) */
.topic-list-item a,
.topic-list-item button {
pointer-events: auto !important;
}
/* 3. Re-enable image clicks */
.topic-list-item .topic-image,
.topic-list-item .topic-thumbnail,
.topic-list-item img {
pointer-events: auto !important;
cursor: pointer !important;
}
/* 4. Re-enable the entire footer stats area */
.topic-list-item .topic-item-stats,
.topic-list-item .topic-footer,
.topic-list-item .post-activity,
.topic-list-item .activity,
.topic-list-item .num,
.topic-list-item .topic-meta-data {
pointer-events: auto !important;
}
/* 5. Kill any overlapping stretched-link pseudo-elements */
.topic-list-item .main-link::before,
.topic-list-item .main-link::after {
pointer-events: none !important;
display: none !important;
}
Thx!
Leo