When viewing a view, using either previous dev build or latest dev build:
Parse error: syntax error, unexpected T_STRING, expecting ']' in /.../drupal-6.17/sites/all/modules/lineage/views_plugin_style_lineage_nested.inc(229) : eval()'d code on line 1

This error does not appear in watchdog. Probably related to something that has changed with the most recent version of views. Note that the view itself seems to be nesting properly, at least.

CommentFileSizeAuthor
#2 lineage_866552.patch830 bytesxjm

Comments

xjm’s picture

xjm
she/her
Primary language English
commented

This is related to an apostrophe in the term name (because of the use of eval()). Patching shortly.

xjm’s picture

xjm
she/her
Primary language English
commented
StatusFileSize
new lineage_866552.patch830 bytes

Attached patch resolves the issue.

xjm’s picture

xjm
she/her
Primary language English
commented
Status: Active » Fixed

Fix committed to -dev:
http://drupal.org/cvs?commit=398614

stinky’s picture

stinky commented

Even after installing the newest dev version, I'm getting following error msg. in views:

"Parse error: syntax error, unexpected T_STRING, expecting ']' in .../modules/lineage/views_plugin_style_lineage_nested.inc(229) : eval()'d code on line 1"

xjm’s picture

xjm
she/her
Primary language English
commented
Status: Fixed » Needs work

#4, can you just confirm quickly for me that your copy of views_plugin_style_lineage_nested.inc contains the function addslashes() on line 229? If it does, can you try to figure out which term is giving the error and post the term name?

(I really should just refactor it not to use eval...)

stinky’s picture

stinky commented

Ah... I didn't realize this was just a patch. I had downloaded 6.x-1.x-dev from the project page, http://ftp.drupal.org/files/projects/lineage-6.x-1.x-dev.tar.gz

but I just now went to http://drupal.org/cvs?commit=398614 and ran the patch. It works great! Thanks so much.

xjm’s picture

xjm
she/her
Primary language English
commented
Status: Needs work » Fixed

Good to hear. The dev builds of modules include patches after they've been committed, but there is a delay of 12-24h most of the time before the dev build gets rebuilt by the packaging script.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.