Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/plugins/wpgraphql-logging/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,7 @@ wpgraphql-logging/
│ │ ├── Rules/ # Rules and RuleManager to decide whether to log a query
│ │ ├── Scheduler/ # Automated data cleanup and maintenance tasks
│ │ └── Store/ # Log storage service
│ ├── Updates/ # Client for the WP Engine plugin updates API
│ ├── Plugin.php # Main plugin class (entry point)
│ └── Autoloader.php # PSR-4 autoloader
├── tests/ # All test suites
Expand Down Expand Up @@ -159,6 +160,14 @@ You can also filter logs with the following filters:

You can delete selected logs or all logs using the bulk action controls.

## Updates

The plugin checks the WP Engine plugin updates API for new versions, so new releases show up on the Plugins and Updates screens in wp-admin like any other plugin update, and you can turn on auto-updates for it. The plugin's `Update URI` header points at the updates API, so WordPress.org is never used for this plugin.

The check runs when WordPress checks for plugin updates. It requests `https://wpe-plugin-updates.wpengine.com/wpgraphql-logging/info.json` and caches the response for five hours. If the API can't be reached, nothing changes and WordPress tries again on its next update check.

If you manage the plugin with Composer, keep updating it with Composer so `composer.lock` stays in sync. wp-admin will still show available updates.

## Uninstallation

By default, WPGraphQL Logging preserves all logged data when the plugin is deactivated to prevent accidental data loss.
Expand Down
Loading
Loading