fertlaw.blogg.se

1. #Webtrees media phpgedview install
2. #Webtrees media phpgedview update
3. #Webtrees media phpgedview upgrade
4. #Webtrees media phpgedview free

webtrees is the second fork of PhpGedView. Webtrees is a fork of PhpGedView, it was created in early 2010, when a majority of active PhpGedView developers stopped using SourceForge ĭue to issues with exporting encrypted software. It is compatible with standard 5.5.1- GEDCOM files. It requires a web server that has PHP and MySQL installed.

#Webtrees media phpgedview free

Webtrees is a free open source web-based genealogy application intended for collaborative use. Partial translations for Yiddish, Galician, Indonesian, Romanian, Serbian and Japanese. to generate export files, sitemaps, etc.Arabic, Bosnian, Bulgarian, Catalan, Chinese, Croatian, Czech, Danish, Dutch, English (GB, US), Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Italian, Lithuanian, Korean, Norwegian (Bokmål and Nynorsk), Persian, Polish, Portuguese (BR, PT), Russian, Slovak, Slovene, Spanish, Swedish, Tatar, Turkish, Ukrainian and Vietnamese. We'll still need a writable directory (e.g. The configuration and privacy files will shortly be replaced by database tables. Note that the importance of this directory will diminish over time. to generate export files, sitemaps, etc.) There are perhaps two reasons for moving /data/ġ) to allow two webtrees installations to share a common directory (useful in development, where I have several installations, for testing/developing various things independently)Ģ) your webserver isn't honouring the. The original one in the webtrees dir, containing just, and your new/chosen one, containing everything else. Note that to do this, you must have two /data/ directories. The setting for this is in the site-admin screen. To keep things simple (for the masses), you can either upload from the desktop, or import from the /data/ directory.Īs with PGV, you can move the /data/ directory (equivalent of PGV's index directory) to another location. Looking to the future, this will allow modules to integrate more closely with webtrees, and offer more features. (Reports in the reports directory, blocks in the blocks directory, themes in the themes directory, etc.) We've simply formalised the module interface, and moved them all to the modules directory. There were always "modular" components in PGV.

#Webtrees media phpgedview upgrade

The idea behind the "disable module" option is that an upgrade won't add a module that you've previously deleted. While all of them are theoretically "optional", you'll have some very empty pages if you disable them all!

Some provide tabs on the indi page, some provide reports, some provide the blocks on the welcome page. You will see which features are provided by each module.

#Webtrees media phpgedview install

I know the risks of using alpha, and I am not complaining especially given my odd install routine :), but I would appreciate help in getting out of this mess without wiping out all files and tables. in the GEDCOM admin section the GEDCOM name displays, but Webtrees displays gibberish in the GEDCOM Admin section below the name. At this point the install is corrupt with seemingly now way to upload a new GEDCOM. At this point it blew up (pages of PHP errrors) due to the lack of the modules directory. I uploaded it to the data dir and proceeded. I manually created it, and was able to proceed.ģ) the gedcom setup has no way (that I found) to select a path to a gedcom out of the data directory (done in PhpGedView so that people will have a harder time viewing/downloading the gedcom). The wizard flagged the media dir as not being writable.

#Webtrees media phpgedview update

Maybe it was sacrificed for ease, but 2 installs no longer seem able to share a media directory.Ģ) to avoid wiping out my existing media when updating via FTP, I created a mask that bypassed both the media and modules dir where I manually update files. phpgedview/media reference in the config. To do this with ease, I set the media directory in the beta to point at the media directory of the production PhPGedView directory, and reference it with a. I ran into the following issues.ġ) I often test my upgrades in a different directory prior to updating to avoid corruption. Having used PhpGedView for a few years, certain habits die hard.