Title: cheese63's Replies | WordPress.org

---

# cheese63

  [  ](https://wordpress.org/support/users/cheese63/)

 *   [Profile](https://wordpress.org/support/users/cheese63/)
 *   [Topics Started](https://wordpress.org/support/users/cheese63/topics/)
 *   [Replies Created](https://wordpress.org/support/users/cheese63/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/cheese63/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/cheese63/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/cheese63/engagements/)
 *   [Favorites](https://wordpress.org/support/users/cheese63/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Widget Logic] another broken in 4.0 post](https://wordpress.org/support/topic/another-broken-in-40-post/)
 *  Thread Starter [cheese63](https://wordpress.org/support/users/cheese63/)
 * (@cheese63)
 * [11 years, 7 months ago](https://wordpress.org/support/topic/another-broken-in-40-post/#post-5345868)
 * Hi there, thanks for the response!
 * It turns out there was a widget that had a custom function in it. The logic in
   the widget did something like this:
 * function some_function($post_id)
    { //make a wordpress DB query using $post_id}
   global $post; some_function($post->ID);
 * The problem is that $post, for the page being rendered, was an integer representing
   the post id, and not the actual $post object as would have been expected! Not
   sure why that is, but I got rid of the logic and everything worked again.

Viewing 1 replies (of 1 total)