Closed (duplicate)
Project:
Commerce PayPal
Version:
7.x-2.3
Component:
User experience
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Mar 2016 at 11:58 UTC
Updated:
16 Sep 2017 at 15:26 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
awald commentedso 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 ?
Comment #3
awald commentedComment #4
andrej galuf commentedI 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:
Remove brackets:
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.
Comment #5
LIQUID VISUAL commentedCould 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.
Comment #6
brickhauser commentedThank 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.
Comment #7
rszrama commentedThis 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.
Comment #8
LIQUID VISUAL commentedI regret getting involved with drupal commerce. It's wasn't ready for multilingual sites or shared servers and no warning was given by developers.