One of the characteristics of EP4 is that an error log generated as part of processing the file(s) is presented to the user within the EP4 admin screen.
The way this has been enabled/performed has been basically through error catching when using standard PHP commands instead of using the ZC related functions. Support of multiple versions of PHP has required specifically formatted code to allow continued operation and to have/keep this EP4 "error log". Ultimately though, compatibility of EP4 with future versions of PHP and ZC arrangements would be improved if ZC functions could be used throughout instead of mysql/mysqli functions.
Look into the way to "overtake" the ZC error processing for the time(s) when it would be desirable to have the EP4 log available/generated. This may mean that the method of error processing is swapped back and forth during operation as a possibility; however, should not do so during the actual processing to reduce the number of extraneous operations during large file processing.
One of the characteristics of EP4 is that an error log generated as part of processing the file(s) is presented to the user within the EP4 admin screen.
The way this has been enabled/performed has been basically through error catching when using standard PHP commands instead of using the ZC related functions. Support of multiple versions of PHP has required specifically formatted code to allow continued operation and to have/keep this EP4 "error log". Ultimately though, compatibility of EP4 with future versions of PHP and ZC arrangements would be improved if ZC functions could be used throughout instead of mysql/mysqli functions.
Look into the way to "overtake" the ZC error processing for the time(s) when it would be desirable to have the EP4 log available/generated. This may mean that the method of error processing is swapped back and forth during operation as a possibility; however, should not do so during the actual processing to reduce the number of extraneous operations during large file processing.