#343 XOOPS REPOSITORY MODULE for CORE and MODULE MANAGEMENT

XOOPS_2.x
open
nobody
Core (214)
7
2012-09-25
2010-02-12
MrGold
No

I cannot even open the download page on sourceforge. People in the third world may not be able to see it. This page is just too long and has just too much of information. Plus it has a lot of old garbage.

There are many developers who offer updating their module via ftp.

Following could be of a great help to the community:

1) ONE PHP FILE AS A START

There could be just one php script in any directory and generates a page asking the user local ftp information.

Executing this script, it will connect ftp.xoops.org, download the latest stable release and begin the installation.

The xoops installer is stable and could be used. My suggestion only requires a plattform on which the current installer could be executed.

2) XOOPS REPOSITORY MODULE

A XOOPS REPOSITORY MODULE needs to be part of the core. From the administration, a page could be generated that checks modules installed in xoops and the ones available for that version of xoops.

The xoops installation could connect to a server, identify the version and thereafter download respective module. It could offer offer a modules page that are compatible to the installed version of xoops and download from the module repository or if there is an update available, it will update.

ADVANTAGE:

Not much to discuss.

This will change the image of xoops, which at the moment bears a very nasty impression regarding the module management. It will help each and every user to save their time to hunt for modules and see which version matches the installation and if it will.

Instead of adding more features to xoops, this needs to be done at the first and foremost priority.

To remind:

Before 3 years, I did place a message as feature reqest. This was assigned to phppp. Since thenm, there is not much done in this regards, although some points made in this request has been implemented. This request is here:

https://sourceforge.net/tracker/index.php?func=detail&aid=1432020&group_id=41586&atid=430843

I hope that todays feature request will be implemented before the next 3 years.

Discussion

  • MrGold
    MrGold
    2010-02-12

    Forgot to mention: With the dramatic change of and upwards the version 2.3+, it has become dificult for every user to identify which version of a module will match with the installation.

    With the above suggestion, this problem will be solved as the module developers needs to has a tag in their xoops_version.php that will allow a detection routine of the installed and available.

    Hence if I have installed 2.4.4 xoops, then it will not download a module which does not have a 2.4.4- (minus sign)!

    This will appear for download only after the xoops_version.php contained in that module is also increased. This could only be done if the module has been tested.

    Otherwise it could appear under untested versions.

    Also, there could be a link to a module. Then it could list a module versions, etc.

    With this, one could also change the xoops versions on the fly and it will work like active xoops SVN LIVE!!!