Closed (works as designed)
Project:
Video
Version:
7.x-2.x-dev
Component:
Amazon S3
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Mar 2012 at 09:42 UTC
Updated:
8 Apr 2012 at 15:57 UTC
Hi,
I try for few month to use you module, but I wonder now if I do the good choice according to the number of fresh module used for this....
My site on localhost was able to put on amazon s3 files, the problem was the transcoder...
Now I put the site in production, the problem comes from the upload of files.
here is the information of configuration attached, everything seems to be OK.
When I upload a file here is the log :
I try to create another bucket (rights are defined ) but an error appears and I can't save this :
Warning : set_time_limit() has been disabled for security reasons dans RequestCore->send_request() (ligne 817 dans /home/www/678906c5db97b26c8a1d100feedfea2c/web/sites/all/libraries/awssdk/lib/requestcore/requestcore.class.php).
the set_time_limit() fonction is not active on my host.
I try to remove the "set_time_limit(0);" in requestcore/requestcore.class.php but I can't save the new bucklet.
I think that is not so simple the code below must be changed I guess...
Do we need this function set_time_limit, which is not listed in the comptability test, and not authorize on all hosting.
Regards,
| Comment | File | Size | Author |
|---|---|---|---|
| AWS SDK for PHP_ Environment Compatibility Test.pdf | 29.37 KB | zorax |
Comments
Comment #1
Jorrit commentedI don't know why AWS doesn't test for the availability of set_time_limit. In any case, the AWS SDK is not developed by me so I can't change it. I am interested in what problem appears when you remove that line.
Comment #2
zoraxHi,
thansk for your help.
I remove two lines (set_time_limit(0)) in requestcore.class.php.
I have flush all caches
In amazon s3 configuration, I record a new bucklet : "almede.film"
OK, configuration saved
Now I create a content with video
I upload, and then a error message appears :
"Le fichier n'a pas pu être transféré." the file could not be transfered
here is the report informations :
FR
Le répertoire de transfert s3://videos/original pour le champ de type fichier field_realisation_video ne peut pas être créé ou n'est pas accessible. Un fichier nouvellement transféré ne peut donc pas être enregistré dans ce répertoire, le transfert a été annulé.
GB
the upload folder s3://videos/original for the field fichier field_realisation_video can't be created or is not accessible . A new file can't be uploaded in this folder, the transfert is canceled.
Comment #3
Jorrit commentedDoes the user entered in the AWS SDK settings have access to that bucket?
Comment #4
zoraxyes, full acess.
just a little point.
Before to change of host, the site was in localhost (wamp) with same configuration.
the transfert was OK, the file was copied on the server.
The problem was the the Postback URL for Zencoder which was impossible to reach in localhost.
So first reaction was to say that it was a hosting problem.
With my hosting interface I can just enable for one hour only the set_limit function. But the result is the same...with or without....
Comment #5
Jorrit commentedWhen you go to the status report of your Drupal installation, does it say "AWSSDK: 1.5.0.1 [compatibility test]" on a green background?
Are any of the entries in the Drupal status report red / yellow?
Comment #6
zoraxyes, in status report every lines are green and if I click in compatibilty test, you have the result in #1.
Comment #7
Jorrit commentedI am sorry, but I am unable to investigate the problem using just issue questions and responses. Is it possible for you to allow me to access your administrative panel? Or perhaps if you can demonstrate the problem when I look at your computer using TeamViewer? Have you tried version 2.5 of the module?
Comment #8
zoraxWith pleasure,
I send you a user account.
Cheers
Comment #9
Jorrit commentedIt appears to be a web hosting issue, related to the PHP setting allow_url_fopen being disabled. I am going to close this issue because it doesn't seem to be a module related issue.
Comment #10
Jorrit commentedI have added a warning to the status page of Drupal to warn users that their PHP configuration is incompatible with the Amazon S3 stream wrapper.