Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

How to preview emoji in v1.7.4

S
sharonyue last edited by

I remember that when I was using v1.6.0, when I type :, the corresponding emoji can show up, and I can click the emoji. But in v1.7.4, I have to click the emoji button in the panel to select the emoji?

When I type :, no emoji show up?
Reply Quote 1
1 Reply Last reply
PitaJ Global Moderator last edited by @sharonyue

@sharonyue if you type :e do some emoji show up? The plugin was modified to not trigger on just a single colon, to avoid it triggering when typing code or at other times when people don't want emoji to be inserted.
Reply Quote 0
1 Reply Last reply
S
sharonyue last edited by

Thank you. To others: problem fixed after reloading the forum.
Reply Quote 0
1 Reply Last reply

3
Posts

571
Views

Suggested Topics

0.6.1 - 0.7.0
General Discussion • • lombisi

11

0
Votes

11
Posts

2996
Views

npm install -g n # Install n globally n 0.10.33 # Install and use v0.10.33 $ git fetch $ git checkout v0.7.x $ git merge origin/v0.7.x ./nodebb upgrade It was dissolved
S

Upgrading NodeBB 0.7.1 Merge Conflicts?
General Discussion • • SimonQ

7

0
Votes

7
Posts

1778
Views

S

@julian Thanks! everything is great now! Upon npm i I received this at the end npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/user/nodebb/npm-debug.log npm ERR! not ok code 0 Is that normal?
Custom Theme broken as result of upgrade from 1.5.3 to 1.7.3
General Discussion • • Gus Surarez

1

0
Votes

1
Posts

674
Views

I work on nodebb 1.5.3 and accidentally made the grave mistake of installing a plugin using ACP and ended up losing all my development repos of non 'npm'ed plugins. At that point I decided to upgrade to latest 1.7.3 release since a fix (#6032) for this issue was supposed to be committed into that build. While I checked breaking change lists for 1.6.0 and 1.7.0, apparently I have over looked something since my list/grid topic-list show up all messed up (with no errors in console). I have a bootstrap based listview and gridview of the topics and I use JS code to select between them but now my page layout is gone like one of the libraries is not loading but I am not sure which one since I don't use anything other than jquery and bootstrap.I cannot figure this out but suspect it may be issue (#5980.) Any help would be appreciated and thank you in advance. Edit: I get the following error intermittently after several clicks and I am hoping to be related: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12) Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12) 2017-12-31T06:55:43.950Z [1840] - error: /category/14/news Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12) Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12) 2017-12-31T06:55:49.005Z [1840] - error: /category/14/news Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12) Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12) ... some more errors I get after refreshes: 2017-12-31T07:42:50.130Z [13716] - error: /category/5/general Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12) Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js: Script execution timed out. at ContextifyScript.Script.runInContext (vm.js:53:29) at ContextifyScript.Script.runInNewContext (vm.js:59:15) at Object.runInNewContext (vm.js:112:38) at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6) at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53) at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16 at tryToString (fs.js:513:3) at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
What does "Top 5 plugin downloads in the past 7 days" on the packages stats site mean?
General Discussion • • Dravere

2

0
Votes

2
Posts

470
Views

The "top downloads" pie chart is a little misleading, actually. The package manager itself doesn't have any visibility on package downloads because those are done through npm, and not nbbpm itself. What it does track is how many people ask nbbpm to suggest a version to download. For example, if you run v1.8.1 and you want to download a plugin, the latest version might not be compatible, so the ACP will query nbbpm for a suggested version. That's counted as a "download" (since the "suggest" call is done behind the scenes and is opaque to the end user). So you could be seeing true downloads... people downloading your plugins... or someone's just hammering GET /api/v1/suggest?package=nodebb-plugin-prometheus a lot
Status v1.1.1
General Discussion • • Jenkler

12

0
Votes

12
Posts

3154
Views

Cool, all forums update 2 v1.1.2 now. Everything seams to work great

| |

How to preview emoji in v1.7.4

Suggested Topics

0.6.1 - 0.7.0 General Discussion • • lombisi

Upgrading NodeBB 0.7.1 Merge Conflicts? General Discussion • • SimonQ

Custom Theme broken as result of upgrade from 1.5.3 to 1.7.3 General Discussion • • Gus Surarez

What does "Top 5 plugin downloads in the past 7 days" on the packages stats site mean? General Discussion • • Dravere

Status v1.1.1 General Discussion • • Jenkler

0.6.1 - 0.7.0
General Discussion • • lombisi

Upgrading NodeBB 0.7.1 Merge Conflicts?
General Discussion • • SimonQ

Custom Theme broken as result of upgrade from 1.5.3 to 1.7.3
General Discussion • • Gus Surarez

What does "Top 5 plugin downloads in the past 7 days" on the packages stats site mean?
General Discussion • • Dravere

Status v1.1.1
General Discussion • • Jenkler