PROBLEM The skin table does not show any row selected to determine which is the selected one.
SOLVED Adding an small feature to display italic, bold text and set a checked image in the current skin row.
PROBLEM The skin table does not show any row selected to determine which is the selected one.
SOLVED Adding an small feature to display italic, bold text and set a checked image in the current skin row.
We've detected 2 problems:
1.- The new algorithm to detect if the password is encrypted don't support passwords with a ":" character
2.- When recover the email configuration the system don't decrypt correctly the password of a previous version (without encryption, backwards compatibility)
- APP_FINISH_DATE is set to 1902-01-01 00:00:00 when create new case
using webservices
- DEL_INIT_DATE is set to NULL when routing case using webservices
- Solved the problem in the fields APPLICATION.APP_FINISH_DATE and
APP_CACHE_VIEW.APP_FINISH_DATE, when you create a new case now set to NULL
- Solved the problem in the fields APP_DELEGATION.DEL_INIT_DATE and
APP_CACHE_VIEW.DEL_INIT_DATE when the case is routed set to the date corresponding
- It was found that an alert was displayed with a not very specific error
- Skin_ajax was modified to allow the skin uxmodern to be copied, moreover to clarify the type of error.
- The activation of a tab in ADMIN does not work with URL (setup/main?s=PMENTERPRISE or setup/main_init?s=PMENTERPRISE)
- Solved the problem, now looks for the variable "s" in the menu to set the active tab
- 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
- Al mostrar el mensaje de error se estaba usando simplemente un formulario normal
- Se cambio el comportamiento cuando existen errores al importar un plugin, se esta redireccionando de nuevo al listado de plugins disponibles y se muestra un mensaje en ExtJS con el error
- Al eliminar el plugin enterprise en un workspace, no se elimina del registro de plugins en los demas workspaces, quedando registros de los plugins en el "plugin.singleton" en cada workspace
- Al eliminar un plugin en un workspace se eliminan tambien los registros en los demas workspaces, se ha implementado la accion "uninstall" para los plugins, ahora al eliminar un plugin se llama a su metodo "uninstall" si esta definido
- It was found that had several labels that are hardcoded.
- Changed hardcoded labels reusing some existing labels and some things were created some labels.
- labels created: ID_INIT_DATE(Init Date), ID_OVERWRITE(Overwrite),ID_BROWSE(Browse),ID_UPLOADING_TRANSLATION_FILE(Uploading the translation file...),
ID_EVALUATION_RESULT ([Success] Evaluation result)
- Labels reused: ID_TITLE, ID_DESCRIPTION, ID_DUE_DATE, ID_FINISH_DATE, ID_SEND, ID_UPLOADED_DOCUMENTS, ID_GENERATED_DOCUMENTS, ID_FILE, ID_FIRST_NAME,
ID_LAST_NAME,ID_ACTIVE,ID_INACTIVE, ID_MSJ_REPORSTO
- image for Starting a case ...
it is labeled translation.ID_TITLE_START_CASE which works only if you change the language to es-ES
-
- a complete refactoring on skingEngine bootstrapper, now this is a class
- the mvc templatting engine was updated to work perfectly with templates that is using extjs engine
- a new "unmodern" was added to contains the new pmos modern main interface
- en realidad no duplica el password, sino que muestra el mismo pero encriptado
- para evitar este tipo de confusiones decidimos dejar vacio el password asi como está en el editor de usuarios, este solo se solicitara si no tiene guardada una contraseña en el servidor o si la direccion del servidor ha cambiado.
solved problem in "import" for plugins, fatal error in class.pluginRegistry.php. Also resolved the problem in inclusion of the variable PATH_SEP in $path
