Blocs V5.1 Beta Build 2

[Jannis]

@Bill

Could you generated a variable that contains an array of pagename & subpath for each page so we can assign the correct path from the page to root?

Still missing a real world use case.

[PeteSharp]

Just updated to MacOS 13.3 this morning.

Selected some text today.

Blocs decided I should go to the beach…

Blocs became non-responsive, while spinning the ball of fun. Then the entire contents of the page disappears, the layer tree was still showing everything.

I had no issues restarting the project at least.

[Jannis]

@PeteSharp

beach

Mauritius ?

[PeteSharp]

Still waiting for Jerry to send the tickets he promised.

[Norm]

This a one of or does it keep happening?

[Bootsie]

It’s not happening here.
Mac Mini M2 with Ventura 13.3.

Another question: is it right that the inspector looks like this when you wrap text in span?

[PeteSharp]

After this I had other work to attend too. I’ll find out tomorrow if it happens again.

[webdeersign]

@norm Is there a missing icon on the “large previews for core Blocs” button? The button is blank.

Also, there is some odd behaviour when selecting a Bloc to be a favourite, in the Blocs list. E.g. selecting a Hereo bloc as a favourite, makes the view scroll up to show the Navigation Blocs above - see 12s into video below.

[pruthe]

My Mac was going to the beach too this morning immediately after updating to 13.3. Was affecting Safari and some other apps. I decided to restart again and all seems OK now, including Blocs.

M2 MacBook Pro

[Norm]

Missing symbol is because the older version MacOS does not have this SF symbol. I’ll add a graphic fallback.

As for the visual bump, it’s most likely your new favourite pushed the favourite list at the top of the Bloc Bar onto a new line or you added your first favourite causing this section to create extra space at the top of the list.

[Norm]

Hey Bill, some answers.

@Bill

api resource calls are showing resources in Project Settings > Project Attachments - those shouldn’t be in there, as resources api is only for resources attached to a specific page. (This is causing multiple files such as file.xxx & file-01.xxx to be exported) If it’s desired to attach resources to all pages then that’s what projectResource api is for.

It depends on the location the Bric is inserted, I’ve updated the developer docs to better explain this. Check the includes section.

@Bill

%pagePathLevel% is NOT being written into main page html on export. Would also like this to be written into template files as well.

It works fine for me using your Bric, this is my export

Remember this only works on export, not preview mode as per the documentation.

This is not generated in preview mode as it has a huge impact on preview speed.

@Bill

svg images in resources folder are not being exported.

SVG images are exporting fine here, as long as the SVG is referenced in the Brics HTML which is the expected behaviour e.g.

<img src="*resource-path/cog.svg">

If you don’t reference the SVG in the Brics html, then you would need to put the SVG file into the includes folder. This would force the SVG to be exported regardless of use.

I hope that helps.

[Bill]

@Norm

Ok,

Re: Project Attachments - I’m pretty sure I always put the bric in the Dynamic area.

Re: pagePathLevel: I just get this on an exported php page:

Could project attachments & page path level differences be due to the OS that the compiler supports? - I’m running 10.14.6 which is a tick behind due to support userbase.

Re: svg images: ahhhh, ok, had to delete & reinsert bric but got images in includes folder to export - glad that’s resolved.

Thanks, Bill

[Norm]

@Bill

Could project attachments & page path level differences be due to the OS that the compiler supports? - I’m running 10.14.6 which is a tick behind due to support userbase.

Blocs 5 is minimum 10.15, so it may be a good time to update.

I’ll check on one of the older macs to see if the pagePathLevel breaks on 10.14.