Hi there,

So iam unable to enable modules specifically the commerce paypal module for my drupal installation.

here are the infos:

my host recently switched to PHP 5.6 and i am having problems with enableing modules since then...

has anyone else got similar problems?

thanks in advance..

CommentFileSizeAuthor
#4 brackets.zip531 bytesandrej galuf

Comments

awald created an issue. See original summary.

awald’s picture

so apperantly i experience these proplems due to the fact that my host upgraded to php version 5.6 - is there a workarround, when will the module be available to be compatible with php 5.6 ?

awald’s picture

Issue summary: View changes
andrej galuf’s picture

StatusFileSize
new531 bytes

I take it you're on Hosteurope?

Try this:

Open the info file of all modules and check if their package names contain brackets. It will look like this:

# /sites/all/modules/contrib/commerce_paypal/commerce_paypal.info
package = commerce (PayPal)

Remove brackets:

# /sites/all/modules/contrib/commerce_paypal/commerce_paypal.info
package = commerce PayPal

save the file.

This should solve your problem. To help you, I've attached a little script to this post that does it for you. From wherever the script was unzipped, write bash brackets.sh DRUPAL_ROOT (for instance bash brackets.sh /var/www/drupal) and the script will update package names for you. You should be good to go until you have updated one of the bracket package modules.

Alternately, use Drush to update / enable / disable your modules. It currently seems that the shell is unaffected by the issue.

LIQUID VISUAL’s picture

Could there be a patch to remove brackets from package line of all Commerce submodules? For many of us on shared servers with careful security teams, this is a problem with Commerce Backoffice, Commerce PayPal (and submodules), Commerce Donate and others. It is a hassle to have to apply the very helpful change mentioned above on any update. Elsewhere, people are arguing perfect against good on this issue. That's unnecessary.

brickhauser’s picture

Thank you Andrej for #4. Worked like a charm.

Also look like this solution works with any module that does not enable via the front end.

rszrama’s picture

Status: Active » Closed (duplicate)

This has been discussed elsewhere. I get your point re: perfect vs. good, but the reality is we can't go through and update every single module folks might be using (that would take incredible coordination across hundreds of modules / maintainers who may not even be around). In my opinion, consistent, if frustrating, but easy to fix for unsupporting environments is better than inconsistency here.

LIQUID VISUAL’s picture

I regret getting involved with drupal commerce. It's wasn't ready for multilingual sites or shared servers and no warning was given by developers.