@julian Thank you. I got it done, yes, I realize during upgrade it may get over written,I hv to do it again.

Hello,
I need couple of minor cosmetic changes in the login page, as given in the image. Will be great if some one can guide me where to make this change.

Hello,

1. I am running on 9.3 and today, when tried to click on Plugins-->Install Plugin menu from ACP, no action was happening (like bringing in plugin list)
2. So I was checking the log file on the server and noticed whenever I clicked Install Plugin menu from ACP, nodebb automatically shuts itself down and restarting.

I could not understand any obvious error...some warning about couple of plugin compatibility are show in log, but that were always there for a month and it did not cause any issue so far till now.

In the last weeks or so, I installed few plugins , but i did not realize this issue or this was never there till today

1. Uninstalled -- nodebb-plugin-google-adsense

2. Installed -- nodebb-plugin-adsense

3. Installed -- nodebb-plugin-ns-likes

4. Installed -- nodebb-widget-ns-stats

Following is the log file output, Pls help...

15/3 15:16 [13039] - info: NodeBB Ready
15/3 15:16 [13039] - info: Enabling 'trust proxy'
15/3 15:16 [13039] - info: NodeBB is now listening on: 0.0.0.0:4567
15/3 15:18 [13039] - error: TypeError: Cannot assign to read only property 'id' of <
at Object.Plugins.normalise (/home/ngsankar/nodebb/src/plugins.js:226:20)
at Request._callback (/home/ngsankar/nodebb/src/plugins.js:217:12)
at Request.self.callback (/home/ngsankar/nodebb/node_modules/request/request.js:198:22)
at Request.emit (events.js:110:17)
at Request.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:1035:10)
at Request.emit (events.js:129:20)
at IncomingMessage.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:962:12)
at IncomingMessage.emit (events.js:129:20)
at _stream_readable.js:908:16
at process._tickDomainCallback (node.js:381:11)
TypeError: Cannot assign to read only property 'id' of <
at Object.Plugins.normalise (/home/ngsankar/nodebb/src/plugins.js:226:20)
at Request._callback (/home/ngsankar/nodebb/src/plugins.js:217:12)
at Request.self.callback (/home/ngsankar/nodebb/node_modules/request/request.js:198:22)
at Request.emit (events.js:110:17)
at Request.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:1035:10)
at Request.emit (events.js:129:20)
at IncomingMessage.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:962:12)
at IncomingMessage.emit (events.js:129:20)
at _stream_readable.js:908:16
at process._tickDomainCallback (node.js:381:11)
15/3 15:18 [13039] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
15/3 15:18 [13039] - info: [app] Database connection closed.
15/3 15:18 [13039] - info: [app] Web server closed to connections.
15/3 15:18 [13039] - info: [app] Shutdown complete.
15/3 15:18 [13064] - info: Time: Tue Mar 15 2016 15:18:20 GMT+0530 (IST)
15/3 15:18 [13064] - info: Initializing NodeBB v0.9.3
15/3 15:18 [13064] - info: [database] Checking database indices.
15/3 15:18 [13064] - warn: [socket.io] Clustering detected, you are advised to configure Redis as a websocket store.
15/3 15:18 [13064] - warn: [plugins/nodebb-plugin-sso-google] Hook filter:user.delete is deprecated, please use an alternative

15/3 15:18 [13064] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p PLUGINNAME to disable it.

• nodebb-plugin-telegram-notifications
• nodebb-plugin-recent-cards

15/3 15:18 [13064] - info: [User-Invitations] Initializing User-Invitations...
15/3 15:18 [13064] - info: [User-Invitations] Synced settings: restrictRegistration=0, invitedUsers=[], defaultInvitations=25, inviteGroup=registered-users
15/3 15:18 [13064] - info: NodeBB Ready
15/3 15:18 [13064] - info: Enabling 'trust proxy'
15/3 15:18 [13064] - info: NodeBB is now listening on: 0.0.0.0:4567

@Nicolas Thank you, i could make it work with this help. It works great.

@Nicolas Thank you for your reply.

1. After the plugin is activated, should I automatically have the file likes_tpl created under /nodebb/node_modules/nodebb-theme-persona/templates/partials/topic/ ?

2. I didnt hv any file created in that path.

3. I uninstalled the plug i ACP and installed in server using npm install nodebb-plugin-ns-likes

4. Got the following warnings....is it an issue ? also i dont see likes_tpl . should i create the file myself ? I know it sounds as a basic question, but will ask anyway. thank you for your patience.

