-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File cannot be reached #647
Comments
Curl error 3 says "URL not properly formatted", but I can't see anything wrong with the parh? I have it locally and running on a staging server, same issue both places.... |
I have the same issue. After the update all previously working feeds are inaccessible to FeedMe. |
I fixed this temporarily by reverting these lines near 134 in /vendor/craftcms/feed-me/src/services/ DataTypes.php
|
Just released 4.2.0.1 with a fix for this: https://github.com/craftcms/feed-me/releases/tag/4.2.0.1 |
I'm still having this issue. It works in production (running on Linux), but on local dev on Windows 10, Feed Me will not import entries from my local JSON file and logs the same error as above. This if check (https://github.com/craftcms/feed-me/blob/develop/src/services/DataTypes.php#L135) returns false for a windows path (in my case, the path returned from https://github.com/craftcms/feed-me/blob/develop/src/services/DataTypes.php#L132 is Looking at previous revisions of |
Description
I had a working feed, but after last update I no longer can process the JSON file provided getting this error: **
**
I have validatet the json file, and also checked if the path provided is reachable from the browser (it is). I have tried moving the file to different location, tried different files, different path formats (http://.... , @web, @webroot etc) all resulting in the same error.
Is there something I'm missing? Has there been a change to how Feed Me works? Anything else I should try to solve?
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: