Module released, file is not found or checksum error

[Sonya]

I have made a new release. It is not possible to download and install this module from Module Manager -> Q -> Quizzard (0.9)

http://s3.amazonaws.com/cmsms/downloads ... rd-0.9.xml

Code: Select all

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>downloads/6604/Quizzard-0.9.xml</Key>
<RequestId>5696D0224668C7A5</RequestId>
−
<HostId>
S7Q99ZkFx9qRZx6KDiEVl5TjrJtzphel4+zM798p4ZrksQRRKO/45IeAZGETMcgY
</HostId>
</Error>

I have uploaded false file while creating changelog for the release in the forge, deleted it and uploaded correct file that is shown here http://dev.cmsmadesimple.org/project/files/276 Now, the file can be downloaded from forge and installed, but not through Module Manager.

I have purged repository cache in my installations.

What can I do to make installation available from Module Manager?

[Jos]

I think this is what happened to my latest release of Gallery (1.4.3) too, although there the message in ModuleManager is that the checksum doesn't match

[Sonya]

Jos,

now, some hours later I have messages:

For Quizzard

Code: Select all

Checksum error. This probably indicates a corrupt file, either when it was uploaded to the repository, or a problem in transit down to your machine. (expected a82477ab828aba0b8c4097ec72e6d37a and got bfdddac7141a1b04266c495b8ef5a2f8)

For GBFilePicker

Code: Select all

Checksum error. This probably indicates a corrupt file, either when it was uploaded to the repository, or a problem in transit down to your machine. (expected 3895a2085ce1324c20ff587438866063 and got 3386876c87d012d6dfb4750100ef3afd)

For Gallery

Code: Select all

Checksum error. This probably indicates a corrupt file, either when it was uploaded to the repository, or a problem in transit down to your machine. (expected 2ab10c6de323f9249ce2ef21decbdebc and got ba7bff868353b61d305ae8519909f2f8)

However, the files listed above are not corrupted in the forge and can be downloaded and installed via XML.

Dev team: Is there any way to automatically update module repository to avoid this stuff?

[gingercat]

I've had the same problem as well . The solution was download the xml file and install that way.

Installing by uploading the module files manually caused upload errors when trying to upload images to the gallery.
Installing from the module manager didn't work as it always returned checksum errors

[bess]

I probably found the cause of these errors and especially how to get around!

The cause (in my case) was to generate the xml file in my local installation under windows (with WampServer, or EasyPhp).

The solution (still in my case) is to upload on one of my websites the new version of my module file by file with FTP, and from my website, generate the xml file.

Therefore the file placed in the forge is not corrupt.

Do not ask me why Windows WampServer or causes this error, I do not know ... but at least I have a working solution.

Can anyone confirm for me or rather me refute this theory?

[Sonya]

The cause (in my case) was to generate the xml file in my local installation under windows (with WampServer, or EasyPhp). Can anyone confirm for me or rather me refute this theory?

Unfortunately, not. I have two modules, both XML are created local with WAMP. The first one is "corrupted", the second is OK. In my case, it is how I have described in my first post. If I release XML and then go to edit this release and replace XML file by another (e. g. if I occasionally uploaded false file while creating release) then it suddenly gets "corrupted". I assume that when a file is replaced in forge, then checksum is not updated, and thus the replaced file does not match and is "corrupted".

[bess]

arg

bad luck...