I installed the Bric and removed the “old” .js file from the project settings and it has the same result. I had to go through the page settings of all 12 pages of the project to see where Blocs had attached the same .js file. It was done on 2 pages.
Updating a Bric and having to verify all your project pages individually is cumbersome.
If the Bric is in the Global Area the attachment will be in the project attachments, like the green notification states, not page attachments. If you have multiple instances of this Bric in the project you could see duplicate file resources.
Any chance I could get both versions of the Bric to try at my end?
At any point had the Bric been used on a pages dynamic area rather than in the Global Area?
And how old is the project? There are various issues that are now patched that caused leftovers when moving custom Brics between the dynamic and global page areas. It could be that these attachments have been there a while caused by a now patched issue.
I am just pointing out that the old file was not attached at all in the project, and yet it was still showing in preview. As shown above in pictures.
I understand page and project attachments.
It’s not every project either. I have had no issues during dev, until I had to update the existing project, using the steps I have mentioned previously.
I know at least one tester who has a site up live, and it’s working correctly. They just had to remove the old js file.
Thats interesting, so the original Bric install would have been in Blocs V4. Out of interest, do you still have Blocs version with an older version of this Bric?
I copy a bloc on one page with a keyboard shortcut cmd + c then switch to another page and paste with cmd + v. That part is fine, but if I then try to move the position of the bloc using the opt + cmd + arrow it fails to move the bloc. The page just scrolls to the top or bottom instead, depending on the arrow direction. If I do the last part with the menu options though it works as expected.
The curious part if that if I copy/paste a bloc to another page, then click on the desktop first before trying in Blocs the keyboard shortcut works correctly, so it seems to be focus related.
To help troubleshoot with custom Brics, I’ve added automatic API debugging in the next beta. Select a Bric and it will light up with all calls made, on initiate and throughout it’s usage.
I think this will help to track down potential issues and lower confusion on their causes.
the default debug API call can still be used for custom stuff, but almost all of the main API calls trigger a console log now.