Closed (outdated)
Project:
Oracle Driver
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Feb 2012 at 19:57 UTC
Updated:
20 Oct 2025 at 09:26 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
aaaristo commentedcan you confirm this appears with 1.11? i cannot reproduce
Comment #2
drupac_shakur commentedI experienced this as well.
It went away after enabling the oracle module.
Edit: I was using 1.10. Just installed this yesterday, right before 1.11 came out.
Comment #3
aaaristo commented1.11 or 1.10?
Comment #4
drupac_shakur commentedI just upgraded from 1.10 to 1.11 and all my issues went away.
Comment #5
minoroffense commentedI still get this message with v1.11
Best way to trigger it is to clear the cache using the devel block.
Comment #6
aaaristo commentedComment #7
minoroffense commentedJust upgraded to 1.12, the messages still appear (visited update.php). Has the fix for this been rolled into 1.12 or is it only fixed in dev?
Would you like more information from me regarding the issue or our environment? I'd like to help in any way possible.
Comment #8
spotzero commentedI got the same notices.
The notices are generated when menu system builds the menu links, that's why they only are displayed on cache clear.
When the menu link points to a callback, $insert_values[$idx] is an array that looks like this:
The attached patch adds a case to deal with this to the cleanupArgValue() function in database.inc.
Thanks,
Comment #9
minoroffense commentedDoes the function exists call need to be there? Or should we just check for any value and let the rest of drupal figure it out if the function isn't there.
Comment #10
spotzero commentedI'm calling function_exists() because I'm not certain that menu callbacks are the only situation where an array will be passed as bind values (it is the only situation where I've seen it happen however). Since I only want and know how to handle that specific case, I use function_exists() to verify that the string being passed in the array is indeed a callback.
Comment #11
brianV commentedThis looks like a good fix. The function_exists() might impact performance slightly, but spotzero makes a good case for keeping it.
I would commit as-is to get this bug / warning fixed, then look at removing the function_exists() call in a separate ticket if it's warranted.
Comment #12
bohartD7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.
Everyone can apply the patches/suggestions above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.
Thanks!