Ruskin
asked on
Building a Vignette Site + CMA initial questions
Hi all,
I am building a Vignette driven web site that will also have a CMA for the content managers.
Im using V/5 release 5.6.3 on Solaris without an app server (only Tcl).
The CMA will have a preview function (dev site) before changes are launched to the live site. I will also need versioning on the site.
Now to my queries:
How easy is it to use the full Vignette CMS functionality with Tcl?
Should I build my own versioning rather than using the built-in versioning?
Any other comments? :)
Kind Regards
// Anders
I am building a Vignette driven web site that will also have a CMA for the content managers.
Im using V/5 release 5.6.3 on Solaris without an app server (only Tcl).
The CMA will have a preview function (dev site) before changes are launched to the live site. I will also need versioning on the site.
Now to my queries:
How easy is it to use the full Vignette CMS functionality with Tcl?
Should I build my own versioning rather than using the built-in versioning?
Any other comments? :)
Kind Regards
// Anders
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Apologies - I see you asked this question in another post.
This is a simpler solution, but the other works as well.
Anyway, if you've got any other questions, just ask - I'll try to remember to check!
This is a simpler solution, but the other works as well.
Anyway, if you've got any other questions, just ask - I'll try to remember to check!
ASKER
Thanks hooker,
I came to the same conclusion, forget Vignette versioning and use two db schemas. It was nice to get it verified though!
I would really appreciate if you kept an eye on this area because I will probably stumble onto other difficulties in the near future!
Have you got any experience with running multiple instances of CMSs on Solaris? I'm using V/5 patched to release 5.6.3.
I came to the same conclusion, forget Vignette versioning and use two db schemas. It was nice to get it verified though!
I would really appreciate if you kept an eye on this area because I will probably stumble onto other difficulties in the near future!
Have you got any experience with running multiple instances of CMSs on Solaris? I'm using V/5 patched to release 5.6.3.
On one of our development environments, we do have multiple CMS on Solaris. I'm not involved in the admin of that, but in general things seem fine.
I don't know why you are using multiple CMS but we use them so that there is a development environment and a production-like test environment.
I would be careful if you're planning to develop multiple sites in different CMSs, e.g. website A in CMS A, website B in CMS B, that will then be in different CMSs on the same live box. At the company I am consulting for, there is group who have done this who are now having lots and lots of problems with their box with this set up now that their sites have grown and have increased traffic - they can't throw enough resources at the box to sort it out. In this case, I think you're better having people develop different sites on the same CMS in separate projects.
I don't know why you are using multiple CMS but we use them so that there is a development environment and a production-like test environment.
I would be careful if you're planning to develop multiple sites in different CMSs, e.g. website A in CMS A, website B in CMS B, that will then be in different CMSs on the same live box. At the company I am consulting for, there is group who have done this who are now having lots and lots of problems with their box with this set up now that their sites have grown and have increased traffic - they can't throw enough resources at the box to sort it out. In this case, I think you're better having people develop different sites on the same CMS in separate projects.
just out of interest,
what sort of site are you developing?
what database?
what sort of site are you developing?
what database?
Some other tips:
1. Cache as many pages as possible and build cache clearing functionality into the functionality that launches the content in the CMS.
2. Limit use of Components, use Libraries instead where possible.
3. My minds a blank ....
1. Cache as many pages as possible and build cache clearing functionality into the functionality that launches the content in the CMS.
2. Limit use of Components, use Libraries instead where possible.
3. My minds a blank ....
ASKER
Thanks for your thoughts and tips!
I am currently developing a rather small Vignette driven web site for an insurance company. PDFs (files) and pure HTML documents (database) can be added to the site to drive various sections (Latest News, Product News, Press Releases etc etc).
The CMA uses MS HTML Editor functionality implemented with IE5.5 (requirement for Content Managers) so I'm not using eWebEditPro.
I am forced to use Sybase 11.9.2 due to company standards.
As I'm quite new to Vignette I haven't really looked into Components that much so I'm only using Libraries.
Thanks again!
I am currently developing a rather small Vignette driven web site for an insurance company. PDFs (files) and pure HTML documents (database) can be added to the site to drive various sections (Latest News, Product News, Press Releases etc etc).
The CMA uses MS HTML Editor functionality implemented with IE5.5 (requirement for Content Managers) so I'm not using eWebEditPro.
I am forced to use Sybase 11.9.2 due to company standards.
As I'm quite new to Vignette I haven't really looked into Components that much so I'm only using Libraries.
Thanks again!
ASKER
When a change is made I would like this to be visible on the development site and I would like the live site to be unchanged until the change in launched.
This could mean anything from editing, deleting or adding a record.
In order to acheive this I do need to hold two different entries of the record in the DB. Can I with a Tcl command tell whether I'm on the development or the live site?
// Anders