Closed Sarke closed 4 years ago
https://github.com/schemaorg/schemaorg/issues/2578#issuecomment-632227864
Looks like they no longer do HTTP content negotiation, and are using Link:
headers instead.
I just released version 1.2.0 with @tomgillett's fix that adds support for the alternate Link header that schema.org now uses.
When
FileGetContentsLoader::loadDocument('http://schema.org')
it now fails on line 105 because it'stext/html
and not json.Not sure when that changed, but it pretty much breaks any schema lookup, unless it is cached.