Tried to update some json files from translations folder of my language and I got the following error trying to build and restart Nodebb. Even after I reverted back the files I still got the error. If someone has any clue about this the help is much appreciated.

SyntaxError: Unexpected token 
 in JSON at position 4536
    at JSON.parse (<anonymous>)
    at /home/admin/web/mysite/public_html/src/meta/languages.js:105:41
    at /home/admin/web/mysite/public_html/node_modules/graceful-fs/graceful-fs.js:90:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:53:3)
2019-03-01T22:47:18.302Z [undefined/15635] - error: Unexpected token 
 in JSON at position 4536
SyntaxError: Unexpected token 
 in JSON at position 4536
    at JSON.parse (<anonymous>)
    at /home/admin/web/mysite/public_html/src/meta/languages.js:105:41
    at /home/admin/web/mysite/public_html/node_modules/graceful-fs/graceful-fs.js:90:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:53:3)

@jtsimoes Maybe @psychobunny has any clue about this. For what it does the plugin is very usefull.

@jtsimoes That happens when a category is not allowed to have questions. I see the problem occurs outside composer too.

@jtsimoes Checked. Plugin settings only allow questions to be enabled for all categories or just some of them, not make them default or not.

Also I notice that categories not ticked on plugin settings still have the dropdown button showing on composer area with "undefined" instead of "question".

QnA plugin enabled. Tried to post a topic. Clicked the arrow button next to submit button to select "Ask as a Question" and I had a topic as a question posted. But clicking that button didn't do apparently anything and I thought initially that it wasn't working.

Is there any way to show something there when "Post as Question" option is active? Also, don't know if only I have that problem in particular, but after I posted a question that way any new post I make defaults as a question post.

@Huỳnh-Phúc-Huy Thanks! I'll take a look at that one too.

@PitaJ Thank you!

@PitaJ Sorry for the late reply, the problem being mine.

I managed to have a simple lightbox - maybe too simple but it does what I need - on my images using this script, and your method to add the required class on the images.

The only problem I have now is the script requires only the <img> whithout the link wrap. In wich case the bug prior to 1.11.1 could have helped me.

Is there any way to deactivate the images.wrapImagesInLinks(posts); other than delete it from public/src/client/topic/posts.js?

I'm not shure how delete works on the Nodebb official forum. If someone reads the post, the problem was on my end. The plugin works as it should.

Last time I checked, prior to v1.11 update, I could make a post already submitted a QnA one by clicking the appropriate link on the post menu dropdown. Now I can't seem to find it there.

Also If I remember correctly, after selecting the best answer, I could select another one to be the best answer, or make the post unanswered. Something like that. I can't seem to find this option either.

Did I broke something on my site since then or those features are gone? Thank you for any response.

I need an image lightbox on my site. None of the available plugins seem to work as they weren't updated in a while. I'd be fine to do basic resizing of the img tag in CSS and open the link with a lightbox.

Unfortunatelly I have to add the lightbox class to link instead of the img tag and I found this piece of jquery, but it doesn't work.

jQuery( document ).ready( function(){
  jQuery( 'a[href$=".gif"], a[href$=".jpg"], a[href$=".png"]' ).addClass( 'lightbox' );
} );

If someone has any clue about this, thank you.

@youhosi Following your response did an upgrade and don't know how but all the themes are working now. Minus my custom theme that I guess it has some bad code in it.

Thank you.

@youhosi Every theme I pick, only thing I get is the default css( similar to nodebb) and nothing else compiled.

Did what you told me and everything i get is:

Clustering enabled: Spinning up 1 process(es).

2018-12-09T19:06:01.533Z [29876] - info: Initializing NodeBB v1.11.0 http://mywebsite
2018-12-09T19:06:04.226Z [29876] - info: [socket.io] Restricting access to origin: http://mywebsite:*
2018-12-09T19:06:04.896Z [29876] - info: Routes added
2018-12-09T19:06:04.899Z [29876] - info: NodeBB Ready
2018-12-09T19:06:04.906Z [29876] - info: Enabling 'trust proxy'
2018-12-09T19:06:04.910Z [29876] - info: NodeBB is now listening on: 0.0.0.0:4567

Still got no solution on this. Any help would really mean a lot.

Had a problem when I tried to update my forum from 1.10.2 to 1.11. Since my forum was at 99% ready to launch, not launched yet, and didn't had a fix then, downloaded only my custom theme and took the chance to install fresh everything, jumping from Ubuntu 16 to 18.

Now I have everything working minus themes less files that apparently are not compiled. Is there anything I am missing, I should look out for?

Thank you for any help.

@baris For me problem solved. With that ocasion, since the site wasn't launched but 99% almost there took the opportunity to make some cleaning and jump also to Ubuntu 18.

Trying to get my site from v1.10.2 to v1.11 and the upgrade parts goes till here

Error occurred
Error occurred during upgrade: MongoError: not authorized on mydatabase to execute command { reIndex: "searchtopic", lsid: { id: UUID("*******************") }, $db: "mydatabase" }
    at /home/admin/web/mywebsite/public_html/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:581:63
(...)

If someone has any clue about what's going wrong, thank you.

Thank you. Now I see how it works.

Needing a terms of use page found out that there is already a tos.tpl template inside theme folder. But I could't see it anywhere on the frontend.

How do I get to use it? Thank you for any help.

@PitaJ No error. But after your reply looked again and saw what I guess is the default way of doing this on Nodebb. And with $(window).on('action:ajaxify.end', function( ) it works as it should. Thank you.