Had a couple errors about unproperly defined vars, patch coming in a day or two, these are fixed just not uploaded.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | image_attach.module_node_211471.patch | 784 bytes | stefgosselin |
Had a couple errors about unproperly defined vars, patch coming in a day or two, these are fixed just not uploaded.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | image_attach.module_node_211471.patch | 784 bytes | stefgosselin |
Comments
Comment #1
stefgosselin commented* This just adds a simple isset() check, gets rid of a few undefined $node->iid errors I was having.
Comment #2
drewish commentedwouldn't
if (!empty($node->iid)) {do the same thing?Comment #3
drewish commentedwhoops, looks like i just accidentally committed that last patch.
Comment #4
stefgosselin commentedHey dre ! Both solutions would work, though semantically isset behaves as expected in all conditions, because isset() returns true if $iid is set to 0, whilst empty() returns false even if variable is SET to 0.
$iid is expected to have a non-zero value , so in this case both functions would fix the problem.
http://zainal.wordpress.com/2006/04/25/8/ <-- see here for code example.
Comment #5
drewish commentedyeah and in this case we're checking isset() and then evaluating it as a boolean. as far as i can tell !empty() does exactly the same thing.
Comment #6
drewish commentedI committed some other fixes for this: http://drupal.org/cvs?commit=100539
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.