Community

Hello everybody!

I meant to post this weeks ago, but some significant life events got in the way (👶) and as it turns out I've completely forgotten how much of a time sink those little ones can be 😆

That said, on with the news!

On 21 May 2023, the NodeBB team met up to conduct their semi-regular roadmap meeting. This meeting was the second part of a two-part series, the first being a retrospective on the past year's work. If you have been around this past year (two years), you'll have noticed some big changes as we launched v2.0 and more recently, v3.0.

The purpose of the roadmap meeting was to formalize and clarify the direction of NodeBB. There were many years where NodeBB's journey was directionally-challenged; we wilfully and often let our own whims dictate what to pursue.

Another high-level goal of the roadmap meeting is to plan out the next few successive releases of NodeBB, and what larger projects we could possibly expect to see achieved when tied to a rough release schedule.

A couple highlights that you could expect to see in the coming months:

A Revamped ACP

We've tasked @vladstudio with a re-design of the admin control panel. We're hoping to have the ACP maintain visual compatibility with Harmony, our new default theme, as well as fix a couple minor, long-standing, issues that we've just learned to live with over the years.

If you're running the latest code in the develop branch, you'll already be able to see it 👀

cada8387-e470-4348-8d4c-5735eb19f206-image.png

More tech debt repayment

There were a number of items that caught our attention years ago, that needed addressing. Two particular ones:

component is the attribute used to discriminate against different elements in NodeBB. Technically this does not validate as the proper attribute should be data-component.

❌ We decided not to pursue this one, as there was no perceived benefit, but only pain (as it would break a lot of plugins and themes). It is not conceivable that html as a markup language will change so much that invalid attributes would block rendering. Simply put, decades of the internet would have to be rendered inaccessible before component became an issue.

thank you for this.

@phenomlab said in Ns embed ACP blank page:

@Wamakaska yes, it is. I configured it that way so NodeBB automatically starts if the server is rebooted. It's a systemd script so will respond to sudo service nodebb stop / start / restart etc.

Oh ok. I don't know that and it works with your command.
Thanks.

Please report this issue on Github.

@pitaj I think for the same reason you can disable themes for users, To have a particular style for a website and not letting the user mess with it in case of bugs.

How much time does it take to see updated version (available for upgrade) of the plugin in ACP?

Ability to collapse trees in ACP preview for Categories.

@agarcia17 That doesn't disable the route, it just removes the link from the navigation menu.

app.user doesn't work?

Proposition:

ACP as a plugin/module. Introduce new namespace, for example nodebb-acp-somename

So you will have:

For themes: nodebb-theme-somename For plugins: nodebb-plugin-somename For ACP: nodebb-acp-somename

Encapsulate current ACP to acp-module, and see, in near future, how 3rd party ACP panel will popup (Angular based, or Material based, or something another...) 😉

@pichalite try this 😄

Dropbox error - 'echo 100000 | sudo tee / proc/sys/fs/inotify/max_user_watches'

Dropbox gives me an error that mentions echo tee 100000 but then it disappears. How to fix or remove msg?

favicon

Ask Ubuntu (askubuntu.com)

Thanks for the fast answers.

I will revoke the post and reply attribute from the registered-users group and create a new group with post and reply permission, where I add users based on some rules.

Problem is solved 🙂

I see he same issue as @Technowix was just going to report. Plugins that are upgradable for me seem to want to downgrade to previous version.

I would love an one click upgrade solution which doesn't use git in the background. git works flawlessly most of the time but in case something isn't right, it might take unexperienced users a lot of time to fix it (like me, even though I'm a developer, I never really used git).

Thanks guys. Looking forward to tag based plugin grouping in the ACP page.

I'm not looking forward to the eventuality that in the first version of this, all the plugins will be lumped under the nodebb tag, because that tag is in practically every plugin 😆

Update to latest version and try again.

@Scuzz Thanks! I think I forgot my username and password, but I have re-install it 😛