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).

custom meta tag

N
NgaNguyenDuy last edited by

Hi everyone, how can i custom meta tag?
Thank so much.
Reply Quote 0
1 Reply Last reply
psychobunny Admin last edited by
You can actually add meta tags in the Themes ACP under Custom JS.

The title is actually misleading, it actually should be called "Custom Header". So you can easily put
```
<meta name="custom" content="custom meta tag" />
```
for example, no problem.
Reply Quote 2
N 1 Reply Last reply
N
NgaNguyenDuy last edited by @psychobunny

@psychobunny said:

<meta name="custom" content="custom meta tag" />

Thank so much. He He.
Reply Quote 0
1 Reply Last reply

3
Posts

1675
Views

Suggested Topics

Tag cloud is bad
General Discussion • • meetdilip

8

0
Votes

8
Posts

1574
Views

E

I agree with your statment
P

Tags visible for guests
General Discussion • • pp81

3

0
Votes

3
Posts

895
Views

P

All checkboxes for guests are unticked. Yes, they can see the tags, not the topics. But the tags are also something they shouldn't see because it more or less discloses the content of the board.
custom metadata in a post
General Discussion • • teh_g

2

0
Votes

2
Posts

792
Views

Nope. You would need to make a plugin. There's no way to add any additional data to the post without writing your own functions to handle the submit action.
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)
P

Custom Homepage Issues
General Discussion • • peter

7

0
Votes

7
Posts

1828
Views

P

No luck with this. Will have to wait for @psychobunny to share some tips.