Feature Requests

@Netto-Hikari said:

fail-safe is more important than SEO

I agree with you there. It may be plugin territory too.

I am definitely sure, the current placement of share button is kind of hidden. I mean it is hidden beneath the "post like" button. Can u place this to the left of the "post like" button or right of it. Just a share button, when a person clicks on it the drop down menu comes with various social medias to share into.

It will be really hard for first time users to find out the share button. I know this can be changed in a custom theme, but even by default the share button should be visible to the members browsing a post.
Screenshot_5.png

In the chat page, instead of displaying "please select a reciepient to view the chat" the latest chat of the member should be displayed, because there is lot of screen real estate, so it would be better to show the latest chat, instead of that prompt message. @julian @a_5mith @baris
chat.png

@julian @a_5mith

I'm a hack on my good days but I'll give it a whirl as soon as I wrap my head around plugins in general.

I have a small stack of plugins we need for our feature set anyway. 🙂

Rather than dragging the button to make it bigger, just click it. 👍

I would be interested in specifying Home page template as cgi parameter to the URL. That way I can skin Home page to match where visitors come from.

@julian said:

ajaxify.go

gracias, amigo! I'll take a stab at it. Update later.

My biggest request by far is to have some sort of centralized permissions system for which groups have access to different functionalities of plugins. This permissions system would allow both user-specific and group-specific permission configuration and would mitigate the amount of small, permission-only plugin admin pages.

This could be done by adding the hook filter:permissions.addFields and then doing something like the database module to get permissions of a certain user or group. This, along with a simplification of settings, would be super helpful for easier creation of plugins. Plugins are going to be the best part of this platform, and if they can be created with more ease, then this platform will be embraced more. This could be done via a plugin, but it would be so much better if it were included in the core.

Client side features requested:

API for accessing certain server-side functionalities. Post parsing on the client side (so I don't have to include markdown.js).

Also, I should mention that after I'm done working on the 5 or so plugins I have in queue, I'm planning on developing a very strong polyfill server-side module library for bringing all browsers up to standard based on user-agent (to minimize unnecessary code).

This is related to an issue resolved earlier.

We found that if a topic's posts contained images pointing to a relative path (e.g. , NodeBB would attempt to load them, causing them to load the entire topic again (since the url is site.com/topic/123/1.jpg).

To combat this, @baris restricted the URL so that the slug must be correct, otherwise the user is sent to 404.

For lack of a better solution, this was the approach we took, so this seems to be the reason why you're running into this issue now.

@julian you always make me think twice!
You win on sorting!
I will explain it to team 🙂

@EisFrei Good read 👍

If you need the plugin as a matter of urgency, send an email to sales[at]nodebb.org and they'l give you a quote for such a plugin. Alternatively, you can add it to this topic and hope that someone will be up for doing it.

I did try posting that earlier from my iPad, but I was having issues with actually making posts. Haven't been able to replicate since. But yes, deleting users also removes their posts.

This is implemented on master now.

Hello,
I'm developing(trying :)) a user applications api system for mobile application. Users register application with ID and Secret. With UserAPI and Token System, posting posts, commenting, and chat.

How can I make UserAPI system?

sorry for my english 😞

@Jacob-Bridges no problem buddy, I've used it myself on occasion, so can't claim to be as highly philosophical as I make out. But i don't believe developers/designers should be forcing non default browser options like target attributes on users. then again, people have argued about it for years, so it's not going to be definitively resolved anytime soon. 😆

Let us know if we can be of any more help, NodeBB are currently hosting a competition, if you're looking at writing plugins, you've joined at a great time. 😆

@julian don't know why but I can't go into the site : packages.nodebb.org

@julian said:

If you're using pm2 loader.js, you should use the restart button in the ACP to restart NodeBB... 😄

I was dag nabbit.

(... or ideally, don't use PM2 at all, since the loader supercedes it. Just: ./nodebb start)

But I like to use pm2 because I use it for all of my other task management needs. Where in the code would it be?

By "dynamic" I mean any environment where these kinds of privileges may be changing frequently. It's not just about moderation, it's about their roles in general (reading and posting privileges). And I understand what an administrator is, but that's not a clean separation. Admin and moderator are roles (not specific, granular privileges) and in one case represented as a group and in another represented as a privilege.

It's not that NodeBB doesn't suit my use case. After finding the moderator option, I can pretty much do what I want to do. It's about the spaghetti process it took to get there. I'd just like to see this be simplified and presented in a more coherent manner.

@pitaj said:

I just don't want to flood other categories with questions. It also doesn't seem like there are many NodeBB users on StackOverflow right now.

Oh hey @baris... XD

If it isn't by default, it probably is if you make a plugin 😉