By bfuzze9898 on

I recently started seeing tons of isset warnings for these. I'm currently using 7.35. I've been working on this site for years and I've never had to set these keys on renderable arrays in the past.

Were there changes made to drupal_render function?
Are there plans to fix this?

Thanks.

⋅ Categories: Drupal 7.x

Comments

Jaypan’s picture

Jaypan commented

drupal_render() is an API function which performs actions based on the data being sent to it. So when you see errors that list drupal_render() it pretty much always means that some other module/theme is sending code to drupal_render(), in an incorrect format. So the problem isn't in drupal_render(), but rather in the code that is calling drupal_render(). The first thing to figure out is which module that is, then you can start looking at the data being passed, and figure out what is wrong with it.

So it's not drupal_render() that needs fixing, it's some other code.

bfuzze9898’s picture

bfuzze9898 commented

Thanks for the response.

Turns out I misread the error. It wasn't an not-isset warning, but an illegal offset warning (what I was passing in was not an array).
I traced this to some complex table logic I botched.

(Where's the "Delete Post" button? ;) )