Repeated Image fields Fatal Error in 3.0.148

[JayGee]

I seem to be running into a repeated fatal error in a fresh PW install version 3.0.148. I can't quite put my finger on the pattern but it seems to be around deleting image fields or removing images from certain image fields.

This is the trace from the log generated by trying to save a page and delete an image from an image field:

Fatal Error: Uncaught Error: Cannot access protected property Pageimage::$original in /wire/core/PageimageVariations.php:256 Stack trace:
1. /wire/core/Pageimage.php(1327): PageimageVariations->getInfo()
2. /wire/core/Wire.php(386): Pageimage->___isVariation()
3. /wire/core/WireHooks.php(823): Wire->_callMethod()
4. /wire/core/Wire.php(450): WireHooks->runHooks()
5. /wire/core/Pageimage.php(1369): Wire->__call()
6. /wire/core/Pageimage.php(399): Pageimage->getOriginal()
7. /wire/core/WireData.php(333): Pageimage->get()
8. /wire/core/PageimageVariations.php(256): Pro
Line 256 of /wire/core/PageimageVariations.php

Earlier in the day I was experimenting with custom fields for images for the first time and kept running into this error, thinking it was me using this feature wrong and not having time to read up I deleted the custom image fields template and went about my business. So now I don't know if I triggered an issue or whether it was never related to the custom image fields in the first place?

Any ideas?

[matjazp]

https://github.com/processwire/processwire-issues/issues/1086

[JayGee]

4 minutes ago, matjazp said:

https://github.com/processwire/processwire-issues/issues/1086

Ah thanks @matjazp - I'll try applying those fixes later as I presume they're currently only in the dev branch? I'm working on a master copy downloaded yesterday.

[matjazp]

1 hour ago, Guy Incognito said:

I'll try applying those fixes later as I presume they're currently only in the dev branch?

Yes, it's on the dev branch. I applied fixes on the current master version until the next master. So far so good.

[JayGee]

On 6/2/2020 at 7:44 PM, matjazp said:

Yes, it's on the dev branch. I applied fixes on the current master version until the next master. So far so good.

Finally got onto trying this out and confirm fix works - thanks for your help ?