It's still a problem, I think it's not only with canDeleteRow list plugin.
Setup to replicate
- canEditRow plugin with error in the php code field, e.g. return $xxx;
- canDeleteRow plugin with correct php
Calling the list will give a number of Joomla system Error messages
An error has occurred with a eval'd field - please inform the web-site owner.
Debug: Caught exception on eval in can delete row : Undefined variable: xxx
The number of displayed errors is changing (can't see how, not related to the number of "false" returns );
No errors if canDeleteRow is returning always true.
So the canEditRow error is still sticky in canDeleteRow logEval.
But I have seen this behaviour in an other list, too with only one canDeleteRow plugin, where the error must have an other source.
There I've got
Caught exception on eval in can delete row : syntax error, unexpected BOOL_TRUE in Unknown on line 16
In both cases the canDeleteRow itself is working correctly (beside the error messages)
Setup to replicate
- canEditRow plugin with error in the php code field, e.g. return $xxx;
- canDeleteRow plugin with correct php
Calling the list will give a number of Joomla system Error messages
An error has occurred with a eval'd field - please inform the web-site owner.
Debug: Caught exception on eval in can delete row : Undefined variable: xxx
The number of displayed errors is changing (can't see how, not related to the number of "false" returns );
No errors if canDeleteRow is returning always true.
So the canEditRow error is still sticky in canDeleteRow logEval.
But I have seen this behaviour in an other list, too with only one canDeleteRow plugin, where the error must have an other source.
There I've got
Caught exception on eval in can delete row : syntax error, unexpected BOOL_TRUE in Unknown on line 16
In both cases the canDeleteRow itself is working correctly (beside the error messages)
