This is from my logs:
2019-05-01T23:05:47.795Z [4567/1956] - [32minfo[39m: [plugins/spam-be-gone] Settings loaded 2019-05-01T23:05:47.858Z [4567/1956] - [32minfo[39m: Routes added 2019-05-01T23:05:47.860Z [4567/1956] - [32minfo[39m: NodeBB Ready 2019-05-01T23:05:47.867Z [4567/1956] - [32minfo[39m: Enabling 'trust proxy' 2019-05-01T23:05:47.872Z [4567/1956] - [32minfo[39m: NodeBB is now listening on: 0.0.0.0:4567 2019-05-01T23:06:46.203Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:44.904Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:45.822Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:46.745Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:47.671Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:48.797Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:49.637Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:50.764Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:51.806Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:52.799Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:53.673Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:54.520Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:55.402Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:56.383Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:57.203Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:58.085Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:58.957Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:19:59.803Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:20:00.659Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:20:01.574Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:20:09.481Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-01T23:37:11.087Z [4567/1956] - [32minfo[39m: [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] - [32minfo[39m: [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] - [32minfo[39m: [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] - [32minfo[39m: [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] - [32minfo[39m: [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] - [31merror[39m: /login invalid csrf token 2019-05-02T11:35:58.144Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:35:59.142Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:00.114Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:01.049Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:01.928Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:02.956Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:03.893Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:05.109Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:06.244Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:07.208Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:08.119Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:36:16.187Z [4567/1956] - [31merror[39m: /login invalid csrf token 2019-05-02T11:48:57.212Z [4567/1956] - [31merror[39m: /login invalid csrf tokenInfinite scrolling issue
-
Hi all,
I've just updated 1.12.x to 1.16.x and it seems that infinite scrolling has issues when, after having scrolled down a bit, either you can't scroll down further or getting back to the top the scrolling doesn't let go up to the very first post.
It has also been reported by some users some weird "infinite flickering" mechanism when scrolling up. (unfortunately it seems I can't upload gif to show the issue)
I'm running 1.16.2 with slick theme. Are you aware of this issues? Is there anything to mitigate the issue ? Can it be something related to nginx configuration?
Thanks, Riccardo
-
@baris feel free to test on plugincafe.maxon.net
-
@baris thanks a lot for the input.
The issue was independent by the theme (slick was 1.3.8) but it seems that removing the height: 100% has fixed the issue.If it gets back I'll let you know.
For the time being, thanks a lot!