Suddenly my phpgedview site has started to act funny. During upload of an updated gedcom (exported from Reunion on Mac) is has stopped checking and converting it into a DOS file, and after upload, which seems to go as normal the changes made to the gedcom does not show up. It seems as if the file has been uploaded, but not being used.
-Kolbjorn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kolbjorn
I'm not sure I understand your issue. Let's confirm what you are doing, please.
1) You have a new GEDCOM for upload. It no longer matters what format it may take as long as it is a valid text GEDCOM.
2) You have replaced your previous gedcom with this new one by importing it or you have added a second gedcom?
What are you doing about displaying it? Are you saying the new gedcom is not showing, at all? Or if you edit, changes are not visible? If the latter, have you approved pending changes? Do you have yourself set to auto-approve changes (user management). Do you have SYNC to gedcom checked? (We would no longer recommend this setting, but you need a regular backup routine.)
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have set myself up for auto-approve. I replace the gedcom with a new one, and changes since last time does not show up. What I find strange is that the Mac to DOS conversion is missing when this happens as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kolbjorn
What Mac to DOS conversion? And if you are uploading a new GEDCOM, what changes would there be? If you provide the DB with a fresh GEDCOM, it only knows that data. If you make changes after the upload, then you would then have changes - which according to your settings - would not need approval if made by you.
So, are you making changes to the uploaded data and these changes are not showing? When you go to make your additions or changes in the GEDCOM data, are you seeing the edit interface, completing the changes and saving them - then seeing the confirmation as the box closes?
If you are saying that you have made changes to the GEDCOM offline, and now upload a replacement GEDCOM and none of those changes are visible within PGV, then you have not properly uploaded the replacement GEDCOM. You would have to select YES to the question: "Do you want to erase the old data and replace it with this new data?"
I'm sorry, but your problem is not apparent to me given your explanation.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another possibility s that you've done the upload outside PGV, using FTP or a similar tool. f this is the case, you need to re-import the newly uploaded replacement GEDCOM.
If you don't do this, your new information won't be copied into the database. All information displayed by PGV comes from the database, NOT from the GEDCOM.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is a bug. I discovered that when doing an upload gedcom for a gedcom that already exists in PhpGedView, that the file is uploaded to target.bak, to preserve existing content in case of processing failure. The code also sets a 'flag' to show that the upload is in the .bak file, and uses that to show the warning about overwriting the existing content. However, it then does not use the .bak file when it does the validation and processing.
Fixed locally, and I am in the process of figuring out what I need to do up commit a patch for this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think there's a bug. The "upload replacement" feature works properly for ordinary GEDCOMs.
We know there's a problem when you're uploading a replacement GEDCOM that's inside a ZIP file. PGV gets all mixed up with the file names. This problem has been around for a long time, and is still on the "to do" list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for all your help, guys. I ended up deleting my old phpgedview stuff. I downloaded a new version via SVN, and I'm currently running the phpgedview-ca since my server is the latest Ubuntu. I thought that might remove som php5 related issues if that was the case. How ever, I have had the same problem since I started using the ca-version. It seems to me as if you remove your old installation, install a fresh copy of phpgedview and then uploads your gedcom, it goes well. It even checks the file before upload and converts it from my Mac-type gedcom (exported from Reunion) to DOS type.
The second time I try to upload a replacement gedcom from Reunion it does NOT find that it is a Mac-type gedcom. It says that the file is ok and the upload goes fine. BUT: The changes included in the new gedcom file is not showing up in phpgedview. The last update date will remain from the first uploaded file. It seems to me like pduby is talking about the kind of stuff I'm experiencing.
My way around the problem, at least it has worked twice, is to use the "upload replacement file" link instead of the "upload gedcom" link I've used before. Then the file is checked, converted and shows up after the upload is finished.
Kolbjorn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kolbjorn:
You are absolutely correct: You MUST use the "upload replacement" option when you wish to upload a replacement for a GEDCOM that already exists on your system. You MUST also be sure to use a file name that's identical to the one that's already present.
However, as I said before, we have a problem when the initially uploaded GEDCOM was contained in a ZIP file. PGV gets confused about the various file names. In this case, it's best to upload a replacement GEDCOM (not in ZIP file) using something like FTP, and then re-import the GEDCOM.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Suddenly my phpgedview site has started to act funny. During upload of an updated gedcom (exported from Reunion on Mac) is has stopped checking and converting it into a DOS file, and after upload, which seems to go as normal the changes made to the gedcom does not show up. It seems as if the file has been uploaded, but not being used.
-Kolbjorn
Forgot to say that I'm using 4.2.3…
-Kolbjorn
Kolbjorn
I'm not sure I understand your issue. Let's confirm what you are doing, please.
1) You have a new GEDCOM for upload. It no longer matters what format it may take as long as it is a valid text GEDCOM.
2) You have replaced your previous gedcom with this new one by importing it or you have added a second gedcom?
What are you doing about displaying it? Are you saying the new gedcom is not showing, at all? Or if you edit, changes are not visible? If the latter, have you approved pending changes? Do you have yourself set to auto-approve changes (user management). Do you have SYNC to gedcom checked? (We would no longer recommend this setting, but you need a regular backup routine.)
-Stephen
I have set myself up for auto-approve. I replace the gedcom with a new one, and changes since last time does not show up. What I find strange is that the Mac to DOS conversion is missing when this happens as well.
Kolbjorn
What Mac to DOS conversion? And if you are uploading a new GEDCOM, what changes would there be? If you provide the DB with a fresh GEDCOM, it only knows that data. If you make changes after the upload, then you would then have changes - which according to your settings - would not need approval if made by you.
So, are you making changes to the uploaded data and these changes are not showing? When you go to make your additions or changes in the GEDCOM data, are you seeing the edit interface, completing the changes and saving them - then seeing the confirmation as the box closes?
If you are saying that you have made changes to the GEDCOM offline, and now upload a replacement GEDCOM and none of those changes are visible within PGV, then you have not properly uploaded the replacement GEDCOM. You would have to select YES to the question: "Do you want to erase the old data and replace it with this new data?"
I'm sorry, but your problem is not apparent to me given your explanation.
-Stephen
Another possibility s that you've done the upload outside PGV, using FTP or a similar tool. f this is the case, you need to re-import the newly uploaded replacement GEDCOM.
If you don't do this, your new information won't be copied into the database. All information displayed by PGV comes from the database, NOT from the GEDCOM.
It is a bug. I discovered that when doing an upload gedcom for a gedcom that already exists in PhpGedView, that the file is uploaded to target.bak, to preserve existing content in case of processing failure. The code also sets a 'flag' to show that the upload is in the .bak file, and uses that to show the warning about overwriting the existing content. However, it then does not use the .bak file when it does the validation and processing.
Fixed locally, and I am in the process of figuring out what I need to do up commit a patch for this.
I don't think there's a bug. The "upload replacement" feature works properly for ordinary GEDCOMs.
We know there's a problem when you're uploading a replacement GEDCOM that's inside a ZIP file. PGV gets all mixed up with the file names. This problem has been around for a long time, and is still on the "to do" list.
Thanks for all your help, guys. I ended up deleting my old phpgedview stuff. I downloaded a new version via SVN, and I'm currently running the phpgedview-ca since my server is the latest Ubuntu. I thought that might remove som php5 related issues if that was the case. How ever, I have had the same problem since I started using the ca-version. It seems to me as if you remove your old installation, install a fresh copy of phpgedview and then uploads your gedcom, it goes well. It even checks the file before upload and converts it from my Mac-type gedcom (exported from Reunion) to DOS type.
The second time I try to upload a replacement gedcom from Reunion it does NOT find that it is a Mac-type gedcom. It says that the file is ok and the upload goes fine. BUT: The changes included in the new gedcom file is not showing up in phpgedview. The last update date will remain from the first uploaded file. It seems to me like pduby is talking about the kind of stuff I'm experiencing.
My way around the problem, at least it has worked twice, is to use the "upload replacement file" link instead of the "upload gedcom" link I've used before. Then the file is checked, converted and shows up after the upload is finished.
Kolbjorn
Kolbjorn:
You are absolutely correct: You MUST use the "upload replacement" option when you wish to upload a replacement for a GEDCOM that already exists on your system. You MUST also be sure to use a file name that's identical to the one that's already present.
However, as I said before, we have a problem when the initially uploaded GEDCOM was contained in a ZIP file. PGV gets confused about the various file names. In this case, it's best to upload a replacement GEDCOM (not in ZIP file) using something like FTP, and then re-import the GEDCOM.