viktorix commented on issue #1630: InsertNodeBeforeNode: existing_node invalid URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1630#issuecomment-473947798 Yes, nginx error log has many of these errors. I didn't notice this before, but these alerts correspond to errors of missing images. But, missing images error is not related to lazy loaded images. ``` 2019/03/18 09:18:27 [alert] 1409#0: [ngx_pagespeed 1.13.35.2-0] InsertNodeBeforeNode: existing_node invalid 2019/03/18 09:18:27 [alert] 1409#0: [ngx_pagespeed 1.13.35.2-0] InsertNodeBeforeNode: existing_node invalid 2019/03/18 09:19:37 [error] 1409#0: *403684 open() "/wp-content/themes/rise-child/images/xit.gif" failed (2: No such file or directory), client: XXX.XXX.XXX.100, server: www.xxx.com, request: "GET /wp-content/themes/rise-child/images/xit.gif HTTP/1.1", host: "www.xxx.com", referrer: "https://www.xxx.com/blog/research-high-need-babies-fact-sheet/"; 2019/03/18 09:19:37 [error] 1409#0: *403684 open() "/wp-content/themes/rise-child/images/icons/visa.png ``` What's interesting, the issue with lazy loading happens on one specific page as far as I can tell. Other pages and posts on this site work fine, lazy loading works as expected. Other pages similar in layout/features work fine. So I'm a bit puzzled as to what may be breaking lazy loading. As I mentioned before, when I reload the page it might work, and then again reload and it won't work. What I noticed, when everything works there are 4 POST requests for ngx_pagespeed_beacon, but when lazy loading doesn't work there are only 2 requests.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
