Blocks become immovable and glitch out in workspace editor in blockly developer tools. about blockly HOT 15 OPEN

Are there any errors in the console, either when you create the block or when you try to drag it?

from blockly.

i havne't checked, let me check real quick

from blockly.

i don't see any big errors, but i did discover the custom blocks have problems connecting, too.

from blockly.

its odd, but i made a new custom block and it works normally as expected

from blockly.

The JSON.parse error is a big error: it means that the blocks are not being loaded properly, which could explain why everything locks up. That might be due to malformed JSON. You can clear your local storage to get rid of saved block definitions that might be loading wrong (although beware that this will delete all of your local custom blocks).

I don't recognize the TypeError or the following script that failed to load.

from blockly.

oh so i will have to delete all my hard work, nevermind

from blockly.

but then why did the new block i had just created not lock up?

from blockly.

If you have enough local custom blocks that you don't want to delete, you can do something more involved to find the bad block and delete only it. The blocks are in local storage under BlockLibraryStorage.blockLibrary.

Chrome developer tools lets you interact with (and modify) your local storage.

However, you shouldn't do this until you figure out what the broken block is and how it is broken.

from blockly.

How do i find the bad block(s)?

from blockly.

also as i specified, i don't use Chrome

from blockly.

Firefox's developer tools have very similar functionality. Here's the documentation on the storage inspector and local storage.

SO, basically, when i created new blocks with no color input, aka black, i noticed they wouldn't move when they were put in workspace, and has been happening to every custom-made block since then. Every single one.

The new block with no color input is probably the trigger, but I can't say without more information. To debug further you can:

• Share your block definition here so I can take a look
• Load the block factory in a private window or in a different browser and try to create the same block, and see if it fails.
  • If you have many blocks, you can go through one at a time until you find a breaking block. I suggest starting with the one with no color input though.

from blockly.

I deleted the ones with no color input, still persists. theres one block i recently created that i think isn't affected by glitch. And how do i share all block defenitions at once?

from blockly.

You can share the block definitions by copying the value of the BlockLibraryStorage.blockLibrary key in local storage from the Firefox web inspector:

from blockly.

https://pastelink.net/71qmn64v

from blockly.

I had just made new blocks ona school computer, and they all had color inputs. They still locked up, with no clear cause why. Can't even screenshot cuz my school disabled the inspection feature.

from blockly.