/
Wrong "getRequestProtectedFields" method placement [5.2.1-RC1]

Wrong "getRequestProtectedFields" method placement [5.2.1-RC1]

Owned by Alex
Last updated: Mar 25, 2014

In  INP-964 - Getting issue details... STATUS  (the 5.2.0-B1 release) we've added the "kDBEventHandler::getRequestProtectedFields" method to allow protecting some of the unit fields from being changed directly from request just by adding a hidden field with a proper database column name in it.

By default we're protecting following field types:

  • primary key - because some of other database records might be referencing that somehow already
  • foreign key -  because it's bad idea to reassign sub-items of a given item to another item

However it turns out that foreign key protection wasn't accounting for the fact, that. Another problem with that method is it's location. Since it's only is created to help out the kDBItem class, then it also should be moved there.

moving_getRequestProtectedFields_method_core.patch

moving_getRequestProtectedFields_method_modules.patch

inappropriate_setfieldsfromhash_usage_core_fix.patch

inappropriate_setfieldsfromhash_usage_modules_fix.patch

Related Tasks

INP-1343 - Getting issue details... STATUS