Novamira integration

Freesoul Deactivate Plugins PRO 1.4.0.0 can tell a Novamira-connected assistant which plugins are safe to turn off on a page, a post type, an archive, or a URL. The assistant reads the settings you already saved and the description of each plugin. It recommends. It does not change those settings when you don’t specifically ask to do it.

Requirements

• Freesoul Deactivate Plugins is active.
• Freesoul Deactivate Plugins PRO 1.4.0.0 or newer is active.
• Novamira is active.
• WordPress 6.9 or newer, and PHP 8.0 or newer.
• The WordPress user connected through Novamira can activate plugins.

There is no switch to enable inside FDP. With both plugins active, the assistant can see the FDP rules on that site.

Connect the assistant

Install and activate Novamira, then connect your assistant to this site and approve the connection. In Cursor, ask in the same chat you use for the site. Write the question as you would ask a colleague.

What you can ask

Ask about one public page, one backend screen, a post type, an archive, or the whole site.

• Which plugins can I deactivate on this product page?
• Which plugins can stay off on the blog archive?
• What is already disabled on https://example.com/contact/?
• Which plugins does the Pages post type already turn off?

Name mobile or desktop only when the question is about that device. A general question ignores the mobile and desktop rows.

What you get back

The answer is a short table:

Plugins that are already disabled for that context are left out of the recommendation. The table is for plugins that are still loading there.

How a page is decided

The assistant follows the same order FDP uses when it builds a page.

• A custom URL row replaces Singles and Post Types. A custom URL row marked as a filter adds its plugins on top of the other rules.
• Post Type settings replace the Singles row, except for a locked post and except when that post type is set to use each post’s own row.
• Plugins disabled on the whole frontend are off on every public page. Plugins disabled on the whole backend are off on every admin screen.
• Untouchable plugins stay active even when a rule lists them.
• Rules for logged-out visitors apply to anonymous visitors on every page.

The result comes from the saved options. It is not a live visit to the page, and it does not measure what the browser downloads.

What it keeps active

The assistant recommends deactivation only for a plugin that is still active in that context, and only when the plugin description makes the choice clear.

It keeps a plugin active when:

• the plugin is untouchable, or it is a security or backup plugin, or it has to run on every request;
• the page is the shop, cart, checkout, account, or a product, and the plugin is WooCommerce or a payment, shipping, or product add-on;
• the plugin is a page builder, a form, a slider, or a multilingual tool, and this page does not clearly do without it;
• the plugin description is too vague to be sure.

Logged-in conditions by user or role are not expanded. If those conditions exist, the answer includes a warning. A plugin that looks unused for anonymous visitors may still be required for a role. Check FDP → Users before you turn it off.

Apply a recommendation

The assistant names the FDP screen and waits. Open that screen and disable the plugins you accept. Nothing is written to the FDP options, post meta, or files at this point.

Example

You can ask:

Which plugins can I deactivate on the single product page?

A useful answer looks like this:

Then you can ask your AI assistant to apply the suggested settings.