A project to test-install, provide descriptions of, and list all modules

replytomk3 · **Posted:** Sun Nov 15, 2009 8:05 pm

I have heard about this for a long time, so now it is time to do something.

I am in the process of:
1) Make a list of all modules like http://mkrd.info/software-discussions/cms-made-simple/list-of-cmsms-modules.html
2) Test-install all modules on 1.6.6
3) Contact authors of modules without descriptions for them to provide descriptions (I will also try to grab it from help/about)
4) Look for any installation, compatibility, or usability problems
5) Make either a wiki or main cmsms site page listing all modules (this will also help to showcase cmsms capabilities to new site visitors)

If anyone has any suggestions or wants to help raise your hand.

Peciura · **Posted:** Sun Nov 15, 2009 8:19 pm

PM me list of 20 modules i should start with. I will report you as soon as i have finished with each of them.

replytomk3 · **Posted:** Sun Nov 15, 2009 8:29 pm

You can choose whatever modules you want to do, but I need to figure out a way for you to upload the results. This table does not really work in a cmsms page (too wide and cut off to letter g due to size), and I don't know if wiki will handle the table.

What do you think?

Peciura · **Posted:** Sun Nov 15, 2009 9:02 pm

To start we need simple table with module name, author email, module description present or not, any file, link to forge,work/ doesn't work, last release date and may be some comments. looks like custom content and form builder should be enough.

Could you place such form in your site and PM me with login data ? If not i will do that tomorrow on my test site.

replytomk3 · **Posted:** Sun Nov 15, 2009 9:31 pm

I will try, but I have not done that before. Maybe I will just go on testing now and adding it to the table.

Jeff · **Posted:** Sun Nov 15, 2009 9:48 pm

One suggestion is to use google docs to share the spreadsheet file.

tyman00 · **Posted:** Sun Nov 15, 2009 9:50 pm

I think you are taking the right steps. But if I may make a suggestion (which unfortunately requires more work) we may need to also address more than just the CMSMS version. Ideally it should be CMSMS version, PHP Versions, Platforms, Database types (maybe even versions).

Anything is better than nothing so please don't get me wrong, I personally can appreciate the efforts you are putting forth.

replytomk3 · **Posted:** Sun Nov 15, 2009 9:55 pm

tyman00 wrote:

But if I may make a suggestion (which unfortunately requires more work) we may need to also address more than just the CMSMS version. Ideally it should be CMSMS version, PHP Versions, Platforms, Database types (maybe even versions).

Something that can be done when the page will be editable by others, but all modules already tested on latest distribution.

replytomk3 · **Posted:** Sun Nov 15, 2009 9:55 pm

ajprog wrote:

One suggestion is to use google docs to share the spreadsheet file.

will take a look. now, I am frantically going thru all modules.

replytomk3 · **Posted:** Sun Nov 15, 2009 9:58 pm

Peciura wrote:

author email, any file, link to forge,work/ doesn't work

I will include author name and email only for modules without description or that appear to be abandoned. We can't make a list of emails public, of course.

tyman00 · **Posted:** Sun Nov 15, 2009 9:59 pm

replytomk3 wrote:

tyman00 wrote:

But if I may make a suggestion (which unfortunately requires more work) we may need to also address more than just the CMSMS version. Ideally it should be CMSMS version, PHP Versions, Platforms, Database types (maybe even versions).

Something that can be done when the page will be editable by others, but all modules already tested on latest distribution.

Cool. If possible maybe add your Platform Information, Webserver information (Apache/IIS, version), PHP Version, Database Software/Version. That way it will reduce the "What are you running, because it doesn't work for me?" questions 8)

Edit: I'd probably just put it at the top of the page till you start getting info from other people.

replytomk3 · **Posted:** Sun Nov 15, 2009 10:13 pm

tyman00 wrote:

replytomk3 wrote:

tyman00 wrote:

But if I may make a suggestion (which unfortunately requires more work) we may need to also address more than just the CMSMS version. Ideally it should be CMSMS version, PHP Versions, Platforms, Database types (maybe even versions).

Something that can be done when the page will be editable by others, but all modules already tested on latest distribution.

Cool. If possible maybe add your Platform Information, Webserver information (Apache/IIS, version), PHP Version, Database Software/Version. That way it will reduce the "What are you running, because it doesn't work for me?" questions 8)

Edit: I'd probably just put it at the top of the page till you start getting info from other people.

First pass is on xampp under xp. Second pass maybe 1and1 hosting Linux infong 2.4, PHP 5.2.11, MySQL 4.0.27, Apache.

What is infong 2.4?

replytomk3 · **Posted:** Sun Nov 15, 2009 10:42 pm

Letters A-E done, list updated on my site.

Peciura · **Posted:** Sun Nov 15, 2009 11:01 pm

Quote:

I will try, but I have not done that before. Maybe I will just go on testing now and adding it to the table.

OK i will create FB form. We will be able to improve it at any time, hide some data from bots, and later to transform data to any form we need.

Looking forward to hearing from aln_cms regarding Module Ratings and Appraisals - Opinions Sought

gnight

Sonya · **Posted:** Mon Nov 16, 2009 7:13 am

Why don't you grab the list of the modules with SOAP as Module Manager does it? Would it not be much easier as making the list manually? With SOAP the list can be kept up to date when new release of the module is published and your test becomes outdated.

If you need help, I am very experienced with SOAP protocol and can assist.

A project to test-install, provide descriptions of, and list all modules [SOLVED]

Who is online