When I go to Administer -> Settings -> Flexinode, I get two warnings:
warning: array_merge() [function.array-merge]: Argument #2 is not an array in c:\wamp\www\mvk\drupal\modules\flexinode\flexinode.module on line 783.
warning: implode() [function.implode]: Bad arguments. in c:\wamp\www\mvk\drupal\modules\flexinode\flexinode.module on line 110.
Also, nothing shows up on the Settings screen except the "Save configuration" and "Reset to defaults" buttons. I assume there should be something else there, but I'm a new flexinode user.
I'm running PHP 5.0.4 on WAMP5 1.4.4.
There's at least one other user who has seen this problem: http://drupal.org/node/19234 .
Comments
Comment #1
logank commentedAs a one-day old newbie, I got these exact same errors while testing a drupal-based site on my local Apache installation. Once I uploaded the installation to my website, the errors disappeared. I don't know why this is, but just a observation.
By the way, to benefit other puzzled newbies, the information that doesn't display is simply a box regarding options for thumbnail sizes and Imagemagick conversion. In other words, nothing that would affect the functionality of text-based nodes.
Comment #2
udare commentedIt seems the issue is that flexinode_invoke_all is still in the v4.5 format. Below is a revision to match the call from module_invoke_all in v4.6. This seems to work fine but needs more testing as I am also a Drupal newbie.
Comment #3
joshua001 commentedI'm also a Drupal newbie, but this problem was immediately solved when I chose NOT to run PHP as a CGI.
Comment #4
jenpasch commentedudare's code worked for me and I still have my php set to run as a cgi. Thanks!
Comment #5
rainynight65 commentedudare's code works for me as well.
Comment #6
vkero commentedudare, thanks... ur fix worked here too
Comment #7
darius commentedI never had the implode warnings, but the empty Settings screen still remains a problem, even with the updated invoke_all() code. I'm running the latest CVS version.
Comment #8
dohertywa commentedRunning 4.6.3
Fixed this problem with the code from udare, thanks. ;)
Posting a patch if it helps any.
Comment #9
micha_1977 commentedpls review the patch from http://drupal.org/node/21673#comment-44197
Comment #10
micha_1977 commented..sorry i changed the title
Comment #11
aries commentedIt works!
Comment #12
dkruglyak commentedcan somebody with cvs access commit the fix? apparently it is not in the HEAD
Comment #13
Bèr Kessels commentedThe last patch is diffed the wrong way arround. Please fix that.
Comment #14
dkruglyak commentedthe patch is not supposed to work after so many changes.
whoever has commit privilege should just manually substitute udare's code and check-in.
Comment #15
Darken-1 commentedudare's code worked for me!
thanx my friend,
Darken
Comment #16
kurkuma commentedudare's code worked for me as well (using drupal 4.6.3 and $Id: flexinode.module,v 1.46.2.3 2005/09/14 01:21:53 killes Exp $).
Thanks.
Comment #17
Marco Palmero commentedI had this error
and the code above from udare worked...
I wonder if there are ramifications when I upload this patched code to the server?
Comment #18
robertgarrigos commentedThis is the right diff patch.
Comment #19
elbarcino commentedHello all....I'm having hte same errors but don't know how to apply the patch. Can anybody advise?
Thanks
Comment #20
mgiffordI think this is a simpler patch that addresses both php warnings that are popping up here.
Comment #21
Bèr Kessels commentedI prefer to have this tested first.
Can someone please review and test?
Comment #22
Bèr Kessels commentedI am bumping this down. Seems to be little interest in debugging a 4.6 version.
Again: all I need is a good review. :)
Comment #23
Bèr Kessels commentedbump: I don't actively maintain a 4.6 version of flexinode. But *will* commit this patch if someone tests it :)
Comment #24
urbanlegend commentedBump: Given that this issue has not been updated in 9 years or more, I am closing this ticket as outdated (no longer needed and/or relevant). However, if anyone feels this represents an issue that is still being encountered in the current version of Drupal, please reopen and/or provide additional comments.