Jethro v2.25.0

This minor release includes various bugfixes and some small enhancements.

Enhancements

• Issue #521 When a mobile number is shown, you can now choose between sending an SMS via Jethro, using the local device (on mobile) or using iMessage (on mac)

Bugfixes

• Right-click "Copy email address" now works when email addresses are shown (used to be over-encoded)
• Issue #344 - you're now warned if SMS sending will fail because the current user's mobile number is blank
• Issue #540 - errors during roster CSV download fixed
• Issue #481 - no longer send emails re notes that I assigned to myself
• Issue #541 - in standalone-safari you no longer have to log in whenever you switch back from another app
• Issue #542 - DB error during install

Upgrade Procedure

1. Log out of Jethro
2. Take a backup of your mysql database
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2018-upgrade-to-2.25.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Log in and test.

Jethro v2.24.1

This release offers some minor enhancements and fixes a few bugs from 2.24.0.

Enhancements

• Person/Family photo uploads on mobile now allow either new-photo or camera-roll selection
• Headcount field now uses numeric keypad in iOS
• Issue #410 - service component usage stats simplified
• DOCX contact list - single-person photos now shown smaller than family photos

Bugfixes

• Issue #524 - custom field values not displayed correctly
• Issue #527 - photo scaling issue
• Issue #474 - group-members listing was too crowded
• Issue #531 - service component sorting is now case insensitive
• Issue #533 - error re archived family members and deleting persons

Upgrade Procedure

1. Log out of Jethro
2. Take a backup of your mysql database, especially if upgrading from a version older than 2.24.0
3. If upgrading from a version older than 2.24.0: Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2018-upgrade-to-2.24.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Log in and test.

Jethro v2.24.0

Enhancements

• Reports can now be configured so that their results are automatically displayed on the home page (Thanks @vanoudt )
• Issue #30 - it is now possible to delete a person entirely (in most cases) and/or to "cleanse" their person record, removing identifying details and leaving an anonymous shell.* Personnel list at the top of a service run sheet now has "email all" and "SMS all" links
• Issue #493 - notes list on home screen now links names to person details, as well as note subject to the note details.
• Issue #519 - if a single-member family has a family photo, treat that as the person photo for the one family member

Bugfixes

• Issue #518 - family photos no longer cropped, just resized
• Issue #508 - custom fields were being wiped by a person editing their details in the members area - now fixed
• Issue #512 - importer now copes better with trailing spaces
• Issue #513 - "other" values were appearing in the history when unchanged - now fixed
• Issue #509 - changes to Feed UUID (ical link) no longer show in history
• Issue #492 - Meaning of the RESTRICTED_USERS_CAN_ADD setting has been clarified
• Issue #506 - age_bracket.is_adult column type corrected in DB
• Issue #457 - zero dates in database, not allowed in recent versions of MySQL, now cleaned up

Upgrade Procedure

1. Log out of Jethro
2. Take a backup of your mysql database
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2018-upgrade-to-2.24.sql (Note there is no SQL upgrade for v2.23).
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Log in and test.

Credits

Thanks @vanoudt for the home-page-reports feature.

Jethro v2.23.2

This release adds some minor enhancements and fixes a few bugs.

Enhancements

• Improvements to page layout in the members area
• Spell check now enabled in rich-text fields
• Roster-pesonnel keywords in service components can now include an index, eg %BIBLE_READER_1_FIRSTNAME%
• Personnel section of service run sheet page now has email/sms links

Bugfixes

• #405 - family photos are now displayed in members interface
• #460 - bulk update sometimes failed the first try
• #470 - error when mysql in strict mode (thanks @Condrad Smith)
• #472 - sometimes running out of memory constructing person history (thanks @Condrad Smith)
• #498 - photo rotation sometimes incorrect, now autodetected

Upgrade Procedure

1. Log out of Jethro
2. Take a backup of your mysql database, especially if upgrading from a version older than 2.22.0
3. If upgrading from a version older than 2.22.0: Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2018-upgrade-to-2.22.sql (There is no upgrade for v2.23)
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Log in and test.

Jethro v2.23.1

Enhancements

• Script to send roster reminders by email or SMS (thanks to @s4069b and @vanoudt)
• Issue #453 - mailto links now open in a new tab for gmail

Bugfixes

• Issue #409 - it's now possible to bulk-update congregation to "none" for contacts
• Issue #418 - resolved issue when some links were opened in a new tab/window
• Issue #455 - people with surname "?" are now visible in the all-persons view
• Issue #400 - invalid characters are now stripped from SMS messages
• Issue #457 - database errors under MySQL strict mode when adding family
• Issue #408 - send-report script now handles grouped results and newlines in values

Upgrade Procedure

1. Log out of Jethro
2. Take a backup of your mysql database
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2018-upgrade-to-2.23.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Log in and test.

Credits

Thanks to @s4069b and @vanoudt for code contributions, and to all the users who post helpful bug reports.

Jethro v2.22.0

Enhancements

• Issue #451 - You can now send mailchimp campaigns and configure mailchimp-sync details from within Jethro

