CMS Made Simple Forums

just downloaded and installed TemplateExternalizer 2.0.2 (via ModuleManager in 1.10.1). Then upgraded to v2.0.3 via the same mechanism. No problems here.

I don't think this is PHP version related though I just upgraded my VM to have PHP 5.3.2 today (ubuntu is so sweet). It could be some kind of timeout error if there is something between your CMSMS install and the CMSMS Web servers causing slow traffic.

Anyways, could you double check your audit log... and your apache error log to see if there are any errors... maybe debug mode would help too..

Hello,

I like to add it to the discussion. All of my modules have problem with the checksum error (Analytics, Extended Content Blocks, MleCMS, MleDomain...).

I always uploading XML files with unique names (Analytics-1.1.xml etc), but without success.

I just tried MleDomains and MleCms ... no problems (other than some notices generated in the install routine).

Calguy.. On a slightly similar topic, I've never been able to install CGExtensions from the XML file.. I always get some sort of error (I can try it again and give you the specific message)... Not a big deal.. I just use the tar.gz file. I've looked this up and haven't found a single mention of this on the forum, so it could just be me. (many different versions on different hosts).

Okay.... I've made some changes to ModuleRepository wrt the checksum stuff. And was able to download the latest version of AdvancedContent with no problems.

things should be better now.

Now:

A problem occurred downloading the XML FILE: Analytics-1.1.xml
A problem occurred downloading the XML FILE: MleDomains-1.1.1.xml
A problem occurred downloading the XML FILE: ECB-1.2.xml

Tested on localhost (wamp), and linux server.

For modules with checksum errors in Mod Manager, I also get the problem if I manually download the XML file and then attempt to install it via file upload in Modules.

This makes me think the problem is with either the XML file or the checksum, and not my server's connection.

I'm trying out your new system, Calguy. Will let you know, and also get debug output for you if the problem continues.

Whatever you did Calguy, I can down manually download the TemplateExternalizer XML file and install it through Modules successfully. So the checksum error is fixed.

However, when I try to install it through Module Mgr, it gives the error:

A problem occurred downloading the XML FILE: TemplateExternalizer-2.0.3.xml

I don't get this error with your modules, or core modules.

We are making progress here, but there is still something not quite right.

Try it now. I did find something.

It's amazing what can happen if you give the developer enough information to at least reproduce a problem.

Joy, joy! Now ModuleManager seems to be working 100%!

A big THANK YOU, Calguy!!!

Still doesnt work:

Analytics
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 eb441b8d0fa28596dad08607b95d17af and got 70e3c2be271add049d3be7f66dbbcd47)

MleDomains
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 477df5bf080315e9bf28739c9b928458 and got 59159473ecba66cd40fb2159e141a0cd)

ECB
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 e1b6301539d27608e4a53f015186b32c and got 0214daa65903713ae9ca6e7fee3041c7)

I tested it at my office and at my home.

I just tried it with TemplateExternalizer 2.0.5 - released this morning - and it fails checksum in the Module Manager, but it passes if I download it and install through Modules.

Just tried MLEDomains 1.1.1 and TemplateExternanlizer 2.0.5 in ModuleManager. Both installed without problems.

At this point if there is a problem with checksums it is probably because of some limitation in your servers configuration, or network configuration. You can try to change this by setting the 'chunk size' preference in ModuleManager to something like 64 (kilobytes)... this will make sure that the file is transferred in multiple 'chunks'.

Because the system literally gathers the md5sum from the file... then sends it.... then sends the file.

Chuck size, baby!!! That's it!

Yes, chunk size!

256K = Check-sum error
64K = No error

...using Module manager, for the module I just tested on.

Is just a fixed number in the Module manager good enough? Is there really any advantage for the users to change this?