Quantcast
Channel: C1 CMS Foundation - Open Source on .NET
Viewing all articles
Browse latest Browse all 2540

New Post: Upgrade Custom Packages

$
0
0
I always thought that if you nicely increased your package's version number (example: 1.0.0 -> 1.0.1) Composite C1 (v4.0) would update your package, or offer you to upgrade.

Yesterday I tried Releasing an updated package to production. So I increased the package version number. (in package creater). Downloaded, edited install config (allow overwrite) and uploaded it to our package server.

At first the package version wasn't updated, so I removed existing package and readded the zip.

On our production server I accessed the packages, but I can't see an option to upgrade (not under available, pkg isn't showing there. And not under installed)

What is the write flow to release updated packages??

Viewing all articles
Browse latest Browse all 2540

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>