ngsankar@T****:~/nodebb$ npm install nodebb-plugin-ns-likes
npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/mocha/node_modules/glob/node_modules/minimatch requires lru-cache@'2' but will load npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/lru-cache, npm WARN unmet dependency which is version 3.2.0 npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/grunt/node_modules/minimatch requires lru-cache@'2' but will load npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/lru-cache, npm WARN unmet dependency which is version 3.2.0 npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/grunt/node_modules/findup-sync/node_modules/glob/node_modules/minimatch requires lru-cache@'2' but will load npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/lru-cache, npm WARN unmet dependency which is version 3.2.0 npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/grunt-contrib-watch/node_modules/gaze/node_modules/globule/node_modules/minimatch requires lru-cache@'2' but will load npm WARN unmet dependency /home/ngsankar/nodebb/node_modules/lru-cache, npm WARN unmet dependency which is version 3.2.0

@Nicolas I came across this plug in and its a great one to make it more like social media where users already are used to.

I have installed this one from ACP and activated the plug-in. I am on nodebb 9.3.
I am not a programmer and dont understand scripts.

If you could help me with the following, will be great. I located the file post.tpl under the path in my server /nodebb/node_modules/nodebb-theme-persona/templates/partials/topic/post.tpl

1.where exactly i should add the line <!-- IMPORT partials/topic/likes_post.tpl -->
2.which exact line i should remove to (delete default one, with chevrons) is
in it will be very helpful.
**3. Also as part of the installation, is there a file /nodebb/node_modules/nodebb-theme-persona/templates/partials/topic/likes_post.tpl expected to be created ? I don't see such file in the folder.

Any advice and help will be useful.

Bu this still not solving "YouTube videos are too large on mobile devices" the original problem in this thread. Other than this CSS (and ignore the important warning) , should o do anything else to solve the original problem ?

I am trying to add the above code in customer css, getting warning...as below and youtube side is not responsive in mobile, any pointer /help ? .

Working Gr8. Thanks for a gr8 plug in.

Following are may questions/clarification/feedback

