Developer FAQ

This page collects frequently asked, integration-oriented questions. It intentionally does not enumerate internal class names, table names, option keys, hook names, REST routes, capability identifiers or release-pipeline specifics — those are internal implementation details.

General

What is this plugin?

ADP Car Market Hub is a WordPress plugin that imports and synchronises vehicle listings from an upstream marketplace into WordPress, and exposes a front-end catalogue (archive, single vehicle, comparison, favorites, search filter) plus an admin area for configuration, imports and lead management.

What are the version requirements?

The plugin's required WordPress and PHP versions are declared in the plugin header and the project's composer.json. Check those values for the currently supported minimum versions.

Where does the plugin store its data?

Vehicle listings and leads use WordPress's standard content storage. Configuration uses WordPress options. The plugin also manages some plugin-specific storage where required for its own functionality. **Direct database access to plugin-managed storage is not supported.**

Does the plugin have runtime dependencies?

No additional runtime dependencies are required beyond WordPress and PHP at the documented minimum versions. There is no JavaScript build step in the released package.

Integration

How do I embed the catalogue in a page?

Use the documented shortcodes.

How do I change the look of a vehicle page?

Override the bundled templates from your theme. See Template System And Overrides.

How do I forward leads to my CRM?

Use the plugin's outgoing webhook configuration in the admin UI rather than hooking internal events. Verify the configured webhook against the current plugin version when you wire it up.

How do I trigger imports from an external scheduler?

Configure the plugin's own automation from the admin UI; it includes the supported, documented surface for this case. Do not depend on internal hook names or undocumented endpoints.

Can I read plugin analytics or Market Insights data from outside the plugin?

No. Reporting is exposed through the plugin's admin UI; internal storage and endpoints are not a public contract.

Support

How do I report a bug?

Use the project's contribution channel described in Contribution Guidelines. For environment information, prefer the diagnostics export available from the plugin's admin UI rather than copying raw log files.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

• The plugin admin settings UI.
• The documented shortcodes.
• Theme-level template overrides as described in Template System And Overrides.
• The general Developer Overview for orientation.

Internal class names, option keys, database tables, REST and AJAX endpoints, cron hook names, capability and nonce identifiers, and release / update infrastructure are treated as implementation details. They may change between releases without notice and are not part of the public integration contract.

Stability and change policy

Anything not listed as a supported public surface above is considered an internal implementation detail. Internal APIs, storage layout and security implementation may change between releases. Do not depend on them from third-party code, themes or external systems. Direct database writes are not supported.

Public documentation notice. This page provides a high-level integration overview only. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation. Supported integration surfaces are the documented shortcodes, template overrides, settings UI and any extension points explicitly published in this section.