By keneso on

Hi,

I got message to update a module (rules), I downloaded the new version (rules-7.x-2.9) from drupal.org, not using the link in the update report, then I uploaded the package thru ftp, then I thought I could just delete the older rules-7.x-2.8, but when I did so the site would go blank, I re-uploaded the old version, and when refreshing everything seemed ok; I re-ran the update report, and all is green with the rules-7.x-2.9, I tried again to delete the older one, but again the site went blank, I re-uploaded it again, and again everything seems fine.

Right now I have both versions on the server, is this going to be a problem, it seems I did a no-no thing, how should I go about updating?

Thank you

⋅ Categories: Drupal 7.x

Comments

yelvington’s picture

yelvington commented

Right now I have both versions on the server,

There's your problem. The new version goes in EXACTLY the same place as the old version.

darol100’s picture

darol100 commented

@yelvington

He is right.

- Darryl Norris
Be Connected: Website | Twitter | LinkendIn | GitHub

VM’s picture

VM commented

how is the old and the new on the server? They can't be in the same folder else the new would have overwritten the old. this indicates that you've placed the new folder outside of the sites/all/modules folder? If yes, overwrite the old version with the new and immediately run update.php

keneso’s picture

keneso commented

Thank you all.

@yelvington, @darol100

There's your problem. The new version goes in EXACTLY the same place as the old version.

Apologies for having given for granted that even if still learning (long way to go) I got that modules go in sites/all/modules; so yes the new version is/was residing EXACTLY in the same place.
See below what caused the confusion.

@VM

how is the old and the new on the server? They can't be in the same folder else the new would have overwritten the old. this indicates that you've placed the new folder outside of the sites/all/modules folder?

Apparently they CAN! At least I managed to do so ;)
Here is the trick:
I noticed that Drupal doesn't care if you upload the module in either of the following "configurations":
sites/all/modules/modul_name
or
sites/all/modules/modul_name-7.x-1.9/modul_name
so I had uploaded the latter, thus having
sites/all/modules/rules-7.x-2.9/rules
and
sites/all/modules/rules-7.x-2.8/rules
I haven't read/found anywhere saying which is best prectice, so I went that way.

Anyhow the problem was here:

If yes, overwrite the old version with the new and immediately run update.php

I just deleted the older version, and ran update.php which I had forgotten to do.

All is fine now, only latest module, and site working fine.

VM’s picture

VM commented

Apparently they CAN! At least I managed to do so ;)

That would be because you are uploading the module files in a two folder structure.

sites/all/rules = is perfectly fine and normal operating procedure which avoids having two of the same module in the same folder. Thus a best practice.

sites/all/modules/rules-7.x2.9/rules = one folder too many. version is listed in admin -> modules pulled from a theme or module .info file. Thus, versioning in the file/folder system isn't necessary.

keneso’s picture

keneso commented

Thus a best practice.

Well I know that now.
Reason for me was that I keep a local copy of the files, and wanted to know the version at a glance without being in the admin of site, and didn't bother to open each folder to upload the unversioned folder.

Now I learned more, and know better, thank you.