errors in Individual report

Sarunas K
2009-10-01
2013-05-30
  • Sarunas K

    Sarunas K - 2009-10-01

    I am getting some errors when trying to generate PDF report for Individual. For some people it works, but for some I am getting this error:

    ERROR 8: Array to string conversion
    0 Error occurred on in function preg_replace
    1 called from line 2393 of file class_reportbase.php in function PGVRvarSHandler
    2 called from in function call_user_func
    3 called from line 1438 of file class_reportbase.php in function startElement
    4 called from in function xml_parse
    5 called from line 2559 of file class_reportbase.php in function PGVRFactsEHandler
    6 called from in function call_user_func
    7 called from line 1459 of file class_reportbase.php in function endElement
    8 called from in function xml_parse
    9 called from line 347 of file reportengine.php

    Any ideas? Thank you.

     
  • Greg Roach

    Greg Roach - 2009-10-01

    Which version of PGV?

     
  • Sarunas K

    Sarunas K - 2009-10-01

    version 4.2.2

     
  • Im

    Im - 2009-10-03

    Sarunas

    Do you have a website where we can take a peek? And which INDI?

     
  • Sarunas K

    Sarunas K - 2009-10-03

    Yes, I have but it just for registered users. Of course, I can make temp user for test purposes and send data by mail.

     
  • Im

    Im - 2009-10-03

    Do we have to log in to take a peek? I mean, does this problem occurs only for 'alive' INDI's or is your site completely closed ?

    You wrote that this is a PDF issue. Does the HTML working for you?
    How does the indi record look like? Or the FAMS?

    I have many more questions or you can just drop me mail with a temp user to see whats going on…

     
  • Sarunas K

    Sarunas K - 2009-10-03

    sorry, I do not know how to send email to you :)
    my mail is sarunas dot kebeikis eta gmail dot com
    site is private and you should log in. For HTML report errors are the same.

     
  • Gerry Kroll

    Gerry Kroll - 2009-10-04

    The problem was tracked down to a 1 EVEN record that didn't have a 2 TYPE sub-record.

    A patch has been provided, and the correction is in SVN too.

     
  • Sarunas K

    Sarunas K - 2009-10-04

    Thank you very much for help. I made a correction to the EVENT records with more or less correct format including TYPE and now it works. Especial thanks to Im Sz (Imsza) and Gerry Kroll (canajun2eh) who identified a problem.

     

Log in to post a comment.