Ah, sorry. I thought the reference was to the admin control panel.

Mamba I noticed you have completely disregarded my last question so I will ask again as it is very relevant to us users....

Please clarify what xoops means when they say a module is "stable/compatible." Are we to understand that is means some functions in the module will work and some may not; is this why such modules are still being listed in your newly updated compatible/stable module list?

Right now there are some mods I want to try and I am confused as to what is what; there are some updated versions of my mods on the Blue Move page, can I use those; do they work 100% with xoops 2.4.4????

Classifieds 2.5
Contact 1.7
Galeria 1.2.7
Weblog 1.41
Mytabs 2.2
Xnews 1.68

for the cpanel prompts, godaddy has a hosting panel and when I get there it will tell me that my applications have new updates available for download. Every time I call for tech support they always tell me that I must first update my xoops first becasue the update probably addresses some of the issues I am having; most of the time the update does however then as already stated another mod or two go out of whack. I have also been instructed in the past from users on this site that I should update so that my mod would work (whatever mod was giving trouble).

Hope that clarifies things; to update or not to update that is the question...

Quote:

Depends on the developer of the module, but I believe any of the "blue move" modules should work with 2.4.4+ short of the developer doing something incompatible by mistake. That is the point of "the blue move". And will rely on the developers knowledge and experience.

NOTHING in life is 100% so you are taking a chance no matter what you do. This is where having a test server is a big thing. You SHOULD be able to setup something such as XAMP on your home computer and use that as a test server if you don't have another computer available.

You should ALWAYS test new software off site so you can make sure they work before you put them on a production server. Even adding a Theme can cause issues that you don't realize until you test it out. And this is not a Xoops thing. This is a generic web thing and is a good practice no matter what you do with the net.

If a module says it is compatible it generally means it works as you would expect on the "compatible" version as it does on the original. Same functions, probably same bugs etc. Just because it is compatible doesn't mean it is stable.

Stable means that there are no known bugs that prevents all the modules functions from working.

If a module is Alpha expect there are A LOT of bugs in it and the end product could be very different. Do NOT use on a production server.

Beta means it has been tested and hopefully works and most functions are done but needs further testing and "tweaking".

RC or Release Candidate means there are no known bugs and is released as a final test to make sure before it can be assumed to be totally working.

Final means as far as the developer is concerned that version is done with NO bugs and NO issues.

Generally a module or program will go to Final before they work on the next version adding new features etc..

Hope that clears that up a little bit...

Rodney

Hey Rodney,
That is perfect!!!!! I did not know about the different stages (Alpha, beta etc). I have seen some download pages with statements that the product still needed testing so those I don't use.

I don't know if this is written anywhere on the site and I missed it but if it is not could you please post so others know; not everyone who uses xoops or other cms are coders or familiar with the jargon.

Thank you so much

Quote:
It's a standard release cycle for software programs

I have never released a program and know nothing about that; good to know.

@BeautyBrains

You wrote

Quote:

Maybe I didn't understand but my module Classifieds 2.5 will work with your version of Xoops. Is it on the Blue Move page? Don't see why if it is. I thought that was for modules that were abandoned by their developer, and no longer work. Unfortunately I don't use those other modules so I can't help you there, but Classifieds should work perfectly and if you do find any errors I would fix them A.S.A.P

Hope this helps a little.

I would like to add my 2 cents to the original point of this thread. I have been watching this thread since it was started and I really think BeautyBrains has made a great observation. There were to many changes over to long of a period of time. I like to keep my modules working without errors for the new versions of Xoops, but ever since about version 2.3 I have had to change parts of my modules for every single version that Xoops has put out. I think that is ridiculous. It seems like I have been non-stop updating my modules for years now, I can't wait until all this Major updating is over.
I could use the break.
I would think that maybe thats why so many modules don't work anymore, and why this Blue Move is necessary (and also a great idea). Maybe some developers got tired of all these changes over so long of a period of time. After all, Module developers do this out of their spare time and if they feel their time is being wasted, they may stop, leaving a bunch of modules that don't work anymore.

Xoops to me is a great CMS and I will always use it, and probably always develop my modules, but I would assume that most developers are not as stuck on Xoops as me and may not wait until these major updates are finished.
I guess I am just saying, I see what BeautyBrains is saying here and I do agree.
I just hope the end is almost near.


Thanks,

John

I too think the Blue Move initiative is promising, but as zyspec points out in this post, there is a desperate need for the core team to create some developer-orientated release notes for each version of Xoops, up to and including the latest one.

Deprecated methods and their replacements would be obvious inclusions, but it is equally important to reveal any other changes that might mean PHP code that worked perfectly well in the previous version would no longer be valid.

I know this might seem a bit kindergarten to experienced Xoops coders, but if the core team want to encourage more people to take up the Blue Move challenge, they can't carry on expecting novice developers to just 'guess' at what has changed.

John there are many people watching this post and it very ufortunate that I was given a "politically correct" response; I still don't know what xoops personal journey has to do with anything I expressed; consumers don't care if your company is bouncing back or going through hard times; they just want to know that the product you provide works; period!

I asked Mamba earlier, " Now in terms of helping to update the mod list, by compatible what do you mean becasue if you are on the letter L, how do you explain that in CBB the welcome forum page does not work? I needed that feature! I left xforum because CBB was supposed to be compatible... For me compatible means every single function in module works with whatever version of xoops I am referencing; nothing less."

Mamba still has not responded to this question; Rodney's response was awesome for additional information and will be used by me going forward however it did not answer the question that I originally asked, "why does the corrected list contain errors?"

... and as you have now pointed out your mod is on a list that is should not be on...

xoops you may not realize it but you are taking two steps forward and ten steps back at every turn; you are doing a whole lot of listening but you are not HEARING what is being asked of you from your membership / users; if you do not hear what is being asked then you can not EFFICIENTLY respond to their needs...