Image Import Extension Points

This page covers image import at the integration level only. Internal hook names, queue identifiers, image-processing flags and storage paths are implementation details and are not published here.

What image import does

When a vehicle listing is imported, the plugin downloads its images, attaches them to the WordPress media library, and links them to the vehicle. Image post-processing (such as format conversion or sizing) is performed in the background and is controlled by settings exposed in the plugin's admin UI.

Integration surfaces

Configure image behaviour through the plugin's admin UI. Once images are in the media library, they are standard WordPress attachments and can be accessed through the regular WordPress attachment APIs.

Internal hook names, queue tables, lock transients, intermediate file locations and processing-pipeline details may change between releases and must not be relied on from external code.

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.