Bugfixes

• Issue #414 - error upgrading settings
• Issue #345 - errors when a custom field had too many options
• Issue #425 - error on SQL upgrade if no custom fields were defined
• Issue #427 - database error with certain MySQL versions due to invalid datetime format in query
• Issue #431 - Bulk actions now work correctly from display-tabular-attendance page
• Issue #440 - sometimes database error when including 'adults in family' in report
• Issue #452 - task notification settings now visible on the system-config page

Upgrade Procedure

1. Log out of Jethro
2. Take a backup of your mysql database
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2018-upgrade-to-2.22.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Log in and test.

NOTE: The mailchimp sync script can still be called with Report ID, mailchimp API key and list ID as command line arguments as before. However to take advantage of the benefits of Issue #451 it is worth moving these values to the Jethro DB and running mailchimp_sync.php without any arguments. The Mailchimp API key is stored in system settings (Admin > System Configuration) and the list ID to which a report is saved in the relevant report's configuration (down the bottom).

Credits

Thanks to @tim-pearce @thesle for contributing to this release.

Jethro v2.21.2

This version adds a few bugfixes to v2.21.

Bugfixes

• Issue #402 - fixed error on reports page in PHP7
• Issue #407 - fixed problem importing values for custom fields whose name contained a space
• Fixed various other PHP7-compatibility issues
• Fixed mysql too-many-connections error in some circumstances
• Fixed bugs with searching on notes-list pages

Upgrade Procedure

1. Log out of Jethro
2. Take a backup of your mysql database, especially if upgrading from a version older than 2.21.0
3. If upgrading from a version older than 2.21.0: Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2017-upgrade-to-2.21.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Log in and test.
8. If upgrading from a version older than 2.19.0 you will see a bunch of messages about settings that have been migrated out of your conf.php file into the database. AFTER you've seen these messages, (a) rename your conf.php file to conf-old.php, (b) rename conf.php.sample to conf.php, and (c) edit conf.php and insert the necessary database details. (Most settings will no longer be in conf.php).

Jethro v2.21.1

This release adds a few bugfixes to version 2.20.0

Bugfixes

• Issue #397 - SMTP_PORT setting is now visible in conf file and system-config page
• Issue #399 - you can now change a person's congregation from something to 'none'
• Issue #390 - groups that should be hidden now are
• Issue #395 - users with only 'view' permission for services can now view run sheets
• Issue #396 - mailchimp sync script now works on linux again

Enhancements

See the version 2.20.0 release notes for the new features introduced there.

Upgrade Procedure - if upgrading from a version OLDER than 2.19.0

1. Log out of Jethro
2. Take a backup of your mysql database. Really, do it.
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2017-upgrade-to-2.21.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
   1 Note: Jethro no longer needs the MDB2 libary, so if you have the MDB2 dropin in your old system, don't copy it to your new one
7. Important extra step: Open Jethro in your browser. You should see a bunch of messages saying "The setting XYZ has been migrated to the database and can/should be removed from conf.php". (Alternative option: Instead of opening Jethro in the browser you can run scripts/migrate_settings.php)
8. Once you've seen the messages above, rename your conf.php to conf-OLD.php. (Make sure you keep the .php extension - otherwise you'll expose your database credentials to the world)
9. Rename conf.php.sample to conf.php
10. Edit conf.php and for each setting that's in there, copy its value from conf-OLD.php.
    NB a) many settings will no longer be in conf.php because they've migrated to the database
    NB b) SMTP and SMS related settings will NOT have been automatically migrated to the database, so either leave them in the conf.php file or enter them manually into the web interface
    NB c) There are new settings for DB_DATABASE, DB_USERNAME etc, but the old PUBLIC_DSN etc still work.
11. Log in to Jethro and check your system configuration at Admin > System Configuration

Upgrade Procedure - if upgrading from v2.19.x or 2.20.x

1. Log out of Jethro
2. Take a backup of your mysql database
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2016-upgrade-to-2.21.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Note: Jethro no longer needs the MDB2 libary, so if you have the MDB2 dropin in your old system, don't copy it to your new one
8. Note: Although there is a new format for database settings in conf.php.sample, the old DSN format still works.
9. Log in and test.

Jethro v2.20.0

This release adds a few new features, fixes several bugs, and makes Jethro PHP7 compatible.

Enhancements

