Closed (fixed)
Project:
Open Atrium
Version:
7.x-2.32
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Feb 2015 at 14:43 UTC
Updated:
4 Apr 2015 at 02:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
wildweaselmi commentedComment #2
mpotter commentedNot seeing that on any of our systems here. The oa_core_get_cache_id() function is passed an optional array of $arg to use to build the cache id (cid). Each element in the $arg array should be a string. I don't see anywhere in Open Atrium where non-strings are passed to it.
To debug this you'll need to add a test between line 68 and 69 for something like this:
That will dump whatever the bad $arg value is and also give a traceback to see who is calling this function with the bad argument. You can post the output here if you want me to help review it.
Comment #3
ttaylor249 commentedI'm seeing this as well, but only occasionally, and not easily reproducible. I added the debugging code from #2, but this causes huge debug traces to be dumped on almost every page load because the $args parameter to oa_core_get_cache_id() is passed empty elements and integer elements. I've changed the debugging code to this:
to better reflect what's actually causing the error message. If I see the error again, I'll post the stacktrace.
Comment #4
katrien_w commentedI have the same error since upgrade to 7.32 yesterday.
If I place the debug code in between 68 and 69 I get a "Parse error: syntax error, unexpected '}' in ...oa_core.cache.inc on line 77".
Comment #5
mpotter commentedSorry, there should be a ; character after the last "print "
" line. So code should be this:
Comment #6
joevagyok commentedI'm having the same issue, I inserted the debugging code, but so huge data printed, it's not possible to copy, my browser also struggling with it, I will try to save it in a file for you.
I'm using 2.32
Comment #7
joevagyok commentedI was able to have smaller output by using an edit form:
http://pastebin.com/H38yDJjF
Thanks
Comment #8
mpotter commented@joevagyok Thanks very much for that stack trace, it really helped.
Here is a patch for oa_core to try for fixing this issue
Comment #9
joevagyok commentedYour welcome Mike!
I don't have git for now, so I did patching by hand. For me it seems good, I mean after drush cc all I had no error afterwards.
Good Job!
Thanks
Comment #10
mpotter commentedCommitted to oa_core dev e669bda
Comment #11
katrien_w commentedI had the error on a space, applied the patch and now I get
Notice: Undefined index: ctools_field_list in ctools_entity_field_content_type_formatter_styles_submit() (line 234 of /mnt/nfs/staging/k00012/htdocs/profiles/openatrium/modules/contrib/ctools/plugins/content_types/entity_context/entity_field.inc).
Is this related?
Comment #12
mpotter commentedNope, that is something completely different and not something I have seen before. Are you sure you applied the upgrade to 2.32 correctly and removed your old files and replaced them with the new files? Sounds like you might have a problem with the entity module. But please post this to a new issue since it's not related to the issue fixed here.
Comment #13
jacrsteiner commentedGreat, patched from #8 and haven't reproduced error since. Thanks.
Comment #14
theflathead commentedI got the same error on the Home page right after logged into Open Atrium 2.
I'm using Drupal 7.34.
The patch worked like a charm!
Thanks, Mike! You made my day :)
Comment #15
FO commentedThanks for the patch !
Comment #16
jacobson commentedHad the same error, and the patch worked for me.