Add-on and Theme error
Permalink
I just did an installation but I'm getting an error when I try to add a new theme or add-on;
Warning: copy() [function.copy]: URL file-access is disabled in the server configuration in /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/marketplace.php on line 85
Warning: copy(http://www.concrete5.org/marketplace/connect/-/download_remote/Ilxv98EfXvjUcUbt9zScjBPS1lv0bMR4ZUYF4xsWTNYGWhiAHstHHxyQrFVZK3uK/391/?csiURL=http%3A%2F%2Fmm.bobulatedesign.com) [function.copy]: failed to open stream: no suitable wrapper could be found in /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/marketplace.php on line 85
Warning: Cannot modify header information - headers already sent by (output started at /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/marketplace.php:85) in /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/view.php on line 791
Warning: copy() [function.copy]: URL file-access is disabled in the server configuration in /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/marketplace.php on line 85
Warning: copy(http://www.concrete5.org/marketplace/connect/-/download_remote/Ilxv98EfXvjUcUbt9zScjBPS1lv0bMR4ZUYF4xsWTNYGWhiAHstHHxyQrFVZK3uK/391/?csiURL=http%3A%2F%2Fmm.bobulatedesign.com) [function.copy]: failed to open stream: no suitable wrapper could be found in /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/marketplace.php on line 85
Warning: Cannot modify header information - headers already sent by (output started at /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/marketplace.php:85) in /homepages/11/d245902131/htdocs/maintaining/concrete/libraries/view.php on line 791
Hey Matt,
Thanks for the answer. I would guess that it is your first guess as I already have a working install on the same server in a different directory.
As the install in question was going to be migrated to the client's server anyway, I simply uploaded a fresh install to a staging area on their server and have had no problems with it.
Cheers,
Bob
Thanks for the answer. I would guess that it is your first guess as I already have a working install on the same server in a different directory.
As the install in question was going to be migrated to the client's server anyway, I simply uploaded a fresh install to a staging area on their server and have had no problems with it.
Cheers,
Bob
Cool, glad it's been resolved. Since replying yesterday I've learned that this was fixed in 5.4.2.1, which was released last week. Here are the release notes:
http://www.concrete5.org/documentation/background/version_history/5...
concrete 5.4.2.1 checks for allow_url_fopen and if it doesn't find it, uses cURL instead.
http://www.concrete5.org/documentation/background/version_history/5...
concrete 5.4.2.1 checks for allow_url_fopen and if it doesn't find it, uses cURL instead.
It sounds like the allow_url_fopen option isn't enabled in your php configuration. You may be able to add a php.ini at the root of your concrete5 site that enables it. Here's what you'll need to place inside:
It's also possible that your server admins have set things up such that supplementary php.ini files are ignored; if this is the case, you'll need to get in touch with your web host to see if they can change the configuration for you.