I don't know for you, but on mobile, when you want to submit a new subject, you don't have a nice and friendly button at the end of the page as a lot of CMS but only a little ">" on the right top area which is really not user friendly...
HOW to change it by a REAL button, easy to see for newbies ? (we are not all nerd lol)
Thank you !
@am1cable said in [nodebb-plugin-dice-and-numbers] Roll dice and generate random numbers:
@Michael-Pfaff I haven't been working on it recently, but I have plans to go through and finish it sometime this year. Will have a look at this while I'm at it!
Hey man, I just went ahead and purchased a plugin made by the NodeBB team. We made it open source if you wanna use that.
It's here for anyone interested: https://github.com/NodeBB/nodebb-plugin-dice
The new version has been released.
Changed version compatibility with NodeBB v1.13.x
Changed main ACP dependencies to use the latest client libraries
Changed file library dependencies to use native File System module
IMO it's a feature for a separate plugin - not this one. This plugin, as the description suggests, is using Notification API, and not Push API.
A Push API-based notification plugin would be great, but it's not just an upgrade to this one as Push API works in fundamentally different way by using a service worker.
The plugin repository is the one in nodebb admin. But the thing about it is that there is no moderation there - it's just npm packages that have nbbpm attribute and compatibility string. If the compatibility string is wrong, there is no way for NodeBB to verify that. You can learn about it here.
Other than that you can just search GitHub, NPM and GitLab for names starting with nodebb-plugin.
New version. Please try out firstname.lastname@example.org
Note: this version requires NodeBB v1.13.0
npm i nodebb-plugin-calendar@latest
Support NodeBB v1.13.0
Fix broken avatar sizing in response lists
Warning multi-day responses in topics are broken in NodeBB v1.13.0, but they should work fine in the calendar interface. I've submitted a PR that will fix this when a new NodeBB version is released
@julian said in [nodebb-plugin-imgur] Imgur Plugin:
Could be that the plugin templates were not built? Try running ./nodebb build and restart NodeBB.
We tried that and still not working. It isn't just Imgur. Can't access Persona settings either.
@gotwf said in Plugin idea: emailrep.io:
Which seems to be nodebb's approach in general w.r.t. stuff like this
In general, yes. We try to not muck around with existing installs too much, but plugins are a little more fast and loose with things like this. Will keep it in mind
I am still in the process of getting an AdSense account, one odd thing I noticed with plugin version 1.0.4 on Nodebb 1.12.2 is a weird rendering / navigation-to issue with the ACP. Whenever I exit the Google Adsense ACP and re-enter the ACP via navigation the ACP will not render. It will only render after one additional refresh or when I paste the ACP url from the navigation menu manually into the browser bar. It does seem to store settings fine.
I already reinstalled the plugin, re-ordered all plugins to the recommended order and did a rebuild a number of times, with no change. I hope this is just a harmless ACP navigation bug?
I am using the latest version of the beep plugin 0.4.2 on the latest version of NodeBB 1.12.2. I have one issue with the beep plugin regarding old topics which were created before I migrated my site to NodeBB which have words which should be censored.
Newly created topics are censored with the beep plugin just fine. In the MongoDB the beep plugin actually saves topics with the censored words, so e.g. "title" : "Ps test censor" or "slug" : "123/ps-test-censor" is persisted in the database. Posts are obviously not modified by the beep plugin in the database but on the fly. Queries on the DB show the full non censored words in all posts be it old or new posts. Old and new posts are correctly censored by the beep plugin on the fly during browsing of NodeBB forum.
To fix this, post processing must be run on all topics in mongodb to modify "title" and "slug" applying the current beep censor rules.
Fortunately, I did not have that many topics to fix, so a quick manual fix is to just open each offending topic once, editing the topic as admin and saving it.
As a future improvement of this plugin, it would be very nice to have a simple button in the admin panel which runs a post-processing script for the above issue. This would be especially helpful on any change of the censor words down the line.