2 one line fixes for better error reporting and save TONS of time
-
I don’t know what others feel, but although WPPipes is an excellent product, trying to debug your pipe is next to impossible because the error messages on failure are practically worthless and you can’t tell which processor failed, especially if you’re using a lot of HTML parsers and a lot of parser code in each.
I decided to dig through the code and was able to make two one line fixes that eliminate most of the time wasting.
1) Identifying which processor failed.
This is the big change that will save you TONS of time. Do the following:
a) Edit wp-content\plugins\wp-pipes\grab.php
b) In function process around line 390 in the file add the following line:
$data['stop']->msg='<br/>PROCESSOR#: '.$i.'<br/>PROCESSOR NAME: '.$pipe->params->note.'<br/>'.$data['stop']->msg.'<br/>';
as shown here:
https://screencast.com/t/j9gBAJnMh2) Better info when an HTML processor fails.
This merely provides the parser code so you can see right away what code is on the line that WPPipes says there was an error in.
a) Edit wp-content\plugins\pipes-processor-htmlparser\lib\psc.php
b) In public static function run_parser_code around line 43, replace this line:
self::setStop( $res, "Error row-{$i}: " . $resf[1] );
with this one:
self::setStop( $res, "Error row-{$i}: " . $resf[1].'<br/>PARSER CODE:<br/>'.str_replace("\n",'<br/>',var_export($funcs,true)));
as shown here:
https://screencast.com/t/yIo1yQdw6XKlThe result when you get an error is the following additional information in the yellow boxes:
https://screencast.com/t/fOBhtmw9BMKIf you upgrade the plugins, you’ll need to reapply these patches again unless they add them to the plugin so we all save time.
ENJOY!
- The topic ‘2 one line fixes for better error reporting and save TONS of time’ is closed to new replies.
