i get this error message:
Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ')' in [server path]/modules/faceted_search/faceted_search_views.module on line 117
i get this error message:
Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ')' in [server path]/modules/faceted_search/faceted_search_views.module on line 117
Comments
Comment #1
David Lesieur commentedSee the notes about updating from 0.11 in the Release notes. ;)
Comment #2
David Lesieur commentedComment #3
alotronic commentedI also got this error - but in a new install NOT an upgrade of version 0.21. Dropped tables and tried dev version but still same error. MYSQL version 4.1, so that's not the problem... and I really want this great module!
Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ')' in [path] /modules/faceted_search/faceted_search_views.module on line 117
Comment #4
matslats commentedMe too. The line in question has some rather odd syntax, which occurs in a line in the next function which also breaks it
$this->get_view()->nodes_per_page;
$this-> get_view()-> name
Comment #5
David Lesieur commentedI've just committed a fix for this. Although the code worked with PHP 5, it did not with PHP 4.
Comment #6
matslats commentedWell done.
You're doing great work!
Comment #7
PeterZ commentedHad the same problem; hosting provider uses PHP4.
Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ')' in [path] /modules/faceted_search/faceted_search_views.module on line 117
I don't know much about PHP, but on another forum it says:
====
It's a well-known issue. In PHP4 you couldn't use the ()-> combination. This has been fixed in version 5. AFAIK, the only workaround available is to introduce a temporary variable:
$ret = ret();
echo $ret->a;
====
URL of forum is:
http://www.gamedev.net/community/forums/topic.asp?topic_id=469982
Looks like a really great module...
Comment #8
David Lesieur commentedComment #9
David Lesieur commentedKeeping the issue open for now, to help people find it.
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.