I have to be honest that I’m extremely disappointed with Pulse CMS. It’s integration with Rapidweaver hasn’t been thought through. Placing Pulse CMS in the resources of a Rapidweaver project is asking for trouble. It will sync the CMS to your site, but any changes you make to the Pulse CMS online will be overwritten should you inadvertently re-publish all files from your project.
I like the idea of a flat file CMS, but pulse is no where near to replacing armadillo and lacks too many blog features such as tags, categories and even the ability to change the date format. There’s practically no SEO meta tags available. It has less features than the built in RW blog.
Putting the Pulse CMS code into the resources area ist just one example how to use it. Don’t forget that there are already 4.000 active Pulse CMS installations outside of the RapidWeaver world.
And as you already found out, it is not recommended to use the demo content for productive usage.
As @instacks points out, you don’t have to put it there. You can do a direct FTP drop in but the resources option is just an idea to avoid having to use FTP.
Tags and SEO tags for each blog post are already built for version 5. And the date format can be changed in the config file already - with an option to do it in Pulse 5 from the settings panel.
Hopefully you can see all the other great features that are in there also already…
Then don’t use the RW resources area and just FTP it to your server. This is my preferred way of doing it and it works brilliantly every time and you control it. I always FTP warehoused images, web fonts and Pulse folders.
You could however, just use the Resources to make the initial FTP transfer and then remove from the Resources area. If you are going to use the Resources area then that is what I think is the best way to do so.
It is all about flexibility of options and catering for RapidWeavers user base who cover the entire spectrum of abilities. For some users it it might be the best place.
Can you explain why it would be the best place for any user? The point to something like Pulse CMS is allowing users to edit content without the need for Rapidweaver. I fully understand that adding it to your resources for the first publish makes sense. I cannot understand anyone recommending leaving it there as edits will be made through the admin login online. Leaving Pulse in the resources creates an unnecessary risk of overwriting files, when removing the folder or encouraging people to remove the folder removes that risk.
I’ve only highlighted it here because I nearly did it and thought others users might benefit from the warning.
Well one example might be that a user completes a site and adds the Resources at the end of the development cycle and does a final update of site. Or you might make a final update to an existing site to add a blog. Depends where you are in the development cycle.
For someone who was about to try Pulse over Total am I right from the reading that for me to be able to ever need to republish they’d lose all their edits? Unless they use a FTP program which really isn’t client friendly to anyone I’ve sold a website to.
If you were to use the RW7 resources to save your Pulse Folder then there is a possibility that it could overwrite - I think. I say I think because I never understood the Resources concept and I would never trust it anyway. However, the best (and only way) is not to use Resources IMO and just FTP the Pulse folder once during the initial upload. Same applies to any syncing needed. If RW is syncing the resources then you really need to set the rules for syncing and I don’t believe those rule options are in place in RW. Forget Resources and just use FTP.
Similarly if you use the Resources for SVG storage and then do any live server SVG edits, you might loose the edits.
Exactly. You FTP load it once to www.domain.com/pulse for example. Job done. The customer just types www.domain.com/pulse/admin into browser or one of the Pulse Apps and they start to add content.
