[Plugin: P3 (Plugin Performance Profiler)] Error reading scan

Under settings -> media, what is the value of “Store uploads in this folder” ?

And what version of P3 are you using?

Settings -> Media is empy. I’m using the default wp-content/uploads folder.
I’m using version 1.3.1

Please go into your FTP client and find your wp-content/uploads/profiles folder. Change the permissions on that folder so that it’s writable by the web server. Here’s a quick step-by-step:

1.) Set the folder to 755, try P3. If it works, stop here. If it doesn’t work, try the next step.
2.) Set the folder to 775, try P3. If it works, stop here. If it doesn’t work, try the next step.
3.) Set the folder to 777, try P3. If it works, stop here. If it doesn’t work, then folder permissions aren’t the problem (and reset the permission to whatever they were originally).

It was no the permissions. What else can I do?

Have you tried using debug mode?

“Error reading scan” means that either the scan file is not present (permissions error or media settings error), there are no lines in the file (use debug mode to see why), or the scan cannot be parsed (each line is a json object).

You can view the scans in wp-content/uploads/profiles/[scan name].json to see if the scan files are being created. If you open the file, you can see if there’s content in it. And if you select any line in the file, you can paste it into json viewer to see if it is valid json.

The scan file is not created.
I tried the debug mod, setting the folder to 777 again.
No file is created and the debug log is empty.

What can I do for the Media settings?

Hi, can you e-mail me the debug CSV dump to kpayne -at- godaddy -dot- com? I’d like to see why if it is even picking up your visits.

Hi nemoprofeta, thanks for contacting me. I haven’t heard back from you, though. If you have more information or want to look into this again, please contact me here or just reply to our e-mail thread. Thanks!

having the same problem. even changed the default media folder.
log is empty – so i can’t mail anything :/

Warning: fopen(xxx/wp-content/uploads/profiles/scan_2012-09-12_437bad28.json) [function.fopen]: failed to open stream: No such file or directory in xxx/wp-content/plugins/p3-profiler/classes/class.p3-profiler-reader.php on line 153

i think it is a path or plugin-failure, because it worked once. but the site is live (now) and i can’t disable everything to check.

so finally no files are created in no folder :/

Hi holospirit,

Do you have a wp-content/uploads/profiles folder? Is it writable by the webserver?

yes, checked all for 755 and even made a new im my media (new) folder.
your .htaccess and index.php even – so this creation seem to work.

is the a “hard-code” way to find out the problem?

The path is determined here:
https://plugins.trac.www.ads-software.com/browser/p3-profiler/tags/1.3.1/classes/class.p3-profiler-plugin-admin.php#L98

Are there any *.json files in the folder? If not, that means P3 can’t (or isn’t) creating the profiles during scanning.

To determine if P3 should be creating these files, but isn’t, use “Advanced settings -> Debug mode.”

To determine if P3 can’t create these files, try chmodding the profiles folder to 777 and running another scan.

Are there any *.json files in the folder? If not, that means P3 can’t (or isn’t) creating the profiles during scanning.

no json-files are created. folder is 777 and “working”

To determine if P3 should be creating these files, but isn’t, use “Advanced settings -> Debug mode.”

debug is empty/not created
(“Profiling Enabled”,”Recording IP”,”Scan Name”,”Recording”,”Disable Optimizers”,”URL”,”Visitor IP”,”Time”,”PID”) – thats all

To determine if P3 can’t create these files, try chmodding the profiles folder to 777 and running another scan.

done, no success.

i played a little – creating files works. i think the problem is somewhere about ajax_start_scan(). i added a random file creation here and it isn’t executed. the auto walk through pages with the iframe seem to work.

:/

Are you using the “Attempt to circumvent browser cache” and “Attempt to disable opcode optimizers” too?

If you have Varnish (etc.) on your site and aren’t using the latter option, then P3 may not be hitting PHP at all. It’s a stretch, but I would be remiss if I didn’t ask.

i think the problem is somewhere about ajax_start_scan().

Have you checked for any errors in your javascript console?

Have you turned on WP_DEBUG and WP_DEBUG_LOG?

Hello, I have encountered the same problem.Linux + apache environment under normal use, but the above error message appears in the windows host.