HuMo-genealogy manual
The HuMo-genealogy manual can be found here: https://sourceforge.net/projects/humo-g ... en_Manual/
Install or update HuMo-genealogy
1) Go to admin page.
2) Install new HuMo-genealogy version.
3) Renew admin page. A message will be shown If there is a database update.
Large family tree
If there is a large family tree (several thousands of persons) it's possible the screen freezes for a moment. The cache (memory) is then filled with data. If cache would be disabled the page would be slow every time.
Use pictures
From the HuMo-genealogy manual:
1) It is advisable to save the names of pictures in small (non capital) letters. That way most problems on Linux servers can be avoided! This is because on Linux servers "Picture.jpg" is a different picture than "picture.jpg".
2) Don't use spaces in filenames and folder names. Example: john_snow.jpg
3) Don't use accent characters (é and è for exampe) in filenames and folder names.
Also see: https://www.mtu.edu/umc/services/websit ... ers-avoid/
Reset admin password
Best way to reset the admin password at this moment if password is lost:
Open PHPMyAdmin
Open table humo_users
Go to the admin user line (or the user name with admin rights)
If there is a field "user_password_salted", empty this field.
Change user_password into: 712697cdade1e78580bf26e564a891f5
This will reset the password to the default password: humogen
Access to website is blocked
There is a security item HuMo-genealogy. If there was a wrong login from a IP address 10x, then this IP address will be blocked. Removal of history or cookies won't help, this is a HuMo-genealogy security item.
There are 2 possibilities to solve this:
1) To change number of logins fails, open file include/db_functions.php and find line 182:
Code: Select all
if ($check_fails > 10) $allowed=false;2) Wrong logins can be found in table: humo_user_log
The problem will be solved is this table is made empty.
Serious problems at website (without showing an error)
- First try go the the page in HuMo-genealogy that has a problem (to create an error line in the log file)
- Log into the providers control panel, and select "DirectAdmin".
- Select your domainname.
- Select "Site Summary / Statistics / Logs"
- Line "Web Error Log" click "100 lines".
A log of errors should be seen. Check if the last error is the error from HuMo-genealogy.
If I have the error message, I can try to solve this problem.
Process large gedcom files
It's possible a standard hosting provider won't process your large gedcom file (small gedcom files with a few thousand persons should be no problem).
Maybe you need a virtual server or your own webserver so it's possible to control the websites settings (timing and memory) yourself.
Other possible solutions to process a large gedcom file:
- Split the large gedcom file and read the parts in HuMo-genealogy. It's possible to add a gedcom file to a family tree.
- Install HuMo-genealogy at a PC or laptop, read the gedcom file. Export the database using PHPMyAdmin. Go to your provider -> PHPMyAdmin, and read the database.
If you have one or multiple very large family trees, and you are using the gedcom import regularly, it's better to change the database id's into BIGINT.
ALTER TABLE humo_persons CHANGE pers_id pers_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT
ALTER TABLE humo_unprocessed_tags CHANGE tag_pers_id tag_pers_id BIGINT(20) UNSIGNED NULL DEFAULT NULL
ALTER TABLE humo_families CHANGE fam_id fam_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE humo_unprocessed_tags CHANGE tag_rel_id tag_rel_id BIGINT(20) UNSIGNED NULL DEFAULT NULL;
ALTER TABLE humo_addresses CHANGE address_id address_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE humo_unprocessed_tags CHANGE tag_address_id tag_address_id BIGINT(20) UNSIGNED NULL DEFAULT NULL;
ALTER TABLE humo_connections CHANGE connect_id connect_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE humo_unprocessed_tags CHANGE tag_connect_id tag_connect_id BIGINT(20) UNSIGNED NULL DEFAULT NULL;
ALTER TABLE humo_events CHANGE event_id event_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE humo_unprocessed_tags CHANGE tag_event_id tag_event_id BIGINT(20) UNSIGNED NULL DEFAULT NULL;
ALTER TABLE humo_location CHANGE location_id location_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE humo_unprocessed_tags CHANGE tag_place_id tag_place_id BIGINT(20) UNSIGNED NULL DEFAULT NULL;
ALTER TABLE humo_sources CHANGE source_id source_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE humo_unprocessed_tags CHANGE tag_source_id tag_source_id BIGINT(20) UNSIGNED NULL DEFAULT NULL;
ALTER TABLE humo_texts CHANGE text_id text_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE humo_unprocessed_tags CHANGE tag_text_id tag_text_id BIGINT(20) UNSIGNED NULL DEFAULT NULL;
ALTER TABLE humo_unprocessed_tags CHANGE tag_id tag_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;