When will Xampp be fixed?

[musicmaster]

When I used Xampp with PHP 5 it was rock solid. As soon as I went to the PHP 7 versions it became unstable. Every Windows update is nowadays a serious risk factor that can leave my database bricked - with no repair option working.

There must be a logical explanation. There must be a way to fix this.

But nothing is happening.

[musicmaster]

The sloppy way this is done is visible when you look for my.ini. There are two copies of my.ini. One is in the /mysql/bin directory. The other in the /mysql/data directory. The first one is filled with settings while the second one is empty. Yet it looks like the script looks at the second one.

Not to mention the splendid idea to assign administrator rights to your Xampp directory. With as a result that every time you exit xampp-control.exe you get an impossible to leave error because the software cannot write to xampp-control.ini.

[Nobbie]

There must be a logical explanation. There must be a way to fix this.

Actually - there IS an explanation. And it has been told many, many, many times. In this forum.
And the fix has been told also many, many, many times. Also in this forum.

But nothing is happening.

That's not quite right. Actually, you are too lazy to find or to read the fixes given here.

Before you fail again and again in finding the fix: Simply run MySQL(MariaDB) as "service" (a simple little cross in the correspondig option from the Xampp Controldialog in front of MySQL). The problem is, that if you do not run MySQL as a service, the server is simply shotdown when you end MySQL. If you run it as a Windows service, the Windows Manager starts and ends MySQL properly.

That has been explained a million of times or so. I have no logical explanation, why you cannot find it.

[musicmaster]

That has been explained a million of times or so. I have no logical explanation, why you cannot find it.

The logical solution would be to make it the default option in xampp-control.exe.

You cannot assume that everyone reads the thousands of posts in the forum.

Dirty shutdown is not the only source of problems. There are more.

Do not fix what isn't broken. It worked with PHP 5. So make that kind of action the default when there are no administrator rights.

Given the wide use of Xampp I estimate that hundreds of thousands of hours have been lost due to the stubbornness of the Xampp maintainers.

[Altrea]

windows services are not the default option because
- windows services are drive letter and sometimes user specific
- xampp philosophy is to set no (or at least as few as possible) system variables/registry keys.

[Nobbie]

Given the wide use of Xampp I estimate that hundreds of thousands of hours have been lost due to the stubbornness of the Xampp maintainers.

And why do you use Xampp? If its so bad and Xampp developers are "stubborn", simply dont use it.
Xampp is only for the little guy who has no idea about servers. If you want to run an Apache server professionally, you choose the wrong tool with Xampp. Xampp is not meant for professional servers.

Xampp can also not replace a trained administrator who takes care of the server. A good administrator neither needs Xampp nor the Xampp Controlcenter. This is only for dorks who otherwise only play games on the computer. System administrators operate Apache and MySQL with the designated interfaces. Actually, you are "stubborn" using Xampp. Dont use it.