Download & Extend

Warning: Attempt to assign property of non-object

Project:Inline
Version:5.x-1.1
Component:Code
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Drupal 4.7.6
PHP 5.2.1
GD 2.0.28
Modules installed: bueditor, front, imce, inline, menu_per_role, simple_access, systeminfo, upload
Site customization: vbDrupal (only touches user-related tables so far as I know)

I can upload images using the standard upload button successfully, but when I click Preview or Submit on the content, I get this error:

    * warning: Attempt to assign property of non-object in /path/path/siteuser/mydomain.com/modules/inline/inline.module on line 231.

Comments

#1

Forgot to mention that on the content preview, in lieu of the inline image, there is this string:

NOT FOUND: http://mysite.com/system/files/brain.jpg

Interestingly, that path works just fine when I simply open that URL into a browser session.

#2

Of course, not using the full path (as I tried first) also generates an error:

Validation error, please try again. If this error persists, please contact the site administrator.

#3

Are you using the private file access method?

#4

Status:active» postponed (maintainer needs more info)

#5

I get the same but for 5.x-1.1, and on line 333, and only on preview. Submit doesn't cause inline image to appear even though its configured to do so.

#6

Turn off auto-inlining and the error goes away.

#7

Status:postponed (maintainer needs more info)» closed (won't fix)

Sorry, this issue has been in the queue for too long.

#8

Version:4.7.x-1.x-dev» 5.x-1.1
Priority:critical» normal
Status:closed (won't fix)» postponed (maintainer needs more info)

I get the same error. When using auto-inline enabled. Commenting out these lines from whatever case is active for their respective nodes makes the error go away and everything works fine.

// $node->files[$fid]->inline = TRUE;

// else {
// $node->files[$fid]->inline = FALSE;
// }

Public file access is enabled.

#9

updating to inline-5.x-2.x-dev fixes the issue. My issue has been resolved.

#10

Status:postponed (maintainer needs more info)» fixed

Heh... although I do not advise people to upgrade to 5.x-2.x yet, you're welcome to be my alpha/beta tester 8)

#11

Status:fixed» closed (fixed)

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