1. It seems to be working in pull mode from telegram (ie. i hv to give /recent or /read topicid etc) to get info from forum.
2. Is it possible to make it work in push mode (when a topic gets new post, can it be pushed to telegram if i am subscribed to it ?

The plugin has a great potential to be a killer one, especially the more and more people are getting into telegram for obvious advantages of multi platform / multi phone.

I tried various options to test..this is my observation.

1. I have used a facebook id to login into this forum, which has read the email id and correct email is is displayed in the profile.
2. I have used the same facebook id in my own forum, there login is successful, but right email is not displayed (instead it is giving email like ([email protected]).
3. Obviously there is something wrong in my forum vs this forum, as same facebook id not returning email id for my forum , but it does return here.
4. Surely i hv to update something in my forum to get the email id.,Any pointer on where to start and proceed to investigate further ?

@exodo . thank you . I managed to install and configure. However after first msg is sent from telegram, nodebb got broken and stopped working.

Its strange , there is no reference to the plugin in the error log...luckily i was clearly noting down action i was doing...and guessed something going wrong here...after i removed the plug in , forum got up and running...i am able to reproduce it now..v0.8.2 is not liking something, but dont know what. Hope u r able to find it...I like the plug in..if this is resolved,...i will surely use it..thanks for ur effort...

following is the error log

3/11 13:14 [15929] - info: NodeBB v0.8.2 Copyright (C) 2013-2014 NodeBB Inc.
3/11 13:14 [15929] - info: This program comes with ABSOLUTELY NO WARRANTY.
3/11 13:14 [15929] - info: This is free software, and you are welcome to redistribute it under certain conditions.
3/11 13:14 [15929] - info:
3/11 13:14 [15929] - info: Time: Tue Nov 03 2015 13:14:10 GMT-0500 (EST)
3/11 13:14 [15929] - info: Initializing NodeBB v0.8.2
3/11 13:14 [15929] - warn: [plugins/nodebb-plugin-sso-facebook] Hook filter:user.delete is deprecated, please use an alternative
3/11 13:14 [15929] - warn: [plugins/nodebb-plugin-sso-google] Hook filter:user.delete is deprecated, please use an alternative
3/11 13:14 [15929] - info: NodeBB Ready
3/11 13:14 [15929] - info: NodeBB is now listening on: 0.0.0.0:4567
3/11 13:14 [15929] - error: TypeError: undefined is not a function
at /home/ngsankar/nodebb/src/user/posts.js:37:12
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:697:13
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:52:16
at done (/home/ngsankar/nodebb/node_modules/async/lib/async.js:248:21)
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:44:16
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:694:17
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:173:37
at /home/ngsankar/nodebb/src/user.js:405:5
at fireFilterHook (/home/ngsankar/nodebb/src/plugins/hooks.js:86:11)
at Object.Plugins.fireHook (/home/ngsankar/nodebb/src/plugins/hooks.js:70:5)
at filterIsModerator (/home/ngsankar/nodebb/src/user.js:400:12)
at /home/ngsankar/nodebb/src/user.js:462:6
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:697:13
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:52:16
at done (/home/ngsankar/nodebb/node_modules/async/lib/async.js:248:21)
at /home/ngsankar/nodebb/node_modules/async/lib/async.js:44:16

@julian as per your suggestion here https://github.com/julianlam/nodebb-plugin-sso-facebook/issues/13

I added console.log(profile); in library.js
as per the link below
https://github.com/julianlam/nodebb-plugin-sso-facebook/blob/e042fac332908b136030cdd3063a221cdb960d36/library.js#L61

The output log give following output and hope this gives you some clue you are looking for

478 { id: '1176537305694066',
479 username: undefined,
480 displayName: 'Gomathi Sankar Namasivayam',
481 name:
482 { familyName: undefined,
483 givenName: undefined,
484 middleName: undefined },
485 gender: undefined,
486 profileUrl: undefined,
487 provider: 'facebook',
488 _raw: '{"name":"Gomathi Sankar Namasivayam","id":"1176537305694066"}',
489 _json: { name: 'Gomathi Sankar Namasivayam', id: '1176537305694066' } }

just checked and realized even i am hving same issue, email is looks like [email protected].

My Log file shows some warning ..is that giving any clue ? I had posted this log in different thread yday.
node app

31/10 05:47 [5865] - info: Initializing NodeBB v0.8.2
31/10 05:47 [5865] - info: [database] Checking database indices.
31/10 05:47 [5865] - warn: [plugins/nodebb-plugin-sso-google] Hook filter:user.delete is deprecated, please use an alternative
31/10 05:47 [5865] - warn: [plugins/nodebb-plugin-sso-facebook] Hook filter:user.delete is deprecated, please use an alternative
31/10 05:47 [5865] - info: NodeBB Ready

@exodo yes, i did npm install inside plugin folder. any idea when 0.9 is expected to release ?

Hello,
I am using nodebb 0.8.2 on mongodb 3.07/ nodejs v0.10.25
and configured nodebb-plugin-sso-google & nodebb-plugin-sso-facebook.
Both Plugin are working perfectly, but I am getting following warning on node app.
-- Can I ignore this as its working fine or should I do something to fix this.
any advise is much appreciated...

node app
30/10 15:36 [1470] - info: NodeBB v0.8.2 Copyright (C) 2013-2014 NodeBB Inc.
30/10 15:36 [1470] - info: This program comes with ABSOLUTELY NO WARRANTY.
30/10 15:36 [1470] - info: This is free software, and you are welcome to redistribute it under certain conditions.
30/10 15:36 [1470] - info:
30/10 15:36 [1470] - info: Time: Fri Oct 30 2015 15:36:43 GMT-0400 (EDT)
30/10 15:36 [1470] - info: Initializing NodeBB v0.8.2
30/10 15:36 [1470] - info: [database] Checking database indices.
30/10 15:36 [1470] - warn: [plugins/nodebb-plugin-sso-google] Hook filter:user.delete is deprecated, please use an alternative
30/10 15:36 [1470] - warn: [plugins/nodebb-plugin-sso-facebook] Hook filter:user.delete is deprecated, please use an alternative
30/10 15:37 [1470] - info: NodeBB Ready
30/10 15:37 [1470] - info: Enabling 'trust proxy'
30/10 15:37 [1470] - error: Error: listen EADDRINUSE
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1039:14)
at listen (net.js:1061:10)
at Server.listen (net.js:1135:5)
at listen (/home/ngsankar/nodebb/src/webserver.js:180:17)
at /home/ngsankar/nodebb/src/webserver.js:57:3
at EventEmitter.<anonymous> (/home/ngsankar/nodebb/src/emitter.js:17:5)
at EventEmitter.emit (events.js:92:17)
at /home/ngsankar/nodebb/src/meta/js.js:218:12
at Object.oncomplete (fs.js:107:15)
30/10 15:37 [1470] - error: NodeBB address in use, exiting...

@exodo , I want to use this plugin. After activating the plugin, it seems to break something and bringing nodebb down. Not 100% sure if this is to do with this plugin, but after removing the plugin, nodebb is back. log output is below, any advise ? thanks.

I am using nodebb v0.8.2 , mongodb 3.0.7 with nodejs v0.10.40.

30/10 10:40 [12462] - info: Time: Fri Oct 30 2015 10:40:44 GMT-0400 (EDT)
30/10 10:40 [12462] - info: Initializing NodeBB v0.8.2
30/10 10:40 [12462] - info: [database] Checking database indices.
30/10 10:40 [12462] - warn: [socket.io] Clustering detected, you are advised to configure Redis as a websocket store.
30/10 10:40 [12462] - warn: [plugins/nodebb-plugin-sso-google] Hook filter:user.delete is deprecated, please use an alternative
30/10 10:40 [12462] - warn: [plugins/nodebb-plugin-sso-facebook] Hook filter:user.delete is deprecated, please use an alternative
30/10 10:40 [12462] - error: ReferenceError: callback is not defined
at /home/ngsankar/nodebb/node_modules/nodebb-plugin-telegram-notifications/library.js:76:11
at handleCallback (/home/ngsankar/nodebb/node_modules/mongodb/lib/utils.js:96:12)
at /home/ngsankar/nodebb/node_modules/mongodb/lib/collection.js:1322:5
at handleCallback (/home/ngsankar/nodebb/node_modules/mongodb/lib/utils.js:96:12)
at /home/ngsankar/nodebb/node_modules/mongodb/lib/cursor.js:666:5
at handleCallback (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:244:5)
at setCursorNotified (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:564:3)
at /home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:672:16
at queryCallback (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:323:5)
at Callbacks.emit (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:95:3)
at null.messageHandler (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:243:23)
at Socket.<anonymous> (/home/ngsankar/nodebb/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)
ReferenceError: callback is not defined
at /home/ngsankar/nodebb/node_modules/nodebb-plugin-telegram-notifications/library.js:76:11
at handleCallback (/home/ngsankar/nodebb/node_modules/mongodb/lib/utils.js:96:12)
at /home/ngsankar/nodebb/node_modules/mongodb/lib/collection.js:1322:5
at handleCallback (/home/ngsankar/nodebb/node_modules/mongodb/lib/utils.js:96:12)
at /home/ngsankar/nodebb/node_modules/mongodb/lib/cursor.js:666:5
at handleCallback (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:244:5)
at setCursorNotified (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:564:3)
at /home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:672:16
at queryCallback (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:323:5)
at Callbacks.emit (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:95:3)
at null.messageHandler (/home/ngsankar/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:243:23)
at Socket.<anonymous> (/home/ngsankar/nodebb/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)
30/10 10:40 [12462] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
30/10 10:40 [12462] - info: [app] Database connection closed.

net.js:1237
throw new Error('Not running');
^
Error: Not running
at Server.close (net.js:1237:11)
at shutdown (/home/ngsankar/nodebb/app.js:294:36)
at process.<anonymous> (/home/ngsankar/nodebb/app.js:174:3)
at process.emit (events.js:95:17)
at process._fatalException (node.js:301:26)

@psychobunny thanks for those good words. Being a newbee, i had done number of trial and error on installation and noted down the steps for my reference. if its useful for someone , happy to share being part of the community. Thanks for ur suggestion for write-up on digital ocean, i will try to make it more detailed and simpler and post it when i hv little time.

1. Create Droplet
2. Give your preferred Droplet name “Test” (please given the name u want, I will use “Test” for this example.
3. Select Droplet Size as required ($5, with 512 MB is sufficient)
4. Choose Desire Region for Droplet
5. Select Default Image Ubuntu 14.04 X 64
6. Ignore SSH Option
7. Create Droplet
8. Your IP Address/Initial root Password of the Droplet Sent to your email id.
9. Login root & password sent. (either use digital ocean console or putty for windows)
10. Create a new user “ngsankar”(please give your desired user id and note the password being given) and give “sudo” access to the user with following command at root
    a. root@test:~# adduser ngsankar
    b. **root@test:~# **adduser ngsankar sudo
11. logout of root
12. login again to the droplet using “ngsankar” and use the password given at the user creation
13. Execute the following commands
    a. ngsankar@test:~$ sudo apt-get install git nodejs nodejs-legacy npm redis-server imagemagick build-essential
    b. ngsankar@test:~$ sudo add-apt-repository ppa:chris-lea/redis-server
    c. ngsankar@test:~$ sudo apt-get update
    d. ngsankar@test:~$ sudo apt-get install redis-server
    e. ngsankar@test:~$ git clone -b v0.8.x https://github.com/NodeBB/NodeBB.git nodebb
    f. ngsankar@test:~$ cd nodebb
    g. ngsankar@test:~$ npm install --production
    h. ngsankar@test:~$ npm start
    i. ngsankar@test:~$ ./nodebb setup (Go with default values for all the quesitons here, except for user name / password , you can decide, which will be nodebb admin...)
    j. ngsankar@test:~$ ./nodebb start
    k. ngsankar@test:~$ node app (check if nodebb is running properly)
14. Now you can see nodebb @ yourip:4567, and welcome to nodebb !!! !!!

@gvimlan, @BDHarrington7 , were you able to get this resolved ?

1. took a snapshot of the droplet.
2. removed node and reinstalled as suggested.
3. Same node version and ended up same error..