Re: Query Regarding Upgrade Process from OpenCMS 10.5.1 to 19
Michael Emmerich via opencms-dev <[email protected]> Fri, 8 Aug 2025 14:25:26 +0200
| Newsgroups | gmane.comp.cms.opencms.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============4361418188265222859==
Content-Type: multipart/alternative;
boundary="------------KdqNPTTqC9gWbwnhY9VgZBGL"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------KdqNPTTqC9gWbwnhY9VgZBGL
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Hello Nivedita,
it depends a bit what you mean by "updating OpenCms 10.5.1 to OpenCms 19".
If you update the OpenCms system itself, this has no effect on your
templates and websites. You "just" update the core system and as the
result you will have some changes in the UI, but your websites and
content stay the same.
The update of the OpenCms core can be done with the updater from the
OpenCms website. As wit all major updates, it is a good idea to make a
backup of your existing system first (web-application and database)
After the update, the website and your template works as before.
The other thing is if you want to update your website with a new
template. Or to say, to make a relaunch with a new template. This is
nothing that goes automatically like the core updater. Here it would
make sense to make this sub-site by sub-site. Maybe it would be make
more sense to set up a new OpenCms 19 in parallel to the existing one
and rebuild the headquarters and sub-sites step by step. But this is
hard to say which is the best solution without knowing whit is there
right now and what should be thee on the new system.
Kind regards,
Michael
Am 08.08.25 um 07:00 schrieb niveditasheoran via opencms-dev:
> Hello
>
> We have a site–subsite system developed using OpenCMS 10.5.1, as shown
> in the
> attached snapshot. In our setup, nvs serves as the headquarters
> website, under
> which nvs-school has multiple subsites.
>
> We are planning to upgrade OpenCMS to version 19 and would like
> clarity on the
> upgrade process for this type of structure. Specifically, should the
> headquarters site and its subsites be upgraded separately, or can the
> upgrade be
> performed for all at once?
>
> As I am new to this, I would appreciate your guidance to ensure the
> process is
> handled correctly.
>
> Kind regards,
> Nivedita
>
>
>
> ------------------------------------------------------------------------------------------------------------
>
> [ C-DAC is on Social-Media too. Kindly follow us at:
> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
> ------------------------------------------------------------------------------------------------------------
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> https://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
>
--
Michael Emmerich
Alkacon Software GmbH & Co. KG - The OpenCms Experts
http://www.alkacon.com
http://www.opencms.org
--------------KdqNPTTqC9gWbwnhY9VgZBGL
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello Nivedita,</p>
<p>it depends a bit what you mean by "updating OpenCms 10.5.1 to
OpenCms 19".</p>
<p>If you update the OpenCms system itself, this has no effect on
your templates and websites. You "just" update the core system and
as the result you will have some changes in the UI, but your
websites and content stay the same.</p>
<p>The update of the OpenCms core can be done with the updater from
the OpenCms website. As wit all major updates, it is a good idea
to make a backup of your existing system first (web-application
and database)</p>
<p>After the update, the website and your template works as before.</p>
<p><br>
</p>
<p>The other thing is if you want to update your website with a new
template. Or to say, to make a relaunch with a new template. This
is nothing that goes automatically like the core updater. Here it
would make sense to make this sub-site by sub-site. Maybe it would
be make more sense to set up a new OpenCms 19 in parallel to the
existing one and rebuild the headquarters and sub-sites step by
step. But this is hard to say which is the best solution without
knowing whit is there right now and what should be thee on the new
system.</p>
<p><br>
</p>
<p>Kind regards,</p>
<p>Michael</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 08.08.25 um 07:00 schrieb
niveditasheoran via opencms-dev:<br>
</div>
<blockquote type="cite"
cite="mid:1670345982.50748.1754629203079.JavaMail.open-xchange@webmail.cdac.in">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div> <span>Hello</span> <br>
<br>
<span>We have a site–subsite system developed using OpenCMS
10.5.1, as shown in the</span> <br>
<span>attached snapshot. In our setup, nvs serves as the
headquarters website, under</span> <br>
<span>which nvs-school has multiple subsites.</span> <br>
<br>
<span>We are planning to upgrade OpenCMS to version 19 and would
like clarity on the</span> <br>
<span>upgrade process for this type of structure. Specifically,
should the</span> <br>
<span>headquarters site and its subsites be upgraded separately,
or can the upgrade be</span> <br>
<span>performed for all at once?</span> <br>
<br>
<span>As I am new to this, I would appreciate your guidance to
ensure the process is</span> <br>
<span>handled correctly.</span> <br>
<br>
<span>Kind regards,</span> <br>
<span>Nivedita</span> </div>
<br>
<img src="https://pramani.cdac.in/signature.jpg"
moz-do-not-send="true">
<br>
<br>
------------------------------------------------------------------------------------------------------------
<br>
[ C-DAC is on Social-Media too. Kindly follow us at:
<br>
Facebook: <a class="moz-txt-link-freetext" href="https://www.facebook.com/CDACINDIA">https://www.facebook.com/CDACINDIA</a> & Twitter:
@cdacindia ]
<br>
<br>
This e-mail is for the sole use of the intended recipient(s) and
may
<br>
contain confidential and privileged information. If you are not
the
<br>
intended recipient, please contact the sender by reply e-mail and
destroy
<br>
all copies and the original message. Any unauthorized review, use,
<br>
disclosure, dissemination, forwarding, printing or copying of this
email
<br>
is strictly prohibited and appropriate legal action will be taken.
<br>
------------------------------------------------------------------------------------------------------------
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a class="moz-txt-link-freetext" href="https://lists.opencms.org/mailman/listinfo/opencms-dev">https://lists.opencms.org/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Michael Emmerich
Alkacon Software GmbH & Co. KG - The OpenCms Experts
<a class="moz-txt-link-freetext" href="http://www.alkacon.com">http://www.alkacon.com</a>
<a class="moz-txt-link-freetext" href="http://www.opencms.org">http://www.opencms.org</a>
</pre>
</body>
</html>
--------------KdqNPTTqC9gWbwnhY9VgZBGL--
--===============4361418188265222859==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVGhpcyBtYWls
IGlzIHNlbnQgdG8geW91IGZyb20gdGhlIG9wZW5jbXMtZGV2IG1haWxpbmcgbGlzdApUbyBjaGFu
Z2UgeW91ciBsaXN0IG9wdGlvbnMsIG9yIHRvIHVuc3Vic2NyaWJlIGZyb20gdGhlIGxpc3QsIHBs
ZWFzZSB2aXNpdApodHRwczovL2xpc3RzLm9wZW5jbXMub3JnL21haWxtYW4vbGlzdGluZm8vb3Bl
bmNtcy1kZXYKCgoK
--===============4361418188265222859==--