Hey,

I'm getting a White Screen Of Death when I go to the configuration page after enabling the AWSsdk module. Any ideas?
Andy

CommentFileSizeAuthor
#7 1183456-libraries-2.x-dependency.patch666 bytesboombatower

Comments

boombatower’s picture

Status: Active » Postponed (maintainer needs more info)

Check the Apache error log and post details. Any sort or error reporting would be useful.

rickvug’s picture

I have the same. The error is "PHP Fatal error: Call to undefined function libraries_load() in /sites/modules/awssdk/awssdk.module on line 46". This was I was using libraries 1.x rather than 2.x. Once I made the switch everything was fine.

What is the specific reason for requiring the 2.x-dev version of libraries rather than 1.x, which is stable? If 2.x is really required it would be nice to enforce this in the info file as per http://drupal.org/node/542202.

rickvug’s picture

Title: WSOD on admin/config screen » Enforce or warn about usage of Libraries 2.x only
Category: support » feature
Status: Postponed (maintainer needs more info) » Needs work

Interestingly "dependencies[] = libraries (2.x)" does not do the trick. I could be interpeting the docs wrongly but my guess is that the version parsing isn't playing nicely with -dev versions.

solotandem’s picture

Versions on dependencies fail if the only release available is a dev release. That is why we are pushing Libraries to make an official 7.x-2.x release.

boombatower’s picture

Yes, then we can add (2.x) as one would expect to work. Feel free to chime in with some support over at #1186636: Provide a 2.x alpha release of Libraries API

boombatower’s picture

Status: Needs work » Postponed

This is waiting on Libraries 2.x stable release. So this is a more appropriate status.

boombatower’s picture

Title: Enforce or warn about usage of Libraries 2.x only » Enforce libraries 2.x dependency
Assigned: Unassigned » boombatower
Status: Postponed » Fixed
StatusFileSize
new666 bytes

Since a 7.x-2.x-alpha1 release has been made (http://drupal.org/node/1296690) we can now enforce this using Drupal 7 core dependency checking.

Will be in 4.3 release.

boombatower’s picture

Also removed -dev from project page description.

magnusk’s picture

Version: 7.x-3.4 » 7.x-4.x-dev
Category: feature » bug

The dependency on libraries is incorrectly specified in the .info file. I don't know what it should be.

I am not able to enable the UI module unless the info file is changed.
drush message:

Module awssdk_ui cannot be enabled because it depends on libraries  (2.x) but 7.x-2.0-alpha1 is available
magnusk’s picture

It works if I remove the version number in parenthesis.

boombatower’s picture

Category: bug » support

Please see http://drupal.org/node/542202 which indicates that the format I used is correct. Did you download the built alpha1 release? or the code from git using the tag?

Drupal core will only see the version if you download the release. The reason I didn't add this sooner as you should be able to read above is core has an issues with -dev releases and (2.x).

magnusk’s picture

While the documentation seems to say that the dependency in info file format is correct, I could not enable the module. Yes, it was with the downloaded alpha1 release of libraries (using drush dl). Is it then a bug in core?

boombatower’s picture

Dunno, I don't have the problem.

boombatower’s picture

Go ahead and open a core issue if you have enough details, lets let this one rest then until we know something.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

magnusk’s picture

If anyone is wondering, I believe this issue was related to #1013302: Composer metadata on dev versions doesn't work in update.php

I don't have the problem now that libraries has an alpha release.