Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Unexpected PHP error [Undefined property: stdClass::$vid] severity [E_NOTICE] in [/Applications/MAMP/htdocs/head/modules/node/node.module line 889] [PHP] Exception
Comment | File | Size | Author |
---|---|---|---|
#7 | node-revisions-test-cleanup.patch | 6.84 KB | boombatower |
Comments
Comment #1
pwolanin CreditAttribution: pwolanin commentedyes, I see this too - using the patched CLI script from: http://drupal.org/node/254166
Comment #2
webchickJust affriming that this is still the case.
Comment #3
webchickStill an issue.
Comment #4
boombatower CreditAttribution: boombatower commentedJust a thought, but it would seem like
should be
Maybe not that simple?
Comment #5
webchickNah, empty() does an isset() and != 0 check, afair.
I think the answer might actually be getting node.module to initialize these properties when it creates a node object. A bunch of if (!isset($property)) set $property type of logic in every single place that does something similar to the test sounds like a silly thing to do.
That said, though, I didn't get a chance to take a closer look at this yet.
Comment #6
boombatower CreditAttribution: boombatower commentedSorry thought that was the line, but node.module was updated and the above stack trace is out of data, make sure you run the tests on your own machine. The code causing notice is:
I agree with webchick, if possible they should be initialized, but I never get these warning when creating nodes through interface?? So is this something related to test environment or the error reporting outside of SimpleTest. I checked in common.inc and it is set to E_ALL as expected, but not sure if there are other conditions.
Comment #7
boombatower CreditAttribution: boombatower commentedThis was an issue with the test itself not passing full node objects to the node API.
I have re-written the test to fit a more standard approach, use less database activity, and check operations more thoroughly.
I have run the complete node test suite and it now passes with NO EXCEPTIONS!
Comment #8
Dries CreditAttribution: Dries commentedTested, reviewed and committed. Thanks.
Comment #9
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.