Modules that only have XML files.

[tswpn]

I think that every mod should have a .tar.gz or zip file instead of just a xml file like some have, because for some reason I can't install mods from xml files, so it would be helpful if every mod had to have a .zip or .tar.gz file as well as an xml file.

[tsw]

I agree to some point, its up to module devs to release those files as they like. but I really like tar.gz better (I like shell better than X also

what problems do you have with installing .xml modules?

[tswpn]

Look at this post by me (same problem with 1.0 stable and same type of error with all modules installed via xml) to see my problem.

[calguy1000]

With the 1.0 series XML distribution is the preferred method, as it prevents many problems with ftp clients, permissions, and things like that, and also with installing and incompatible module.  And believe me we encounter ALL of those problems.

The XML method helps solve this problem.

[tswpn]

With the 1.0 series XML distribution is the preferred method, as it prevents many problems with ftp clients, permissions, and things like that, and also with installing and incompatible module.   And believe me we encounter ALL of those problems.

The XML method helps solve this problem.

But I dosn't always solve the problem, as I have pointed out!

[Piratos]

I am not a friend of this xml technic with cmsms.
some writers using the source as a example and with xml i can see only the encrypted shit.

and  the file is 4 ..5 times greater as a zip.

Other opensource systems has only zip or gz and can do that all.

------------------------
So tell me why there is no xml file shown with the modulemanager and 1.0.

[cyberman]

Other opensource systems has only zip or gz and can do that all.

Think too it would be better to merge xml and zip to module.xml.gz for ModuleManager.

[calguy1000]

I am not a friend of this xml technic with cmsms.
some writers using the source as a example and with xml i can see only the encrypted shit.

and  the file is 4 ..5 times greater as a zip.

Other opensource systems has only zip or gz and can do that all.

Most web servers, and browsers enable inline compression using gzip, so having a blah.xml.gz wouldn't buy much except reduce some disk space on the module repository side.

and the xml file only has encoded the source, it is decoded and stored as regular php files once it's installed, and the xml file can go away.  Then you can look at the source all you want for learning how to do things.

------------------------
So tell me why there is no xml file shown with the modulemanager and 1.0.

I'm not sure, check your logs, and view the source of the page for any errors.  If there's anything to be fixed, I'd like to get it done as soon as possible.

[mahjong]

So tell me why there is no xml file shown with the modulemanager and 1.0.

The Module Manager takes too much time to download the list of XML modules. If the user has a slightly slow connexion, the script times out, and the error message gets hidden under the tab bottom because of the javascript.

Code: Select all

Fatal error: Maximum execution time of 60 seconds exceeded in \modules\nuSOAP\classes\nusoap.php on line 2650

[calguy1000]

okay, there are some things I can do down the road to help with that, but unfortunately not much....esp if you can't override the max execution time, etc. it'll always be a problem, especially as the list of modules grows.

There is always the old way of downloading the xml files directly from the forge, and then uploading them in the modules page.

[Piratos]

Maximum execution time of 60 seconds

I have not this problem.

The MM works without any errormessage some times and at the end nothing is shown.

[nonty]

Those of us that runs in a hosted environment where the provider will not turn on suEXEC in the apache installation have serious problems with the XML files.

I use the permissions 2777 for the 5 directories that needs public write access cmsms including the modules directory, but that only means that the new files and directories will still be owned by httpd (which appache in my case). This makes it rather difficult to manage the installed modules afterwards. E.g. the FeedbackForm module has a directory (correctly named output) that can get the output from forms... but with umask=012 this directory is not writable and further I cannot make it writable short of writing and executing a small .php file...

[The very same problem is seen in the image manager and the file manager.]

We need a solid solution to "the create new file" process before the XML files are the only distribution media.

[Piratos]

stored as regular php files once it's installed

i know that but i will not install all  the modules only to show the source.

[calguy1000]

well then you still have choices, you can go to the forge and either download the daily tarballs (though I'm not sure if they're working or not), or check out the modules from svn, or you can even browse them from the viewcvs in the forge.  there's still alot of choices just to 'look at the source'

[cyberman]

either download the daily tarballs (though I'm not sure if they're working or not),

Does not work  ... tried often.