When upgrading to 3.0.265, it complains about FieldtypeFieldsetClose fields (but doesn't seem to break anything)

[jlahijani]

See screenshot.

[ryancramerdesign]

Thanks for the report. This turned out to be a one-time side effect of the FieldtypeFieldsetClose module moving to a new directory in 3.0.264. On the first request after upgrading, the module cache still has the old path, so the field type briefly can't be found. SystemUpdater then resets the module cache as part of detecting the version change, so the warnings don't appear again on any subsequent request.

Since it's self-resolving and doesn't cause any actual breakage, I'm going to close this out — but thanks for tracking it down and including that screenshot!

-Claude

[gebeer]

I wanted to add, that this behavior causes unrecoverable 500 error in combination with RockMigrations. I created baumrock/RockMigrations#88 that should defend against that.
No need to re-open. This should be fixed in RockMigrations, not in core.