After a period on inactivity I have come back to learn Web Serving and Web Site development. I downloaded and configured the most recent version of UniServer. The first couple of times I was able to start and stop both Apache and MySQL. After some configuration changes like enabling password requirement with cookie method for phpmyadmin, MySQL does not stop and when I check my running processes I notice that mysqld-opt.exe has continued to run. I'm having to kill/stop this manually to restart all (Apache & MySQL). Is there something wrong, please help.

 

Running Uniserver on Windows XP SP3

Browser - Firefox 3.6.12

Running US 5.6.15-Nano

Running Z-Controller

 

Z-Controller 1 - Beta 1.2

Uniform Server version: 5.6.15-Nano

WinBinder version: 0.46.191

WinBinder PHP version: 5.3.3

 

Thanks very much.

Uniform Server is an integrated package allowing all main components to work in harmony. Reconfiguring phpmyadmin’s authentication method other than “config “ breaks the control architecture.

 

Enabling cookie authentication method prevents the MySQL server being correctly shut down hence the issue you have experienced.

 

All the best

Ric

Uniform Server is an integrated package allowing all main components to work in harmony. Reconfiguring phpmyadmin’s authentication method other than “config “ breaks the control architecture.

 

Enabling cookie authentication method prevents the MySQL server being correctly shut down hence the issue you have experienced.

 

All the best

Ric

 

Thanks for the quick response. It is still unexplained as to why it worked in the previous version of UniServer, and not this updated release. I think something in the code is structured incorrectly when I put in the "cookie" authentication method. Not being a programmer I'm extremely challenged with it. Hope the developers of UniServer take a look at this. Thanks again for your time.

 

PS: Is there an alternate? I definitely don't want to use the config method. How about the "http" method? Will this resolve the issue?

I'm afraid that, at least the default behaviour in the treatment of "cookie" has changed in PHP 5.3, such that it may break some applications "worked in the previous version of" PHP (to be more specific, not due to the big UniServer ensemble) ...

 

Alternative would depends upon your real target, e.g., what kind of result would be expected ...

 

Thanks for the quick response. It is still unexplained as to why it worked in the previous version of UniServer, and not this updated release. I think something in the code is structured incorrectly when I put in the "cookie" authentication method. Not being a programmer I'm extremely challenged with it. Hope the developers of UniServer take a look at this. Thanks again for your time.

 

PS: Is there an alternate? I definitely don't want to use the config method. How about the "http" method? Will this resolve the issue?