10-21-2009, 08:31 PM
Thanks Seacrest, that's that's I suspected.
MAVIC/UnDoug, I dabbled with Contribute back on version 2.0, and my recollection was that:
1. One had to buy licenses for each workstation that might be doing updating (unlike open source CMS)
2. The functionality wasn't as robust as a true open source CMS, more like Dreamweaver on Training wheels.
3. The synchronizing/locking/unlocking of files between the designer and content managers didn't always work 100%.
Perhaps it has come a long ways since then. Will give it a second look in any event. Don't think having to have Contribute installed on every workstation where updates might be made would be acceptable though. Maybe that has changed?
Thanks.
MAVIC/UnDoug, I dabbled with Contribute back on version 2.0, and my recollection was that:
1. One had to buy licenses for each workstation that might be doing updating (unlike open source CMS)
2. The functionality wasn't as robust as a true open source CMS, more like Dreamweaver on Training wheels.
3. The synchronizing/locking/unlocking of files between the designer and content managers didn't always work 100%.
Perhaps it has come a long ways since then. Will give it a second look in any event. Don't think having to have Contribute installed on every workstation where updates might be made would be acceptable though. Maybe that has changed?
Thanks.