This look straightforward so I try to answer :), i think the node version is incorrect. you need to upgrade > 4.0.

I suspect nodebb is now talking to VC, because its a bit quiet in the forum.

Hope VCs inject $10m into the development of nodebb, because this software really superb!

Great job and good luck guys!

hi,

I am trying to explore if its possible to create a widget that contains React component. Is there any example implementation that I can refer to?

Thanks in advance!

@AOKP Actually, I think Nodebb are doing a great job. With new version releases, old plugins may failed, this is inevitability process.

Btw, which version are you using now? You can always downgrade to previous version that you are using.

hi, I need a new feature that was merged in master branch. As we know, master branch is always unstable and so I am hoping to work on a stable tag. So two questions below:

1. Is there any release date planned for v1.1.3?
2. What is v1.1.3-auto.x? Is it stable, i.e. pass the unit tests?

Thanks, please advise me.

hi experts,

I am a newbie, so pardon for if my question is noob. Basically, I want to write a plugin / widget that will query a new restful api that i will be to implement.

Do I need to:

1. modify the nodebb's core to add the restful apis or
2. implements at the plugin's library.js and it will auto-bind the new restful api at the server (is this possible?).

Thanks and appreciated.

@julian said in Local login take a long time...:

var bcrypt = require('bcryptjs')

Many thanks @julian and guys, you save my day. It is working now, reduce to ~700ms.

Thanks @yariplus.

I want to write a new restful api that will query a new table (mongodb document) on the same server that nodebb resided. The data will be populated by a cron job running on the server.

I guess I understand what you meant. Let me go and have a look on your widgets implementation. Thanks for the help!

I also think Nodebb need a redactor editor because basic users may not be custom to markup language.

The issue now is that the default composer and redactor composer are incompatible, several plugins that was developed for the default composer will not work for redactor. I hope Nodebb can standardize the composer for both expert and novice users.

Thanks @baris and @PitaJ for the nice info, I will try it out.

@PitaJ said in Any code format plugin?:

<script>
require(['highlight'], function (hljs) {
require([
'https://cdnjs.cloudflare.com/ajax/libs/highlightjs-line-numbers.js/1.1.0/highlightjs-line-numbers.min.js'
], function () {
$(window).on('load action:ajaxify.end', function () {
setTimeout(function () {
hljs.initLineNumbersOnLoad();
}, 100);
});
});
});
</script>

Perfect!

Similar to markdown code block ``` but with additional of line numbers, is such plugin available?

Please advise, thanks.

I have just found that its possible by changing the language file, eg. global.json, pages.json. Other than language files, can it be configured using the admin gui?

Is it possible to configure the title and change from Home to other text such as Best Forum for the homepage?

eg. to get the result Best Forum | NodeBB.

p.s: I understand that the Title Layout can be changed and I think the layout is perfect. It is just the title of the homepage that I wish to change.

@Giggiux did you customize the theme? It look cool.

@yariplus Great, this is what i need

@yariplus hmm you are right, thanks. Somehow I have to make the ".click' listener trigger first (ordering) before the composer listener.

@yariplus Thanks for your suggestions. I just found out that the default composer validates for 0 content length on the client-side, which mean I have to modify the codes there. And the reason it has to be on client-side is because the composer will block the topic submission if the content is empty.

Use-case

1. User create a new topic.
2. User click submit button.
3. Client-side check if the content is empty. If content is empty, insert "xxx" to content.

Is there any client-side hook that invoke upon topic submission (#2) before going to server?

Thanks!

Yes, I second this.

As a developer, I love MD as it is pretty easy to use once you master it. However, the layman out there are not familiar with MD.

As such, I support the notion that the stock editor should be WYSIWYG instead of markdown.