plugins/context_reaction_block.js starting at line 3 causes errors because it is passing empty values to the $.each function via
$('form.context-editor:not(.context-block-processed)')
I need to narrow down the cases to reproduce this, but you should be able to reproduce it by enabling context module and admin_menu module and a contributed theme (there is a diff error with .each in the seven theme, so it may mask this behavior).
Then in jquery.js line 33, add a console.log(arguments.callee.caller) in the .each function (as decribed here: as described here: http://stackoverflow.com/questions/280389/how-do-you-find-out-the-caller...), you'll then need to add one above in the other call that starts with ,.each
Then load the page up in a console enabled browser such as Chrome and check out the message, it will show that block of code as the offender.
Sorry that I don't have a proper patch at the moment, but it should probably just check to see if there are results for that jQuery selector first before acting on it.
Comments
Comment #1
tekante CreditAttribution: tekante commentedThis seems odd to me. If the selector doesn't find any items to pass forward to the chained each call then that call should not be executed. I am also unable to replicate this issue. Please advise if you have a more specific set of steps for reproducing the module (can you specify which contributed theme you are using).
Comment #2
autopoietic CreditAttribution: autopoietic commentedI believe I am also encountering a similar problem. The following test code does not run when logged in while context module is enabled.