@PitaJ said in Help with Upgrade to v1.13.x:

@Michael-Pfaff yeah I'd check git status before doing anything and run reset if there are changes

Much appreciated @PitaJ!

That seemed to work. Looks like there's a plugin causing the site to bug out.

I believe this is fixed in the latest master branch.

This is from my logs:

2019-05-01T23:05:47.795Z [4567/1956] - info: [plugins/spam-be-gone] Settings loaded 2019-05-01T23:05:47.858Z [4567/1956] - info: Routes added 2019-05-01T23:05:47.860Z [4567/1956] - info: NodeBB Ready 2019-05-01T23:05:47.867Z [4567/1956] - info: Enabling 'trust proxy' 2019-05-01T23:05:47.872Z [4567/1956] - info: NodeBB is now listening on: 0.0.0.0:4567 2019-05-01T23:06:46.203Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:44.904Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:45.822Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:46.745Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:47.671Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:48.797Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:49.637Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:50.764Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:51.806Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:52.799Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:53.673Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:54.520Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:55.402Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:56.383Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:57.203Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:58.085Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:58.957Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:19:59.803Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:20:00.659Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:20:01.574Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:20:09.481Z [4567/1956] - error: /login invalid csrf token 2019-05-01T23:37:11.087Z [4567/1956] - info: [plugin/iframely] iframely responded with error: {"status":417,"error":"Iframely could not fetch the given URL. 429"}. Url: http://www.wdrb.com/story/39585380/its-game-on-during-nerdlouvia. Api call: http://iframe.ly/api/iframely?origin=nodebb&align=left&api_key=6973ed56efecf5d8548108&url=http%3A%2F%2Fwww.wdrb.com%2Fstory%2F39585380%2Fits-game-on-during-nerdlouvia 2019-05-02T00:43:42.736Z [4567/1956] - info: [plugin/iframely] iframely responded with error: {"status":403,"error":"The page is private and requires a login."}. Url: https://hangouts.google.com/hangouts/_/qo43i4llbzdv5gmvxnb4ajunqee. Api call: http://iframe.ly/api/iframely?origin=nodebb&align=left&api_key=6973ed56efecf5d8548108&url=https%3A%2F%2Fhangouts.google.com%2Fhangouts%2F_%2Fqo43i4llbzdv5gmvxnb4ajunqee 2019-05-02T01:32:30.455Z [4567/1956] - info: [plugin/iframely] iframely responded with error: {"status":403,"error":"Iframely could not fetch the given URL. The page appears to be private or requiring a login"}. Url: http://themonstersknow.com/why-these-tactics/. Api call: http://iframe.ly/api/iframely?origin=nodebb&align=left&api_key=6973ed56efecf5d8548108&url=http%3A%2F%2Fthemonstersknow.com%2Fwhy-these-tactics%2F 2019-05-02T04:45:22.871Z [4567/1956] - info: [plugin/iframely] iframely responded with error: {"status":417,"error":"Iframely could not fetch the given URL. 429"}. Url: http://www.wdrb.com/story/36868273/nerds-come-together-for-louisvilles-only-tabletop-gaming-convention. Api call: http://iframe.ly/api/iframely?origin=nodebb&align=left&api_key=6973ed56efecf5d8548108&url=http%3A%2F%2Fwww.wdrb.com%2Fstory%2F36868273%2Fnerds-come-together-for-louisvilles-only-tabletop-gaming-convention 2019-05-02T10:21:13.697Z [4567/1956] - info: [plugin/iframely] iframely responded with error: {"status":403,"error":"Iframely could not fetch the given URL. The page appears to be private or requiring a login"}. Url: https://company.wizards.com/job/game-designer-dungeons-dragons-job-renton-wa-us. Api call: http://iframe.ly/api/iframely?origin=nodebb&align=left&api_key=6973ed56efecf5d8548108&url=https%3A%2F%2Fcompany.wizards.com%2Fjob%2Fgame-designer-dungeons-dragons-job-renton-wa-us 2019-05-02T11:35:57.170Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:35:58.144Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:35:59.142Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:00.114Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:01.049Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:01.928Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:02.956Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:03.893Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:05.109Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:06.244Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:07.208Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:08.119Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:36:16.187Z [4567/1956] - error: /login invalid csrf token 2019-05-02T11:48:57.212Z [4567/1956] - error: /login invalid csrf token

@julian said in Error Upgrading from 1.10 to 1.11:

I suppose it used to assume database 0 on start, but no longer 😄

Yeah, I was freaking out a little bit. Glad it was such an easy fix and many thanks to @PitaJ for trouble shooting it for me so quickly.

Check out the event lot page in the ACP (under advanced). The user's deletion event should have been logged, and the IP address should have been saved.

... as long as your NodeBB is new enough, that is 🙂

Seems like the mobile chat cursor doesn’t show up in the text box on mobile. I’m on iOS 11.2.6.

This occurs both on my forum v1.8.1 and the NodeBB forum. Contrast with Google Hangouts mobile app.

I know chat isn’t the priority, especially on mobile but it’s a great feature to have. Especially since the latest refinements have been so nice. Also, adding in a few extra features for chat (drop a photo in there, etc) with buttons would be nice.

1_1521737570954_9F908A24-4199-4DC7-94A9-196A6E4AF3C0.jpeg 0_1521737570953_7034A422-159A-4DB9-BEAC-5354EE6A9646.jpeg

@baris seems to be working on v1.8.1 now. Thanks!

Basically had to delete everything and build from ground up.

@pitaj said in Noticing "Active Plugins" That Aren't Actually Installed?:

That list reflects the activated plugins on your forum, ignoring whether or not they are installed. You can fix it by disabling the plugins via running ./nodebb reset -p [plugin name] for each plugin.

In the future, make sure you disable the plugins before removing them.

Excellent. Thank you!

@pitaj said in NodeBB Forum looks jacked up on my Desktop using Chrome:

Try clearing your cache.

That seemed to work. Odd. Thanks.

For reference, other notifications on mobile look great.

0_1513887912209_other-notification.jpg

@baris said in v1.5.3 Can't mention groups?:

Check the ACP page for the plugin. You should be able to enable group mentions there.

Thanks, @baris! I knew there was something I was overlooking and forgot @mentions were actually a plugin.

Here is my list https://www.nodebb.se/topic/4/bra-plugin-att-känna-till

npm install npm@4 -g should also fix this issue

Thanks, @baris! Happy to help.

@julian said in Chat Input Box Not Visible Mobile:

Hm, then looks like focus is there... when you start typing does it focus onto the textbox?

Nope. I just have to guess that my typing is correct. 😃

@psychobunny Amazing plugin!

I have one small issue. Can I set it up to automatically enable comments each time a new blog post is made instead of having to click Publish to NodeBB?

@baris said in Simple CSS Problem:

I just tested on this forum and it seems to work fine. What version are you on?

I got it working....

Helps if I enable Custom CSS. :shame: