Hi, I've already filed this as an Issue under Colophon but thought it might be worth listing here also since the error code I see indicates that the problem might be in the Panels Info file. . .
I get the following error when accessing the Colophon page on my site. . .
warning: Error parsing sites/all/modules/panels/panels_views/panels_views.info on line 3 in C:\wamp\www\sites\all\modules\colophon\colophon.module on line 236.
I'm not sure if this is a Colophon problem or a Panels problem, since I'm not PHP literate. . .
I'm not sure if I should be cross posting this, sorry if I'm stepping on any toes. . .
Thanks for a great module. I'm new to Drupal and Panels (when the full release comes out) will be one of the things that make the whole package ROCK for me!
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | panels_323895.patch | 4.28 KB | drewish |
Comments
Comment #1
austintnacious commentedActually so I just looked at the files referenced in the error message and it seems to me like colophon.module has a problem with the parentheses in panels_views.info
Line 3
description = Integrates Views as Panel panes (content types).If I remove "(content types)" from that line and run Colophon again the error goes away.
So I don't know if this points to a problem with colophon.module or the use of illegal / inappropriate characters in panels_views.info
I'll copy this comment to the issue I created for Colophon and whoever needs to fix it can do so whenever. . .
Thanks again!
Comment #2
drewish commentedThe description needs to be quoted. This patch quotes all the descriptions in case someone decides to add wacky characters to them later on.
Comment #3
merlinofchaos commentedI'm not sure I agree with drewish. If Drupal's parser parsers it, then I don't agree that some contrib module should tell me that my strings have to be quoted when Drupal doesn't make me quote them. That's the contrib module failing to parse correctly.
-1 this patch.
Comment #4
drewish commentedmerlin, i'm guessing Colophon is using php's parse_ini_file() which provides the following note:
Drupal core uses drupal_parse_info_file() which seems more flexible in it's handling of strings.
Comment #5
drewish commentedthough there's also something to be said for either following the documentation or fixing it...
Comment #6
merlinofchaos commentedIf it's using parse_ini_file() then it will have problems anyway, as parse_ini_file() can't handle the [] syntax that Steven added.
Comment #7
drewish commentedthen lets bump it over.
Comment #8
Max_Headroom commentedFixed as per #4. Please test dev.
Thanks
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.