Blocs 4.5 is here 🎉

Bugs noted so far:

  1. I used an image in my top menu across all pages - menu background image no longer shows in editor.
  2. When I go to drag an image into an image element, this no longer works - the asset is added to the asset manager, but does not get added to the editor (or maybe it does but the UI doesn’t update it) - this is annoying as I often clone sections then replace captions and images.
  3. Saving behavior may be even worse than ever, or maybe it’s just as bad as it’s been, but when typing and Blocs save, once it eventually completes (this should NOT be a blocking/takes focus operation!!), it doesn’t even retain the position your cursor was in, sometimes just scrolling to the end of the page. Way to disrupt workflow. :frowning:

Blocs > View > Wireframe…

Interesting, double check you haven’t enabled wireframe mode accidentally with the keyboard shortcut.

Regrading point 3, this is caused by auto backup, we are hoping to have some improvements with how this functions later in the year. In the meantime you can adjust the prefs in main app preferences to disable it completely or set longer backup times.

Does this mean I have to rework all of my dark-themed websites a third time? :roll_eyes:

1 Like

Looks like that was it (wireframe mode on the missing menu header texture/bg image), although checking the menu (I had cycled through the View menu once I saw this) doesn’t indicate on the menu it’s enabled, e.g. bit a checkmark next to it in the menu - that would be a good standardization.

Something’s still up with image behavior though - dragging an image onto a page with an existing image used to highlight and replace the existing image, adding it to the asset library if it wasn’t already there. Right now it seems to add to asset library but not replace or update the image. I checked in preview mode to see just in case it was replacing but simply not updating the image in editor view, but nope - adding to asset library if it wasn’t in there, but it’s not replacing/updating the image on the page, instead forcing me to select the image in the editor, drop the image from finder into the asset lib window, then clicking on it. (time waster)

I know the ‘why’ on the background save, but it’s fundamentally flawed and annoying as heck. I’ll go ahead and disable it altogether for now, but I’ve yet to see any professional-grade software with this behavior - do the save in the background, and if it has to be ‘blocking’, then at the very least don’t move the current cursor focus position. Please. :slight_smile:

1 Like

It’s great that you added lists to the right-click content menu but I’m confused as to why there is the same abundant structure that gets inserted with the list rather than just making a text list, inline with the rest of the text, like that way it’s done in this forum software.
Lists are text not structure in my opinion. While you need a certain structure with text, I would rather just see a basic typographic list without the unnecessary CSS structure associated with it. Like the example below.


  • Item
  • Item
  • Item
  • Item


I’m not sure what you mean? You can select text and turn it into a list with the text selection menu.

Aside from that, the other new list features will simply insert an empty list structure as they have no text selection to populate the list with.

Check the video at the top for an example of quickly turning text into a list.

Btw Lists won’t be nested within a text Bric. The structure is separated for cleaner code.

But in fairness the list Bric icon is very misleading, I’ll get this cleared up in the next update. Maybe we need two list brics :thinking:


Everything is editable, but I do generally find the amount of Lorem text inside a list is too much when a paragraph bric is added if you create the list that way. When that is done repeatedly it requires quite a lot of cleaning up.

1 Like

Yeah I think an alternative Bric is required here, a list pre-populated with single text lines.

I’m guna see if I can get it added in the next update.


If you can’t…who could? :stuck_out_tongue_winking_eye:

Rich the Weather Guy

Does anyone else see crashes when adding icons to buttons?
MacBook Pro (13-inch, M1, 2020)
Button crashes (368.5 KB)

How strange can you send me a copy of that project please.

Thank you for all your efforts @Norm, I have come to appreciate Blocs immensely and love using it. I continue to learn more through this excellent forum and friendly members who are always willing to help.

Just saw the Blocs 4.5 video and love the features, I’m tempted to upgrade. I am still using Blocs 4.1.1 because I need to keep updating my work and am a bit paranoid about the fact that I may come across problems if I upgrade. Is there a way I could keep and run both versions, that way I can experiment knowing that I can always fall back to 4.1.1 even though I may never need to.

I think (and I may be wrong), that you could just rename your Blocs app to Blocs411 or whatever, and have Blocs 4.5 also and they both work, albeit not at the same time.
I stand to be corrected.

1 Like

So I’d have to download the 4.5 app as opposed to go through the upgrade process, is that right?
Also, I will probably have to reinstall brics but that is not a problem. I would not need to run both versions at the same time, keeping version 4.1.1 and backups of all my files would just be a precaution.

Just rename your existing Blocs app to something like Blocs-old or whatever you like. Download the app fresh rather than as an upgrade and install in your applications folder. I very much doubt you will have any problems at all like that. Blocs has had many positive changes since 4.1.1. Your current brics are maintained and should appear in 4.5. I have Blocs 3 and 4.5 installed, plus betas usually.

Having a backup of files is always wise. I sometimes save new versions of projects as something like newclient-blocs-4.5-bs5

1 Like

Thank you @Flashman for your informative and detailed response. You’ve definitely encouraged me to give it a try :grinning:

Some of you may not have seen there is an update to 4.5.1 with a critical fix for forms on some servers when using PHP 8. Simply upload the site again using 4.5.1.

Is this happening with 4.5.1 also?