Menu

MySql error

Help
2010-11-12
2013-05-30
  • Bill Lancaster

    Bill Lancaster - 2010-11-12

    My phpgedview is working fine despite always getting a message like :-

    ERROR 2: fopen(./index/): failed to open stream: Is a directory
    0 Error occurred on in function fopen
    1 called from line 1277 of file functions_import.php in function write_file
    2 called from line 1376 of file functions_import.php in function accept_changes
    3 called from line 197 of file functions_edit.php in function replace_gedrec
    4 called from line 1483 of file edit_interface.php
    Warning: fopen(./index/): failed to open stream: Is a directory in /customers/lancasterfamilyhistory.co.uk/lancasterfamilyhistory.co.uk/httpd.www/phpgedview/includes/functions/functions_import.php on line 1277 ERROR 6: Unable to open GEDCOM file resource. Unable to complete request.

    Update successful

    I don't understand the message - any ideas?

     
  • Gerry Kroll

    Gerry Kroll - 2010-11-12

    PGV is trying to open your existing GEDCOM file for writing, so that changes you have just completed can be posted to it.

    The Unix/Linux userid under which PGV is running may not have sufficient rights, or the file/path no longer exists.

     
  • Bill Lancaster

    Bill Lancaster - 2010-11-17

    Thanks for the thoughts - still can't make sense of it.

    I created a new pgv on another website.  This time I specified "/index/" (Path and name of GEDCOM on server) when creating a new gedcom.

    I don't get error when adding items.

    The new pgv shows ./index/index  for the gedcom file
    The original shows   ./index/

    Is this significant?

     
  • Bill Lancaster

    Bill Lancaster - 2010-11-17

    Also, if I try to edit the gedcom configuration I get this "The GEDCOM file, ./index/index, does not exist at the specified location."

    The working website has a file called "index" in the index directory, copying it to the nonworking website only creates a second gedcom

     
  • Bill Lancaster

    Bill Lancaster - 2010-11-17

    Solved! (I hope)
    Edited config.php so a file called "index" was expected at ./index/
    copied file "index" from working website
    changes made to the problem website no longer produces errors

     

Log in to post a comment.