I just purchased pulse recently and I am finding it very difficult to port website designed from blocs to Pulse CMS.
I can not run the pulsecms installer. I have watched all the tutorial videos and followed the step by step but still cant seem to port a blocs template and even access admin panel.
So far, I have exported the blocs website project as template, replaced the 'contents folder and ātemplate folderā from blocs in replace of pulse 5 contents and template folder.
Tried to run the pulsecms installer, received an error message:
I would like to know how blocs users have successfully port their website to pulse, Kindly give a step by step especially when using an ftp to transfer (what assets do you transfer to the server and what you do afterwards).
Thanks in advance.
PS: tried getting information from PULSE forums and no help so far, figured i would ask fellow blocs users.
Also kindly let me know if I went about it the right way as far as exporting to pulse
So far, I have exported the blocs website project as template, replaced the 'contents folder and ātemplate folderā from blocs in replace of pulse 5 contents and template folder.
Hey @Norm and @pulsecms ,
I have been using blocs with pulse 4 for my websites a while and Iām about to redesign some of them and was going with pulse 5 for the new settings with multi blog etc.
I donāt want to start before blocs is compatible with the new pulse 5 since building without blocs is not an option for me. Is the compatibility still in the workings or is it ready to use, havenāt been able to find any information on this.
@Norm: I have a suggestion. I donāt use pulse, but I think this pulse compatibility issue could easily be avoided if export options were labelled with the supported pulse version. So exporting would be for āPulse 5.xā or āPulse 4.xā rather than a generic export for Pulse.
Thereās also the question of supporting for multiple pulse versions if there are version incompatibilities. Without that you would be forcing people to not updte blocsapp or to have to update their Pulse version.
I hope the Pulse developers warns you ahead of their new releases, so there are no surprises.
I guess this idea follows for other CMS support too.