Error after purging a category (async?)

Solved Technical Support

Suggested Topics

  • 0 Votes
    24 Posts

    @baris Using the below site, reminding me of just how powerful Chrome Developers tools are, I was able to Copy As Curl the specific PUT command.

    Curl Convert

    Then using the same command and just changing the CID, I confirmed the same command works for all of them.

    This is what ended up working, it includes all the recorded headers, of which some will be removed as not necessary:

    curl '' \ -X 'PUT' \ -H 'Connection: keep-alive' \ -H 'Accept: */*' \ -H 'DNT: 1' \ -H 'x-csrf-token: H5FMJEaY-CthHWM_2Unzf7DtoPeryGq_JejE' \ -H 'X-Requested-With: XMLHttpRequest' \ -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36' \ -H 'Content-Type: application/json; charset=UTF-8' \ -H 'Origin:' \ -H 'Referer:' \ -H 'Accept-Language: en-US,en;q=0.9,zh;q=0.8,zh-CN;q=0.7,zh-TW;q=0.6,ja;q=0.5,ko;q=0.4,th;q=0.3' \ -H 'Cookie: _csrf=27ygKMdG0c0EyiVsJKAkKpId; express.sid=s%3AdODaXfUpLz7NTFsijWLq0d2rPUhH1Ki4.qkyxWOaxlBy%2BLDRpTYbhWS9QkD9IJE%2FRTN1vIhp7yV4' \ -H 'sec-gpc: 1' \ --data '{"backgroundImage":"/assets/uploads/category/category-84.jpg"}' \ --compressed \ --insecure

    Then using the cURL convert site, was able to save as javascript and modify to our needs so that we could loop through all categories.


  • 0 Votes
    17 Posts

    @djensen47 said in Category watch/ignore set default for all users?:

    @baris So the _key is as you described, the value is the user id, and the score is the watch state?

    That's correct, and the records do not exist until a user explicitly changes the setting on the category page. Until they change it the default from the ACP is used.

    There are 3 possible values.

  • 0 Votes
    3 Posts

    drag and drop works for me, it can be a little fiddly though

  • 0 Votes
    5 Posts

    What does node app --upgrade net you?

  • 0 Votes
    11 Posts

    I don't see any problems there thought. Except for the bad value for main, it is supposed to be a javascript file; But since other NodeBB themes share this bad value it should not break anything. o_O

    After a quick search with the search engine of my choice I've found this stackoverflow question with a similar issue. There doesn't seem to be a solution but moving your repo out of node_modules and either symlink (by hand; as the answer describes) or npm link it.