I have just discovered that the ownership and permissions on my remotely-hosted PGV archive were all over the place. With a lot of fiddling, I was able to delete the lot and unpack a fresh tarball. Unfortunately the permissions in it were incorrect, with a lot of directories and subdirectories being permission 755.
My main problem is that I can open an edit window, but I can't type in it, or close it. I can edit the GEDCOM record directly. This has been like it for some time, and it has survived the reinstall. My local copy is fine. Where should I start looking?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Further on editing: A new member has just edited extensively, and I accepted her edits O.K. I am coming to the conclusion that the problem is limited to my account. Re-installing failing to fix it suggests that the problem is in the database, not the program. Intuitively, that doesn't make sense, but the easy test is to create a fresh admin account.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have just discovered that the ownership and permissions on my remotely-hosted PGV archive were all over the place. With a lot of fiddling, I was able to delete the lot and unpack a fresh tarball. Unfortunately the permissions in it were incorrect, with a lot of directories and subdirectories being permission 755.
My main problem is that I can open an edit window, but I can't type in it, or close it. I can edit the GEDCOM record directly. This has been like it for some time, and it has survived the reinstall. My local copy is fine. Where should I start looking?
Permissions: I have run fixperms.sh then chmodded the index/ directory This issue seems O.K.
Editing: Editing a persons reference number is possible. The problem seems confined to data fields.
Further on editing: A new member has just edited extensively, and I accepted her edits O.K. I am coming to the conclusion that the problem is limited to my account. Re-installing failing to fix it suggests that the problem is in the database, not the program. Intuitively, that doesn't make sense, but the easy test is to create a fresh admin account.