Todas las versiones registradas, de la más nueva a la más antigua, con lo que cambió en cada una.
Última 2.4.25 versiones
Sin fecha · 5 versiones
2.4.2
Última
1 mejora4 correcciones
Mejora
Added a css ID to the user profile elements. This class will be styled in version 5.9 and later of Awesome Support.
Corregido
An array error.
Do not show Product And Availability title in user profile if user is not allowed to edit them
Re-factored conditions that show the product and availability for an agent in the user profile to use the internal wpas_is_agent functions.
Fixed "Notice: Trying to get property of non-object" message.
2.4.0
1 nuevo
Nuevo
Added option to control which roles can set agent availability
2.3.0
1 nuevo
Nuevo
Added a sixth algorithm that is a variation on algorithm #1.
2.2.0
3 nuevos
Nuevo
Added option to prevent the algorithms from running for specified channels. This allows you to run it for normal tickets but let things like Gravity Forms or Emails assign their own agents without fear of being overwritten by this module.
Added internal support for a smart-agent-bypass flag. If a metavalue is set to 1 or true in a meta field called _wpas_bypass_smart_agent on the ticket, the smart agent algorithm is not run.
Added internal support for an algorithm override flag on the ticket. If a metavalue is set in a meta field called _wpas_smart_agent_algo_override, that value will be used as the algorithm value ( currently valid values are 1 - 5 )
2.1.0
4 nuevos2 mejoras7 correcciones18 cambios
Nuevo
Added option to explicitly use the core round-robin algorithm
Added in additional time fields (2 more sets for a total of 4).
Added in four more algorithms for assigning agents
Add the current time below the agent's availability time so users can more easily figure out any timezone differences between their time zone and their hosting server.
Mejora
Changed action hook used to calculate and stamp ticket with agent - used a later hook.
Change the "Plugin Name" to Awesome Support: Smart Agent Assignment
Corregido
Settings and values that should be unique to each user on each site were global to all sites for the same user when running on multi-site (replaced update_user_meta function calls with update_user_option function calls)
Some settings logic was not checking for empty arrays before attempting to use the array.
Multi-site logic fix - Original logic assumed the users table was always going to be prefixed by 'wpdb->prefix' but users table is prefixed with 'wpdb-base_prefix'.
Multi-site logic fix - Settings and values that should be unique to each user on each site were global to all sites for the same user when running on multi-site (replaced update_user_meta function calls with update_user_option function calls)
Fixed translation strings
Fixed selection of agents for algorithm by introducing an option to decide which roles are agent roles for the selected algorithm.
