Project

General

Profile

Actions

Feature proposal #2030

closed

New event prepareFieldDataNotSaved as else-case for trigger prepareFieldDataSave does not fire for readonly fields in frontend

Added by krileon over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
22 October 2010
Due date:
% Done:

100%

Estimated time:
1:00 h

Description

With prepareFieldDataSave not firing for read only fields it results in integrations such as CB Privacy failing. Source is shown in comprofiler.class.php as follows.

@function saveTabsContents( &$user, &$postdata, $reason ) {
global $_CB_framework, $_PLUGINS;

$fields                    =    $this->_getTabFieldsDb( null, $user, $reason, null, false );
$result = true;
foreach ( $fields as $field ) {
if ( ( ! ( ( $field->readonly > 0 ) && $_CB_framework->getUi() 1 ) ) || ( $reason 'register' ) || ( $reason == 'search' ) ) {
$_PLUGINS->callField( $field->type, 'prepareFieldDataSave', array( &$field, &$user, &$postdata, $reason ), $field );
}
}
return $result;
}@

The IF statement plainly blocks read only storage on front-end. Seams an additional check needs to be made for CB privacy OR new trigger to fire for raw preparefielddatasave for integrations to use.


Related issues 1 (0 open1 closed)

Related to CB Privacy - Bug #1998: fields set as read only will not save their privacy controlsClosedbeat23 September 2010

Actions
Actions

Also available in: Atom PDF