• Custom fields of type "select" can now support an "other" option with textual value entry.
• When adding a family, you can now select a group to add each member to. (Each group has a new property to control whether it's available in the add-family form)
• In the note-listing pages, you can now filter by keyword
• In the note-listing pages, you can now display full notes instead of summary listing
• Family contact list DOCX export now includes family photos
• Photos are now visible and editable in the mobile interface, including access to the phone's camera and photo library.
• Script to email a report (@s4069b)
• In service component credits, (c) is now converted to © on save
• Jethro no longer relies on the legacy MDB2 database library, which simplifies installation (@vanoudt)
• Entering database details into the config file now uses a simpler format (@vanoudt)
• Jethro is now compatible with PHP7

Bugfixes

• Issue #364 - wrong filename extension for DOCX download in safari
• Issue #361 - importer failed silently when it encountered an invalid age bracket
• Issue #368 - Microsoft Excel was interpreting Jethro's CSV exports as incorrect file type sometimes
• Issue #370 - Family CSV export was failing
• Issue #372 - Non-congregational roster roles were not being displayed in the listing
• Issue #377 - The mailchimp sync script now uses Mailchimp API v3, resolving various issues
• Issue #351 - personnel were not updated when an old service run sheet was copied
• Issue #382 - congregations were being duplicated on install
• Issue #378 - task-notification settings were missing from the system-configuration page
• Issue #373 - family photo upload from add-family form was not working
• Issue #360 - error message about timezone during install
• Issue #301 - no-phone icon was being shown on rosters when SMS gateway wasn't even configured.
• Bible readings were sometimes getting squashed in wide rosters
• Errors with the smsbroadcast SMS gateway were not being detected properly (@vanoudt)

Upgrade Procedure - if upgrading from a version OLDER than 2.19.0

1. Log out of Jethro
2. Take a backup of your mysql database. Really, do it.
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2017-upgrade-to-2.19.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
   1 Note: Jethro no longer needs the MDB2 libary, so if you have the MDB2 dropin in your old system, don't copy it to your new one
7. Important extra step: Open Jethro in your browser. You should see a bunch of messages saying "The setting XYZ has been migrated to the database and can/should be removed from conf.php". (Alternative option: Instead of opening Jethro in the browser you can run scripts/migrate_settings.php)
8. Once you've seen the messages above, rename your conf.php to conf-OLD.php. (Make sure you keep the .php extension - otherwise you'll expose your database credentials to the world)
9. Rename conf.php.sample to conf.php
10. Edit conf.php and for each setting that's in there, copy its value from conf-OLD.php.
    NB a) many settings will no longer be in conf.php because they've migrated to the database
    NB b) SMTP and SMS related settings will NOT have been automatically migrated to the database, so either leave them in the conf.php file or enter them manually into the web interface
    NB c) There are new settings for DB_DATABASE, DB_USERNAME etc, but the old PUBLIC_DSN etc still work.
11. Log in to Jethro and check your system configuration at Admin > System Configuration

Upgrade Procedure - if upgrading from v2.19.x

1. Log out of Jethro
2. Take a backup of your mysql database
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2016-upgrade-to-2.20.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Note: Jethro no longer needs the MDB2 libary, so if you have the MDB2 dropin in your old system, don't copy it to your new one
8. Note: Although there is a new format for database settings in conf.php.sample, the old DSN format still works.
9. Log in and test.

Credits

Thanks to @vanoudt for work on the MDB2 replacement and SMS integration and to @s4069b for the send-report script.

Jethro v2.19.2

This release fixes various problems with 2.19.0

Bugfixes

• Issue #342 - the system-wide search now matches the beginnings of words within names, not just the beginning of names
• Issue #343 - some pre-existing person reports did not work after upgrading to 2.19.0
• Problems with installation

Upgrade Procedure - if upgrading from a version OLDER than 2.19.0

1. Log out of Jethro
2. Take a backup of your mysql database. Really, do it.
3. Apply all applicable upgrade SQL files from the upgrades folder to your mysql database, including upgrades/2017-upgrade-to-2.19.sql
4. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
5. Unzip the new files into the right place (don't just overwrite the old files)
6. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
7. Important extra step: Open Jethro in your browser. You should see a bunch of messages saying "The setting XYZ has been migrated to the database and can/should be removed from conf.php". (Alternative option: Instead of opening Jethro in the browser you can run scripts/migrate_settings.php)
8. Once you've seen the messages above, rename your conf.php to conf-OLD.php. (Make sure you keep the .php extension - otherwise you'll expose your database credentials to the world)
9. Rename conf.php.sample to conf.php
10. Edit conf.php and for each setting that's in there, copy its value from conf-OLD.php.
    NB a) many settings will no longer be in conf.php because they've migrated to the database
    NB b) SMTP and SMS related settings will NOT have been automatically migrated to the database, so either leave them in the conf.php file or enter them manually into the web interface
11. Log in to Jethro and check your system configuration at Admin > System Configuration

Upgrade Procedure from 2.19.0

If you have ALREADY upgraded to 2.19.0 then to upgrade to 2.19.2 you should

1. Log out of Jethro
2. Take a backup of your mysql database.
3. Move away your old Jethro files (eg. rename your jethro folder to jethro_old)
4. Unzip the new files into the right place
5. Move your old conf.php and files/ subdirectory (if not empty) back into your jethro folder.
6. Special step: If possible, run scripts/fix_reports.php to resolve Issue #343. NB this is ONLY needed if your system was already upgraded to 2.19.0.
7. If you are not able to run the fix_reports.php script (eg if you don't have command line access) then log in to Jethro and test all your person reports. If any report produces a database error when you click "show results", you'll need to "edit configuration" for that report and adjust the "age bracket" rule.