Site Directives and Custom php.ini

I've been trying to setup a custom php.ini file for virtual hosts. There's a lot of good info about this on the web, but none of it seems to be working for me using ISPConfig 3.

I'm running ISPConfig 3.0.2.1 on Ubuntu 10.04 (RC1) with PHP 5.3.2 and Apache 2.2.14. The site is set to use suPHP 0.7.1.

First, I tried adding the following to the site directives:

Code:

suPHP_ConfigPath /var/www/fpzhosting.com/etc/

and I have a custom php.ini file in that directory. But none of the settings in that php.ini file are being applied. For example, the file clearly states:

Code:

open_basedir /var/www/fpzhosting.com/web/

But when I look at that site's phpinfo(), open_basedir is set to "none".

So I tried to look at the /etc/apache2/sites-available/fpzhosting.com.vhost file to make sure the directive I added was in fact present. It was, but it was at the bottom of the file. I don't know if this line needs to be between the same <directory> tags as the other suPHP directives, so I moved it there just to be sure and tried again. Still no joy, the custom php.ini file isn't being used.

So next I tried adding the directive to the site's root .htaccess file. Again, it didn't work. The file at /var/www/fpzhosting.com/etc/php.ini does not appear to get used at all.

 

This still doesn't work. My custom php.ini file still isn't being used.

Additionally, I notice there's a PHP open_basedir field right in the options for the site in ISPConfig, and it already has all the necessary values filled in, but phpinfo() still shows "open_basedir" as "none". What is the point of this field if it doesn't actually do anything?

I'd like to point out how incredibly frustrating ISPConfig 3 has been to work with so far... the documentation is miserable, the options in the control panel are not clear (some make no sense at all), and half the features don't appear to function as expected. I keep coming back here for help, and the help I get is usually inadequate and sometimes takes days to receive. Sometimes I get no help at all unless I practically beg. I REALLY REALLY want to give ISPConfig 3 a chance, but so far, my experience has been very discouraging. I feel like I'm wasting my time, and my server will never be up and running.

Are there paid support options for ISPConfig 3 which would give me _adequate_ support? I'm ripping my hair out trying to get things setup properly, and strongly considering changing to a paid product. If the paid support options are no better than this, then I give up.

 

"There's worst, but it's more expensive" .

 

I think (hope) that yoplait is saying that there are worse control panels that cost more.

In my experience, that is true!

IPSConfig is an excellent control panel and its free!
...and what is better, if it doesn't do something the way I want it to do it, I can change it myself.

What could be better?

 

