WP-Memory-Usage

2.2.1

Improvement: Under “Diagnostics,” more data is now collected for the AI prompt to help suggest appropriate measures.

2.2.0

New: You can now choose whether settings and log files are stored in files (recommended default) or in the WordPress database. If saving to files does not work, you can try the database option.

2.1.1

Improved: Show a warning on save if the log path is not readable and writable, and optimized the loading of translations

2.1.0

• New: Diagnose tab generates a ready-made AI prompt (copy & paste into ChatGPT, Claude, etc.) for instant analysis
• New: Diagnose tab — full PHP/WordPress configuration snapshot (OPcache, GC, extensions, php.ini settings and more)

2.0.2

• Improved: Replaced PHP 8.0 syntax (match expressions) with PHP 7.4 compatible code — broadens hosting compatibility

2.0.1

• Fix: Skip log file rotation when no log file has been created yet

2.0.0

• New: Admin backend tabs — Settings, History, Digest, Actions, Memory Thresholds, Check Installation
• Improved: Dashboard widget shows latest digest status badges (warn / danger / critical)
• New: Plugin logo
• Removed: Manual “Multiple Memory Measurement” feature

1.2.12

• New: Expose data for server monitoring via API
• Compatible with PluginCheck Version 1.8.0

1.2.11

• Tested with WordPress 6.9
• Compatible with PluginCheck Version 1.7.0

1.2.10

• Tested with WordPress 6.5.4
• PluginCheck 1.0.1 compatible (except trademarked_term)
• Escaping output, using gmdate() instead of date()

1.2.9

• Bugfix: Fixed “Average MB” calculation that could trigger a PHP Deprecated warning. Thank you @dimalifragis.
• Tested with WordPress 6.4.3 and 6.5-RC