Closed wu-lee closed 3 years ago
Hello,
I suspect that a file is blocked by the module when not logged in. Do you have the same error when you log in?
I should allow file access based on a regex to allow all js
and css
files. When I have a little time I will try to update this.
No, the error doesn't seem to show up when I'm logged in.
This is the normal behaviour: when not logged in, URL access are restricted. When logged in, nothing is restricted anymore.
I have created a new release, it should automatically update the npm repo.
I no longer have a nodebb forum, can you test this new version and check:
1.0.1b is alive. https://www.npmjs.com/package/nodebb-plugin-private-forum
Thanks - currently running our forum without this package, but haven't had time to test it so far, sorry.
I just tried my plugin on a fresh NodeBB installation.
It appears that the behaviour you described is completely normal when you are not logged in. The Lavender theme seems not to handle the error when you are trying to access to a page that is protected by my module.
I am searching for a way to force the Lavender theme (or the nodeBB interface) to redirect to the login page.
After installing this plug-in (v1.0.0 on NodeBB v1.16.0, Lavender theme v5.0.17) , I've noticed new errors appearing both in the browser console, and the server logs.
To reproduce this, I visit the site as an anonymous user, and click on a public category title which is visible. This does nothing visible, but in the console logs are the following errors. These errors disappear when I disable this plug-in and rebuild, and re-appear again when it is enabled (and rebuilt). I don't seem to see these errors when visiting as a logged-in user.
And these server-side: