-
If you think you have programming skills or influence in leading the UNA team, I suggest you do something more useful instead. These problems are not only about me, you need to do a little cleaning in the UNA script.
Insert a version control in the UNA installation script.
Enter a version check algorithm for each module in the market. with a tick: Compatible module for UNA X.X.X cores. verified by UNA team. Or unverified and then everyone assumes the risk of checking on their own test server.
Each programmer should have the possibility to add different versions for his module for diferent version of UNA core.
Introduce an installation log generator in the core, so instead of asking for the root password on a client server, you only ask for the installation logs.
-
https://una.io/view-product/dolphin-to-una-migration
This module is not even on the market, it is on github and is included in the latest version of UNA, .13.0.0-RC
it does not say anywhere that it is not functional with UNA, but it is included in it, if it doesn't work with UNA 13 why is it included in it? Where is your logic and where is the version control?
When a module is not tested, why is it included in the master version of UNA? I would be curious to understand what logic the UNA team is guided by, I don't see any yet. It was installed without any problem and then where is the control version? Why didn't it prevent me from installing if it is not compatible with this version?
https://github.com/unaio/una/tree/master/modules/boonex/dolphin_migration
-
https://una.io/view-product/spotlight-ads
where is it written for this module, for example, which core version is it compatible with? Where does it say what version the module has? Where does it say what version of php was tested is needed to run? where does it say the database version with which it was tested?I probably don't see that I'm an idiot. And I wonder, you from UNA, what planet do you come from? If a control version is not necessary, why don't these modules work as they are declared. In order for a software to work, certain conditions are necessary, these conditions must be declared. Or it doesn't matter to you, the important thing is to make money. Here in Europe things are much clearer, probably in Australia the government will not ask you what you sell, and how it works, important for them to collect some taxes. If a control version is not necessary to be declared, why don't these modules work as they are declared. In order for a software to work, certain conditions are necessary, these conditions must be declared from the beginning. Or it doesn't matter to you, the important thing is to make money. Here in Europe things are much clearer, probably in Australia the government won't ask you what you sell, and how it works, important for them to collect some taxes. Is that your company too?
-
I don't use cpanel, it's just a normal cloud server, I only work in ssh. I don't see the point of cpanel. I don't like complicated and non-functional things. cpanel is slow, and can't do everything you need, it's good for those who don't have experience in server administration and love buttons, but that comes with too many limits. the last time I used cpanel was about 10 years ago
Comment to Where have the photo albums gone?