This project is read-only.

Upgrading a module

Topics: Troubleshooting, Writing modules
Apr 2, 2011 at 1:44 AM

Hi all,

I have just tried installing a new version of my module over a previous version from a package. The installation process gave me multiple warnings that such files already existed (practically for every file in the package) and thus it was skipping them. I then rechecked files in file system -- old files were unchanged, so new files had been really skipped during installation.

So am I doing something wrong? Or should I uninstall the previous version of the module before installing a new one?

Or is there something I need to take into account when generating a package?



Apr 2, 2011 at 1:49 AM

I want to know how to handle this issue, too.

Did you try delete the old file manually?

Apr 2, 2011 at 11:39 AM

What module was it?

Apr 2, 2011 at 8:57 PM

@Jetski5822 - it was my own module

@freeflying1222  - yes, when I delete files first, or manually copy them in the file system overwriting old files -- then everything works fine. But I want to know what happens to users of the old version of my module when they install a new version through the Orchard admin interface.


Apr 2, 2011 at 9:09 PM

Just wondering, did you install the original version thru a package or just copy the files in? Maybe it's a file permissions related thing. Try both install and upgrade steps thru packages on a clean instance.