-
Notifications
You must be signed in to change notification settings - Fork 4
Test steps
Gerrit Uitslag edited this page Apr 26, 2023
·
4 revisions
- Add new plugin
[testdomain]/plugin- state:
waiting
- state:
- Get activation url from sent mail and use
- state:
initialProcessing
- state:
- use
dokuwiki:updateGitcommand- it creates/update folder for the new repository:
- if dir not exists, create
[datafolder]/<type>/<name> - create remote fork (if github) in the account https://github.com/dokuwiki-translate or the test account
- create local clone in
[datafolder]/<type>/<name>/repository - if success:
- reset error count and last update time
- if
initialProcessingit set repository state toactiveand sent extension ready mail
- if repository exists, pull changes and push to fork
- if dir not exists, create
- it updates the serialized language data
- search the respectively language folders
- retrieve
en/and others - process
.phpand.txtfiles - remove and recreate stats
- store serialized language data in
[datafolder]/<type>/<name>/lang/<langcode>.ser
- it creates/update folder for the new repository:
- Ready for translating. Submit a translation.
- stores
TranslationUpdateEntitywith id, state:undone, etc - stores file with serialized array of
LocalTextobjects in[datafolder]/<type>/<name>/updates/<id>.update
- stores
- use again
dokuwiki:updateGitcommand, to create patch and sent it- make folder
[datafolder]/<type>/<name>/tmp - create local clone in
[datafolder]/<type>/<name>/tmp - get array with LocalText objects from
[datafolder]/<type>/<name>/updates/<id>.update - add for each LocalText a language file to local git
- commit the additions to local git
- remoteadd 'github', branch 'lang_update_', checkout, push to 'github'
- create pull request
- if failed:
- set error and sent error mail
- always remove
[datafolder]/<type>/<name>/tmpfolder - always remove the
TranslationUpdateEntitywith id, etc - note:
[datafolder]/<type>/<name>/updates/<id>.updateis not removed.
- make folder
Process
- Translation process
- CronJob overview triggers some commands.
- Commands for regular tasks and occasional maintenance
Files
Maintenance/development
- Deploying to Production is done from GitHub
- Development setup
- Maintenance
- Alternative Git interaction when setting up development setup
- Test steps for checking working of the tool
Documentation
- Components of Symphony used for the Tool
- More detail about using Doctrine
- Description working of the Forms