Please provide instructions how someone can test this, otherwise it will just site here for enough 3 months without comment

Instructions on how to test it? Details on how it arises can be found in the related issue I filed prior to writing the fix. (#6157)

As a manual test, install an extension (and to be thorough, update it at least once) that does not have a schema update present in, nor a provision for one to have ever happened. It will probably have to be a custom-made one for this purpose, as the custom in extensions to this point has been to always provide a schema update that's basically a no-op (does nothing) as a workaround to the bug (don't get me started on workarounds vs fixes). If an extension that has never had a schema update installs correctly and updates code once without throwing an error, it passes.

Thanks for the update and for adding the link to the original issue. However it is still pretty hard for anyone to test without and extension that matches your conditions. Do you have one?

It's a specialized bug you will likely only encounter in the early stages of creating an extension (component more likely than any other one). I can probably sanitize one of mine (remove the proprietary info from it, as it's custom-built for a particular site rather than generic) but it might be just as easy to take an early version of an existing one (that only has the empty schema update) and simply delete the do-nothing schema update file. (You might even be able to use the hello world component from the tutorials for it, as it documents including it.)

I'll do some rummaging around when I get home; I can probably locate or reproduce an early draft of the component I was working on for a JCM article before things got hectic around here. It'll suck as a component, but it should put the bug on display.

Would be great if you could. The fewer hoops people have to jump through to test an issue the more likely it will be that they will test it

@Paladin I agree with this fix but giving us a test component will definitely help get you testers

I know. But unfortunately the one that surfaced this problem has long since progressed past that point and I’ve been hit with a “perfect storm” of emergency tasks that need done, not the least of which being a web host that just packed up and left town with several of my servers, and most of my DNS information, pre-empting my time rather drastically. Either use the description I gave on how to duplicate this issue, or be patient and I’ll dig something out when the dust settles.

On Jun 17, 2015, at 3:39 PM, George Wilson > wrote:

@Paladin https://github.com/Paladin I agree with this fix but giving us a test component will definitely help get you testers

—
Reply to this email directly or view it on GitHub #6156 (comment).

Merged on review