Kurt Payne

Hi Eric, I’ve e-mailed you about this.

Eric,

If you go to advanced metrics, how many visits do you see?

What version of WordPress is this on?

Adam,

Thank you so much for pointing this out. This bug was fixed in 1.1.1 and re-introduced in 1.1.2. It’s been fixed again, in 1.1.3 and in the development brand (tentatively versioned as 1.2.0).

There’s a thanks to you in the readme.txt file, but it’s not showing up on the plugin page yet. You can see it here:

https://plugins.svn.www.ads-software.com/p3-profiler/trunk/readme.txt

Hi adamf,

Please ensure that wp-content/plugins/p3-profiler/.htaccess is no longer on your server. This file was removed in the latest version.

If you’re still seeing a broken interface, can you include a screenshot of javascript errors from your browser’s console (or Firebug). If there an error, please also include a screenshot of the offending lines.

Thank you!

Eric,

Are you using varnish or nginx in your production environment?

When you’re looking at the profile, if you go to advanced metrics, how many visits do you see?

Hi Eric,

Are you using WP Super Cache on your local site as well?

Eric,

You’re welcome! The main problem we’re facing is that if the plugin is loaded early, it can be more accurate when tracking the WordPress core, and some plugins. But if it’s loaded early, it’s outside of the WordPress framework, and that’s where we’re seeing most of our the support issues.

We’re experimenting with a version of P3 that sacrifices a little accuracy for a lot more compatibility.

Eric,

Can you verify that /PATH/wp-content/plugins/p3-profiler/.profiling_enabled exists and is writable by the webserver?

Can you chmod the file, temporarily, to 666 to see if the message disappears?

Hi Eric,

Are you seeing the message in red that says “Cannot set profile flag file [click here to fix]” ?

As far as WordPress SFTP support is concerned, I understand this is an important issue and I see that you have already opened a topic about this.

As for P3, the latest version (1.1.2) was just released. One important change was made to the page that requests FTP credentials. The file that needs to be writable is displayed at the bottom of the page if you want to fix the permissions manually.

Hi erick_paper,

There’s a file that needs to be written to the plugin’s folder (p3-profiler/.profiling_enabled). It needs to be readable and writable by WordPress. If it isn’t set up correctly when the plugin is installed, then P3 offers to correct this situation using WordPress’ built in file system functions.

P3 only passes the FTP credentials through to WordPress. They are not stored or sent anywhere else.

These pages have more information on the exact API used:

https://ottopress.com/2011/tutorial-using-the-wp_filesystem/

https://codex.www.ads-software.com/Filesystem_API

Hi Chris,

..the scan stops and a popup for saving my feeds is opening.

One of the URLs that is scanned is your feed URL. The intent is for users to their feed displayed in the iframe in the scanning dialog. Depending on the browser, this may be rendered as text, or xml, or a formatted page.

Can you post a screenshot of what you’re seeing?

Hi chocaccro,

Please remove the current version of P3 and install the development version:

https://downloads.www.ads-software.com/plugin/p3-profiler.zip

Hi Cecilio,

Thanks for getting back so quickly. I’d like to get more info via e-mail if you’re willing.

Hi Cecilio,

I’ve been working with another customer on a similar issue. I’m not sure if it’s the exact issue you’re experiencing, but if you try out the development version of P3 it may resolve the problem you’ve reported.

https://downloads.www.ads-software.com/plugin/p3-profiler.zip

There’s a new option for “Attempt to circumvent browser cache” in the advanced settings dialog. It should be enabled by default. This should fix any problems with requests that were not being logged by P3 because of a browser or server cache.