I fear, that's what it looks like in phpmyfamily 1.4.x. In my 2.0.x version logging in as admin gives me a link for "complete gedcom". The export I remember to have programmed for the 1.4 version only existed in a zip file on my webserver 10+ years ago. I deleted it at some time and have looked at some possible places on old hardware. Unfortunately without success. The safest way of achieving your goal is probably: - sqldump of your database - install of version 2 on a local computer - restore database...
Hi there, for a few days now I can log in as Admin to view and change things. I have seen that when I am logged in and go to a screen of a person, I can create a gedcom file of that person. But no relationships are shown in this. For example, the "Details" screen does contain marriage data and children and brothers and sisters, but they are not in the gedcom. And does a gedcom file have to be created for each person? I thought that the entire family tree was included in a gedcom file.
Thanks for clarifying. I should have read the whole thread, sorry. From what I can see in your "Genealogie Vlieland" database is, that you have quite a number of media files. That is not really a problem, as only references to the pictures are exported. If there is more than one picture per person it seems to depend on the target systems import what is going to happen. Pictures can be assigned to events in gedcom, but the phpmyfamily export only assigns to individuals.
Thanks Geltmar for the detailed answer; as I explained earlier there are indeed 3 different databases and they are completely separate. So they can also be exported separately.
Okay, I'll try to describe, what worked for me, what's currently (probably) wrong with the export and some things I did to repair the data. backup everything !!! esp. the database follow the instruction to upgrade from latest phpmyfamily 1.4.x to 2.2.x (this shouldn't do much to the data, some restructuring of the database and basically you get a new codebase, that is completely different. Within that codebase there is a gedcom.php to export all data in one gedcom file) I did some adjustments to...
Hello Geltmar, thanks for your message. Can you tell me some more about the "somewhat workable" and also about those "quirks" in relation to "good enough? The database concerned in our case contains more than 22.000 people. So you'll understand that manually fixing things afterwards is no option!
Just want to encourage you to go the "upgrade road". It's quite some time time ago, but I was able to migrate from 1.4 tree to 2.x. Once everything is in there, a somewhat workable gedcom export is available. I used it last month to migrate to webtrees. The export has some quirks, but depending on your data might be "good enough".
Thank you Ian. I'll contact the guy who owns the website and perhaps we'll be able to make an export-file.
possibly under preferences - I think you will need to be an admin There aren't that many places to look! I am running version 2 so can't really compare but it should be similar
Thank you, Ian, for your answer. Where can I find the gedcom export that you mentioned? Or how do I do that?
yes, it's very outdated and effectively no longer maintained I believe there's a gedcom export although I can't remember how well it works in 1.4.2 That would be the first thing that I would try Depending on how technical you are, you could try updating to the latest version as that contains various updates/upgrades but that may not be entirely trivial gedcom is probably still the way to go
Who can help? A genealogy website was once created with phpmyfamily v1.4.2 (http://www.cpvanderlaan.nl). This website contains 3 separate databases, namely genealogy Fam. Van der Laan, Genealogy Vlieland and Vlieland 40-45. I am now interested in the 2nd database: Genealogy Vlieland. This contains data on almost 22,000 people. The man who once set up all these databases has asked whether the Cultural Historical Association Vlieland wants to take over this database and continue to maintain it. But,...
I definitely wish I could contribute. I recognise enough to debug a chunk however it really is it. I'm using this now as it's the perfect to maintain as you can read more. The few others accessible are not person friendly at all. Hopefully your plans will exchange :)
Insert picture
Marvin Francois, Effectively! that was the error. $ sudo apt install php-bcmath $ sudo systemctl restart apache2 And work fine! Very thanks!!
debian stretch PHP 7.0.33-0
sounds like you do not have the BCMath extensions for PHP enabled. http://php.net/manual/en/book.bc.php On Sun, Mar 10, 2019 at 5:54 AM Dani damufo@users.sourceforge.net wrote: Hello: pmfv2-2-0 I get this error. Fatal error: Uncaught Error: Call to undefined function bcsub() in /home/user/phpmyfamily/inc/footer.inc.php:38 Stack trace: #0 /home/user/phpmyfamily/people.php(265): include() #1 {main} thrown in /home/user/phpmyfamily/inc/footer.inc.php on line 38 Very thanks! [feature-requests:#59] https://sourceforge.net/p/phpmyfamily/feature-requests/59/...
Which version of php are you using?
Hello: pmfv2-2-0 I get this error. Fatal error: Uncaught Error: Call to undefined function bcsub() in /home/user/phpmyfamily/inc/footer.inc.php:38 Stack trace: #0 /home/user/phpmyfamily/people.php(265): include() #1 {main} thrown in /home/user/phpmyfamily/inc/footer.inc.php on line 38 Very thanks!
Wonderful !! as long as I can test.
Support for PHP7+
I've just released 2.2.0 which should support this - sending a longer release email
Creating Branch 2.2.0
pdo means PHP Data Objects, it is the current accepted and supported database connection type that needs to be used when using PHP 7. the original version of PHPMyFamily used the fully deprecated mysql database connector, but that can no longer be used. the pdo brqanch is a rewrite that switches the code to use PDO. http://php.net/manual/en/book.mysql.php On Thu, Feb 14, 2019 at 2:48 AM Dani damufo@users.sourceforge.net wrote: OK! What is the difference between the branch pmf2-2.2.0 and the branch...
OK! What is the difference between the branch pmf2-2.2.0 and the branch pmf2-2.2.0-pdo? What mean pdo?
I have moved it to the sourceforge version of git which is a lot better than CVS! If you think that's not good enough then please open a new ticket. Back to the original ticket - it's nearly ready for a new release for php 7 - I'll try and do it next week.
More upgrade work
Could it be possible to add the code to a git repository (github, gitlab ...)? I thought that would help the collaboration.
Support for MySQL 5.7 - primarily replaces 0000-00-00 dates with NULL - also fixes transcript associated to person
Add in files for docker-compose for local dev
Update CHANGELOG
Convert install script to use PDO methods
Convert CurrentRequest date format query to PDO
I am really interested in this. About to install what you have, Have been using this since at least 2010.. was running it on PHP 5.6 until I had to upgrade to 7
It's quite a big chunk of work... If anybody else wants this then please add a note here to push me in to doing it a bit faster - I will do it, and try to do it fairly soon, but don't want to promise anything. (volunteers also welcome!) Having said that: I'm running an existing site on PHP 7 using the pmf2-2.2.0 branch from git - there's a bunch of stuff that doesn't work but a lot that does
Fix transcript errors
Rename error function
Remove mysql_connect as it's no longer supported in PHP 7
Fetch dojo using https
Support for PHP7+
Altered for 1.3.0 release
Initial revision
googlized
added 1.4.2 release
New release (1.4.1)
rereleased with version increment
rereleased with version increment
Updated for the release of 1.3.1
Merge www.phpmyfamily.net
Broken link fixed
New release (1.4.0)
Remove submodules
Initial revision
Minor logic fixes
date restriction around join for when not logged in
Change geocode lookup to take account of server configuration
Fix for when there's no parent
Remove parent restriction
Increase size of source and reference fields
Update dojo version
Add string for message when filtered select for people doesn't match
Always use FilteringSelect when dojo is enabled
Change to use text/json instead of text/json-comment-filtered
Comment out content-type header as it causes a 500 error on some hosts
Update to dojo version
Add rich text editing
Change to use do_headers_dojo so that drop downs work
Add TRIM when migrating names
Add columns for image and transcripts directories - path is relative to document root and can be outside the document root
Table for storing details of records imported via gedcom
Increase size of lat/long columns
Table for storing details of sources
Table for storing details of sources
Table changes associated with introduction of sources and associated of images/transcripts with events
*** empty log message ***
Changes associated with introduction of sources and association of images/transcripts with events
Strict rules changes
Add columns for image and transcripts directories - path is relative to document root and can be outside the document root
Allow for images outside of document root
Strict rule changes and moving certification to source
Strict rule changes and moving certification to source
Class for details of sources
Ignore any files with database connection details
Check dojo is enabled before including
Check dojo is enabled before including
Changes to fit new data model
Formatting change and other minor fixes
Change version
Add more strings
Add image and file directory columns
Replace schedule
Various fixes
Add sources info
Add gedcom and source DAOs
Allow for sources and other events
Changes to do with the introduction of sources
New module for gedcom processing