PHP 5 Configuration link

I've been fighting a problem with some php code and have not been unsuccessful at finding a resolution to the problem. So I asked a friend of mine to look at the issue and he asked me to turn on php debug and after some discussing we found out that I don't have some of the options that he has on his server. The link that I'm missing is under services and PHP 5 Configuration. Do you have any ideas on what I could be missing? They are both on FreeBSD OS and have Virtualmin 3.703 running on them. I've attached a couple of screen shots of the two servers waynecrop.jpg has the link and mycrop.jpg does not.

Thank you for any help!

Status: 
Closed (fixed)

Comments

Does the domain in mycrop.jpg have the PHP execution mode set to fcgid or cgi , at Server Configuration -> Website Options? Only in these modes will per-domain PHP configs exist, and be editable at Services -> PHP 5 Configuration.

Otherwise, you need to edit the global PHP config, which will probably be at /usr/local/etc/php.ini

I have tried it on both cgi and fcgid. Neither seems to give me the options.

Ok .. are you logged in as root, or as the domain owner?

Also, does the etc/php5/php.ini file existing under the virtual server's home directory?

I am logged in as root.

I looked in the home directory and have a etc directory and inside of their, there is a link to php.ini -> php5/php.ini.

Thanks!

Does the php5/php.ini file exist though?

Also, does upgrading to Virtualmin 3.72 (the latest release) help?

I ran the updates on the server now running 3.72 Pro still no link.

But looking at the php5/php.ini file I don't believe the file exists.

Thanks!

That's a bug .. so the etc/php.ini link actually points to a file that doesn't exist?

If so, you should copy your system's global php.ini file (maybe at /usr/local/etc/php.ini) to etc/php5/php.ini , and make it owned by the domain owner.

That is what the problem was. I put the php.ini file in the domains directory and changed the owner and now I have the link.

Thanks!

Cool .. perhaps it was somehow deleted by mistake.

Automatically closed -- issue fixed for 2 weeks with no activity.