User login
Active forum topics
- Mass publishing
- page content layout and duplication problem
- Why the tag <portlet:actionURL/> misses my servlet params?
- Retrieving the Menu from VAP
- Unable to delete the channels and the presentation templates
- Unable to see VCM Site List / Template List inside VAP Server Console
- How to insert Content Instance into Relator?
- Vignette's geographical presence
- Vignette 6 based websites
- menu bar disappeared
Reflections on Vignette
It is pleasant to find people who share your thoughts. Like Sean McMains, after reading his post "A programmer's reflections on Vignette", you think: - Ooh, there is someone out there like us, with the same problems like our team".
All the issues he describes in this blog, has happened to our team: the fight against that byzantine API, the impossible updates of the content types, the lack of functionality of Dynamic Site, the complex interface to users, etc... I also have the same feeling that It needs 4 times more work than it ought to be.
His conclusion is the same of our team, Vignette fits well for a site with lots of traffic and lots of content. If you need a flexible site, with less content, other cms will fit better. What do you think?
Comments
Thanks for the link!
Thanks for the link back to my weblog. I didn't figure that we were the only ones out there having such issues.
We're using Magnolia now, for what it's worth, and are very happy with it.
We're unhappy with Vignette
We're using Vignette for 2 big websites with lots of traffic and lots of content and we are unhappy with Vignette.
Base on my 10+ years experience working with various Content Management Systems (CMS) and 6 months using Vignette I can affirm that Vignette is THE worst CMS I have ever worked with.
I’m working for a large respected Canadian organization and we are very unhappy with Vignette. We are switching to another CMS. I won’t tell the name of the new CMS or the organization. I’m expressing my personal opinion here. And I don’t want to make publicity for the other tool before trying it.
Here are some naked facts about Vignette:
CONS:
- Their tech support is poor and slow. They aren’t able to fix simple Vignette bugs.
- Very expensive in our case $250,000 to $500,000 so far and growing.
- Vignette is mostly a Consultingware: A CMS first developed for a limited number of consulting clients, then hastily rebranded as a “product” matching everybody needs. The fact is it doesn’t match OUR needs.
- Counter-productive tool for employees. Awful workflow.
- Poor documentation & support from Vignette.
- Steep learning curve. Complicated interface.
- Security features are dangerously weak. Easy for concurrents to access sensitive information. A friend of mine is testing security features as a living to prevent hacking, according to his testing it takes less than 5 minutes to hack Vignette and access sensitive information.
PRO: Sales team.
More reviews from other Vignette users: http://www.cmsmatrix.org/vignette-cmportalsolution/vignette-cms-whos-usi...
Hi
The numbers you're giving just don't make sense. A single license for Vignette is around 20K which is in line with others in the same market. I've not seen the kind of bugs you're talking about. what specific bugs were not fixed? I've found vignette support to be helpful when I've had problems or questions.
The tech docs seem ok to me and I've used them several times to get the platform installed, configured, and running. I had some questions along the way but they were answered on the vignette forums.
What specific security problems? It's all based on j2ee with passwords stored in third-party LDAP. I've never had a problem with security. Hacking is another matter but this typically takes place in the front-office on the app servers or web-servers. Vignette CMS is in the back-office and is 99% of the time inside the corporate network.
If you give me specifics I'd be glad to share my experiences with the VCM product and try to help you resolve any problems you're having... I've been using VCM/Portal for several years on several sites and could probably give you some pointers on how to use the products.
Regards,
Davis