Flux de travail d'utilisation quotidienne

--- This document describes the operational workflows that administrators and dealership staff perform on a regular basis when managing vehicle inventory through the ADP Car Market Hub plugin. It covers checking imports, reviewing leads, validating the frontend, and monitoring system status.

When to use this document

Read this document if you:

• Are responsible for the daily or weekly operation of a vehicle listings site powered by this plugin.
• Need a practical checklist for verifying that imports ran successfully, leads are being received, and the frontend is displaying inventory correctly.
• Want to understand what to look for and where to look when something appears to be wrong.

For full configuration and setup guidance, see the Manuel de l'administrateur.

---

Overview

Under normal operating conditions, the ADP Car Market Hub plugin runs largely automatically. The scheduled importer fetches updated vehicle data from the AutoScout24 API at configured intervals, downloads images in a background queue, and keeps the WordPress inventory synchronised with the live listing.

However, operational staff should regularly verify that:

1. Import runs are completing successfully.
2. New and updated vehicles are visible on the frontend.
3. Customer leads are being received and processed.
4. The plugin log does not contain unresolved errors.
5. The image queue is not accumulating a significant backlog.

---

Workflow 1: Checking import status

Perform this check daily or after each scheduled import run.

Steps

1. Log in to the WordPress admin dashboard.
2. Navigate to ADP Car Market Hub → Dashboard.
3. Review the KPI row: - Check Total vehicles to confirm the inventory count is as expected. - Check New (last 7 days) to see how many vehicles were added recently.
4. Review the Inventory Trend chart to confirm that import runs have been producing results over the past week.
5. Review the Needs Attention section for any actionable issues such as vehicles missing images or short descriptions.
6. Navigate to ADP Car Market Hub → Import & Limits.
7. Review the last import time and last import status displayed on the tab. Confirm the most recent run completed without errors.
8. If the last run time appears unexpectedly old (for example, more than 24 hours ago on an hourly schedule), check whether the cron is running. See the Checking the cron status workflow below.

What to look for

• The last import timestamp should align with your configured schedule (for example, roughly every hour for an hourly schedule).
• The number of imported vehicles should reflect your AutoScout24 inventory.
• No persistent error notices on the Import & Limits tab.

---

Workflow 2: Reviewing the plugin log

Perform this check daily, or immediately when a suspected import failure occurs.

Steps

1. Navigate to ADP Car Market Hub → Logs.
2. Review the Recent Errors panel at the top of the page. This shows the latest error-level log entries from the last 2,000 lines of the log file.
3. Review the Recent Warnings panel for non-critical issues that may still require attention.
4. If errors or warnings are present, note their timestamps and content.
5. Scroll down to the Log Viewer to see the raw log file and search for context around specific entries.
6. Adjust the Lines field if you need to see more history, then click Reload.

Common log patterns to watch for

If you identify errors that cannot be resolved by reviewing settings, export the diagnostics file from the Tools tab and contact support.

---

Workflow 3: Reviewing and processing leads

Perform this check daily or on any frequency appropriate to your inquiry volume.

Steps

1. Navigate to ADP Car Market Hub → Leads.
2. Review the list of leads. New leads have the status New.
3. For each new lead: - Check the customer name, email address, phone number, and message. - Note which vehicle the inquiry is about. The listing reference links to the AutoScout24 detail page when available. - Contact the customer through your normal sales process. - After contacting the customer, change the lead status to Contacted. - After completing the sales interaction, change the status to Closed or Spam as appropriate.
4. If you need to share leads with another system (for example, a CRM), click Export CSV to download all currently visible leads as a CSV file. Apply any search filters first if you want to export only a subset.
5. Delete leads that are confirmed spam or are no longer needed to keep the list manageable.

Notes

• Lead status changes are saved immediately when you select a new status.
• The CSV export includes all leads matching the current search/filter state, or all leads if no filter is active.
• Leads are stored as WordPress posts. They are not automatically forwarded to external systems unless you have configured a webhook or integration separately.
• Test drive requests submitted through the Test Drive feature are also recorded as leads if the Test Drive feature is enabled.

---

Workflow 4: Checking system health and cron status

Perform this check weekly, or immediately after a suspected scheduling failure.

Steps

