4
Thanks DJ, I'll look into them.
You're absolutely right - we definitely don't want to reinvent the wheel. That's exactly why I've asked here for advise and why I am looking for the best practices, so I can re-use it in the modules I am working on right now.
The issue is that we have a lot of modules that are, as you said, "old"
![](https://xoops.org/uploads/smil3dbd4d6422f04.gif)
Things changed, improved, and there are newer modules, but I don't have the time to evaluate all of them, so I was curious if somebody did it already and can make recommendation on what is the best way to do it. Basically, what is the
current best practice?
And it could be that the method in an "old" module is still the best
![](https://xoops.org/uploads/smil3dbd4d6422f04.gif)
The basic issue is that there are many typical "functions" that are being used in modules, for example:
- set preferences at installation
- upload a file
- delete file
- create a menu tabs
etc.
so for people who are trying to update/refresh their "old" modules for 2.5.0, it might be useful to have a catalog of "best practices" on how to provide a specific function. The was the ideas behind "Blue move" and sharing "best practices" - see the
example here