I agree with you about production and test environment: migration of portlets and template is easy to achieve but how about the contents of the pages ? Before the import/export of pages in 4.5 version, is there a solution with the database (we use postgreSQL). ?
That's exactly what I was saying ;-)... Excepted fake content for test purpose, your dev/test environement should have no "real content" as this content (and indirectly the underlying database model) may have been corrupted by your template or portlets development steps. So even with an XML Export/Import module, this will never 100% guarrantee that the exported XML DOM is not corrupted.
So ideally:
- Develop locally
- Then test (perf, etc..) in a copy of your prod environement (if any)
- Finally migrate your tested changes to the prod environment with your real data (or use the Jahia patches/upgrades to updgrade).
Cheers St�phane
Regards, Dominique Pellat
On Wed, 02 Feb 2005 10:13:14 +0100, St�phane Croisier <[EMAIL PROTECTED]> wrote: > > Hi, > > I do not understand what you are trying to achieve. If you plan to migrate > a production server with real content from 4.0.4 to 4.0.5, please use the > available patch (without deleting your virtual sites). If you only plan to > continue your ongoing test and development on a 4.0.5, please just use a > full fresh installation of Jahia and just copy your set of templates + > webapps in the right directories. > > In all the cases, please do not put in production a Jahia test/dev server > you initially used to develop/debug your templates. The database may then > be corrupted by your JSP tests (... and system hard crashes... ). So always > develop your templates/portlets from a local dev workstation and, once > fully tested and stabilized, migrate them to the production server. > > Cheers > St�phane > > At 18:29 31/01/2005, you wrote: > >Hello, > > > >I have some trouble after suppressing the last virtual site on a Jahia > >server 4.0.4 (in a preparation to a migration toward the 4.0.5 > >version): migration was ok, but I have now the message: "the virtual > >site has not been found": then I want to force the access to > >administration pages, in order to be able to create a new virtual > >site, but after entering user/pwd, the login page display again and > >again , and I have no more access to Jahia administration. > >Do you have a hint to create this virtual site manually, or am I > >oblige to reinstall the whole Jahia version 4.0.5 ? > > > >Thanks by advance ! > > > >Dominique Pellat > >
