PHP7 compatibility

[josemi-ca]

The plugin doesn't work under PHP 7:

Read here: https://wordpress.org/support/topic/php-7-support-3/

[danieldunderfelt]

This would be quite important to get working. Everyone on PHP7 basically SOL because there's no other plugin like P3.

[frankiejarrett]

Long story short is this is going to require a complete rewrite of P3.

PHP 7 is pretty amazing, but unfortunately it broke backwards compatibility with the way debug_backtrace() has fundamentally worked in the past, which P3 and other profilers rely on to profile the call stack.

As you can imagine, this is going to take a considerable amount of planning, time and help because we'd essentially be throwing away what we have and starting from scratch. Additionally, whatever approach is decided for the profiler engine to work on PHP 7 would still need to be PHP 5.4 compatible as well, at minimum.

[JavierSegoviaCordoba]

Any update about this?

[xtechgamer735]

Its a bit out of order that GoDaddy, one of the biggest hosting companies in the business cant spare a few developers for a few days. Or just delete the plugin.

[nemeth-it]

Sad, at the current point I could need this plugin a lot.

I'm surprised that there is no warning on the Wordpress Plugin Page (installed and Repository). With such a big incompatibility issue it could become weeks or month until a wordpress-admin would recognizes deprecated or not longer maintained plugins.

So not everything is GoDaddys or the plugin-developers fault. But I would suggest, that they add more hints about this issue on the about-page until it got fixed.

[MACscr]

yep. pretty disappointed myself. No other plugin exists that i know of that works like this one too.

[nemeth-it]

Working like this one, is true. P3-Profiler was really helpful zu visualize slow plugins really well. But there are still plugins who do also a good job to find the reason why a WP-Installation runs suddenly so slowly.

I use Query Monitor now, as long it is activated, it shows in the too-bar on each page-load what and how many stuff got loaded and slowed down your page. (Querys from Themes, Plugins, Hooks and so on.)

[webdados]

RIP P3 :-(

[mkormendy]

Long story short is this is going to require a complete rewrite of P3.

PHP 7 is pretty amazing, but unfortunately it broke backwards compatibility with the way debug_backtrace() has fundamentally worked in the past, which P3 and other profilers rely on to profile the call stack.

As you can imagine, this is going to take a considerable amount of planning, time and help because we'd essentially be throwing away what we have and starting from scratch. Additionally, whatever approach is decided for the profiler engine to work on PHP 7 would still need to be PHP 5.4 compatible as well, at minimum.

So stop wasting time and start rewriting. 😀

[davidfavor]

https://wordpress.org/about/requirements - state minimum PHP version is now 7.3 so seems like targeting support for 5.4 - 5.6 might require a huge effort, for very little gain.

Just a thought.

[r44cx]

@NoZIMM Not related to this issue, at all.

woops, wrong tab

[MACscr]

Long story short is this is going to require a complete rewrite of P3.

PHP 7 is pretty amazing, but unfortunately it broke backwards compatibility with the way debug_backtrace() has fundamentally worked in the past, which P3 and other profilers rely on to profile the call stack.

As you can imagine, this is going to take a considerable amount of planning, time and help because we'd essentially be throwing away what we have and starting from scratch. Additionally, whatever approach is decided for the profiler engine to work on PHP 7 would still need to be PHP 5.4 compatible as well, at minimum.

like anyone that cares about performance is running anything less than php 7

[gabriel-munteanu]

I did a fix for this issue. There is a pull request for this: #8. Meanwhile you can download the plugin with the fix included from here: https://github.com/gabriel-munteanu/wp-p3-profiler/blob/master/p3-profiler.zip