
marcovtwout
Member-
Content Count
9 -
Joined
-
Last visited
-
marcovtwout started following Lovebaby19
-
Lovebaby19 started following marcovtwout
-
The solution that I used here (http://forum.uniformserver.com/index.php?showtopic=3234&do=findComment&comment=11936) still works fine, currently running on ~6 developer setups.
-
I took an educated guess and performed the following steps upgrading PHP 7.1 to the latest patch release: - Downloaded latest zip VC14 x86 Thread Safe from http://windows.php.net/download#php-7.1. Note that the extensions directory is named "ext" instead of "extensions" - Merged changes in PHP ini config files (mostly paths) Are there any official instructions on how to update the PHP-module? In case I missed anything.
-
marcovtwout started following UniController.exe: Allow empty password for mysql root user and New releases stalled?
-
It seems this project is becoming abandoned, too bad since UniServer was the only WAMP-package that was consistently up to date.. :/
-
I see that there are no incremental PHP releases for Uniserver in the last 2-3 months, when are they expected? (PHP is on 7.1.3 while Uniserver is still on 7.1.1)
-
Stoppling MySQL: Unable to perform clean shut-down. Kill process
marcovtwout replied to marcovtwout's topic in MySQL
Does anyone read these bug reports? Am I reporting in the right place? -
Stoppling MySQL: Unable to perform clean shut-down. Kill process
marcovtwout posted a topic in MySQL
Using latest UniServer Zero XIII. In home/us_config/us_config.ini I use another data dir: [MYSQL] datadir=S:/data/mysqlWhen I open UniController.exe and click "Stop MySQL", I get the following message in a popup: "Unable to perform clean shut-down. Kill process". -
I want to use UniformServer as a development environment. Securing mysql-access with a password for the root user is not an issue here. So I configured the root user to have an empty password. Every time I start UniController.exe, it prompts me to set a mysql root password, and does not allow an empty password. I don't understand why the UI application must enforce this. Can this behavior be changed?