The problem went away when I cleared my cookies.

My installation has been working generally well for quite a while, but now all of a sudden, I generally can't post anything. The screen says "Forbidden" and the log says "invalid csrf token", which is also what it says when I try to log out. Stopping and restarting nodebb didn't clear it up. Any suggestions?

@julian Works (once I upgraded to a compatible NodeBB)! Thanks again!

@pitaj Works great! Thanks!

I don't know what Bootbox is for, but evidently NodeBB 1.18.4 depends on Bootbox 5.5.2, which has a cross-site scripting vulnerability according to npm audit.

@dunlix I just need to try it out in the wee hours so it's less likely I crash the site while someone is trying to use it.

@dunlix I tried upgrading the plugin and the code tells me that it is not compatible with the version of NodeBB I have.

Awaiting resolution of https://community.nodebb.org/topic/16111/upgrade-from-nodebb-1-13-3

I tried an upgrade with ./nodebb upgrade, but my installation is still at 1.13.3.

Updating NodeBB...

1. Updating package.json file with defaults...  OK

2. Bringing base dependencies up to date...  started
npm WARN [email protected] requires a peer of nodebb-plugin-emoji@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of textcomplete@^0.14.2 but none is installed. You must install peer dependencies yourself.

audited 1363 packages in 11.977s

77 packages are looking for funding
  run `npm fund` for details

found 107 vulnerabilities (3 low, 51 moderate, 48 high, 5 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

3. Checking installed plugins for updates...  OK
4. Updating NodeBB data store schema...
Parsing upgrade scripts... 
OK | 0 script(s) found, 84 skipped
Schema update complete!


5. Rebuilding assets...  started
...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
...
[benchpress] warning: output bloat due to ambiguous inner BEGIN
     --> <unknown>:139:14
      |
  139 | 			<!-- BEGIN questions -->
      | 			           ^^^^^^^^^ `questions` could refer to the top-level value `questions` or the `.questions` property of the current element, so compiler must emit code for both cases
      | note: Migrate to modern syntax to avoid the ambiguity. This will become an error in the future.
...
[benchpress] warning: keyword outside an interpolation token is deprecated
     --> <unknown>:33:19
      |
   33 | 			{{{each icons}}}@value{{{end}}}
      | 			                ^^^^^^ help: wrap this in curly braces: `{@value}`
      | note: This will become an error in the v3.0.0

2021-10-25T11:31:44.536Z [4568/13825] - info: [build]                  templates  build completed in 1.296sec
2021-10-25T11:31:44.537Z [4568/13825] - info: [build]                  languages  build started
2021-10-25T11:31:53.959Z [4568/13825] - info: [build]                  languages  build completed in 9.421sec
2021-10-25T11:31:53.959Z [4568/13825] - info: [build]                     sounds  build started
2021-10-25T11:31:53.962Z [4568/13825] - info: [build]                     sounds  build completed in 0.003sec
2021-10-25T11:31:53.963Z [4568/13825] - info: [build] Asset compilation successful. Completed in 40.021sec.


                                                                                    NodeBB Upgrade Complete!

@julian said in Codepen Plugin:

I've fixed up the codepen plugin and published it to npm

Thanks!

If I just uninstall it and reinstall it from the control panel in NodeBB, does that get the new version?

@baris said in Codepen Plugin:

iframely plugin

Looks like that's a paid license, so would be a no-go for us.

@pitaj Yes, I did.

I have nodebb-plugin-codepen 0.2.0 (Latest 0.2.0) installed and active on NodeBB v1.13.3, but it does not work. A user has tested it on the present support forum, where it does work. Any suggestions?

@pitaj NodeBB v1.13.3. nodebb-plugin-composer-default 6.3.25

@dunlix said in Tiny Text-Entry Field:

try deleting the composer plugin, rebuild, re-install composer plugin, rebuild

What might have made it necessary to do that? We have nothing customized except the config of how NodeBB talks to the mailer, plus maybe some settings, e. g. the default notification settings for new users.

On my installation, when a user starts to write a post, the input field is about 3/4 inch high. In the present support forum, it's more like 2.5in. What could be the cause of this difference?

@pitaj Thanks. Your advice shows me that should the same thing happen in a production installation, there would likely be some way to solve it. So I would like to mark this question as solved, but I don't see how that is done. Is that strictly an admin function here?

@pitaj, NodeBB 1.13.4-5. Node v12.18.3. The database is on a local copy of MongoDB. It happens every single time.

$ cat config.json
{
    "url": "http://staging.votingtheory.org",
    "secret": [censored],
    "database": "mongo",
    "mongo": {
        "host": "127.0.0.1",
        "port": 27017,
        "username": "",
        "password": "",
        "database": "nodebb",
        "uri": "mongodb://nodebb:[censored]@localhost/nodebb"
    }
}

Now I will try disabling all plugins. Restarting maybe would have sufficed, but I am telling it to rebuild. Now I am able to register!

If you tell me your public key, I will arrange your access.

I installed NodeBB and at first it worked, including with registrations, but somewhere along the way, it became unable to accept a registration as a new user. It tells the person they failed a CAPTCHA, but no CAPTCHA is visible. Can anyone suggest how to figure out what broke it? I have another installation going that does not have this problem. I installed it fresh. On the one that broke, I did disable a couple of plugins, but I have re-enabled them, and checked that the set of enabled plugins in the installation that fails and the one that works are now the same. I configured both installations to send e-mail via the submission port. Haven't done anything else to them that I can remember.