Community

I like it very much, and I am willing to use it for secondary development. The large screen and almost full-screen experience on the mobile phone make me feel like using a native app

In 2020-2021 years I tried NodeBB for the first time, it seems then it was the ~1.5 version of the forum and I remember exactly what I fell in love with at first sight - the navigator in the header 🙂

F88C54E1-721F-4EB9-97E5-5D2550CF28D2.jpeg

Oh thanks @julian!
I didn't realise that, thanks for clarifying it!
All working now 🙂

cheers

@julian said in September 2022 Design Preview (New Base Theme):

We have taken a number of approaches to the design and are close to showing off another preview very soon (an actual one with real content!)

Wow! I look forward to 😳

@PitaJ thank you! will give this a try 👍

@macfan Not strictly true -- while you can accomplish a lot with just front-end styling, our theming engine allows you to change the underlying templates as well, so you are not limited to having elements in specific positions.

For example, if you want to have your reply buttons somewhere else on the page, or remove them altogether, you can do so by updating the topic.tpl template.

After some more code digging and experiments I can answer my own question. A theme is a normal plugin and as such does not inherit any behavior from other plugins.
So you need to copy everything you need from the base theme library.js to your child theme. And of course, you need to declare client scripts explicitly.
Loading of missing templates from base theme is the only link between the base and the child theme.

@julian maybe you have something for hide something text? bcs it Снимок экрана (47).png
doesnt work ,-,
Снимок экрана (48).png

@pitaj Thank you so much! That worked. 👍

@baris Thank you very much. This worked! 🙂

€: I additionally use the hook

$(window).on('action:ajaxify.start', function (ev, data) { $('div.topic-header-image').hide(); });

so that the header container with the image is hiding immediatly and before ajaxify.end 👍

Thanks for the help and sorry if the "terrible" word hurts your feeling, I didn't mean to.

@PitaJ said in the issue of benchpressjs:

First off, calling their work "terrible" is a really bad strategy if you're trying to get help from someone. I'll still help, because I like being helpful, but please don't act this way in the future.

#1. about Interpolation, benchpressjs does NOT allow to retrieve array by index, like this:
<h1>{localNews.topics[0].title}</h1>

If you're trying to just get a specific single element of an array, you just put the number as the property name, like so:

<h1>{localNews.topics.0.title}</h1>

I see this isn't documented, so I'll open an issue to document this behavior.

#2, about helper function, I created one like this:
Benchpress.registerHelper('getByIndexInArray', function (arrayData, i) {
return arrayData[i];
});

and call this helper function like this:
<h5>{getByIndexInArray(localNews.topics, 1)}</h5>

But it seems like the index "i" can not be passed into the helper function, since in this helper function, I always got "i" as undefined.

Your helper is correct, it's how you're calling it that's the issue. Benchpress doesn't have numeric literals, it only has string literals. Putting just 1 in there is telling Benchpress to look up the property "1" on the global object, and call the helper with that value (which is undefined in your case). Your helper will work if you call it like this instead:

<h5>{getByIndexInArray(localNews.topics, "1")}</h5>

I will also add a note to document this behavior in the paths and helper section.

Issue is here: https://github.com/benchpressjs/benchpressjs/issues/89

@pasib glad you found the issue

Help me pls )

Thank you @PitaJ for pointing me in the right direction. I adapted my code to the link you sent me.

(function (factory) { if (typeof module === 'object' && module.exports) { factory(require.main.require('benchpressjs')); } else { require(['benchpress'], factory); } }(function (Benchpress) { const logger = (data) => { console.log('Logger helper', data); return ''; }; const customHelpers = { register, logger, }; function register() { Object.keys(customHelpers).forEach(function (helperName) { Benchpress.registerHelper(helperName, customHelpers[helperName]); }); } register(); if (typeof module === 'object' && module.exports) { module.exports = customHelpers; } }));

Just by doing this made it work client side. But then it stopped working server side. That was easily fixed though by running helpers.register in my library file.

const helpers = require('./lib/helpers'); helpers.register();

Hope this helpes someone!

Thanks @baris, I will have a look.

Been offline for a bit but it looks like this has been addressed. This has been fixed by @julian in commit d33d965 to nodebb-theme-persona and commit 9d202d9 to nodebb.

Thanks Julian!

the answer is in this topic :
https://community.nodebb.org/topic/11906/add-a-class-to-the-body-if-the-template-is-404/3

nah, not gonna do this.

@insuusvenerati try running ./nodebb build and then start NodeBB

Hi, guys. I built a forum called V2MM for Chinese freelancers, and I built a theme with the same name.

nodebb-theme-v2mm on github.

Its still under development, but there are a few unique features:

Show topics of subcategories in parent categories. Support special topics, such as external link topics. Special category template.

0_1479194670448_Screenshot from 2016-11-15 15-12-56.png
0_1479194684150_Screenshot from 2016-11-15 15-13-23.png