@julian said in Hook for modifying session cookie:
Hi @asdrubalivan! That's an interesting conundrum you've got there...
However, it seems last last year, @oplik0 used sameSite: 'Strict' for API routes, or at least, those requiring the CSRF token.
Not a dev so don't follow most of this but my eyes did pick out the cross site and strict, and yes, necessary for CSRF. Seems trying to work around that would be less than advisable? I guess it ultimately depends on your security stance and cost/benefit but I'd be wary of circumventing. It's a freakin' war zone out there. And an election year for U.S. so expect community and blogger sites to be targeted vigorously and relentlessly.
My $0.02. We now return you to your regularly scheduled programming...
I don't think that there is one. But you could make one yourself, of course.
You could have the same effect, I think, by just posting in the group, though. Once you want to get a public message to everyone on the forum, the forum is the best mechanism for that.
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
Please Give Solution for Ads.txt issue too.
so AdSense Section is complete for NodeBB
Is any way to add ads.txt?
ive uploaded file through admin panel. but for google it needs like domain.com/ads.txt
I am currently running NodeBB v1.13.x and using bearer token for authorizations.
I need to use some admin APIs http://localhost:4567/admin/manage/privileges , but right now , it is showing 403 error. Please let me know if there are some specific way to use admin APIs .
New version. Please try out email@example.com
Note: this version requires NodeBB v1.13.x
npm i nodebb-plugin-calendar@latest
Fix #128: unhandled promise rejections when restoring a post without an event
New Release 1.5.1
Back from the dead with a bunch of bug fixes, code rewrite to current node and NodeBB, and new pictures for the guide topic!
Fixed crash if camo was not installed locally.
Fixed crash if an incorrect url was specified.
Fixed crash if installed on windows.
Fixed settings not changeable after original setup.
Removed old or useless hooks.
Corrected dead links and emails.
Changed compatibility to >= NodeBB 1.0.0
When using Redactor as composer, clicking 'New Topic' or 'Reply' button will create multiple GIF button. See screenshot below:
The GIF button multiplies every time I close the composer and reopen it. It doesn't happen if I'm using the default Composer.
Anybody face the same issue?
@julian said in Advanced Editor Plugin:
You'll probably want to use the Quill Composer, which is our official (in development) WYSIWYG composer.
You should be able to download it from the plugins list.
Don't you use markdown here?
Well looks like I was an ID10T on this one. npm install pulls the original Annihil version cuz that is where package.json tells it to grab it from.
Manual installation of Julian's/NodeBB 3rd Party forked version, available here: https://github.com/NodeBB-Community/nodebb-plugin-email-blacklist
Coupled with my URL query string update above and ... voila! Now works dandy w/both manually added addresses and istempmail.org API key.
The function isTempMail's path var needs to be thusly:
path: '/api/check/Your-API-Key-Here/' + email
Or maybe I neglected the trailing slash first time around. In any event, geronimo, there ya' go.