Log Page

The AltTexty log page provides a detailed record of the plugin’s activities, especially those related to alt text generation and other significant operations.

This log is invaluable for troubleshooting, monitoring API usage, and understanding how AltTexty is interacting with your images.

You can typically find this page under AltTexty -> Log in your WordPress admin dashboard.

Understanding the Log Table #

The Log page displays entries in a table format with the following columns:

• Timestamp:
  • What it shows: The date and time (according to your WordPress timezone settings) when the log entry was recorded.
  • Hover: Hovering over the timestamp will show the time in GMT.
  • Sorting: You can click the “Timestamp” header to sort entries by date, either the newest first or the oldest first. By default, it shows the most recent entries at the top.
• Image:
  • What it shows: If the log entry is related to a specific image, this column will display a small thumbnail of that image and its WordPress Media Library ID.
  • Link: The thumbnail and ID are usually linked directly to the “Edit Media” screen for that image, allowing you to quickly navigate to it.
  • No Image: If an entry is a general plugin notice (like “Log table cleared” or “Context Rescan started”), this column will show an em-dash (—) indicating no specific image is associated.
  • Sorting: You can click the “Image” header to sort by Image ID.
• Status:
  • What it shows: The outcome or type of the logged event. Each status is color-coded for quick visual identification:
    • Success (Green): Indicates a successful operation, typically successful alt text generation.
    • Error (Red): Indicates a problem occurred (e.g., API error, failed to save data).
    • Warning (Orange/Yellow): For non-critical issues or important notices that aren’t errors.
    • Skipped (Grey): An operation was intentionally skipped (e.g., alt text already existed and the overwrite rule was “empty” or “never”).
    • Info (Blue): General informational messages about plugin processes (e.g., starting a bulk scan, settings updated).
    • Debug (Purple): Detailed technical information, usually only relevant for troubleshooting by developers or support.
  • Sorting: You can click the “Status” header to sort entries by their status type.
• Message / Alt Text:
  • What it shows: This is the main detail of the log entry.
    • For Success statuses related to generation, this column will typically display the actual alt text that was generated and saved.
    • For Error statuses, it will show the error message.
    • For Skipped statuses, it will explain why the image was skipped.
    • For Info or Debug statuses, it provides details about the specific action or data point being logged.

Filtering Log Entries #

Above the log table, you’ll find filter controls to help you narrow down the entries:

• Status Filter Dropdown:
  • Allows you to select a specific status (e.g., “Error”, “Success”, “Skipped”) to only view entries of that type.
  • The default is “All Statuses.”
• Filter Button:
  • After selecting a status from the dropdown, click this button to apply the filter and refresh the log table.

Managing the Log #

• Clear Entire Log Button:
  • Location: Above the log table.
  • Action: Clicking this button will permanently delete all entries from the AltTexty log table.
  • Confirmation: A JavaScript confirmation popup will appear asking you to confirm this action, as it cannot be undone.
  • Purpose: Useful for clearing out old logs to start fresh, or if the log table becomes very large over time. A new log entry will be created indicating that the log was cleared.

When to Check the Log Page:

• Troubleshooting: If alt text isn’t generating as expected, or if bulk processes seem to stall or complete with unexpected results, the Log page is the first place to look for error messages or clues.
• Monitoring: To see how often AltTexty is processing images, especially if you have auto-generation features enabled.
• Understanding Skips: If images aren’t getting alt text, the log can tell you if they were skipped (e.g., due to overwrite rules) and why.
• Checking API Responses: For Error or Debug level entries related to API communication, the log might contain parts of the API response that can help diagnose connection or request issues.

Thank you.