View Issue Details

IDProjectCategoryView StatusLast Update
0000003Timekoin ServerGeneral Issuepublic2012-06-20 16:23
Reporterepstrom Assigned ToKnightMB  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version1.0 
Target Version2.41Fixed in Version1.2 
Summary0000003: Unable to jump to row 0 on MySQL result
DescriptionWarning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 26 in /home/directsp/public_html/epstrom.com/timekoin/function.php on line 685

Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 27 in /home/directsp/public_html/epstrom.com/timekoin/function.php on line 686
Steps To ReproduceOpen Home , Send / Receive Pages
TagsNo tags attached.

Activities

KnightMB

2012-06-19 21:45

administrator   ~0000002

This is the result of the "mysql_result" not finding the data requested. It's actually not an error (because if there is no row, then it reports 0). But for some reason is logged by PHP due to a E_WARNING setting for error reporting. We noticed during development long ago and the only to get rid of it is to turn off the E_WARNING by removing it from "error_reporting" in your php.ini file.

The only solution would be to use a slower way to getting the same information with more commands. Our hope is that this bug in PHP will one day be fixed.

epstrom

2012-06-20 06:31

reporter   ~0000004

error_reporting(NULL);

could be used at configuration.php, since it's used by every page

KnightMB

2012-06-20 16:05

administrator   ~0000005

Thanks for that jewel, all these years I thought this could only be disabled in the php.ini file, but a php command that does it for you is even better. This will certainly be included in the next release!

KnightMB

2012-06-20 16:23

administrator   ~0000006

error_reporting(E_ERROR | E_CORE_ERROR | E_COMPILE_ERROR);

This was added to the code to show only fatal errors in the software, should they happen. All warnings that have no effect on the software will no longer be logged or displayed.

Issue History

Date Modified Username Field Change
2012-06-19 17:36 epstrom New Issue
2012-06-19 21:45 KnightMB Note Added: 0000002
2012-06-19 21:45 KnightMB Assigned To => KnightMB
2012-06-19 21:45 KnightMB Status new => acknowledged
2012-06-20 06:31 epstrom Note Added: 0000004
2012-06-20 16:05 KnightMB Note Added: 0000005
2012-06-20 16:23 KnightMB Note Added: 0000006
2012-06-20 16:23 KnightMB Status acknowledged => resolved
2012-06-20 16:23 KnightMB Fixed in Version 2.41 => 1.2
2012-06-20 16:23 KnightMB Resolution open => fixed