@julian said in Google Recaptcha v3 not working:

As far as I know ReCAPTCHA v3 should be working, I'll let @bentael know if there's been a change.

Fine, thanks.

@oplik0 said in Google Recaptcha v3 not working:

v3 is not just "a better reCAPTCHA" and it is not replacing v2.

v3 only offers "invisible" reCAPTCHA, but even if Spam Be Gone supported that (it doesn't yet) it still wouldn't work because it passes different data.
reCAPTCHA v2 is binary - either user is a robot or not.
v3 doesn't just pass "true||false" but instead passes a score from 0.0 to 1.0 and it's up to the application to determine what score is a success. It also never shows user a challenge as it's not supposed to interrupt the user in any way.

So to sum it up: for Spam Be Gone to support v3 would mean changing the way it handles reCAPTCHA and I'm not even sure if it's a good idea. v3 is supposed to continuously chceck if user is a bot without interruptions, so it's best used for frequent user actions like posting or login, not for things like registration that happen once per user and it's not a big deal if it interrupts user with a challenge. So I'd say it'd be better for Spam Be Gone to extend its functionally to use v3 on login and posting, and leave v2 on the registration page.

That convinced me Thanks a lot.
Unfortunately I'm not a developer and do not know how to develop a plugin, but I'll highly appreciate if it's developed by anyone (NodeBB team or another mate).

My Q/A forum for python programming language
https://pythonforum.ir

Hello,

I have enabled Spam Be Gone plugin to use Google Recaptcha, but I see that I only can use v2, and v3 is not working.
When I enter v3 site and secret key, I see that the key does not work.
I use v1.12.2 on VPS.

Could you help me if there's something to fix at my end?

@julian said in How to be noticed of new posts by email?:

@inna hello!

This is likely the plugin you are looking for

https://github.com/NodeBB/nodebb-plugin-category-notifications

@julian hello,

Thanks

@baris that was fine and nothing was wrong with hierarchy.
It seemed it took some time to affect the changes. Now it's as you wrote down, and my forum is working.
The issue is solved, thanks.

@pitaj thanks a lot, it works fine:)
Thanks a lot for helping me.

@pitaj Sure, why not:)
In the path /to_your_nodebb_path/node_modules/nodebb-theme-persona/library.js (or whatever file and path you want to add), after the first line which is 'use strict';, add these lines below the first line:

const helpers = require.main.require('./src/controllers/helpers');
const categories = require.main.require('./src/categories');
const meta = require.main.require('./src/meta');
const relative_path = require.main.require('nconf').get('relative_path');
helpers.buildCategoryBreadcrumbs = async function (cid) {
	const breadcrumbs = [];

	while (parseInt(cid, 10)) {
		/* eslint-disable no-await-in-loop */
		const data = await categories.getCategoryFields(cid, ['name', 'slug', 'parentCid', 'disabled', 'isSection']);
		if (!data.disabled) {
			breadcrumbs.unshift({
				text: String(data.name),
				url: `${relative_path}/category/${data.slug}`,
				cid: cid,
			});
		}
		cid = data.parentCid;
	}
		if (meta.config.homePageRoute && meta.config.homePageRoute !== 'categories') {
			breadcrumbs.unshift({
				text: '[[global:header.categories]]',
				url: `${relative_path}/categories`,
			});
		}

		breadcrumbs.unshift({
			text: '[[global:home]]',
			url: `${relative_path}/`,
		});

	return breadcrumbs;
};

Then comment out line starting with var meta by adding two //:

//var meta = require.main.require('./src/meta');

Then you can restart by either of these ways:

• /nodebb_path/nodebb restart
• service nodebb restart
• systemctl restart nodebb

Regarding custom plugin, I'll consider it soon.

@twissell Since I had your problem at the beginning of starting my forum. you should both edit your config.json file and /etc/nginx/sites-available/your_doman.conf file.

Here is my config.json file:

{
    "url": "http://pythonforum.ir",
    "secret": "SECRET",
    "database": "mongo",
    "port": "4567",
    "mongo": {
        "host": "IP",
        "port": "PORT",
        "username": "user",
        "password": "password",
        "database": "db",
        "uri": ""
    }

and here is my /etc/nginx/sites-available/your_doman.conf file:

server {
    listen 80;
    server_name pythonforum.ir www.pythonforum.ir;
    root /path_to_nodebb;
    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:4567;
        proxy_redirect off;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

Of course my website is running in SSL, but it should work for your without SSL too.