Wouldn't it be nicer for plugin authors to always show 'compatible' with the last release that the plugin was compatible with?
I think I would be reluctant to add a badge to my READMEs that tells my potential users that this plugin doesn't (yet) work with a NodeBB version that has just been released.
Just a thought
I installed emailer-sendgrid plugin by julianlam on my NodeBB versions 1.12.2 which says its compatible with this version. However, when I go to the Plugins -> Emailer (Sendgrind) and click it, the /admin/plugins/emailer-sendgrid page just loads indefinitely and never actually comes up, ever. Do you know what could cause this and some troubleshooting steps? One thing I did try is I restarted NodeBB after I installed it and logged out and logged back in. I DID NOT do a rebuild/restart though.
Hey @am1cable! Very cool plugin. I started using it on my forum and it started generating errors. Not sure if you are still putting work into this thing, but thought you should know!
Here's the output:
2019-10-21T19:34:24.718Z [4567/17167] - error: uncaughtException: Cannot read property 'toString' of undefined
TypeError: Cannot read property 'toString' of undefined
at Object.parsePost [as method] (/var/www/html/community/node_modules/nodebb-plugin-dice-and-numbers/library.js:22:193)
at replenish (/var/www/html/community/node_modules/async/dist/async.js:1011:17)
at iterateeCallback (/var/www/html/community/node_modules/async/dist/async.js:995:17)
at parse (/var/www/html/community/node_modules/nodebb-plugin-emoji/build/lib/parse.js:155:9)
at getTable (/var/www/html/community/node_modules/nodebb-plugin-emoji/build/lib/parse.js:141:9)
tail: './logs/output.log' has become inaccessible: No such file or directory
tail: './logs/output.log' has appeared; following new file
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" : "P***s test censor" or "slug" : "123/p***s-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.
so just in case it might be related, I would like to update our situation...
After 1.12.2 upgrade, we had "restart required" problem because of poll plugin, you can see the post above...
But, currently we are using updated 0.3.3 version of the poll plugin and forum works fine and "restart required" error is also gone...
@Deendyal-Agarwal said in [nodebb-plugin-ns-awards] NS Awards, Give Medals!:
I am getting error when creating new Medals (NodeBB Version : 1.12.2)
Request URL: http://localhost:4567/api/admin/plugins/awards/images
Request Method: POST
Status Code: 404 Not Found
does the plugin break with 1.12.2?
it would be suck if plugin breaks whenever nodebb is updated.
@Nicolas Hello!, im trying install plugin at 1.12.2 and not work
when i press button, i lost focus on textbox and not writer ::: and.. when i create manual, spoiler button not work
T_T its a bug on 1.12.2?
Seems like it can work without any backend, although is easy to circumvent when used in that way. I think the hardest part here would be making it look sensible, as the version on that website seems far too big for the composer
As for implementing it properly - you'd have to somehow pass its response along with the post, but if you manage to do that it shouldn't be hard to actually handle it as it's just one simple http request to their api.
@oplik0 thanks, unfortunately we cannot use in topic search since our forum is paginated. Currently, it is showing the same result as it would show you do 'find function of the browser', unfortunately this way is not useful for us.
Thanks for "solr" recommendation, we have actually tried that before in our development forum, but somehow it wasn't working (right now I could not remember what the problem was), but we will look into that further to see if we can use it.
@satishbh Also to add more context to this for others who come across it (using the older version):
The root cause of the error was having an S3 bucket that wasn't public. The plugin then handled the thrown error by the S3 API incorrectly, which was fixed in:
I found the reason that my bucket wasn't public.
joysboy created this issue in june07/nodebb-plugin-cloudstorage
Aws s3 don't work
committed to june07/nodebb-plugin-cloudstorage
This allows you to log in via a WordPress.com account, not an account from your own WordPress site.
That said, there no account syncing, if you don't already have an account you are given one, that's all
I recently have updated Nodebb to 1.12.2 and this plugin to ver 0.3.1. I did put the Telegram Token and the room Id but I don't receive new topics nor reply to the Telegram group.
I have tried this from the server:
curl -X POST "https://api.telegram.org/botMyToken/sendMessage" -d "chat_id=-My_Chat_id&text=testing"
This works fine. Furthermore, if I talk to the bot it reply nothing and If I put a command, I get this message:
UserID not found.. Put your TelegramID again in the telegram settings of the forum. :(
I was able to get my TelegramID by checking bot's status in:
It still gives me the "Uid not found" message furthermore I don't receive notifications like upvotes and so on.
I have two questions:
Why it is not sending messages to the group?
Why the bot is answering with an error message instead of my TelegramID. This is important since forum users should be able to configure it in a esay way.
EDIT: I noticed that if I enter the TelegramID into a user, when I create a new topic or reply to an existing topic, Nodebb restats with this error message:
2019-08-26T18:03:52.827Z [4567/14717] - error: uncaughtException: forumURL is not defined
ReferenceError: forumURL is not defined
Otherwise if I interact with a user without TelegramID, Nodebb doesn't restart. If I uninstall nodebb-plugin-telegram, all users works fine.