Blocs 3.4 Beta Build 1

Hey everyone,

I hope you have all had a nice summer. In-between beers in the sun and hanging with family, I’ve had my head down working on Blocs 3.4, as I mentioned a few times now, rather than add new features for your websites, I’ll be addressing long standing issues with Blocs and looking at improving areas that cause the most support request and issues.

This release focuses on an area that is probably the most common issue Blocs users run into and that is the management of project assets. Aside from fixing a range of issues in this area I’ve also added some new features that (when fully tested and stable) should hopefully make working with Blocs even more user friendly and cause a lot less headaches.

New Asset Management Features.

Support for Embedded Assets
Blocs 3.4 has an upgraded file format, which allows project assets such as images, videos, additional style sheets etc to be saved into the actual Blocs files. This change took A LOT of work, I’ve tested it internally for weeks, but of course this is a beta so expect the unexpected. This feature is enabled by default on new projects and can be switched off in project settings (misc).

Asset Embed For Old Projects
If you want to embed all of the assets in a pre 3.4 project, you’ll be happy to learn that I’ve added a feature to do that. One click and your projects assets are all embedded into the project file.

File > Project Assets > Embed All Assets in Project

Generate Package Support
So if you don’t want to embed assets in projects, but want a way to make transporting files between Macs easier? You are going to love the new Package generator. One click and everything used in a project is stored in an organised directory ready to be moved to another Mac.

File > Export > Generate Package

Asset Manager Workflow Improvements
The Asset Manager is used to assign assets in Blocs with the exception of the project settings and the class editor. This is now rectified in Blocs 3.4, when you opt to change the project favicon or a classes background image, the Asset Manager is now used.

Minimum MacOS Requirements
Blocs 3.4 now requires MacOS 10.12 minimum, the app will no longer boot on anything lower.

This is just a few of the improvements in Blocs 3.4, you can view the full change log on the download page for a more detailed breakdown.

As this version of Blocs (3.4) makes heavy changes to project files and structures, please ensure you only use backup projects with it until the dust settles after the first few beta builds.

Download Blocs 3.4 Beta Build 1

Known Bugs in Build 1

Empty font selection dropdown - Fixed and ready for build 2.


Man it’s sucks to be you! :rofl:
Yes, I’ve been enjoying the summer, took a trip to the Sturgis Rally in South Dakota, drank more than a few beers, and played it the lake.

Seriously, thanks for your hard work as us Blocheads know you always deliver.

Look forward to testing the beta.



Thank’s a lot! Will start trying it now. Thrilling…

1 Like

This one caught my attention:

“Updated and modernised Blocs file format for future proofing”

This sounds intriguing, however as a first beta, users should definitely maintain a copy of existing projects prior to saving a new copy with a different name in 3.4. Give yourselves an easy exit if things go wrong.


Good news!
But what about Wordpress support?

That’s coming, it’s a separate thing to the main Blocs application.

1 Like

Thank you @Norm for designing and maintaining one of the easiest and best Web Building program out there!
Even thought I can’t install because I don’t make the minimum requirement by the time I do upgrade you will be at Version 4 and who knows what Blocs will be like then. :smile:


@Norm After copying a single bloc of content from one page to another I have seen a worrying tendency to duplicate the entire content of the first page to the second one. This has happened twice now in the last 30 minutes. We’ve seen this previously in Blocs and it seems to be back with 3.4. I can send you the project files if that helps.

I also found that when I was working on one page it was still showing the name of the previous page I had just copied from. I had to flick back & forth a few times until it showed the correct page, but soon after I found it had wiped the entire contents and replaced it with what was on the first page.

1 Like

The page navigator has had a lot of changes under the hood and has been rewritten to use a newer version of a grid component.

This all sounds related to that.

At which part of the UI was the name not refreshing?

On the page dropdown or in the sidebar navigator?

There was no correct change in the page selector on the top right of the interface.


I didn’t look at the pages in the left hand side panel while this was going on, so I don’t know what was happening there.

I had been working on a page called south west and wanted to duplicate some of the formatting with lists to the south east page. After duplication, it was still showing south west at the top of the south east page. Soon after the entire south east page had been wiped and replaced by the south west content.

I was just in the process of filing a support ticket and attaching the project files.

1 Like

No need for file. I think I know whats going on.

I’ll get this patched up.

OK I’d just sent you the ticket #8774. It includes the original 3.3 file, plus the one done with 3.4 so you can check this yourself.