Title: Detect disabled plugin when using shortcodes
Last modified: June 2, 2023

---

# Detect disabled plugin when using shortcodes

 *  Resolved [tezalsec](https://wordpress.org/support/users/tezalsec/)
 * (@tezalsec)
 * [3 years ago](https://wordpress.org/support/topic/detect-disabled-plugin-when-using-shortcodes/)
 * Hi Jose,
   would it be possible to build in a mechanism that your plugin automatically
   detects when a certain shortcode is used on a page but not executed because the
   underlying plugin is disabled by your plugin?I spent a few hours recently, to
   figure out why a certain shortcode would not execute. I was blaming WPML, I was
   blaming Elementor, I was blaming cache, but then, after shutting down plugins
   one by one, the cause was your plugin. Not a bug, but a personal configuration
   I had forgotten about, and needed to be applied to a new page containing the 
   shortcode.Example:Contact Form 7 is disabled on all pages but the contact page
   by your wonderful plugin. So far, so good. A year later, the site becomes multilangual,
   a second contact page is created in another language, but the shortcode won’t
   work, because the administrator (me in this case) forgot all about the plugin
   being disabled on all pages other than the original contact page.So the checked
   conditions would be:– if logged in as admin– if page content contains the shortcode
   brackets, suggesting the shortcode has not been executed– your plugin shows an
   admin message saying: shortcode not executed, possibly due to disabled plugins,
   the following plugins are disabled on this page.Maybe this is too far fetched
   and maybe you do not consider this the responsibility of your plugin, and I would
   agree, but it would be super user-friendly for people being not always sharp 
   on the invisible effects of your plugin. So, I just wanted to hand you the option
   to take into consideration. Thanks for considering it. 🙂Much Thanks! Regards,
   Tez

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Jose Mortellaro](https://wordpress.org/support/users/giuse/)
 * (@giuse)
 * [3 years ago](https://wordpress.org/support/topic/detect-disabled-plugin-when-using-shortcodes/#post-16789920)
 * Hi [@tezalsec](https://wordpress.org/support/users/tezalsec/)
 * something similar is already implemented in the PRO version.
   Read [Decide what to do after saving a single post](https://freesoul-deactivate-plugins.com/how-deactivate-plugiins-on-specific-pages/main-settings/)
 * If you set “Check if the right plugins are disabled”, every time you save a page/
   post, FDP will check if there are plugins that had to be active but aren’t. In
   the case of an orphan shortcode, it would detect the issue.
   It will not tell 
   you which plugin was wrongly disabled because it would require too much time 
   every time you save a page/post, but it will tell you that there are some plugins
   that should not be disabled. This is because to detect which plugin was the cause
   it has to load the page every time disabling one plugin after the other, and 
   it would require too much time. But after you see the warning, you can use the
   auto-suggestion to ask FDP which plugins are needed. See here: [https://freesoul-deactivate-plugins.com/how-deactivate-plugiins-on-specific-pages/auto-suggestion/](https://freesoul-deactivate-plugins.com/how-deactivate-plugiins-on-specific-pages/auto-suggestion/)
 * This is a feature that we will not put to the free version because we also need
   to sell the PRO version 🙂
 * In any case, I suggest always checking the preview of the page before saving.
   Selectively disabling plugins can be very powerful but also not very simple.
 * Have a great day!
 * Jose
 *  Thread Starter [tezalsec](https://wordpress.org/support/users/tezalsec/)
 * (@tezalsec)
 * [3 years ago](https://wordpress.org/support/topic/detect-disabled-plugin-when-using-shortcodes/#post-16790160)
 * Very clear, thank you, Jose! I will consider the PRO version in the future! 🙂
    -  This reply was modified 3 years ago by [tezalsec](https://wordpress.org/support/users/tezalsec/).

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Detect disabled plugin when using shortcodes’ is closed to new replies.

 * ![](https://ps.w.org/freesoul-deactivate-plugins/assets/icon-256x256.png?rev=
   2847508)
 * [Freesoul Deactivate Plugins - Disable plugins on individual WordPress pages](https://wordpress.org/plugins/freesoul-deactivate-plugins/)
 * [Support Threads](https://wordpress.org/support/plugin/freesoul-deactivate-plugins/)
 * [Active Topics](https://wordpress.org/support/plugin/freesoul-deactivate-plugins/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/freesoul-deactivate-plugins/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/freesoul-deactivate-plugins/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [tezalsec](https://wordpress.org/support/users/tezalsec/)
 * Last activity: [3 years ago](https://wordpress.org/support/topic/detect-disabled-plugin-when-using-shortcodes/#post-16790160)
 * Status: resolved