Hi. Recently my internet service provider broke my derekdigital site which I built with Blocs 2.x and PulseCMS 5.1 - and got to work with a lot of help and advice from @pulsecms and Norm at Blocs app.
So yesterday I thought it was time to fix the site using Blocs 3.0.6 and PulseCMS 5.2.1. I decided to do a fresh install of PulseCMS - after taking a backup of the original site
White labelling and installation of Pulse CMS went smoothly, and after doing a few modifications to my Blocs file, I exported my site as a Pulse 5 theme. I then transferred the files in the content and template folders generated by Blocs to my Pulse site. I then returned my blog txt and jpgs - from the backup I made - to the new Pulse site too.
I launched the site and the home page appeared as expected. Yay! But then I found none of the navigation works. Pages cannot be found Everything is there, because I can see it and amend text and images via the Pulse Admin Dashboard. Itās just the pages that donāt appear. However links to external sites, that Iāve added in the footer of the home page do work.
Iām sure there is a simple fix for this. My question is how? Iād love get my PulseCMS/Blocs site up and running again asap. Thanks! D
I followed the instructions on this site and got the internal server error message. So it looks like everything is correctly installed.
Iām going to strip out the navigation in Blocs app and rebuild it, to see if opening a 2.x document in Blocs 3.0.6 caused the problem. Norm at Blocs app has also asked to have a look at the file, so will send to him, if I still canāt get things to work.
But reading recent posts on this forum, it appears others are using the same versions of PulseCMS and Blocs are getting things to talk to one another.
Hi @pulsecms, Iāve sent my file to Norm at Blocs for him to have a look at. Itāll be interesting to see if he can put his finger on what is going one.
So Iām afraid Iāve removed Pulse CMS from my machine for the time being. Iām not sure whether it is an issue with my ISP, or the way software apps interact with one another, but something clearly isnāt working. Instead of spending more time getting frustrated, Iām going to take a break, and come back to it fresh in the new year.
Hi @Raimo
I donāt know why, but my projects with pulse and blocs work. Did you use special brics or something else ?
When it helps you can send me your blocs file and I give it a try on my test sever ā¦
tom
Hi ā¦
sorry, my English is not so good. What do you mean with āreferenceā Pulse block folders ?
And I donāt use tags ⦠What I do is only to use the blog system for client and set some text blocks so the client can change the text ā¦
sorry
tom
Okay, been playing with it, and at least I can get the 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}}
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.
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.