max
July 24, 2017, 4:41pm
1
Hi there,
i’m getting an “IO Error” (“The result cannot be determined due to a non-document-error.”) at https://validator.w3.org/nu/
Does anyone have the same issue? Is it a server fault on my site?
best regards,
flavio
July 25, 2017, 6:40am
2
Seems that the error means
One specific case that causes this is a server that claims the file is compressed, but then serves an uncompressed file.
I tried one of my sites with Gzip off and I got the same issue, but I don’t have an answer yet on what could be the cause of the problem, as I cannot find any indication in my headers that the document is compressed when it’s not.
glass
September 12, 2017, 1:11pm
3
I get this as well. It seems related to this archived grav community post:
We are using OG matedata for our pages for social sharing and Facebook and Twitter are working OK. We have an issue/problem with LinkedIn sharing - it does not pull content from defined metadata or page itself.
We checked lot of combination of metadata with adding ?1 (?2, etc.) to end of URL to avoid LinkedIn cache issue and there was no progress. Then, we saved one of the pages as a source code - as a html and put back on the server - and it worked! LinkedIn sharing was reading OG metadata and…
…and this issue:
opened 12:29PM - 05 Sep 17 UTC
closed 08:52PM - 14 Sep 17 UTC
cannot replicate
I am having the same issue as referenced in the Grav Community Forum archive:
h… ttps://discourse.getgrav.org/t/linkedin-url-sharing-not-working/1818
So that you need not refer to it, here is the content of that post:
------------------------------------------
We are using OG matedata on our pages for social sharing and Facebook and Twitter are working OK. We have an issue/problem with LinkedIn sharing - it does not pull content from defined metadata or page itself.
We checked a combination of metadata by adding ?1 (?2, etc.) to end of URL to avoid LinkedIn cache issue but there was no progress. Then, we saved one of the pages source code as an html file and put it back on the server - and it worked! LinkedIn sharing was reading OG metadata and it was OK (as it was for other socil networks).
Does anyone have any idea what should we do to enable Linkedin URL sharing with Grav CMS?
Best regards,
Vladimir
------------------------------------------
Like Vladimir (above), I can’t share pages on Linkedin. I know it is not an Apache conf file issue, or an htaccess issue, or a bad code issue because I can create a static version of the page and it shares just fine.
I do not have caching or compression enabled.
To test, I can type the following urls into LinkedIn and see if a page preview appears:
- /news (does not have preview on LinkedIn)
- /new.html (does have preview on LinkedIn)
The first url is a grav-controlled url, the latter is a static html reproduction of the news page from grav which is at the site root.
Server is a typical ubuntu mamp style setup (without the MySQL) hosted on AWS. I regularly check permissions and make sure these bases are covered:
```
sudo chown -R ubuntu:www-data .
find . -type f | xargs chmod 664
find ./bin -type f | xargs chmod 775
find . -type d | xargs chmod 775
find . -type d | xargs chmod +s
```
Any help appreciated.
Thanks!