I am using the php_events list plugin to run some code in onDeleteRows.
The list is using the Div template.
I use the $model->rowsToDelete array to determine values of various elements as a way initializing some variables used in the php code.
This line no longer works and errors out with "invalid index".
$fid = $model->rowsToDelete[0][0]->fb_member_facilities___facility_id_raw;
Suddenly (I have no idea when/why this started happening) the first index in that rowsToDelete array is no longer zero. The first index is now the Joomla user ID - which just seems to make no sense to me at all.
In debugging, I traced this as coming from line 1313 in list.php. where the _groupId is somehow being initialized as the Joomla user ID. This is the part of the list.php code that is trying to "// Check if the data has a group by applied to it" - in the formData() function.
But exactly how the _groupId always ends up as the user ID is beyond me - and it's beyond my pay grade (of zero) to fix this bug that was apparently recently introduced into the fabrik code.
I suppose I could just rewrite my onDeleteRows code to compensate for this change - but that wouldn't solve the problems that this might be introducing elsewhere - in hundreds of other Fabrik users' code - would it?
The list is using the Div template.
I use the $model->rowsToDelete array to determine values of various elements as a way initializing some variables used in the php code.
This line no longer works and errors out with "invalid index".
$fid = $model->rowsToDelete[0][0]->fb_member_facilities___facility_id_raw;
Suddenly (I have no idea when/why this started happening) the first index in that rowsToDelete array is no longer zero. The first index is now the Joomla user ID - which just seems to make no sense to me at all.
In debugging, I traced this as coming from line 1313 in list.php. where the _groupId is somehow being initialized as the Joomla user ID. This is the part of the list.php code that is trying to "// Check if the data has a group by applied to it" - in the formData() function.
But exactly how the _groupId always ends up as the user ID is beyond me - and it's beyond my pay grade (of zero) to fix this bug that was apparently recently introduced into the fabrik code.
I suppose I could just rewrite my onDeleteRows code to compensate for this change - but that wouldn't solve the problems that this might be introducing elsewhere - in hundreds of other Fabrik users' code - would it?