Submitted by singhdd on Mon, 01/09/2017 - 10:53
HI, I added PHP 7.1.0 to my Ubuntu 14.04 installation. It works fine otherwise but the user's are not able to change PHP configuration of 7.1.0. They can change configuration on other PHP versions. You can check that it is working fine on the PHP info page at https://thedemo.cf/infophp.php
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 01/09/2017 - 20:56 Comment #1
Does it help if you login as
root
and then click on System Settings -> Re-Check Configuration?Then log back in as the user, and see if the link works?
Submitted by singhdd on Tue, 01/10/2017 - 01:36 Comment #2
No that doesnt help. I had already done this before testing it first time even. I did it again but it didn't change a thing. Also restarting webmin doesnt help. The php.ini is owned by the user.
root@serv:/home/thedemo/etc# ls -al
total 28
drwxr-xr-x 6 thedemo thedemo 4096 Jan 9 22:14 .
drwxr-x--- 12 thedemo thedemo 4096 Jan 9 22:17 ..
-rwxr-xr-x 1 thedemo thedemo 107 Dec 25 11:49 git.basic.passwd
drwxr-xr-x 2 thedemo thedemo 4096 Dec 25 11:49 php5
drwxr-xr-x 2 thedemo thedemo 4096 Dec 25 11:49 php5.6
drwxr-xr-x 2 thedemo thedemo 4096 Dec 25 11:49 php7.0
drwxr-xr-x 2 thedemo thedemo 4096 Jan 9 22:14 php7.1
lrwxrwxrwx 1 thedemo thedemo 14 Jan 9 22:14 php.ini -> php7.1/php.ini
root@serv:/home/thedemo/etc# cd php7.1
root@serv:/home/thedemo/etc/php7.1# ls -al
total 80
drwxr-xr-x 2 thedemo thedemo 4096 Jan 9 22:14 .
drwxr-xr-x 6 thedemo thedemo 4096 Jan 9 22:14 ..
-rwxr-xr-x 1 thedemo thedemo 71448 Jan 9 22:14 php.ini
root@serv:/home/thedemo/etc/php7.1#
Submitted by JamieCameron on Tue, 01/10/2017 - 14:31 Comment #3
What if you click on Edit Virtual Server for this domain (as root), and then just save it with no changes?
Submitted by singhdd on Wed, 01/11/2017 - 10:49 Comment #4
Yes, this is working fine. Tested with 2 other accounts as well. Saving in Edit Virtual Server with no change fixes the Not allowed error
Submitted by JamieCameron on Wed, 01/11/2017 - 14:52 Comment #5
Ok, the next release of Virtualmin will fix this properly..
Submitted by JamieCameron on Wed, 01/11/2017 - 14:52 Comment #6
Submitted by utweb-systems on Wed, 09/13/2017 - 09:34 Comment #7
Howdy folks,
which version of virtualmin was this for? I believe we may be seeing the same problem and are currently using v5.07.
-victor
Submitted by JamieCameron on Thu, 09/14/2017 - 00:43 Comment #8
We are on the 6.00 release now, so I'd recommend upgrading.