General Discussion

@hariom-vashisth Thank you

This is not possible yet, would be a nice enchancement. https://github.com/NodeBB/NodeBB/issues/5777

@julian look like. very good. i am waiting.... this. persona ver. thx. julian

@julian thanks, but I have tried to listen to the hook, and the callback in the action:ajaxify.contentLoaded listener excute even ealier than the callback in $(document).ready ,why is that...

Nvm. Works! Thanks!

Here you go! https://community.nodebb.org/topic/9447/howto-inject-hidden-data-into-composer/8 This should get you started. You'll need to edit the composer.tpl, or inject html at composer load, checking if the post is a new topic.

@frgilb said in Publish content/post from other apps?: @deha: I agree, with the write api plugin you should be able to solve your problem. There is even a python library available: https://pypi.python.org/pypi/pynodebb/. It is quite old but still works with up to date nodebb. Unfortunately, not all api calls are yet implemented, but it is easy (and quite obvious) to extend it. @baris said in Publish content/post from other apps?: Take a look at https://github.com/NodeBB/nodebb-plugin-write-api Thanks, helpful.

use nodebb-plugin-write-api and you can create how many post you like using ajax instead socket.io PS: creating your own posts doesn't mean your site will be any good. It will look "not poor", but it will be anyway.

You can do this in the custom HTML section... wrap it in <script></script> An HTML widget might also work.

Sweet, this keeps boosting my confidence in NodeBB

@bravominski 네~~ ^^

There are a lot of factors that could go into choosing which technology to use for your web application stack, which are probably too numerous to list here. However, some reasons to choose NodeJS come with advantages like: Its the same language one the client and server side code can be shared Less context switching when developing FE vs. BE It's designed to be asynchronous, so it forces encourages you to think in terms of delegation the ecosystem is huge the language is developing rapidly (could also be a disadvantage) Some disadvantages might be: Not strongly typed (but there are a solutions to that problem like TypeScript and Flow) JS is single-threaded, so it's not a good choice for CPU-intense operations It can be harder to do things you need to do synchronously (not impossible, but more verbose compared to an imperative language like Java or python) There are some oddities to the language that can be frustrating. In terms of tutorials, I've watched a few of Derek Banas' videos, and I like his teaching style. I've heard the Egghead tutorials are really good too, and definitely check out MDN as you progress. Nothing beats actually getting in there and trying stuff though, developing a plugin for NodeBB can teach you a few tricks.

@teh_g Thanks! It would come in handy. I'll do that.

Has anyone tackled this for a project? I assume the less files can be shared with some planning. Any tips?

@pichalite thx a lot ~~ ^^ have good day https://youtu.be/4Pu1ZRkXbGY

@pichalite Dang, I thought this would be much easier now

Ok, so 1.5.x branch is stable to use. Is 1.x.x maintained for bugfixes only or just for history sake?

@PitaJ testing reply

Hi everyone, I use the sso plugin with wordpress and find it cannot log out at the same time. So I found that way. It might a little bit dangerous because it just delete cookie. Is there any other way to log out at same time? This is my way to logout Logout wordpress -> Delete Cookie of NodeBB -> return to nodebb homepage Step 1: create this php file under wordpress dir <?php require( dirname(__FILE__) . '/wp-load.php' ); wp_logout(); setcookie("express.sid", FALSE, time()-YEAR_IN_SECONDS, '', "~~FORUM_COOKIE_DOMAIN~~"); header("Location: http://~~FORUM_COOKIE_DOMAIN~~/"); exit; Step 2 : make NodeBB can access this file when logout When we logout form NodeBB, it send us to /logout and a string. So I use the nginx as proxy server to access php files. here is my config file of nginx location ~ .*\.php$ { rewrite ^/(.*) /$1 break; proxy_pass http://localhost:82; proxy_buffer_size 128k; proxy_buffers 32 32k; proxy_busy_buffers_size 128k; } location / { rewrite /logout http://~~~FORUM_DOMAIN~~~/logoutbbs.php break; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://io_nodes; proxy_redirect off; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }

@sebastianneubert yeah one option is to do that. Another option is using a subdomain. Any reason why a subdomain wouldn't work for you?