Plugin Dependency Questions​

Summary: Learn which Antimanual Builder plugins are required, optional, or deactivated, and how dependency checks affect AI, Pro, and page-building features.

The Plugin Dependency Questions section explains which Antimanual Builder components are required, which are optional, and what to expect when a dependency is missing. In practice, this helps you plan installation, avoid configuration errors, and understand why certain features may not appear until the correct plugin, license, or AI provider is available.

What counts as a plugin dependency

In Antimanual Builder Pro, a dependency is any external requirement that must be active before a feature can function correctly. Common examples include the free Antimanual Builder plugin, the parent Antimanual plugin for AI connectivity, and optional services such as a configured API key or a trusted CDN asset.

This design keeps the system modular. Core page-building functionality can run independently, while advanced features are enabled only when the supporting plugin or service is present. That approach reduces unnecessary loading and helps maintain compatibility across different WordPress environments.

Do I need the companion Antimanual plugin?

The companion Antimanual plugin is required when you want to use AI-related features, knowledge base bridging, or provider-based workflows. If it is inactive, the builder cannot read the parent plugin’s settings, and AI endpoints return a dependency error until the plugin is activated and configured.

• Use the companion plugin for AI provider connections.
• Use it when you want shared settings and knowledge base context.
• Expect dependency notices if the plugin is missing or disabled.

For setup guidance, see 7 Proven WordPress Security Tips for Businesses. If you are only editing pages manually, you can continue with the visual builder without enabling AI features.

Do I need Antimanual Builder Pro?

Antimanual Builder Pro is required for premium workflows such as advanced importing, dynamic content handling, and large-scale page planning. The free builder provides the base editing framework, while Pro adds tools that extend import, migration, and AI-assisted page creation.

If Pro is deactivated, pages already built with the free plugin generally remain usable, but premium controls and import features will no longer be available. This is why dependency checks are important: they prevent broken editor states and make feature availability explicit.

Related setup information is available in and .

What happens if a dependency is deactivated?

When a required plugin is disabled, the builder typically shows a dependency notice rather than failing silently. This makes troubleshooting faster and avoids data loss. In some cases, the interface may offer a one-click activation button so administrators can restore the missing dependency directly from the settings screen.

• AI features stop sending provider requests.
• Settings that rely on the missing plugin are hidden or disabled.
• Pages may continue to display static content, but dynamic behavior may be reduced.

If you manage multiple environments, verify plugin status before publishing. A staging site may work differently from production if the parent plugin, license, or provider key is configured in only one location.

How to verify dependency readiness

Before you begin building, confirm that the correct plugin stack is active and that required settings are complete. This is especially important for AI-assisted workflows, where the plugin checks whether the parent plugin is active and whether an API key is available.

• Check that the free base plugin is installed and active.
• Confirm that the Pro plugin is installed when premium features are needed.
• Verify that the companion plugin is active if AI or knowledge base features are required.
• Test the page after activation to ensure dependent assets and controls load correctly.

When external assets are involved, use trusted sources and pinned versions where possible. For more on controlled asset loading, see .

Best practices for dependency management

Good dependency management keeps your site stable, fast, and easier to maintain. Avoid loading duplicate libraries, and prefer only the assets needed for the current page or feature set. This reduces conflicts and makes troubleshooting more predictable.

• Use only one library for each feature set.
• Prefer pinned versions over generic “latest” URLs.

For larger pages or imported projects, dependency review is not optional. The structure, active plugin stack, and external assets should all be checked together so the final page behaves as expected across desktop and mobile devices.

Troubleshooting dependency issues

If a feature does not appear, first confirm that the relevant plugin is active, then check whether the correct license, API key, or asset source is configured. If the page still fails to load a control or panel, refresh the browser and review the WordPress admin notices for dependency warnings.

In most cases, restoring the missing plugin or rechecking the provider settings resolves the issue. If the problem occurs during import or AI generation, the dependency may be related to a parent service rather than the builder interface itself.

For the broader setup workflow, continue with and .