Documentation · Admin Reference

Tools Reference

This document is a reference for the Tools screen of the ADP Car Market Hub plugin (Car Market Hub → Tools). It covers exports, cache management, taxonomy synchronisation, the API connection test, demo data and the diagnostics centre.

When to use this document

Read this if you need to:

  • Export imported vehicle data for backup, audit or migration.
  • Force the plugin to re-fetch fresh data from the AutoScout24 API.
  • Re-attach taxonomy terms (make, model, fuel, colour …) to imported vehicles.
  • Verify that the API credentials are working.
  • Install or remove demo data for a sales demo or staging environment.
  • Run targeted diagnostics on a single vehicle post or generate a system snapshot for support.

Overview

The Tools screen is the operational toolbox for administrators. It groups maintenance actions into independent cards so they can be triggered without leaving the page:

  • Setup Wizard — opens the optional six-step First Setup Wizard. Available at any time, even after the wizard has been completed or skipped. Running it again lets you reconfigure setup mode, the dealer profile, the AutoScout24 connection, the default pages and the frontend feature defaults; existing settings are preserved unless you explicitly change them.
  • Export Vehicles — CSV or JSON download of imported vehicle data. This card only appears when the Export feature is enabled; it can be hidden.
  • Cache Clearer — clears the OAuth2 token cache and the model cache.
  • Taxonomy Sync — re-applies taxonomy terms from stored values for every imported vehicle.
  • API Connection Test — performs a live request against AutoScout24 with the current credentials.
  • Demo Data — installs or removes a tagged set of demo vehicles, leads, alerts and analytics.
  • Diagnostics Centre — single-post diagnostics, dry run preview and a JSON system snapshot.

Requirements or prerequisites

  • A user with the plugin's management capability.
  • For the API Connection Test and Cache Clearer to be useful: valid API credentials configured in Settings.
  • For Diagnostics on a single post: the WordPress post ID of an imported vehicle.

Step by step instructions

Export imported vehicles

  1. Open Car Market Hub → Tools.
  2. In the Export Vehicles card, click Export CSV for spreadsheet workflows, or Export JSON for structured data and developer use.

Clear caches

  1. In the Cache Clearer card, click: - Clear Token Cache — removes the cached OAuth2 access token. The next API request fetches a new token. - Clear Model Cache — removes the cached vehicle-model lookup data so it is rebuilt on demand.
  2. The status line indicates whether a token is currently cached.

Use after credential changes, after switching API environments, or when fresh API data is required.

Synchronise taxonomies

  1. In the Taxonomy Sync card, click Run Taxonomy Sync.
  2. The plugin iterates over all imported vehicle posts and re-applies taxonomy term relationships (make, model, fuel, colour and other vehicle attributes) from the values stored in the vehicles table.
  3. The number of processed posts is shown after the run.

Use when filter terms appear missing, outdated or out of sync (for example after a database migration or a plugin re-activation).

Test the API connection

  1. In the API Connection Test card, click the test button.
  2. The plugin issues a live request to the AutoScout24 API with the current credentials and reports the result.

Run this after updating credentials or when imports start failing unexpectedly.

Install or remove demo data

  1. In the Demo Data card, click Install Demo Data.
  2. The plugin installs 10 demo vehicles: 8 are published immediately, and 2 appear as not-yet-imported listings on the Car Importer page so you can exercise the import workflow. It also creates example leads and search alerts and synthetic analytics covering 30 days.
  3. To revert, click Remove Demo Data. Only records created by the demo installer are removed; real customer data is not affected.

The card shows a live currently installed summary (imported vehicles, pending importer listings, leads, alerts and analytics events) or No demo data installed when nothing is present. After you install or remove demo data, a last install/removal summary panel reports what was created or cleaned up.

Use for product demos, internal review and frontend testing without a live AutoScout24 connection.

Diagnose a single vehicle post

  1. In the Diagnostics Centre, locate Diagnose a Vehicle Post.
  2. Enter the WordPress post ID of an imported vehicle and submit.
  3. The plugin returns post metadata, image references, the AutoScout24 raw payload (if present) and live API responses for the listing and equipment endpoints.

Run a dry run

  1. In the Diagnostics Centre, locate Dry Run.
  2. Submit. The plugin previews the data it would import from AutoScout24 without writing any changes to the database. The preview is capped at roughly 25 rows and is shown as a JSON preview.

Use to verify the API data structure before a full import.

Share a system snapshot

  1. In the Diagnostics Centre, expand Show System Snapshot.
  2. Copy the JSON content and attach it to a support ticket or share it with your operations team.

The snapshot includes plugin version, site URL, WordPress and PHP versions, theme name, log status and a redacted view of key plugin settings (only flags such as Client ID set: yes/no; raw secrets are not exported).

Configuration reference

The Tools screen does not store its own settings. It is a launcher for one-shot operations.

ActionCardResult
Export CSVExport VehiclesSpreadsheet-friendly file with imported vehicles.
Export JSONExport VehiclesStructured JSON with imported vehicles.
Clear Token CacheCache ClearerCached OAuth2 access token is removed.
Clear Model CacheCache ClearerCached vehicle-model lookup data is removed.
Run Taxonomy SyncTaxonomy SyncTaxonomy term relationships re-applied on every imported vehicle.
Run API TestAPI Connection TestLive request to AutoScout24, success or error reported inline.
Install Demo DataDemo DataTagged demo vehicles, leads, alerts and analytics created.
Remove Demo DataDemo DataTagged demo records removed.
Diagnose PostDiagnostics CentrePer-post technical report.
Dry RunDiagnostics CentrePreview of API data without writing changes.
Show System SnapshotDiagnostics CentreJSON snapshot for support.

Operational notes

  • All actions in this screen are direct, one-shot operations. There is no scheduling here.
  • The Token Cache status indicator (Token cache active / No token cache) reflects the OAuth2 token currently stored in the WordPress transient store.
  • Demo data is identified by an internal tag so removal is safe and does not touch real customer records. Verify this behavior in the current plugin version before publishing if you operate on a production site.
  • Exports can be large depending on the number of imported vehicles. CSV is generated as a stream; JSON is generated in memory.
  • The diagnostics post lookup performs a live API call to AutoScout24 for the listing and equipment endpoints. The result section displays any error returned by the API.
  • The system snapshot intentionally omits raw secrets. Treat it as low-sensitivity but still internal.

Troubleshooting

  • Export download is empty. No vehicles are imported yet, or another plugin intercepts admin-post.php requests. Confirm the importer has run successfully on Car Importer Reference.
  • Taxonomy Sync reports zero processed posts. No vehicle posts exist yet. Run an import first.
  • API Connection Test reports failure. Re-check Client ID, Client Secret and Base URL on Settings, then click Clear Token Cache and try again.
  • Diagnostics returns "Missing listingid or sellerid meta on this post." The post is not an imported vehicle, or the post pre-dates the current vehicle storage layout. Re-import the vehicle.
  • Demo data does not install. Confirm the user has the management capability and that the database can write the demo records. Check Logs for details.
  • System Snapshot shows client_id_set: no. Credentials are not stored. Save them in Settings before testing.