I'm getting a fatal error when running cron:

Fatal error: Cannot access empty property in sites/all/modules/cdn2/cdn2_field.inc on line 206

Comments

kylebrowning’s picture

kylebrowning commented

Can you do me a favor and show me a dump of the node object?

Also, have you tried using version 1.10

I dont believe this error exists there.

kylebrowning’s picture

kylebrowning commented
Status: Active » Closed (fixed)

Closing after 2 weeks of no activity

ebeyrent’s picture

ebeyrent commented
Status: Closed (fixed) » Active

Sorry to reopen this, but I upgraded to 1.10, and still got the error.

Since the error was happening when cron was running, I had to add some debug code to the function in order to figure out which node is failing.

Here's a dump of the node that I think is having the issue:

stdClass Object
(
    [nid] => 345
    [type] => video
    [language] => en
    [uid] => 144
    [status] => 1
    [created] => 1267540939
    [changed] => 1267540939
    [comment] => 0
    [promote] => 1
    [moderate] => 0
    [sticky] => 0
    [tnid] => 0
    [translate] => 0
    [vid] => 345
    [revision_uid] => 1
    [title] => Highlight video
    [body] => test video upload
    [teaser] => test video upload
    [log] => 
    [revision_timestamp] => 1267540939
    [format] => 1
    [name] => foo@yahoo.com
    [picture] => 
    [data] => a:11:{s:7:"role_id";s:1:"3";s:7:"captcha";s:0:"";s:11:"captcha_sid";s:3:"413";s:16:"captcha_response";s:5:"hcxf3";s:10:"current_id";s:1:"5";s:12:"current_date";s:10:"1260805522";s:7:"display";s:1:"3";s:13:"form_build_id";s:37:"form-b96f473b04424e555ef7b65007580b4c";s:11:"signup_role";s:1:"3";s:17:"signup_stepnumber";i:4;s:16:"signup_stepcount";s:1:"3";}
    [path] => content/highlight-video
    [field_video] => Array
        (
            [0] => Array
                (
                    [assets] => Array
                        (
                            [0] => Array
                                (
                                    [video_token] => 90a9607c-2607-11df-b945-a5f93cf3477e
                                    [preset_name] => flash_flv_ultra_wide
                                    [status] => complete
                                    [asset_fetch_url] => link
                                    [file_size] => 8882kB
                                    [video_length] => 00:03:38.61
                                )

                            [1] => Array
                                (
                                    [video_token] => 90a9607c-2607-11df-b945-a5f93cf3477e
                                    [preset_name] => 320x240_thumb
                                    [status] => complete
                                    [asset_fetch_url] => link
                                    [file_size] => -0kB
                                    [video_length] => 00:03:38.61
                                )

                        )

                    [video_token] => 90a9607c-2607-11df-b945-a5f93cf3477e
                    [splash_image_number] => 1
                )

        )

    [field_video_thumbnail] => Array
        (
            [0] => 
        )

    [uuid] => 3060184444b8d23cb0739a9.05279007
    [last_comment_timestamp] => 1267540939
    [last_comment_name] => 
    [comment_count] => 0
    [taxonomy] => Array
        (
        )

)
Cactii1’s picture

Cactii1 commented

I'm also getting this. Exactly as stated line 206.

The same node worked just 2 days ago.

** UPDATE **

I dropped the asset... re-uploaded the video and the same error still applies.

** ANOTHER UPDATE **

Clearing the cache resolved the problem.

*** YET ANOTHER UPDATE ***

It wasn't the cache... This module does not play nice with the Fivestar module. Enabling the module recreates the error while disabling the module fixes it.

IncrediblyKenzi’s picture

IncrediblyKenzi commented
Assigned: Unassigned » IncrediblyKenzi
IncrediblyKenzi’s picture

IncrediblyKenzi commented

Looking at line 208:

$items = $node->{$field_name};

I will set this up to check for field_name before committing to display it, but realistically this function shouldn't get called unless field_name is valid.

Second, I don't see how having fivestar installed would have any impact on whether the field data can be recalled.

Cactii1’s picture

Cactii1 commented

Just installed this module on a brand new Drupal 6 site - with the Fivestar module enabled I get the same error - disable Fivestar and all is good!