After updating to 1.5, the following error appears:
Parse error: syntax error, unexpected T_STATIC in \sites\all\modules\contrib\entitycache\includes\entitycache.entitycachecontrollerhelper.inc on line 96
My Drupal system still runs on PHP5.2, which is sufficient for D7.
I guess the new functionality requires higher PHP -version then Drupal 7 does.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | parse_error_syntax-2619270-5.patch | 2.12 KB | joelpittet |
Comments
Comment #2
johnvComment #3
joelpittetFrom the project page
Are you using that with 5.2?
Comment #4
joelpittetActually while I disagree with the support for 5.2 this feature is only available for PHP 5.5
https://3v4l.org/B0DuC
So in your case I'd suggest upgrading.
Comment #5
joelpittetI think this is the way we've done this before D8.
Comment #6
joelpittetThis still needs 5.3 for the late binding @see https://secure.php.net/get_called_class
Comment #7
johnvRegarding #3.
I posted #2149793: Don't bother using this module ??.
I dont understand that opinion, since even on my dev machine this module greatly reduces db query load.
Comment #8
joelpittetIt's a quote from the homepage of this... I didn't write it nor do I maintain this module.
I'm trying to help solve the problem here. 5.2 doesn't have the feature these classes are using so may be ever so hard to fix it for 5.2 but my patch fixes 5.3 up.
Also you'd get much faster site going to php 5.3 or better anyways. @see http://www.lornajane.net/posts/2012/php-5-4-benchmarks
Comment #10
catchCommitted/pushed to 7.1-1.x, thanks!
Comment #11
ey commentedShouldn't we also update the project page and indicate the new requirement of PHP version 5.3 or newer?
Comment #12
joelpittetThanks @catch. @pc-wurm that wouldn't hurt I don't think. What would be cool is if the project's PHP requirement could be read on to the page automatically on all project pages. But I guess that would be in the drupal.org/infra queues.
Comment #14
RunePhilosof commentedEven with this patch, I couldn't get drush rr to complete.
I needed to disable the module, upgrade the files, then enable the module again.