introduced a potential bug that occurs whenever the persistent field has both a corresponding is and corresponding get method. E.g., given:
The fix for attempted to reuse the code that is used to resolve the getter method for property-access, in which case it is illegal for there to be both. That is not the case here however.
Please also fix this in the next 5.2.13 release, thanks. As far as I can see this is not in the 5.2 branch yet...
Backported to 5.2.13.