Sorry for my english if it's not the good sentence, but mike_p has well understood what I wanted to say .
(maybe it's just a french free sentence ? ... I was thinking about "There's better, but it's less expensive....")


Free is beautiful, Ispconfig too !

 

Well obviously suPHP_ConfigPath only works for suPHP. I haven't quite reached that level of dumbness yet. But right now, for me, it's not working. Also, I clearly stated in my OP that I was using suPHP.

Also, I referred to the field directly above the "Apache Directives" text area which is labeled "PHP open_basedir" and contains a bunch of directories which all point to the web root. Why doesn't this field actually do anything? phpinfo() still shows open_basedir as "none". Nothing is working for enabling open_basedir.

Nope, not at all. That's not my complaint in the least, my apologies if I expressed myself poorly. My complaint is that the documentation for ISPConfig 3 is almost non-existent. What little documentation there is is terrible. ISPConfig 3 is so different from ISPConfig 2 that using the latter's documentation with the former is impossible. When something doesn't work as intended or expected, there's nowhere to turn for help except this forum, and apparently the only people who actively participate are the main developers. This is in stark contrast to other forums like Joomla, phpBB and others, where help can be found readily from countless contributing members who aren't necessarily developers. I would love nothing more than learn ISPConfig 3 properly and then contribute on this forum, but learning it is a very aggravating task so far.

There are billions of smokers in the world. Millions of people choose to bite their nails. Countless people think the iPad is the best thing since sliced bread. Your argument is meaningless.

Your software is not a perfect nirvana. Like all such software, it currently has bugs and is missing some key things. If it were perfect, it would never need updates and it wouldn't currently be at version 3.0.2.1.

For example, what the heck are these two fields supposed to be? They're not even labeled!!!



Sure, eventually I figured out they were the UID and GID because it's essentially the same field layout as on the FTP User screen, but this is just another example of small things that generate confusion. Another thing that needs work: there's no option (that I found) to auto-create the DNS zone when creating a new site. This was an excellent feature in ISPConfig 2 that I can't find in ISPConfig 3 anymore.

Please don't sit there and pretend that "there aren't any problems with ISPCOnfig in general".

I don't know anymore... is paid support as bad as this? Where all my concerns get thrown back in my face and blamed on me? I already get that for free, I don't need to pay for it.

 

The big problem matey is that your approach has been very rude and you tried to 'blame' ISPConfig for problems in the software that it controls.

For example there is no way that ISPConfig shoudl be held repsonsible for the 'deprecated #' warnings from PHP. That warning did not exist before version 5.3. Do you think ISPConfig should be repsonsible for replacing those comments in all the ini files that come with the other software packages?

And all your problems with localised PHP.ini: they're not down to ISPConfig yet you're having a rant about ISPCOnfig when you can't get it to work. Go to the PHP forums and have a hissy fit there instead.

If you set out to blame people, it's always going to come back in your face.

Troubleshooting at a distance requires a very careful analysis of what is going wrong: you then have to rule out any simple obvious causes. When offering support (whether free or paid) the last thing you need is having the person you're trying to help throw his toys out of his pram when you go through these steps.

You must know the famous story of the Wordperfect support line...

 

I think that you can help ispconfig to be better in using the bug tracker. If there isn't enough features, you can do a feature request... Or even, like some people here, you can develop plugins !

I have seen a member of this forum who is begining a web site about the documentation of ispconfig, all initiative are good when it is a free software !

I participate in some free forums, and, in fact, it's always "irritating" to see some people that just comes to say "it's bad, it doesn't work" in place of trying to help the thing to progress...

Free software grows well because of good will. Criticize is surely a good thing, but only when it's not done with bad feelings .

 

I don't understand why you are using ISPConfig 3 if you prefer ISPConfig 2 - there is even a howto for installing ISPConfig 2 on Lucid Lynx.

I am beginning to think that you are having a lend of us happy ISPConfig 3 users!!

 

That is incorrect. I did not blame ISPConfig for the "deprecated #" warning. I mentioned that the cron log file was filled with them, and I said the cron log was useless. Feel free to go re-read that statement in the other thread. Cron is not ISPConfig. Perhaps the developers are a little too sensitive, immediately assuming that any comment is targeted at ISPConfig when it's not. When I asked for help in that other thread (never ONCE blaming ISPConfig for my woes, and simply asking for a better understanding of why things were happening a certain way), I got a response that implied it was all my fault, it couldn't possibly be the fault of ISPConfig, and I ended up getting no help answering my questions.

However I *did* eventually blame the guide for that "deprecated #" issue, and that was incorrect on my part. The issue only happens when using a version of Ubuntu (and therefore php) that the guide was not written for, and for that I apologize.

 

Actually I did! I switched to lucid with ISPConfig 2, since there's a guide for that and the documentation is far more complete for ISPConfig 2. With any luck, I won't need to use this forum at all!

 

Ok... Finish to blame each other??? Not a good way to work well!
Where i can fix the default root document by site? (index.php, index. html, etc )? Do it by hand or available somewhere in ispconfig?

ISPConfig 3 is FREE... TEAM are hot and responsive... I'm come from Plesk... Much more feature, user friendly, etc... Same for cPanel... But VERY VERY EXPENSIVE!!! My goal is to make some cash with hosting clients... Not put money in other hand with VERY EXPENSIVE LICENCES!
So... If you dont want headhache, go with plesk, cPanel, or even with hosting company that make job for you!

IMHO

 

I need to know if it is possible to have
http://admin.mydomain.com redirect to https://mydomain.com:2087 but without :2087 in the url ? Many firewall block redirection to port other than 80 (which cause me frustration )
I work for a school that think is better to block access to learning tools

 

Thank you...
It's a nice to have too A module to make easier apache directive ( a least standard one)
Thank you for fast reply!
You make my day!

 

And i need documentation to write plugin for ISPConfig 3... I have 3-4 nice tools to add...
By the way, the tools "resync", it's should be nice to put a bouton where the resync is require or to make a feature like resync on save
And for folder in private with "protected folder user " dont work