![]() ![]()
a list of tables, plus a list of every step you've taken), I can't really suggest anything. Phpgedview webtrees media code#There is nothing in the code that creates tables in the PGV database. > I can see that the wizard already created some tables in the existing PGV but not user accounts, preferences and configuration) by exporting your data to a GEDCOM file, and importing that into webtrees. If you want to use the transfer wizard, then I'd suggest installing webtrees on the PGV server, and then using phpmyyadmin to copy the database to your new server.Īlternatively, you can transfer your genealogy data (i.e. "localhost" and "127.0.0.1"), then webtrees won't be able to work this out. Note that if the two databases *are* on the same server, but you have given them different names (e.g. This only works if the two databases are on the same server The data is copied using SQL statements such as INSERT INTO webtrees.wt_table SELECT * FROM phpgedview.pgv_table. This means that webtrees found the configuration file for PGV, and the database is on a different server to webtrees. to generate export files, sitemaps, etc.> I get 'PhpGedView must use the same database as webtrees.' 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. Phpgedview webtrees media 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. Phpgedview webtrees media 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. Phpgedview webtrees media 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |