Image upload plugin fails to upload an image and I receive the following error:
call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'yui_editor_image_upload' was given in ... /includes/menu.inc on line 348.
I worked around the error by removing all entries from the Paths field of the YUI Editor profile.
Comments
Comment #1
lil-1 commentedHi,
I got the same after giving anonymus user the YUI editor access and image upload permissions.
Paths entries removing helps but how else to exclude YUI editor from apearing on block add/edit pages for example?
Comment #2
codeseek commentedI haven't had to edit or add blocks since running into the error. I suppose you could disable/enable YUI Editor when working with blocks (a pain), or you could try enabling the Code plugin for the YUI Editor and use that when editing blocks. I used it when editing a node and it seemed to work.
Comment #3
jdanthinne commentedGot the same error.
Don't understand what it has to do with menu.inc by the way.
Very annoying.
Comment #4
drubbI've got this error, too. And for me it has nothing to do with defined path entries or field ids, but with a simple bug in file handling on certain server constellations:
Images get uploaded, but after upload they have the wrong file attribute "600" instead of "644", wich leaves them unaccessible and forces this error. You should just include a little patch in YUIE's image_upload_inc:
Don't know whether this is a drupal, php or apache bug, but I've seen this fix in other modules already.
Regards,
Boris
Comment #5
deshilachado commentedsubscribing,
for now i just removed everything from the path entries
(i used the path for speed reasons: #232286: It slows down the whole site?)
Comment #6
mecano commentedpossible fix here : http://drupal.org/node/320517
Comment #7
alarcombe commentedThis is fixed for me by adding
yui_editor/image_upload
to the Paths setting in the profiles that you wish to use YUI's image uploading.
Cheers,
A
Comment #8
Marcus Aurelius commentedThank you so much! Needs to fixed in the next version right?!