Failure to execute the short code of plugins in version 2.0.0

Hi @namjooo

if a shortcode doesn’t run when FDP is active it probably means the plugin that defines that shortcode is disabled.
I suggest you check all the settings of FDP.

But this problem does not exist in version 1.9.5.8

Did you roll back to 1.9.5.8 to confirm it? If not, upgrading to 2.0.0 may only have deleted the cache of the website.
Theoretically, v. 2.0.0 hasn’t important changes that impact the deactivation of the plugins. Most changes are in the backend.

Can you share the page where you have the contact form?

Have a great day!

Jose

Hello
Yes, I know for sure that the plugin should not be disabled and these plugins were not selected to be disabled by your plugin, but in version 2, their shortcode output was affected.
Many plugins that have shortcodes and those plugins were not selected by your plugin to be disabled, and even the name of those plugins in the “view-source CTRL+U or Inspect element” section is not of the disabled plugins, but they cause the shortcode output to be disabled. .
No, The cache was also deleted and had nothing to do with the cache, but the problem was solved by going back to the previous version.

No, I cannot share this page because I have to install the new version for it, and all other pages, as I said, the shortcodes of some other plugins will be disabled, for example, the shortcode of the table builder plugin.
Thanks

Hi @namjooo

for me, it’s not possible to reproduce the same issue, and I did many tests with Contact Form 7 and FDP v. 2.0.0.

Nobody else until now reported the same issue.

Moreover, I can assure you, that nothing in the code of FDP can cause this issue directly. FDP doesn’t do anything with the shortcodes. Totally not possible. 100% sure about. that.
It may happen that FDP disables the wrong plugins for unexpected bugs, or whatever, but it doesn’t do anything with the shortcodes. If you don’t see the output of a shortcode you have only two possibilities:

• the plugin that defines the shortcode is not active
• a third plugin is the cause of the issue

However, the real world is many times different than the theory, and of course, I may miss something. This is why I did many tests, but as said I was not able to reproduce the same issue.
The only possible causes for me are a conflict with a third plugin that happens only with v. 2.0.0, or FDP wrongly disabling those plugins. You may see them when you inspect the page because for example their assets are cached. I know you are sure they are not disabled. If this is really the case, probably, it’s a conflict with a third plugin.
Please, give me the complete list of your plugins after exporting it with FDP.
Please, read here to see how you can export the list of your plugins.

After having that list I will be able to install all the free plugins with one click, and I can try again to reproduce the issue.

It would be great if you could create a clone of your installation, and then update FDP to v. 2.0.0 on the cloned website. This would also be useful for you in the future, not only for FDP. Having a staging environment where you can test the updates is always a good thing, especially if you have many plugins.

If you can create a staging environment I will give you some suggestions to find the cause of the issue.
Until you have v. 2.0.0, if I can’t reproduce the same issue after installing the same plugins, and nobody else reports the same issue, it’s not possible to help more.

Have a great day!
Jose

Hi @namjooo

do you still need help with this issue? Did you have the opportunity to create a staging environment?

Have a great day!

Jose