upskill-event-manager/wordpress-dev/wordpress/wp-content/plugins/event-tickets-plus/lang
bengizmo d1509b3d60 feat(dev-env): implement backup-based development workflow
This commit introduces a more reliable and consistent approach to setting up
the development environment using backups:

- Add setup-from-backup.sh script for environment setup from existing backups
- Standardize script naming and organization
- Move obsolete scripts to bin/obsolete directory
- Update documentation with new workflow instructions
- Create migration guide for transitioning to new workflow
- Update Memory Bank with workflow improvements

The new workflow provides:
- More reliable environment setup
- Faster setup process
- Offline development capability
- Consistent development environments across team members

Breaking changes:
- setup-dev.sh is replaced by setup-from-backup.sh
- sync-and-setup.sh is replaced by separate scripts
- verify-with-wpcli.sh is no longer used

Migration path is documented in MIGRATION_GUIDE.md
2025-03-26 11:26:18 -03:00
..
event-tickets-plus-af.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-ar.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-bg_BG.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-ca.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-cs_CZ.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-da_DK.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-de_DE.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-de_DE_formal.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-el.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-en_CA.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-en_GB.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-es_ES.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-et.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-fi.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-fr_CA.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-fr_FR.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-hu_HU.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-id_ID.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-is_IS.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-it_IT.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-ja.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-lt_LT.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-lv.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-nb_NO.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-nl_NL.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-pl_PL.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-pt_BR.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-pt_PT.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-ro_RO.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-ru_RU.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-sk_SK.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-sl_SI.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-sr_RS.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-sv_SE.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-tr_TR.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-uk.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-zh_CN.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus-zh_TW.mo feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
event-tickets-plus.pot feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
readme.txt feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00

If you are interested in contributing to translations, you can get started at https://translations.theeventscalendar.com/projects/event-tickets-plus/

On that site you can also find the .po translation files for doing local translations. We do not include these in the plugin itself to save space.