Title: dharmaduf's Replies | WordPress.org --- # dharmaduf [ ](https://wordpress.org/support/users/dharmaduf/) * [Profile](https://wordpress.org/support/users/dharmaduf/) * [Topics Started](https://wordpress.org/support/users/dharmaduf/topics/) * [Replies Created](https://wordpress.org/support/users/dharmaduf/replies/) * [Reviews Written](https://wordpress.org/support/users/dharmaduf/reviews/) * [Topics Replied To](https://wordpress.org/support/users/dharmaduf/replied-to/) * [Engagements](https://wordpress.org/support/users/dharmaduf/engagements/) * [Favorites](https://wordpress.org/support/users/dharmaduf/favorites/) Search replies: ## Forum Replies Created Viewing 2 replies - 1 through 2 (of 2 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Ninja Forms - The Contact Form Builder That Grows With You] error on site after upgrading to WP 3.5](https://wordpress.org/support/topic/error-on-site-after-upgrading-to-wp-35/) * Thread Starter [dharmaduf](https://wordpress.org/support/users/dharmaduf/) * (@dharmaduf) * [13 years, 5 months ago](https://wordpress.org/support/topic/error-on-site-after-upgrading-to-wp-35/#post-3259963) * Looks like the 1.3.5 release fixed my issue! Many thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Ninja Forms - The Contact Form Builder That Grows With You] error on site after upgrading to WP 3.5](https://wordpress.org/support/topic/error-on-site-after-upgrading-to-wp-35/) * Thread Starter [dharmaduf](https://wordpress.org/support/users/dharmaduf/) * (@dharmaduf) * [13 years, 5 months ago](https://wordpress.org/support/topic/error-on-site-after-upgrading-to-wp-35/#post-3259954) * No worries man… You offer a great plugin for free. * It’s quite possible that something else in my install/db/upgrade is jacking the plugins. Widget Logic had problems too (had to switch the settings to “load Logic when all PHP loaded” to get it to stop throwing a “in_array() expects parameter 2 to be array” error. * So I tried in the interim to reproduce these errors on my local (non-production) environment with a clean install of WP3.5 and couldn’t. * Looks like I’ve got some work cut out for me with fresh installs on the production server(s) in the near future. * Thanks for the response. Looking forward to 2.0 Viewing 2 replies - 1 through 2 (of 2 total)