Im not too sure about that, It could break websites, take wordpress for example if you have some custom mods installed forcing your users on the server could break their websites.

Try and explaing to them you forced updates on their website. I bet that would lose some providers business.

Sure but if you can have select box for every one of the sites ?

so if you want to update 20 sites you can select only 20.

i have 300 sites with joomla 1.5 now is 1.5.25 all our sites is 1.5.24 and we will updated it to 1.5.25 now i can go for every site to do the update but i want a mass button for all this or select all sites that i want to update with the latest version.

We are working on this.
There are many concerns with this that need to be addressed. It is a little complicated as it can break sites as well.
Hence we are taking into account every information we get.
But we are making this as we speak.

-----------------------For immediate support please email us at our Support email address. PMs sent to any Softaculous Team member or posting in the forums is not the official way to get support.

Sir we are working on it, we are redesigning the architecture of Softaculous to implement this feature.
It is going to take some time because we have many scripts. Once the architecture is ready we will be able to implement this feature.

It's possible that you are being overcautious.
Could you please explain how doing a series of updates in a loop would be different from a user interactively clicking the buttons, and visiting the update URL?

Also, consider that a decent host offers regular backups, and really good hosts have something like R1Soft CDP, which allows point and click rollback. For Joomla, there is also an extension called Akeeba Backup which packages the files and database.

Certainly, in your license, you have no legal liability? If you pop up a warning when the feature is enabled, and pop up a warning any time it is attempted to be used, that should be sufficient. Indeed, you could decline to run or queue any automated version of an update that had not been run manually in the last 60 minutes....meaning... the WHM user is reponsible to run 1 update, verify the results, and only THEN, queue the other updates.

This doesn't have to be a tool that our grandmothers could use, it's a tool for competent systems administrators.

Few scripts require to be visited after to upgrade the database and if the database is not upgraded it could break the site.
We will discuss the above points with our Development team and add this feature soon.