Cronologia Commit

Autore SHA1 Messaggio Data
  glajarige 01f748e8b6 Customers portal : Fixed a bug in BrowseBrick APIs. Calls to static functions were made as $this-> 9 anni fa
  glajarige a764e2e117 Customers portal : Improved error message on autocomplete field when the portal configuration is incorrect 9 anni fa
  romainq a219579a2f Code freeze for 2.3.0 9 anni fa
  glajarige b71e12aa6a Customers portal : Comment for context tag 9 anni fa
  dflaven 4431bfe450 Internal: context tags to (programmatically) identify the context of the execution. 9 anni fa
  glajarige 63bf00c438 Customers portal : Final touches on default portal configuration 9 anni fa
  glajarige cb3a24a866 Customers portal : BrowseBrick : Extra field columns can be hidden in list mode while remaining filterable. (Use case example : Hide a "keywords" attribute to enable filtering on it) 9 anni fa
  dflaven a6a2b7b1a7 Support of Custom Fields in the Excel export... not really nice but should be usable. 9 anni fa
  dflaven d21704a184 Internal: Read-only fields are no longer stored in the form as hidden fields. 9 anni fa
  glajarige 229e725070 Customers portal : Fixed a bug on profile picture edition. Button was not working on Firefox. 9 anni fa
  glajarige 9d4399cb12 DataModel : Reserved location_id field OQL filter in order to start the JOINs from the Location object. Otherwise the Intersect limitation was raising. 9 anni fa
  romainq c65496ee4c Code refactoring : fix of #876 implemented in 2.0.3 as [r3161], moved to a place where it will fix other implementations of the setup 9 anni fa
  glajarige 6578442d0c Customer portal : Fixed a regression in CSS, form field labels were no longer bold 9 anni fa
  glajarige 1a1e04df7c Customer portal : Readonly attachments when object is not longer editable 9 anni fa
  glajarige 62d9c35886 Customer portal : Security exception raised when adding contact on a new UserRequest / Incident. This was caused by a bug in the SecurityHelper while checking scopes for a class that had no objects yet. (R-011452) 9 anni fa
  romainq f777982798 Custom fields: solidified the internal APIs against creative usages (null =>default value) 9 anni fa
  dflaven 513fb341a4 Security: prevent grouping on password fields since it may lead to disclosure of the encrypted version of the password. 9 anni fa
  romainq bd2151198a Fixed a regression introduced in iTop 2.3.0-beta: menu collapse mechanism broken when adding a shortcut (but it is restored when reloading the whole page). 9 anni fa
  dflaven 4f4009384e Properly sanitize the "switch_env" parameter and take it into account only if it contains a valid value. 9 anni fa
  dflaven 54dc153d7d #1167 Error while upgrading db model from v 2.1 to 2.2 with orphan attachments. 9 anni fa
  dflaven a946094c23 File or image upload is not supported (and thus disabled) when using the [+] button to create a new object inside a popup dialog. 9 anni fa
  glajarige 5d434613b5 Customer portal : LinkedSet fields can now be display a specific list of attributes instead of the z-list 'list' attributes. This is defined in module_design/classes/class/lists/list (see example in itop-tickets/datamodel.itop-tickets.xml) 9 anni fa
  romainq 6bcab2c587 User/status must be read-only in demo mode 9 anni fa
  romainq 1d69c5f27c OQL: fixed an old limitation, hierarchies can now be expressed both ways. Example of a query that now works fine: SELECT Organization AS root JOIN Organization AS child ON child.parent_id BELOW root.id WHERE child.name LIKE 'Combodo'. In the previous implementation, the operator was interpreted as '='. 9 anni fa
  dflaven 6188d09657 "Search Drawer" is closed by default, unless the configuration parameter "legacy_search_drawer" is set to "true". 9 anni fa
  glajarige d1cde3ed0c Customer portal : Edit profile picture 9 anni fa
  dflaven 5a63878541 New field on the User class to enable/disable user accounts. 9 anni fa
  romainq faf80a3d01 A few updates of the readme (valuable for the beta!) 9 anni fa
  romainq 9a75b66d4a #1169 Broken link to iTop Wiki in itop-tickets.htm 9 anni fa
  romainq 99ec255431 Internal: DBSearch::Intersect to throw an exception whenever any of the merged queries have a queried class that does not correspond to the first joined class. This is a limitation of the current implementation of Intersect. Allowing such use cases would require quite a rework of that API. 9 anni fa