1. Navigate to ADP Car Market Hub → System & Help.
2. Review the environment check indicators: - PHP version – must be 8.1 or later. - Memory limit – 256 MB or more is recommended. - Maximum execution time – 60 seconds or more is recommended. - Uploads directory – must be writable for image imports. - cURL and OpenSSL – must be present for API calls. - GD or Imagick – required if WebP conversion is enabled.
3. Review the Cron schedule status indicator: - If using WP-Cron, this shows whether a scheduled event is registered and when the next run is expected. - If using server cron, confirm that your external cron job is configured and running separately.
4. Review the Image queue status: - A small queue size (0–50) is normal. - A queue size above 1,000 triggers a warning badge. This may indicate the image queue worker is not running or is falling behind. - If the queue is large, use the Run image queue now button to process it immediately.
5. Review the API connection test result. Click the test button if available to confirm the API is reachable with the current credentials.
6. If any indicator is in a warning (yellow) or error (red) state, review the corresponding section in the Manuel de l'administrateur or the Troubleshooting section below.

---

Workflow 5: Validating the frontend inventory

Perform this check after each significant import run, or weekly during normal operation.

Steps

1. Open your site's vehicle archive page in a browser (not logged in to WordPress admin, or using a private/incognito window to see the public view).
2. Verify that vehicles are displayed in the archive grid with images, titles, prices, and key specifications.
3. Apply one or more filter controls (for example, filter by brand or fuel type) and confirm the results update correctly.
4. Click on an individual vehicle to open its detail page.
5. Verify that the detail page shows: - At least one image (or the image gallery if multiple images were imported). - The vehicle specifications table (make, model, year, mileage, price, engine, etc.). - The equipment list (if applicable). - The vehicle description. - The contact form. - The financing calculator (if enabled). - The test drive form (if enabled).
6. Submit a test contact form submission and confirm: - The thank-you confirmation is shown on the page. - A lead appears in ADP Car Market Hub → Leads within a few seconds. - The notification email is received by the configured recipient address (if email delivery is working on your server).
7. If vehicles are missing from the archive or the detail page is incomplete, check the Logs tab for errors and verify the vehicle's post status under CMH Cars → All Cars.

Checking vehicle post status

1. Navigate to CMH Cars → All Cars in the WordPress admin sidebar.
2. Search for the specific vehicle title, or use the status links (All / Published / Draft) above the list.
3. Confirm the post is published (status: Published).
4. If the post is in Draft status, either publish it manually or change the Default post status in Settings to publish for future imports.

---

Workflow 6: Triggering a manual import

Use this workflow when you need to immediately refresh the inventory outside the automatic schedule, for example after adding new vehicles to your AutoScout24 account.

Steps

1. Navigate to ADP Car Market Hub → Import & Limits.
2. Click the Trigger now button to start an immediate import run.
3. For a full import with progress monitoring, use the Batch-Wizard: - The progress bar shows vehicles processed, estimated remaining time, and the current action. - You can pause, resume, or abort the wizard at any time.
4. After the import completes, review the status summary for the number of vehicles added, updated, or skipped.
5. Verify the results by checking the Dashboard and the frontend archive page.

Notes

• Manual triggers and the automatic cron scheduler share the same import lock. If a scheduled run is already in progress when you click Trigger now, the manual trigger will be skipped.
• Import runs initiated via the Batch-Wizard process one vehicle at a time by default. This prevents timeout errors on servers with restrictive execution time limits.

---

Workflow 7: Checking for vehicles with quality issues

Perform this check periodically to maintain inventory quality.

Steps

1. Navigate to ADP Car Market Hub → Dashboard.
2. Review the Vehicle Readiness section, which highlights: - Vehicles without images. - Vehicles with unusually short descriptions.
3. For each affected vehicle, click through to the individual vehicle post to investigate.
4. If images are missing: - Check whether the image queue has a backlog (System & Help → Image queue status). - Run the image queue manually if needed. - Check the Logs tab for image download errors.
5. If descriptions are short or missing: - Review the original listing on AutoScout24. - If the AI Assistant is enabled, use it to generate a description for the vehicle. - Alternatively, edit the vehicle post manually to add or improve the description.

---

Operational notes

• Dashboard caching: Dashboard data is cached for approximately 3 minutes. Reload the page to see the most recent data after an import.
• Change detection: The importer uses content and image hashes to skip unchanged vehicles. A high number of "skipped" entries in the log is normal and means the import is working efficiently.
• Multiple seller IDs: If multiple seller IDs are configured, the import runs for each seller in turn. Errors for one seller do not block imports for other sellers.
• Import log verbosity: Verbose logging, if enabled, writes very detailed per-vehicle entries to the log. This is useful for debugging but increases log size. Disable it during normal operation.

---

---

Dépannage

---

Documents connexes

• Manuel de l'utilisateur
• Manuel de l'administrateur
• Flux de travail d'importation de véhicules
• Flux de travail de gestion des leads
• Flux de travail d'utilisation du frontend