Warning: file_get_contents()

please remove a persona link. i have make a mistake to insert this.

@eccezioni I’ve edited the links. PLEASE pay attention next time. Don’t post things in public forums that you aren’t okay with being public.

Hi, thanks for the support, please remove the important link [ics_calendar url = “https:………..”]
Thanks a lot.

The link was changed to be an invalid one, you’re fine.

I tried this on my test system using your original URL (don’t worry, it’s not accessible here anymore and I will not share it), and I observed that I could access the URL directly in my browser and download the ICS file, but when I tried to load it with my site, I got a slightly different error:

Warning: file_get_contents(REDACTED): failed to open stream: HTTP request failed! HTTP/1.0 403 Forbidden in /REDACTED/wp-content/plugins/ics-calendar/ics-calendar.php on line 111

I looked into this, and I believe the issue is that Airbnb has their servers configured to detect if the request is coming from a “real” web browser, or from another web server, and they are blocking access to the calendar from web servers, to prevent “scraping” of data.

This is completely understandable, since another site could potentially be using these calendar feeds to siphon business away from Airbnb.

There are possibly some ways around this, but since Airbnb has gone to the effort of blocking this type of access, you would likely be violating their terms of service in trying to circumvent the restrictions.

You may want to contact Airbnb to see if there’s an allowed mechanism for using the ICS feed to populate a calendar on your site.

hello, thanks for the proof you made, just that using another plugin the Airbnb calendar is imported correctly on the website. If you want I can take a look at it all. so I assume the problem is not airbnb. If you authorize me I send you the link of the other plug-in that makes me import the Ical icl feeds. Thank you

Thanks, that would be helpful. You can email me at the support address on the admin screen for my plugin.

Version 2.1.0 introduces a new method of retrieving the file that tries cURL first and then falls back on the old file_get_contents() method. Since I don’t have access to a server that’s configured in a way that prevents accessing the file, I have no way of testing directly whether or not it resolves this issue, but I am going to mark this thread as resolved. Feel free to follow up or start a new thread if there are still any problems with this.