

Tony if your like me, and all you use is the zip code tax calculation and hate ads and. If you need further help nuking the resource hog (jetpack) I suggest disabling all the modules in jetpack. Someone asked if this removes jetpack from taking up resources, no. *If you're like me, you're only using it for free woo commerce tax calculation and you never want to see jetpack again as well as your annoyed about how much resources it takes from your ultra light wordpress. Jetpack triggers super late which is why setting a priority of 1 or 11 or 99999 won't clear it.

"admin_init" is a way of calling the action before any other hook is triggered in wp-admin (call back only). The code above unsets the admin menu item from administrators in wp-admin. paste in functions.php removes menu item for admin usersįor the people that never want to see jetpack again. You can minimize conflicts by manually replacing old shortcodes with new ones.Add_action( 'admin_init', 'wpdocs_remove_menus' ) When multiple plugins use shortcodes with the same name, it causes conflict. Fix some basic speed issues without plugins. The problem using old shortcodes is that the name of the shortcode, “contact-form”, is a common word, so it’s possible that other plugins use the same name. Jetpack is a common WordPress plugin with lots of features that are unneeded and largely slowing down sites. I deactivated the plugin and clicked on Delete in the WP Dashboard. The old shortcode is still supported for backward compatibility. I had Wordpress' Jetpack installed but I want to completely remove it from my page.

This is the simplest way to avoid problems if you intend to use Jetpack features other than the contact form.

You can deactivate the contact form module and continue using other features of Jetpack. Deactivating Jetpack’s contact form module I’ll post here how you can avoid Jetpack problems and use Contact Form 7 with Jetpack successfully. As a result of this, your customized contact form is replaced by Jetpack’s plain contact form, and the submitted message may be sent to an unintended destination. Unfortunately, Jetpack’s contact form module, newly introduced with Jetpack 1.3, conflicts with other contact form plugins including Contact Form 7.Ī typical problem is that Jetpack hijacks other plugin’s contact form shortcode.
