That would be great for a more easy way to config plugins that add new fields to the profile page, like 'nodebb-plugin-ns-custom-fields'.
We would no longer need to modify the files on the server and we would be able to do this in real time and right on the ACP panel!
@MJ said in We've got banned from Imgur breaking their TOS.:
Or is there some way to resize photo's so we can save space. When making a picture with phone most of the time its 7 to 12 MB p/photo, if there is a way to resize it to a 500 kb jpg file or something we can store all the images ourself.
By writing shell scripts, you can, yes.
For example, you can set up a cronjob to delete all images older than 30/60 days from the public/uploads/ folder.
Or perhaps you can run convert -resize 640x on all images after 60 days' age to reduce size.
Alternatively, you can set up a DigitalOcean volume (or something equivalent) and save your stuff there for less cost.
I still cannot figure it out. I see the tid: in some of the topics, but it's got the topic id in it, not a tag id. I'll buy someone a $100 Amazon (or other) gift card (or $100 worth of ETH/BTC) if they release on github a bulk tagging plugin that allows me to add one or multiple tags to all topics/posts in a category. I know it's not much, but I'm not generating any revenue off this site and have limited budget.
So I have looked at this in greater detail and here are the problems 1 I see.
The sortedset really only records two bits of information: the UID and the filename. If anything more is needed the filesystem will have to be queried and logic added to evaluate the file. My view is I'd rather store this in the DB and pick it up in a single query than collect the data from the filesystem on the pageload.
This process lacks the post validation check for uploads. This leaves debris in both the database and on the file system.
I didn't spot a cleanup system that might take care of this.
1 These are from the perspective of the problem I think I am trying to solve, aside from the couple I saw that are duplicates of issues I created in my own efforts.
I think I have discovered another breaking change that you didn't mention, though it is probably super-niche.
This commit: https://github.com/NodeBB/NodeBB/commit/ec91ef1c644044bba44198b031913655e784b4bb
broke our custom SSO plugin. The result was that after successfully logging in our external identity provider and being redirected to our Forum's callback endpoint, I was ending up not logged in (the button in the header still said "Log in") and stuck on /register/complete roadblock. It looked like our Passport strategy verify callback, that parses output from the identity provider and fetches user data via OAuth2 was not invoked at all.
It turns out that the changes in this commit don't play well together with passport-oauth2 (https://github.com/jaredhanson/passport-oauth2) internal ability to protect against CSRF (which we were using). This strategy was already using state parameter to pass its own CSRF token. I don't have more time to investigate but I suspect things shipwrecked when NodeBB overwrote the state parameter with its own CSRF token.
Turning off passport-oauth2 internal CSRF protection (by removing state: true from its options) fixed the issue.
julianlam committed to NodeBB/NodeBB
Found a "hidden" file in the nginx/sites-available and nginx/site-enabled folders.
Deleted that and now I only have one nginx warning left.
When running 'sudo nginx -t' this is the result:
nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:80, ignored
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Ok i have now also removed the return 301 (line 4) in the nginx server block, I think it also conflicts with the rewrite in line 5.
And boom HTTPS works.
Next thing though, we still don't get to see a greenlock in firefox or chrome. It says something about the site only being partially secure. Any idea why that happens?
Now also fixed, our logo was still referring to a http link, removed the domain and just made it point to src="/assets/uploads/system/site-logo.png"
PS. any other tips or adjustments on the config files is also welcome
FWIW, it's a few years later -- I was able to log in via elinks (a lynx variant used by one of our members), and though the interface was a little messy it worked. Search seemed to not work (or I wasn't using it right), but I could browse. Writing a reply to a post seemed impossible though, as I got "403 forbidden." Have not tried with JAWS or the like yet. I'm not sure if this is on the roadmap to change but here is a quick note that these are the results as of June 2018.
@jarko said in Running backup while NodeBB is running:
The question is pretty much all in the title.
Is it ok to run the mongodump command to backup the database + make a backup of user pictures while NodeBB is running? Or should the backup script run ./nodebb stop before and ./nodebb start after? I guess the real risk of something going wrong regards the database dump.
doing backup daily for a year without stop, no issues
So we are running our forum using Cloudfare, and we see CF has an option for AMP support. if we turn that on in CF, would node bb all pages enable this AMP itself?
Or is there any plugin or core in node bb which supports AMP?