@julian This worked great. I did this in my main client file (like persona.js). require(['hooks'], (hooks) => { hooks.on('filter:script.load', (data) => { const replaceMap = { register: { target: 'forum/register', with: 'replacement/register', }, }; const replace = replaceMap[data.tpl_url]; if (replace) { const index = data.scripts.indexOf(replace.target); if (index > -1) data.scripts[index] = replace.with; else data.scripts.push(replace.with); } return data; }); }); Then I can just add my scripts that I want to replace to the replaceMap object.

@baris This worked like a charm. Thank you!

@julian said in Why isn't email required anymore?: There were two issues with this: Incorrect emails would bounce, causing reputation issues over time I run my own mail server and my forums are "small" so the bounces land in my queue/spool and are not a real problem. I see how this could cause significant grief otherwise, especially on larger forums. I also use IsTempMail, which seems pretty effective on its intended targets. I wonder how many others do? Been a while since I played with those knobs but iirc, it was pretty painless to set up. NodeBB prior to this change would allow any email to be entered, even other peoples' emails. A lot of sites do this, and it's not necessarily something we should guard against, but I personally find it really annoying when someone uses my email to sign up for random sites. Hard nut to crack, this one. Maybe add a disclaimer to the welcome message along the lines of "Somebody, hopefully you, used this email address to register for our community at URL. If this was not you we apologize for the inconvenience."?

@julian Okay, I'll do that. Thanks!

@magnusvhendin Settings->Advanced User Obligatory reading: https://github.com/gorhill/uBlock/wiki/Advanced-user-features Although it still does allow some stuff I'd rather not see, on balance I tend to favor "Medium Mode" : https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium-mode Once you're "in the advanced user" modes, enable various "noop" rules to season to taste. Speaking of which, you probably also should read up "Dynamic Filtering": https://github.com/gorhill/uBlock/wiki/Dynamic-filtering For those more visual and auditory learners: youtuber link: https://www.youtube.com/watch?v=2lisQQmWQkY Have fun! o/

@magnusvhendin No problems. For clarity, once you have the plugin installed, you want this section [image: 1623843635716-b1d9072d-265a-486d-ae9b-f29d49fbed83-image.png]

Hello @jalathpc_demo I tried to create a patch: https://github.com/LM1LC3N7/nodebb-plugin-private-forum/releases/tag/v1.3.1 I no longer have a NodeBB instance, so let me know if it works (I am honestly not sure, as /logout should be allowed as you are logged in. It would be interesting to check if req.loggedIn is correctly set when using SSO. This could be why the plugin is not working as you need. NPM link: https://www.npmjs.com/package/nodebb-plugin-private-forum/v/1.3.1

Yep, I see the issue. I'm not looking to push any changes. It was more out of curiosity on why there are several different names within essentially the same function.

Is there some way to hide all topics within a category from all feeds (recent, popular, new, the digest)? I need the topics to be accessible (and usable) to all users directly, but not searchable or showing up at random.

Please report this issue on Github.

@baris That's it! Thanks a lot.

Thanks for the clarification @PitaJ! I did a lot of experimenting but I guess I didn't get the right combination. I think I never tried naming the module with its extension. That might have been it. For anyone who might be interested in the actual solution, here it is: In file-explorer.js: define('azure/file-explorer', ['components'], function (components) { const FileExplorer = {}; FileExplorer.init = function () { // Init stuff here }); return FileExplorer; }); In plugin.json: "modules": { "azure/file-explorer.js": "static/lib/file-explorer.js" }, In admin.js: define('admin/plugins/azure', ['settings', 'azure/file-explorer'], function (settings, fileExplorer) { fileExplorer.init(); }); In main.js: $(document).ready(function () { require(['azure/file-explorer'], (fileExplorer) => { fileExplorer.init(); }); });

Hmm, ./nodebb build --verbose should give more info, don't think it displays the order of plugins though.

Hi all! I've run into an issue that when I deploy a new version of my theme/plugin, most users don't get any changes done until they do a hard refresh. This only seems to affect the client side Javascript, so everything looks updated, but in reality functionality gets lost. Has anyone stumbled upon something similar? Is there a better way to release code? The background in this is that I have forked Persona and built upon it, so all changes to the platform is basically in the theme. Is there a way to make sure all clients receive all updates? Thanks!

Hi all! I was wondering if there's a simple way to add my custom fields (from the ns-custom-fields plugin) to the regular edit.tpl. I'm making a private forum aimed at professionals and would really love it if I could have everything in one place. What I'm currently looking to add is Company, Title and possible some more in the future. An idea I have is to just put them in the available form and then using the custom-fields "API" in the backend (on save) to store them separately. Any ideas are welcome. Sorry to tag you (@Nicolas, the creator) but I believe you can answer this question quite easily. Thanks!

@baris Awesome, thanks a lot!

When I remove enctype="multipart/form-data" from the form in registerComplete.tpl it works. So this has to do with encryption and maybe that I don't have HTTPS on my local machine. So then my question is, why is this not on the form that transmits the username and password?

Thank you @baris for the swift response. I have no need for backwards compatibility in my theme, so I think I will hold off on bigger changes.

Thank you @PitaJ for pointing me in the right direction. I adapted my code to the link you sent me. (function (factory) { if (typeof module === 'object' && module.exports) { factory(require.main.require('benchpressjs')); } else { require(['benchpress'], factory); } }(function (Benchpress) { const logger = (data) => { console.log('Logger helper', data); return ''; }; const customHelpers = { register, logger, }; function register() { Object.keys(customHelpers).forEach(function (helperName) { Benchpress.registerHelper(helperName, customHelpers[helperName]); }); } register(); if (typeof module === 'object' && module.exports) { module.exports = customHelpers; } })); Just by doing this made it work client side. But then it stopped working server side. That was easily fixed though by running helpers.register in my library file. const helpers = require('./lib/helpers'); helpers.register(); Hope this helpes someone!

@baris Just what I needed. Thanks a lot!!