PluginProbe
Code Profiler – WordPress Performance Profiling and Debugging Made Easy / 1.9.6
Code Profiler – WordPress Performance Profiling and Debugging Made Easy v1.9.6
1.9.6 1.9.5 1.9.4 1.9.3 trunk 1.4 1.4.1 1.4.2 1.4.3 1.4.4 1.5 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.6 1.6.1 1.6.10 1.6.2 1.6.3 1.6.4 1.6.5 1.6.6 1.6.7 All 41 releases
← All changes | readme.txt +125 -5 1.6.71.9.6 View file →
@@ -1,10 +1,10 @@
1 1 === Code Profiler - WordPress Performance Profiling and Debugging Made Easy ===
2 2 Contributors: bruandet, nintechnet
3 -Tags: profiler, debug, optimize, performance, seo, benchmark, statistics, debugging, speed, profiling
3 +Tags: profiler, debug, optimize, performance, benchmark
4 4 Requires at least: 5.0
5 -Tested up to: 6.4
6 -Stable tag: 1.6.7
5 +Tested up to: 7.1
6 +Stable tag: 1.9.6
7 7 License: GPLv3 or later
8 8 Requires PHP: 7.1
9 9 License URI: https://www.gnu.org/licenses/gpl-3.0.html
10 10
@@ -15,9 +15,9 @@
15 15 = A profiler to measure the performance of your WordPress plugins and themes. =
16 16
17 17 Code Profiler helps you to measure the performance of your plugins and themes at the PHP level and to quickly find any potential problem in your WordPress installation.
18 18
19 -You can profile the frontend and backend of WordPress, a custom URL, or even send a POST payload, custom cookies and HTTP headers to profile a contact form, a checkout process or an AJAX action among many other possibilities.
19 +You can profile the frontend and backend of WordPress, as well a cron events, a custom URL, send a POST payload, custom cookies and HTTP headers to profile a contact form, a checkout process or an AJAX action among many other possibilities.
20 20
21 21 It generates an extremely detailed and easy to read analysis in the form of charts and tables that shows not only which plugin or theme, but also which PHP script, class, method and function is slowing down your website. It displays many useful additional information such as database queries, file I/O operations and disk I/O usage as well.
22 22
23 23 It makes it very simple to locate any bottleneck problem in your themes or plugins in order to solve it and speed up your website.
@@ -42,9 +42,9 @@
42 42 * GET/POST methods, custom cookies and HTTP headers.
43 43 * [Pro] Export all tables and charts in CSV file format.
44 44 * [Pro] Filtering options
45 45
46 -Learn more about [Code Profiler Pro](https://code-profiler.com/).
46 +Learn more about [Code Profiler Pro](https://nintechnet.com/codeprofiler/).
47 47
48 48 == Frequently Asked Questions ==
49 49
50 50 = What are the differences between Code Profiler and services such as Google PageSpeed or GTmetrix? =
@@ -91,8 +91,128 @@
91 91 11. [Pro version]: Database queries performance.
92 92 12. [Pro version]: Remote connections monitoring.
93 93
94 94 == Changelog ==
95 +
96 += 1.9.6 (23 September 2026) =
97 +
98 +* Better error handling during the profiler activation and deactivation.
99 +* [Pro version] : The "Do not display more than X rows in a table" option applies now to the table of the "Profiles List" page too.
100 +* Fixed a problem with multiline strings that some localization tools doesn't seem to handle correctly.
101 +
102 += 1.9.5 (12 June 2026) =
103 +
104 +* Fixed a bug where users couldn't download the grah as a PNG image with the latest version of FireFox (151.0.2+).
105 +
106 += 1.9.4 (09 June 2026) =
107 +
108 +* This release includes many small fixes and adjustments to make Code Profiler better (bugs fixed, better error management etc).
109 +
110 += 1.9.3 (18 May 2026) =
111 +
112 +* Fixed small UI compatibility issues with WordPress 7.0.
113 +
114 += 1.9.2 (24 April 2026) =
115 +
116 +* Removed the warning about composer; it was confusing and has become obsolete.
117 +* Updated the profiler's browser signatures.
118 +* [Pro version] : Removed a double-slash bug in file paths.
119 +* Fixed a bug where the HTTP response log could be empty.
120 +
121 += 1.9.1 (19 March 2026) =
122 +
123 +* Cron events can be profiled with WP-CLI using the `--wpcron` parameter.
124 +
125 += 1.9 (05 February 2026) =
126 +
127 +* It is now possible to profile cron events: on the profiler main page, click "WP-Cron" and select the cron to profile.
128 +* Updated browser's signatures.
129 +* Updated Chartjs library.
130 +* Small fixes and adjustments.
131 +
132 += 1.8.2 (23 December 2025) =
133 +
134 +* A warning message will be displayed if the Xdebug extension is loaded as it can impact the profiler's results.
135 +* [Pro version] : Code Profiler will warn if SAVEQUERIES has been disabled by the user.
136 +
137 += 1.8.1 (09 Octobre 2025) =
138 +
139 +* When profiling with WP-CLI, the results can be returned in JSON-encoded or CSV format, using the new `--out=<json|csv>` parameter. The output can be redirected to a file, e.g., `wp code-profiler run --out=csv > /tmp/results.csv`.
140 +
141 += 1.8 (1st October, 2025) =
142 +
143 +* This version introduces a new feature requested by many users: the possibility to re-run an existing profile. In the "Profiles List" table, click on the "Re-run" row action link and Code Profiler will run again the profile with the same options and parameters.
144 +* Fixed an "Automatic conversion of false to array is deprecated" message in PHP 8.1+.
145 +* Small fixes and adjustments.
146 +
147 += 1.7.7 (23 June, 2025) =
148 +
149 +* Fixed an issue where the profiler wasn't able to detect if the connection was over HTTPS when running WP CLI.
150 +* Fixed a potential "Function _load_textdomain_just_in_time was called incorrectly" notice when running WP CLI.
151 +
152 += 1.7.6 (19 June, 2025) =
153 +
154 +* You can now enter a raw POST payload as opposed to a formatted one, by selecting the "Profiler > Advanced Options > HTTP Method > Content-type > application/x-www-form-urlencoded (raw)" option.
155 +* [Free version] : Fixed a PHP "WP_List_Table::__set(): The property is_empty is not declared" error.
156 +* The "HTTP response log" will show the POST payload (if any) for the last profile.
157 +* Updated ChartJS.
158 +* Small fixes and adjustments.
159 +
160 += 1.7.5 (06 May, 2025) =
161 +
162 +* An option to enable PHP error debugging when the profiler is running was added. It is enabled by default and can be turned off in the "Settings" page.
163 +* Updated ChartJS.
164 +* Fixed a few deprecated notices in translation loading, when starting the profiler.
165 +
166 += 1.7.4 (April 11, 2025) =
167 +
168 +* Prevent duplicate items in the "File and folder exclusions" list.
169 +* Fixed a PHP 8.4 "fgetcsv(): the $escape parameter must be provided" deprecated notice.
170 +* [Pro version] : Fixed several PHP 8.4 "fputcsv(): the $escape parameter must be provided" deprecated notices.
171 +* Ensure compatibility with the latest WordPress 6.8.
172 +* Updated ChartJS.
173 +
174 += 1.7.3 (February 15, 2025) =
175 +
176 +* Updated ChartJS.
177 +* Updated browser's signatures.
178 +* Truncated exported CSV data to max 32,000 characters per cell to prevent a "maximum numbers of characters per cell was exceeded" error in Libre Office and similar spreadsheet apps.
179 +
180 += 1.7.2 (November 26, 2024) =
181 +
182 +* The profiler will now save to a log the HTTP headers and body response of the last profile. It can be useful to debug errors. To view the log, click on the "Logs" tab of the main page.
183 +* Fixed a "Function _load_textdomain_just_in_time was called incorrectly" PHP notice.
184 +* Updated ChartJS.
185 +* Small fixes and adjustments.
186 +
187 += 1.7.1 (September 27, 2024) =
188 +
189 +* Fixed a "Security keys do not match" error message that occurred when some object caching plugins were installed on the site. The profiler will no longer temporarily save the key to the database to prevent it from being cached by such plugins.
190 +* Fixed a fatal error when profiling a child site on a multisite installation with WP CLI.
191 +* [Pro version] : Fixed a bug with some row action links in the "Methods and Functions Performance" that were displaying "View function" instead of "View script" when the script was loaded either with the PHP "require" or "include" expression.
192 +
193 += 1.7 (August 14, 2024) =
194 +
195 +* The system information report includes now an AJAX API test to make sure the endpoint is accessible to the profiler.
196 +* If the profiler returned a 301/302 HTTP redirection error message, the new location would be written to the log.
197 +* Updated ChartJS.
198 +
199 += 1.6.10 (May 30, 2024) =
200 +
201 +* Fixed a bug that affected Microsoft Windows OS only. In some cases, it wasn't possible to view, delete or rename a profile.
202 +
203 += 1.6.9 (May 27, 2024) =
204 +
205 +* You can now exclude files and folders from the profiling process. See "Advanced Options > File and folder exclusions" in the profiler's main page.
206 +* Fixed a bug where optional HTTP headers could be truncated.
207 +* Replaced all calls to glob() with DirectoryIterator() to make file search compatible with remote files.
208 +* Updated ChartJS.
209 +* Updated browser's signatures.
210 +
211 += 1.6.8 (February 14, 2024) =
212 +
213 +* Fixed an issue in the theme switcher where, in some cases, a child theme could throw an error because the wrong stylesheet was loaded.
214 +* Improved the parsing of the backtrace when attempting to find which plugin or theme initiated a remote connection.
95 215
96 216 = 1.6.7 (February 10, 2024) =
97 217
98 218 * If you want to profile different themes, you can now select which theme to load when the profiler is running.