Can V7.1.6 sites no longer connect to the package repository?
Hi, just trying to install a package into a 7.1.6 site but I get an error message saying "our.umbraco.com refuses to connect".
There is no error log message but there is a console error saying "Refused to display 'https://our.umbraco.com/error/?aspxerrorpath=/repo/' in a frame because it set 'X-Frame-Options' to 'sameorigin'." Is this the case, that the package repo no longer supports older Umbraco versions because they load into an iFrame?
Any work around available or am I going to have to do an unplanned upgrade and if so, to what minimum version?
Rather than upgrading, you should still be able to download packages from https://our.umbraco.com/packages and use "Install local" to install them.
If there had been a deliberate decision to remove support for the old iframe-based package repository, I'd expect to see a 404 error rather than this error page, so hopefully it's just a temporary problem.
If you do want to upgrade anyway, it looks like 7.5.0 would be the minimum version.
The error appears to come from a header being sent back from the packages site so I get the html in the response but the browser won't show it, hence it doesn't give a 404. It's just Umbraco don't want it appearing in an iFrame which is a bit unfortunate for older sites. Particularly if the owners don't have the necessary skills to fathom what's happening.
In the end I installed via NuGet but was a faff (historical reasons, not technical).
You're not getting the right HTML back in the response, though. Something in https://our.umbraco.com/repo/ is failing, and you're redirected to the error page. That error page then includes the X-Frame-Options header.
Presumably our.umbraco.com is set up to include the header unless the page expects to be displayed in an iframe, and the error page includes it by default.
Can V7.1.6 sites no longer connect to the package repository?
Hi, just trying to install a package into a 7.1.6 site but I get an error message saying "our.umbraco.com refuses to connect". There is no error log message but there is a console error saying "Refused to display 'https://our.umbraco.com/error/?aspxerrorpath=/repo/' in a frame because it set 'X-Frame-Options' to 'sameorigin'." Is this the case, that the package repo no longer supports older Umbraco versions because they load into an iFrame?
Any work around available or am I going to have to do an unplanned upgrade and if so, to what minimum version?
Thanks,
// Craig
Rather than upgrading, you should still be able to download packages from https://our.umbraco.com/packages and use "Install local" to install them.
If there had been a deliberate decision to remove support for the old iframe-based package repository, I'd expect to see a 404 error rather than this error page, so hopefully it's just a temporary problem.
If you do want to upgrade anyway, it looks like 7.5.0 would be the minimum version.
Thanks Steve,
The error appears to come from a header being sent back from the packages site so I get the html in the response but the browser won't show it, hence it doesn't give a 404. It's just Umbraco don't want it appearing in an iFrame which is a bit unfortunate for older sites. Particularly if the owners don't have the necessary skills to fathom what's happening.
In the end I installed via NuGet but was a faff (historical reasons, not technical).
Cheers,
//Craig
You're not getting the right HTML back in the response, though. Something in https://our.umbraco.com/repo/ is failing, and you're redirected to the error page. That error page then includes the X-Frame-Options header.
Presumably our.umbraco.com is set up to include the header unless the page expects to be displayed in an iframe, and the error page includes it by default.
is working on a reply...