When trying to install Drupal Commons using Aegir it fails due to the getID3() library path not being set early enough.

The error is

The getID3() module cannot find the getID3 library used to read and write ID3 tags. The site administrator will need to verify that it is installed and then update the settings.

The workaround is to create a symlink (see http://drupal.org/node/931438#comment-3555778 ), but this is unnecessary if the order of tasks performed by the installation profile is changed.

Comments

skwashd’s picture

Status: Active » Needs review
StatusFileSize
new827 bytes

Attached is a patch against the 1.1 release that solves the problem. Now the variables are set first which stops getID3 killing the installation.

You will need to use -p1 to apply the patch. Is there some reason why Drupal Commons isn't using CVS or some other public VCS? I would make creating patches a lot easier.

I tested the patch using Aegir and the standard browser installation methods and both worked fine.

mstef’s picture

That definitely fixes it? Still seems like the required variable is set after getId3 is installed.

skwashd’s picture

Status: Needs review » Needs work

Recent testing is now inconclusive. Marking as needs work due the fact that it isn't reliable.

mstef’s picture

Perhaps it's getID3 that should be patched?

boztek’s picture

I seem to remember that barracuda / octopus ships with a commons platform. Perhaps we should review what they did to get it going as well?

mstef’s picture

Really? Got a link?

skwashd’s picture

omega8cc use the well documented symlink hack - http://github.com/omega8cc/nginx-for-drupal/blob/master/aegir/barracuda/...

I plan to test a patch to getid3 tonight before I crash or first thing in the morning.

mrfelton’s picture

Subscribe

skwashd’s picture

This slipped right off my todo list. I will try to work on it this week.

skwashd’s picture

Issue tags: +buyaline

The problem with installing Drupal Commons and any other installation profile which depends on the getID3 module that the module is overly harsh on misconfigured environments.

The attached patch downgrades the errors to warnings when sites are installed via drush (and also Aegir). I am open to rerolling the patch to always use REQUIREMENT_WARN in getid3.install. I understand the reason for the fatal in getid.module, except when Aegir or drush is responsible for the install.

This is my first patch under buyaline, to learn more visit http://buyaline.drupalgardens.com

skwashd’s picture

Project: Drupal Commons » getID3()
Version: » 6.x-1.x-dev
StatusFileSize
new2.26 KB

Reassigning to getid3 queue and attaching patch.

skwashd’s picture

Status: Needs work » Needs review

Fixing status

skwashd’s picture

Title: Commons can't be installed by aegir » getID3 chokes when being installed via Aegir

Update title be more accurate

kostajh’s picture

This patch works well for me, thanks!

drewish’s picture

I think the ternary would be clearer:
$severity = defined('DRUSH_BASE_PATH') ? REQUIREMENT_WARN : REQUIREMENT_ERROR;

astonvictor’s picture

Issue summary: View changes
Status: Needs review » Closed (outdated)
Issue tags: -

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks