Hi. Faced such a problem. The solution is somewhere here on the forum. It is necessary to execute a script in the mongo console. Need to search.
db.objects.update({_key: "config"}, {$set: {cookieDomain: ""}});
I can be mistaken.
Hi. Faced such a problem. The solution is somewhere here on the forum. It is necessary to execute a script in the mongo console. Need to search.
db.objects.update({_key: "config"}, {$set: {cookieDomain: ""}});
I can be mistaken.
@BuZz said in "Recent cards" not working, NodeBB 1.4.5:
you need to use v 0.3.1 for nodebb v1.4.5
npm i [email protected] --save
Thanks!
It is working!
Help me!
Translate google, sorry.
Noticed when upgrading to 1.4.5 on the running forum. Reproduced on the clean version 1.4.5. There is nothing suspicious in the logs. In the search here on the forum did not find anything.
Are there any ideas where to look for a mistake?
@JasperNL отлично выглядит!
@Kalbaskin отличное решение по Тунгуске! Литвинов видел ?
Good work!
@Jenkler Translated via Google.
The domain expired for several months, trying to go at it a few times during this time.
You probably have contact details for a person who was taken for the support of this forum? You sent him letters, he is responsible?
Очень жаль, если форум российской поддержки просто так прикроется без объяснения причин.
@mechanix vi ./forum/node_modules/nodebb-plugin-recent-cards/static/templates/partials/nodebb-plugin-recent-cards/header.tpl and restart nodebb
Replaced 56 line here
vi /home/node/forum/src/database/mongo/main.js
@baris
Sumptuously! Search works! Many thanks! Problem solved! Close the topic!
I used to think that such behavior could be due to mongorestore but testbed tried several times to repeat, everything works like clockwork. In production for some reason, there is an error. When you try to search obviously also returns an error, you can not perform the action because the argument is not a numeric value. So somewhere in the logic determined that the value may
@baris
[root@localdomain ~]# mongo --version
MongoDB shell version: 3.2.0
[root@localdomain ~]#
Thanks!
@baris Ok, thk. 24h
@Apxukoc said:
'limit' field must be numeric
I have two now. One search works, the other does not.
Everywhere running MongoDB. The problem is not in the database. You need to change your search, this line says "... limit 'field must be numerik ..."
16/12 14:02 [3148] - [31merror[39m: /api/search
MongoError: Failed to parse: { find: "searchpost", filter: {}, projection: { _id: 0, id: 1 }, limit: "50" }. 'limit' field must be numeric.
at Function.MongoError.create (/home/node/forum/node_modules/mongodb/node_modules/mongodb-core/lib/error.js:31:11)
at queryCallback (/home/node/forum/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:282:36)
at Callbacks.emit (/home/node/forum/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:95:3)
at null.messageHandler (/home/node/forum/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:249:23)
at Socket.<anonymous> (/home/node/forum/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:262:22)
at Socket.emit (events.js:95:17)
at Socket.<anonymous> (stream_readable.js:765:14)
at Socket.emit (events.js:92:17)
at emitReadable (_stream_readable.js:427:10)
at emitReadable (_stream_readable.js:423:5)
Use apache or nginx.
I insert a screenshot of the error when trying to link the search.
In any case, the problem is solved in one line.
Help me .
@william.owen
This suggests that it is not in the driver connection and not in the installation script. It tells us that the database connection is not possible, even though you have previously reported that the port is open.
@julian
I write through Google Translate, sorry.
I needed a script run at boot time, I got it
The only thing you surely noticed that there will be no check to verify the process. But such monitoring I solved by Zabbix
telnet localhost 6379 ?
@william.owen
telnet localhost 6379 ?
netstat -npl | grep 6379 && echo 'Port open. Good.' || echo 'Port Closed. Redis started ?'