You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Kris Popat (JIRA)" <ji...@apache.org> on 2012/05/09 12:42:06 UTC

[jira] [Commented] (WOOKIE-332) wookie php connector relies on file_get_contents which is sometimes disabled

    [ https://issues.apache.org/jira/browse/WOOKIE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271289#comment-13271289 ] 

Kris Popat commented on WOOKIE-332:
-----------------------------------

Hi Lucas,

Sorry it's taken me a little while to look at this.

I'm having a little difficulty applying the patch to check it.  Would it be possible to recreate the patch file without the full paths?

Thanks

Kris
                
> wookie php connector relies on file_get_contents which is sometimes disabled
> ----------------------------------------------------------------------------
>
>                 Key: WOOKIE-332
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-332
>             Project: Wookie
>          Issue Type: Improvement
>          Components: Connection Framework
>    Affects Versions: 0.9.0, 0.9.1, 0.9.2, 0.10.0, 0.10.1, 0.10.2
>         Environment: GNU/Linux 2.6.32-220.2.1.el6.x86_64
> php5
> elgg platform
>            Reporter: Lucas Anastasiou
>            Assignee: Kris Popat
>            Priority: Minor
>              Labels: patch
>             Fix For: 0.10.0
>
>         Attachments: curl_for_php_connector.txt
>
>
> Since a few weeks ago our server admin disabled php's function
> file_get_contents (for security reasons) which resulted for our elgg
> plugin not to work. 
> I did a quick goole search and found that disabling file_get_contents
> is quite usual in virtual servers setups - dreamhost for example has 
> it locked.
> In the other hand curl might not be enabled as well but i guess is
> more likely for file_get_contents to be unavailable instead of curl

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira