Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By tpeelen on
All,
My ISP recently upgraded to PHP5.3. It gave me several problems because this PHP version is not yet supported by Drupal (will be in Drupal 7). However several work-arounds are available and well documented in this forum.
One issue however I did not find yet. On the page that displays the modules (site construction) some errors like below occur:
warning: syntax error, unexpected BOOL_TRUE in modules/<any module>/<any module>.info on line 3 in /.../includes/module.inc on line 195.
Probably it has something to do with the gtrans module I'm using, but I'm not sure. Anyway I found a working solution that I like to share with anyone having the same problem. I will answer my own question for this (split personality ;-) ).
Comments
I found it has something to
I found it has something to do with text being interpreted. For instance my comment module gives the following description in comment.info:
In the description the word "on" is used. This seems to result in "description" being interpreted as a boolean. Putting double quotes around the text resolves the issue. So I changed the description line into:
Probably it is not a good way to resolve the issue permanently the way it should, but it works for me to get around it. Maybe someone can give a more permanent solution?
For Drupal 5.22, the following .info files need to be altered
thanks
thanks for this solution, it worked fine for me.
I had this problem (also Drupal 5) with:
And a similar issue in line 4 with Module Add On
Thank you!
Nice, this worked like a charm! After solving problems with ereg, split, parameter 1 and other annoying stuff, I was happy to so easily find a solution for this problem. Thanks for posting :-)
Hi, I was also having the
Hi,
I was also having the same problem. But my solution is a little bit different. I hope it may be helpful for others.
I just replaced the following (line 195 in module.inc):
$info = parse_ini_file($filename);
with this:
$info = parse_ini_file($filename,false,INI_SCANNER_RAW);
and it worked like a charm.. all errors are removed.
Thanks!
It really works for me. This method is much convenient than replacing each file with another code. I recommend others to try this.
Upgraded to php 5.3
There are a lot of errors in my site under D5 after upgrading to php5.3:
I replaced the following the line 195 in module.inc
with new line
It seems to fix all of them.