@Norm Okay, been playing with it, and at least I can get the test site to load now using @tom2 suggestions
- make sure there is both a “Page Name” and “SEO Title” for every page in your Blocs 3 project
And in the Pulse 5 Project “export” settings
- “unclick” Minify HTML
- “unclick” Minify Main CSS
- “unclick” Enable Lazy Loading
So at least the exported files now work with Pulse 5
I also figured out how to add Pulse compatible “Blocks” that can be nested in folders
- don’t use the Blocs 3 “Pulse Bric”
- instead use a “HTML Widget” and put in the regular Pulse tags for your blocks {{block:folder-name/block-name}} example {{block:home-page/main-content}} that way you can organize your editable areas into “folders” in the Pulse dashboard, makes finding them far easier… you will have to create the folder and editable area through the Pulse dashboard though
- AND this seems like it will also embed whatever other Pulse tags you want. I tried it with a Pulse {{masonry:galname}} “tag” and inderneath it, a {{justforms}} “tag” (Pulse 5’s advanced form builder) on this test page
Now what still doesn’t work is the “on-screen editor”, no little pink boxes… Something else is still getting over-ridden when exporting the Pulse 5 project out of Blocs 3.
One other note - by using “Pulse Tags” inside of HTML Widgets instead of “Pulse Brics” - all content editing is done through the Pulse 5 Dashboard (and hopefully, if we can get it working, the “in-line editor” which is sweet for the clients!)
- When you upload any page changes from Blocs to your Pulse install, you only need to upload the “Template” folder, and the “Pages” folder inside the “Content” folder. That way you never worry about wiping out any changes that were made by you, or your client.
I have posted this over on the Pulse CMS forums as well