Welcome, Guest. [ Log In ]
Question   Do you support this PHP module or extension?
Search KBase


Top 5 in this Area:
1. What's the difference between PHP-CGI and PHP as an Apache module?
2. PHP Security
3. Compiling your own custom PHP
4. Can I run a phpbb forum (message board) on my site?
5. Do you support this PHP module or extension?

 
Do you support this PHP module or extension?
We support a fair number of PHP modules. Here's a list of some of them:

  • calendar
  • ctype
  • curl
  • GD (Version 2, TTF, GIF, PNG, JPG, PNG, WBMP, XMB)
  • mysql
  • overload
  • pcre
  • xml
  • zlib

  • As mentioned in this article, you can compile PHP in your user space (if you're on a plan that includes shell / CGI access) and run it as a CGI. While we don't provide support for this if you have difficulties getting it to work (ie you need to have some degree of expertise with compiling software on a *nix system and familiarity with PHP), we do have several customers who have done this successfully.

    Last updated: Jan 07, 2005.

    User Post (2004-08-31 12:19:59 by ardco)
    Here is a small script to list the available PHP functions on the server:
    http://www.cs.uofs.edu/~beidler/web_prog/PHP_MySQL/source/chapter21/list_functio ns.phps


    I don't know why the link above has a space added towards the end, but you'll get a 404 error if you don't fix/delete it.
    User Post (2003-08-20 19:59:28 by csgoadm)
    Another good way to get the PHP information for the local server is to run this command at the console:

    php -i > phpinfo.php

    Stick the created file into your web directory and link to it. This page will even show you how the configure command was structured.
    User Post (2003-07-08 21:35:51 by trooperdesigns)
    <p>Looks like installing PEAR in your home directory works well, and is painless!</p>
    <ol>
    <li>Create a directory to install PEAR: e.g. ~/php.</li>
    <li>Run "lynx -source http://go-pear.org | php" in this directory.</li>
    <li>During the installation, change the directories to match your configuration. PEAR will create directories as appropriate. Don't forget to change PEAR's bin directory to something you can write to, e.g.: ~/bin.</li>
    <li>PEAR should then download all the sources and configure itself using the directories provided above.</li>
    <li>Run "~/bin/pear config-show" to see the configuration of your new PEAR installation. Ensure these directories are writable and readable by your user and apache. Use "~/bin/pear config-set setting value" to modify these settings to your ~/php PEAR installation.</li>
    <li>Add the "~/bin/pear" binary to your path. If your shell is BASH, type "export ~/bin:$PATH". Don't forget to add this to your .bash_profile, using "echo PATH=~/bin:$PATH >> ~/.bash_profile"!</li>
    <li>Simply add "php_value include_path ".:/home/username/php"" to an htaccess file telling PHP to use your new PEAR installation.</li>
    <li>Enjoy the fruits of your labour.</li>
    </ol>
    <p>Don't miss out on the invaluable online documentation: http://pear.php.net.</p>
    <p>- ed</p>
    User Post (2003-03-31 11:49:34 by hunsvotti)
    I wrote my portal engine to rely heavily on PHP PEAR. PEAR is installed at DreamHost but for some reason include_path would always be null, even though it was set otherwise in php.ini. I discovered that the solution was to use the php_value directive in a .htaccess file. The following .htaccess makes sure that PHP can see PEAR. It also has PHP4's session management system point to one of your subdirectories rather than saving them in /tmp, which is messy and a security risk. (Note that your user_sessions dir must be chmod 777'd unless you are running php-cgi.) It also has a RewriteEngine configuration that prevents people from stealing your bandwidth by doing 'img src=http://yoursite.com/something.png'.
    <p>
    order allow,deny

    allow from all<br>
    php_value include_path ".:/usr/local/lib/php"<br>
    php_value session.save_path "/home/yourusername/user_sessions"<br>
    RewriteEngine on<br>
    RewriteCond %{HTTP_REFERER} !^http://yoursite.org.*$ [NC]<br>
    RewriteCond %{HTTP_REFERER} !^http://www.yoursite.org.*$ [NC]<br>
    RewriteRule .*\.(png|gif|jpg|jpeg|bmp)$ http://yoursite.org/no-hot-linking [R,NC]