- Nuevo feature
- Funcionalidad para la instalacion de parches
- Nuevo feature implementado, se ha adicionado una nueva opcion al comando ./processmaker
Esta nueva opcion trabaja de la siguiente manera:
Caso 1 - ./processmaker patch-install MyPatch.tar
Caso 2 - ./processmaker patch-install path_to_patch/MyPatch.tar
Para el caso 1, el archivo tar debe estar fisicamente en la ruta:
path_to_processmaker/shared/patchs (si no existe el directorio "patchs", crearlo y darle todos los permisos)
Para el caso 2, el archivo debe existir en la ruta que se especifica
* Available from version ProcessMaker-2.5.1-testing.3
- No se modificaba la estructura porque no se tenia seteado la variable ENVIRONMENT_SETTINGS.
- Se modifico la funcion upgradeCasesDirectoryStructure para que cree la variable si no existe.
- Se movio la funcion upgradeCasesDirectoryStructure para que sea independiente al realizar el upgrade.
- se creo la funcion update-structure-directories para ejecutar por consola teniendo como parametro el workspace.
- No se modificaba la estructura porque no se tenia seteado la variable ENVIRONMENT_SETTINGS.
- Se modifico la funcion upgradeCasesDirectoryStructure para que cree la variable si no existe.
- Se movio la funcion upgradeCasesDirectoryStructure para que sea independiente al realizar el upgrade.
- se creo la funcion update-structure-directories para ejecutar por consola teniendo como parametro el workspace.
- No se realizaba la verificacion en la tabla PERMISSIONS de la base de datos RBAC al realizar upgrade.
- Se agrega la funcion verifyPermissions en la clase rbac.php la cual verifica los permisos, realizando los insert de los permisos que faltaran de acuerdo a la funcion loadPermissionAdmin, al realizar el upgrade.
- No se realizaba la verificacion en la tabla PERMISSIONS de la base de datos RBAC al realizar upgrade.
- Se agrega la funcion verifyPermissions en la clase rbac.php la cual verifica los permisos, realizando los insert de los permisos que faltaran de acuerdo a la funcion loadPermissionAdmin, al realizar el upgrade.
Description: ./files directory cannot be up 32000 directories max at ext3 configuration.
Solution : split the uid case directory at 3 level to create a tree structure. Apply this new structure to all PM. Set a upgrade procedure at time to use processmaker upgrade <workspace> commnand as su.
- To upgrade the system with:
php -f processmaker upgrade
No complete the upgrade, can't load all system classes
- Fixed, now be load all classes with Bootstrap class
* Available from version ProcessMaker-2.0.46
PROBLEM the backup is too bigger to be handle in some os configurations systema files
SOLUTION A new class will help to compress into several files instead one.
to use the new feature the admin would use and extra option as follow:
processmaker workspace-backup -s {}
to restore may use :
processmaker workspace-restore -m
In both case there are to new arguments -s and -m, these are for use the new feature only, if they are not added the old way is still available.
PROBLEM the backup is too bigger to be handle in some os configurations systema files
SOLUTION A new class will help to compress into several files instead one.
to use the new feature the admin would use and extra option as follow:
processmaker workspace-backup -s <megabyte max files size> {<workspace>} <destinationFile.tar>
to restore may use :
processmaker workspace-restore -m <workspace> <destinationFile.tar> <workspacedestination>
In both case there are to new arguments -s and -m, these are for use the new feature only, if they are not added the old way is still available.
- Files created/uploaded to "PATH_DATA/upgrade" not are deleted, this
in ProcessMaker (core) and Enterprise (plugin)
- Improved the creation/loaded of the files, once completed, are eliminated
* Available from version 2.0.44
- In Centos 5.4 is not possible to restore a backup file of ProcessMaker. we are using the next command.
- Adjustment in the restore backup, in the erased the hidden files.
- The APP_CACHE_VIEW table does not contain the changes made in the CONTENT table when you rename processes/tasks
- The name change in processes/tasks is now reflected in the APP_CACHE_VIEW table
- Note.- The APP_CACHE_VIEW table contains values ..for only one language
