Scratch2Offline V.444.3 / Windows 10.0

Hello,

I made custom block using HTTP extension And It worked well under V.442.
The blocks described like bellow.

{
…
“blockSpecs”: [
,
],
“menus”: {
“outAPins”: ,
},
“type”: “serial”
…
}


After update to V444.3
Dropdown list is not opened because blockID with ‘.’ (V01.write)
list is opened if I don't use ‘.’ in blockID.

But,
After saving scratch with custom blocks (even if I use the blockID without ‘.’,)
the custom blocks are displayed as “undefined” block when I reopen.

How can I fix it.

Thanks.

{
…
“blockSpecs”: [
<“ ”, “write %m.outAPins %n”, “V01.write”, “out”, “100”>,
],
“menus”: {
“outAPins”: <“out”>,
},
“type”: “serial”
…
}

I used <> instead of because is not displayed.

I just hit the same bug and posted about it (apologies for the double posting). Glad it's not just me:
https://scratch.mit.edu/discuss/topic/188818/

In my case the extensions had been working fine for over a year, and have been used by a few thousand people. Something changed between 442 and 444.3

Might be worth posting in the connecting to the physical world forum and/or the developing extension forum as well with a link to this warning that upgrading to the new version may break some http extensions?

Hello,

First off, I want to reassure everyone that I didn't intend to break or deprecate anything with the recent changes to the extension system. We recently released an official extension for the LEGO WeDo 2.0, and I had to make some changes to the extension system because of the “.” in the extension name.

Unfortunately, as you now know, the way that I made that change caused some problems with other extensions. This is a known issue and will be fixed ASAP; I've already implemented a proposed fix so it shouldn't take long.

Thanks for your patience, and again, my apologies for the trouble.

cwillisf wrote:

Hello,

First off, I want to reassure everyone that I didn't intend to break or deprecate anything with the recent changes to the extension system. We recently released an official extension for the LEGO WeDo 2.0, and I had to make some changes to the extension system because of the “.” in the extension name.

Unfortunately, as you now know, the way that I made that change caused some problems with other extensions. This is a known issue and will be fixed ASAP; I've already implemented a proposed fix so it shouldn't take long.

Thanks for your patience, and again, my apologies for the trouble.

Thank you. cwillisf.
I hope it can be fix ASAP - using ‘.’ and saving problem that block is shown as ‘undefined’.
Thanks for your effort.

There is no bug.

What is the status of this bug? When can we expect a fix?

Version 445 fixes the problem for a new project, but for existing projects (projects saved prior to 443, the blocks still come up undefined. Please, please, please fix this as soon as possible!!!!!