Community

Ok, this works

<!-- IF categories.children.length --> <!-- BEGIN children --> <!-- IF @first -->(Sub-forums: <!-- ENDIF @first --> <a href="\{relative_path\}/category/{categories.children.slug}" itemprop="url">{categories.children.name}</a> <!-- IF [email protected] --> &middot; <!-- ENDIF [email protected] --> <!-- IF @last -->)<!-- ENDIF @last --> <!-- END children --> <!-- ENDIF categories.children.length -->

Just put it somewhere between <!-- BEGIN categories --> and <!--END categories --> in home.tpl

And take both \ from {relative_path}.. it seems that nodebb parses it... so I had to type...

Opened an issue. Getting rid of Bootstrap is currently close to impossible without modifying NodeBB.

Ok. it was my first pull request ever, hope I did it correctly. =]

Here, application of the ajaxifying class to the #content element

@baris Thanks, but there's no way to just get all the most recent posts in a category, including all subcategories posts? The templating engine doesn't seem to allow anything too complicated (nor anything complicated at all in fact), so I don't think I can like aggregate the different arrays and sort them...

Maybe it's something that you should be able to configure? Subcategories is a quite recent addition so it's normal that no such thing has been implemented / thinked about yet, but maybe it's something you might want to have.

I really want all my posts on my main page (WIP theme http://nodebb-test.ribesg.fr/)

If you've forked the Lavender theme, just add the original source as another remote:

$ git remote add upstream git://github.com/NodeBB/nodebb-theme-lavender.git

Then every time you want to merge the latest changes in:

$ git fetch upstream && git merge upstream/master

Thanks for that. I would expect some way to configure that. Removing that line would also apply that to all widgets areas, on all themes, right?

My workaround is to add a plznohide class to the appropriate widget areas' divs and add this to either my theme CSS or the "Custom CSS":

.hidden.plznohide { display: initial !important; visibility: visible !important; }

It seems to work as expected. Being able to configure if each widget area should be hidden in the ACP would still be nice.

you're the best

@Escuiquirin LOL I wish! Glad I could help though 🙂

@agarcia17 Yes I did but then I deleted it because I changed the way I displayed my menu after some feedback.
But here's what I've done

//Check if there's unread messages var unread = setTimeout(checkUnread,500); //Update Unread messages on events socket.on('event:chats.receive', function(data) {toggleUnread(data)}); socket.on('event:new_notification', toggleUnread); socket.on('event:new_post', toggleUnread); socket.on('event:new_topic', toggleUnread); function toggleUnread(data) { if (data) var receptor = data.message.touid; if (!$('#unread').length) { var unread = '<span id="unread" title="Vous avez des messages non lus" class="bounce-small infinite animated">'; if (receptor != undefined) { if (receptor == window.app.uid) $(unread).insertAfter('.header-top .menu'); } else { $(unread).insertAfter('.header-top .menu'); } } } function checkUnread() { $('#unread-count, #notif_dropdown i, #chat-count').each(function(){ var n = $(this).attr('data-content') if (n > 0) { toggleUnread(); return false; } }); }

I hope it can help you.

I used nodebb-theme-quickstart aswell for deep-space (galaxygraph theme) I think I didn't edit the readme.md
Nice theme Julian, may I suggest to not use transparency on categories since I guess the background can be changed it can cause issues of readability. I dig the idea of the big background photography rather than the content.

Heh ... you responded in the time it took me to update the value and restart my NodeBB. Nice.

@agarcia17 I've omitted something the empty guide div should be added before the others with class category-item.

The Classic theme is based off of Lavender yet it does not have the pinterest-style categories.

If it works for you, keep it up.

The semi-official way to do this is to fork the plugin you want to use, and make the appropriate changes.

Then, add the original repo as an upstream branch (using lavender as an example):

git remote add upstream https://github.com/NodeBB/nodebb-theme-lavender.git

When you want to update to the latest lavender for your theme, merge or rebase:

git checkout master && git fetch upstream && git merge upstream/master

Display Names aren't currently in NodeBB. Its not really something that has been requested that much. Considering you can change usernames.

@vatsal Yes I'm sure "folder-name" : "public/folder-name" means you can use /plugins/your-theme-name/folder-name/whatever
The first parameter correspond to the name that will be used after theme-name/folder, while second parameter means this alias points to path.

@baris
Managed to find the following line

<div class="<!-- IF categories.class -->{categories.class}<!-- ELSE -->col-md-3 col-sm-6 col-xs-12<!-- ENDIF categories.class --> category-item" data-cid="{categories.cid}" data-numRecentReplies="{categories.numRecentReplies}">

in

./node_modules/nodebb-theme-lavender/templates/home.tpl

So I proceed to change it to

<div class="<!-- IF categories.class -->{categories.class}<!-- ELSE -->col-md-3 col-sm-6 col-xs-12<!-- ENDIF categories.class --> category-item category-class-{categories.cid}" data-cid="{categories.cid}" data-numRecentReplies="{categories.numRecentReplies}">

?

Thanks @esiao I've been wondering how this would look.

Thanks for reporting the bug @mootzville, the templates property is no longer required in a custom theme's theme.json in v0.5.1 (but since we haven't even launched v0.5.0 yet, don't worry about a thing, the fix is backwards compatible)

I usually make a custom.less file and put all my edits in there with or without the !important tag, as needed. @frissdiegurke 's fix should work as well.