Posted on: 2012/4/11 9:26
Re: Fmcontent new version : Test and report bugs
I write about 20000 codes for news module and I hoped it be good option for next version. I clean to many codes and write codes in corect way and this module can be Coordinator whit xoops 2.6 easy. But users just say : " WE have other news module ! rename it !!!! "
Voltan, you've been one of the best supporters of XOOPS, and we've been working well together on several modules.
But as DCrussader said, we cannot have several different modules with the same name. It creates confusion, as users won't know which one they are using.
Let's assume for a second that somebody downloads your module, copies the files over his "news" module, and then updates it. What happens then? Will the module work? If not, who will explain to him that he had the wrong module? And what happens if his data becomes corrupted? What happens if his Website's "News" won't work correctly anymore and he starts losing customers/visitors? Who will clean up his data? Will he be still happy with XOOPS?
Having the same name for two different modules that are not compatible, is confusing for the users, and simply too dangerous, if there is a risk that they can corrupt their XOOPS installation and/or data in the database.
Just think about the situation if authors of ALL these modules would call them News:
- Mastgo Publish
When Nicolas started work on his "fmContent" module, it was originally called "Content". And I've asked him to rename to something else, because we've already had a "Content" module developed by Kerkyra. And we've came up with the prefix "fm" (which stands for "ForMuss") for his modules, and we've got fmContent. This was similar to the "wf" prefix for modules from Catzwolf - a clear distinction of the name and the origin of the module.
"Publisher" by Trabis is a good example how it could be done, if the user wants to have a module called "News", but doesn't want to mess with URL rewriting in .htaccess . Publisher can be cloned to whatever name we want. So I could have "SmartSection", import the data from it into Publisher, then delete "SmartSection", and clone Publisher into SmartSection again, so all my links from other Websites pointing to "www.mysite.com/modules/smartsection/item.php?itemid=23"
; are working correctly , and the data is also correctly imported.
So if you create a "vNews" or "voltanNews" module, and it can be cloned/renamed into "News" for new users, or it can import existing News content, and then cloned/renamed into "News", then everybody would be happy.
Voltan, I did look into your module, and it has some nice features, and you put a lot of work into it. Since the current News module from Hervet is a little bit outdated, if you could make your module a "drop-in plug & play
" module, which can be copied over current "News" module, and updated, and it will work properly, then we could make it the "official" replacement for "News", and tell people to use it going forward.
Could you make it a "drop-in plug & play
But I don't think we can tell our current users: "We have a new module called News, but it's incompatible with your existing News module, and it won't work with your data, so stay away from it." Because the question from them will be: "So why are you calling it then News"?
whit this development Strategy XOOPS have dark Future. I hope we come to corect way
I really don't know how the issue of "module naming" relates to "XOOPS Future"? Clearly, I sense some frustration from you
So what future would you like to see for XOOPS as it relates to your "News" module? What would make you feel more comfortable? Please tell us more, so at least I can understand better what you have in mind.