When I click "add new comment," I get this error. Fatal error: __clone method called on non-object in sites/all/modules/cck/includes/content.token.inc on line 30. I have no idea how long this has been going on, so I'm not sure if it's caused by the latest 3.x-dev update or not. Any ideas? I'm lost as to what's causing this.

CommentFileSizeAuthor
#5 cck-token_fatal_error-988890.patch839 bytesyched

Comments

yched’s picture

yched commented
Status: Active » Closed (duplicate)

Bummer. This is caused by #736440: CCK Provokes PHP memory leak with recursive objects, that I committed yesterday.
Let's move this over there.

yched’s picture

yched commented

@traceelements : *should* be fixed now in latest -dev.

I could use a confirmation on your side, though, since I was not able to reproduce the error you reported. Thanks !

traceelements’s picture

traceelements commented

It's still happening after installing latest dev. It it possible this is being caused by another module?

tribalrose’s picture

tribalrose commented
Component: General » content.module
Category: support » bug
Priority: Normal » Major
Status: Closed (duplicate) » Active

Just got this error when I submit a webform from Webform module if that helps narrow things down.
The form submissions show up in the Webform results tab but try to view them brings up the error message again.
...and trying to add a comment to a node also gets the same error.

yched’s picture

yched commented
Status: Active » Needs review
StatusFileSize
new cck-token_fatal_error-988890.patch839 bytes

Gee, how many safeguards do we have to put in there ?

Can you try the attached patch ?

tribalrose’s picture

tribalrose commented

Never mind... (head hung in shame) I thought I was running the current dev.
Updated and all is well again without the patch.

yched’s picture

yched commented
Status: Needs review » Fixed

;-)
Good to know, thanks for reporting back !

yched’s picture

yched commented

Er, except I overlooked @traceelements' report in #3 :-(.

Sounds surprsing though. Waiting for confirmation on his side that the dev release faiils and that patch #5 fixes it.

traceelements’s picture

traceelements commented

Not sure what fixed it, but everything seems to be working fine now. Thanks!

Status: Fixed » Closed (fixed)

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