1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

php.ini file editing...

Discussion in 'Plesk for Linux - 8.x and Older' started by ilustrate, Jul 12, 2005.

  1. ilustrate

    ilustrate Guest

    0
     
    on an oscommerce install I received this error before i even got to install. any idea how i can reach this file from plesk control panel. or how do i actually go about getting to it so that i can edit it?

    FATAL ERROR: register_globals is disabled in php.ini, please enable it!
     
  2. jamesyeeoc

    jamesyeeoc Guest

    0
     
    I believe you posted elsewhere that you used ot use Telnet but cannot on Plesk.

    It would be more secure for you to switch to using SSH in place of Telnet.

    See http://www.ssh.com for their free program version (they also have a commercial product).

    Once you SSH into the server as root, you will be able to do pico /etc/php.ini (or nano or vi).

    Although if you only need certain PHP settings on a per domain basis, you can put those php_admin_flag options into a vhost.conf or .htaccess file for just that domain which needs it.
     
  3. ilustrate

    ilustrate Guest

    0
     
    hey james, this ssh sounds good. i'm lost though. the mirrors have plenty of options for the 3.2 non commercial download but the documentation looks pretty rugged. Is this non commercial version something i can run on windows and connect with?
     
  4. jamesyeeoc

    jamesyeeoc Guest

    0
     
  5. ilustrate

    ilustrate Guest

    0
     
    thanks alot. i first downloaded the source code by accident and was totally lost. i realized i needed to install the client version. thanks alot. i really like the way you end up teaching me the proper way to do things. i'm really proud of doing things this way. i got it installed on windows and i started the program but for some reason it doesn't want to connect. do i have to connect to the root of my server? if yes how do i do this?
     
  6. ilustrate

    ilustrate Guest

    0
     
    ooops. i just noticed you said that already.
     
  7. ilustrate

    ilustrate Guest

    0
     
    what do you recommend i do. it sounds pretty good to do this on a per domain basis. i really honestly don't even know what configuration is more common.
     
  8. ilustrate

    ilustrate Guest

    0
     
    when using SSH. What should i put in Host Name? to login as root of my plesk server?
     
  9. ilustrate

    ilustrate Guest

    0
     
    i managed login via SSH and have reached the


    [root@admin root]#


    how do i proceed to find php.ini so that i can edit it?
     
  10. jamesyeeoc

    jamesyeeoc Guest

    0
     
    It's located in /etc/

    so if you use pico, nano, or vi

    pico /etc/php.ini

    or

    nano /etc/php.ini

    or

    vi /etc/php.ini

    I don't know what editor you used to use once you telnetted into a server...
     
  11. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Well, I personally like to do things on a per domain basis. So if you want to do that, you will have to create or edit the domain's vhost.conf or vhost_ssl.conf file.

    Look in
    /home/httpd/vhosts/domain.com/conf
    to see if a vhost.conf or vhost_ssl.conf file exists.

    If it does not, then use an editor (pico, nano, vi) to create one (or edit the existing).

    To turn register_globals on, and safe_mode off:

    <Directory /home/httpd/vhosts/domain.com/httpsdocs/whateverdirectory>
    php_admin_value register_globals 1
    php_admin_value safe_mode 0
    </Directory>

    where 0=Off, 1=On
    There are some cases where you would actually use the words On and Off instead of numbers, but on my current test server I have to use the numbers for it to work.

    If this is going on a non-SSL site, then put it into the vhost.conf file.

    If this is going on an SSL site, then put it into the vhost_ssl.conf file
     
Loading...