Repository navigation
Releases: Tywed/webtrees-telegram
Release list
v0.2.3
0.2.3 — Access, cron, and message fixes
After upgrading, open the module settings and update crontab with the new URLs (they now include a secret key).
- Settings and configuration changes are limited to site administrators
- Bot token stays on the server and is not shown in the browser
- Cron endpoints require a secret key (403 without it); you can regenerate it from settings
- Sensitive values are redacted from error text
- Changes digest sends updates since the last successful run, not a calendar day
- Names are no longer double-escaped; age is shown as “N years”
- Form markup and event-type handling cleanup
- Requires webtrees 2.2+ (PHP 8.3+)
Full Changelog: v0.2.2...v0.2.3
v0.2.2
0.2.2 - Reliability and i18n fixes
- Fixed test message and cron errors: removed debug output causing "Headers already sent", improved Telegram API error messages (#17, #5)
- Fixed events missing from daily messages (header-only): event key normalization, orphan block assembly (#14)
- HTML escaping for auto-generated message content; compact year display option (#6)
- Removed module translations that override webtrees core strings (#18)
- Admin list no longer crashes when user/tree was deleted; null tree guard in cron
- Correct release tag naming: use
v0.2.1/v0.2.2instead ofv.2.0.1(#16)
Full Changelog: v0.2.1...v0.2.2
v0.2.0
What's Changed
This update introduces enhanced notification capabilities, including support for multiple module configurations to manage notifications for different chats and family trees. It also adds a dedicated cron job for sending tree changes and a test message feature for easier configuration validation. Additionally, new AI-generated translations have been integrated.
Attention: The cron job link has changed in this version. Please update it on your server after upgrading and check the old settings module.
Full Changelog: v.0.1.3...v.0.2.0
v.0.1.3
What's Changed
- message splitting when messages exceed 4096 characters (only remains a problem if the message for an individual event exceeds the limit)
- added option not to send date and location
Full Changelog: v.0.1.2...v.0.1.3
v.0.1.2
What's Changed
- Rewrote the message generation logic based on Greg's code. Sending all events, counting the date and place of the event.
New Contributors
- @HerzScheisse made their first contribution in #3
Full Changelog: v.0.1.1...v.0.1.2
v0.1.1
Release Notes
- Added customization for the start and end of messages
- Script execution limited to once per day
- Option to filter events by living individuals
- Event type selection (currently supporting birthdays and weddings)
Full Changelog: v.0.1.0...v.0.1.1