PHP5/SQL5 Upgrades

[commando]

Originally Posted by GatorDaveC

Probably a bit more then 32 days since we are starting March 8th.

Here's what hostgator support said

Originally Posted by Milton B

Only 10 servers per day are converted so you should see the change within a week or so.

If support is correct and Dave is wrong the changes are starting immediately. It would be very irresponsible of HostGator to make such a major change without sufficient warning to test and migrate all of our system to MySQL5/PHP5. I know for a fact I have incompatible SQL as i've tested it.

Originally Posted by commando

Here's what hostgator support said

If support is correct and Dave is wrong the changes are starting immediately.

When it comes to what happens on HostGator (his) servers, DaveC is never wrong, as he's the one that signs off on the changes. *grin* There was an internal email sent about the upgrades a little while back, but a new one was just sent out today to ensure everyone is on the same page. The migration of existing servers starts March 8th. New shared servers, ones that are being put online from this point forward, are provisioned with the new php5 configuration from the start. I hope this clears things up.

[commando]

March 8th is much better, thanks.

Originally Posted by GatorDaveC

Hi Bill,
The PHP5 Handler will still exist. Each server that is being upgraded will be posted here... I guess I could make a quick script to just parse the CPanel contact e-mails and say that the server has been upgraded etc..We'll see.

At the moment we are still working on testing scripts that might have problems with the upgrade.

How do we know if that handler line is enabled for our server? I use wordpress 2.2.x on my sites, as long as I can test php5 compatibility with the ability to roll it back easily, that would be great.

[GatorDaveC]

Originally Posted by Jaycee29

I am the site developer for a client who is hosted on hostgator, and I have a couple of questions about this upgrade.

1) Will short_open_tag be turned on by default on PHP5? I have quite a few scripts I've written with <? ?> declaring the PHP code sections.

2) If 'no' to the first question, how can I turn it on in my client's account? I saw someone mention that directory-level php.ini files are allowed. Would I just create one in the account's root directory with short_open_tag = 'on'?

Thanks for all your help and good luck with the upgrades.

Of course short tags will be turned... Come on who likes using the full PHP tags when you are trying to code something quickly.

[boxcar]

Originally Posted by GatorDaveC

Yes for at least a little while,

How long is a little while?

[Elijah]

Originally Posted by kmaw

The upgrade doesn't even start until March 8. Better look elsewhere for your problem.

Oh sorry, I guess the site move from reseller to shared somehow caused problems.

[SnapDaddy]

I have an account on a semi-dedicated server. Are they scheduled for updates as well?

Thanks!

[slapshotw]

SnapDaddy,

As semi-dedicated are essentially just larger shared plans, then yes, you'll likely be upgraded.

-Matt

[SneakyWho_am_i]

Hey guys. I have some questions, and some answers. Some of the answers have already been mentioned here but I have a forum where every day ten people will show up to repeat a question you've just answered seven thousand times so there's probably no harm in some repetition here

Some of this will be pure speculation or opinion, I will try to point out which things don't have sources, but I won't cite my actual sources cause this is mostly from memory.

If you do find your answer in here, don't rush to thank me, as much of it was taken from other posts in this thread.
@HG STAFF/MODS: Some of this is bound to be utter rubbish, I won't be offended if you moderate - trim out anything you don't agree with etc, it's all good.

WAIT! FIRST IS A BIG, BIG QUESTION
I have a shared account AND a reseller account. I would like to opt out for the shared account (which always used php5 anyway) and remain opted in for the reseller account (which had kittens when I tried to run it without php4).. Can this be done? Should I put my shared details into the form and hit OK? I suspect I'm taking this out of context but it says:

If you are a reseller and you opt-out, it will put all of your accounts on the opt-out list. Please make sure you authenticate with your main reseller account.

I don't want to opt out as a reseller, I only want to opt out with the one shared account which is NOT a child of the reseller account. Scared to pull the trigger though in case I accidentally opt out for the reseller account as well.


MYSQL
Many of you are worried about the change to MySQL disabling your scripts. I'm 99.99% certain IT WON'T CHANGE ANYTHING FOR YOU. Don't quote me on that, but I think the MySQL guys allow us to still use a lot of deprecated MySQL 4 functions in v5. Many of the changes involve mysqld itself, and if you don't know what that is you don't have much cause for concern imho. I'm not hugely experienced with MySQL but I have a test box at home with v5 on it and I can't tell the difference from the application's perspective.

FANTASTICO
Hostgator are good guys, I trust that these "common scripts" they're working on are largely the Fantastico scripts which they host and to some extent support. If you want to be sure your script will work, DON'T OPT OUT.

OPTING OUT
You'll be upgraded whether you like it or not. Don't opt out unless you've tested your site and know that it needs no modification to work under php5.
You're not opting out of the upgrade (you can't!), you're only opting out of having them automatically update your scripts to fix them for the new version.
You can't opt out of the upgrade.
You're opting out of having Hostgator magically fix your scripts.

TEST SERVERS
in my humble opinion as your fellow user... You don't even need test boxes for this. Copy your database or copy and rename all your tables. Copy your filesystem into a subdomain. This is if you're really desperate guys, come on. That is your test box.
php5 has been available on my server since I signed up (last year) but php4 was always the default. I've been running php5 the whole time though with this (or something very similar) in my .htaccess file:

AddHandler application/x-httpd-php5 .php

Simple. Magic bullet. Now you can see TODAY if your scripts are compatible with what was available (probably) all along.

OPTING OUT (part 2)
If your scripts were all written by a freelancer (so Hostgator probably can't automatically upgrade them) and DON'T work under php5, don't panic. You don't even have to notice the difference when they upgrade your server. Just make sure you have this line in your .htaccess on the day they upgrade you (and before, can't hurt):

AddHandler application/x-httpd-php4 .php

It's as simple_as_that.
WARNING though, they will eventually uninstall php4 - I think you have a year on the outside. Consider this as a cheap way to buy extra time to work on upgrading your scripts. If you can't do it yourself, DON'T OPT OUT. And if you have exotic scripts you might want to consider hiring a freelancer or your nerd brother or whatever.

OPTING OUT part 3 - HOW DO I FIND THE NAME OF MY SERVER?
This will make you laugh/smile. What's your domain name? I'm going to assume that you own example.com..
... You do know your own domain name, don't you?
At a Linux, Windows, BSD or DOS terminal, try this command:

telnet example.com 25

Please, for crying out loud, put your own server name in there. You're now connected to sendmail. Don't whip out the MAIL FROMs and RCPT TOs, just read what it tells you. On the first 220 line:

220-gator277.hostgator.com ESMTP Exim 4.68 #1 Thu, 14 Feb 2008 03:31:12 -0600
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.

I'm gator277.hostgator.com
If you REALLY want to opt out (please don't), this is what you put into the form under "server name". Simple. No editing files, no visiting queer websites, easy peasy. TO be polite make sure you close the connection by typing

quit

before you go.

MORE ON .htaccess
if .htaccess is bothering you, you don't know what it's about? Google it :P Ok if you do google it, read the Apache docs, webmasterworld, w3schools probably.
Basically open your text editor (gedit, kedit, notepad, whatever) and create a file called ".htaccess" (no quotes) - yes, the whole filename is the extension, deliberately to hide it etc.
Into that, put whatever apache configuration directives you need, save it and upload it. It will then affect the directory into which you upload it, and all its subdirectories (I think?).
There's a good chance you have a .htaccess already present for your application. If so, great! Just add your code to the TOP of the existing file.

WILL PHP5 BREAK MY SCRIPTS?
Probably not. php5 is definitely safe (from memory) for at least phpbb, smf, joomla, mambo.... (but may break 3rd-party modifications/extensions - I really seriously doubt it)...
... I tried whichever versions you get through fantastico and tested each extensively (for suitability for a personal project).. I tried the latest two stable versions of Joomla!, AND 1.5 Beta (which was very cool). You should check while you have the chance, but php5 has been around for quite some time now (php6 coming soon) so unless your site is ancient, most of your scripts will probably be happier in php5 than they were in php4. True story.

WHY WOULD ANYONE WANT TO UPGRADE TO PHP5?
Well, to crack out some good old fashioned alarmist FUD, if you don't know what you're doing, php4 will get you HACKED. PHP4's vulnerabilities are increasingly well-known, it's not nearly as powerful or versatile as php5, etc. Also as staff here have pointed out more than a couple of times already, php4 is DEAD. They (the guys @ php, not @ hostgator) are stopping work on it so it's going to be about as secure as that blue letter e web browser virus explorer, twenty four months from now.

HOW DO I KNOW WHICH VERSION OF PHP I'M RUNNING?
make a file called phpinfo.php and include only this:

<?php phpinfo(); ?>

I dunno if it'll do you any good but there it is. Upload it and execute it.

I WANT TO HAVE REGISTER_GLOBALS (or something) ENABLED IN PHP5, HOW DO I GO ABOUT IT?
Three ways:
http://www.google.co.nz/search?q=ini_set
I was going to say you could do it through Apache but apparently it is not so. Here is the link
http://nz2.php.net/configuration.changes
but don't even bother trying to do it through htaccess (darn), apparently it will be ignored.
Third way (and this is what I use):
set some php.ini directives.

There's plenty of information at php.net about setting php.ini directives. What i didn't understand the first time was that you're only really OVERRIDING DIRECTIVES, as opposed to wiping the whole configuration. On that note, here is a nice sample php.ini to tweak to your heart's content. Before I post it here are some caveats:
- be careful you don't break the terms of your use of the service. For example, if you enable persistent database connections, you won't be getting any HostGator christmas cards or whatever
- I don't guarantee that this file is safe to use in any way, acceptable, fit for any purpose etc other than EDUCATION. Please check that every value is acceptable to you and your host before you use it. This is not quite the original one that HostGator sent me, but it is very similar, after I just started playing with it.
Because I didn't understand 100%, I just rolled up and asked support for a copy of the default so I could be safer with it (here's mine so you hopefully don't have to)

Without further ado
PHP.INI works ok for me with php5, has for almost a year soon:

[PHP]

;;;;;;;;;;;
; WARNING ;
;;;;;;;;;;;
; This is the default settings file for new PHP installations.
; By default, PHP installs itself with a configuration suitable for
; development purposes, and *NOT* for production purposes.
; For several security-oriented considerations that should be taken
; before going online with your site, please consult php.ini-recommended
; and http://php.net/manual/en/security.php.


f;;;;;;;;;;;;;;;;;;;
; About this file ;
;;;;;;;;;;;;;;;;;;;
; This file controls many aspects of PHP's behavior.  In order for PHP to
; read it, it must be named 'php.ini'.  PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory.  The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple.  Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and parentheses:
; |        bitwise OR
; &        bitwise AND
; ~        bitwise NOT
; !        boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
;
;  foo =         ; sets foo to an empty string
;  foo = none    ; sets foo to an empty string
;  foo = "none"  ; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.
;
; All the values in the php.ini-dist file correspond to the builtin
; defaults (that is, if no php.ini is used, or if you delete these lines,
; the builtin defaults will be identical).


;;;;;;;;;;;;;;;;;;;;
; Language Options ;
;;;;;;;;;;;;;;;;;;;;

; Enable the PHP scripting language engine under Apache.
engine = On

; Allow the <? tag.  Otherwise, only <?php and <script> tags are recognized.  
; NOTE: Using short tags should be avoided when developing applications or
; libraries that are meant for redistribution, or deployment on PHP
; servers which are not under your control, because short tags may not
; be supported on the target server. For portable, redistributable code,
; be sure not to use short tags.
short_open_tag = On

; Allow ASP-style <% %> tags.
asp_tags = Off

; The number of significant digits displayed in floating point numbers.
precision    =  12

; Enforce year 2000 compliance (will cause problems with non-compliant browsers)
y2k_compliance = On

; Output buffering allows you to send header lines (including cookies) even
; after you send body content, at the price of slowing PHP's output layer a
; bit.  You can enable output buffering during runtime by calling the output
; buffering functions.  You can also enable output buffering for all files by
; setting this directive to On.  If you wish to limit the size of the buffer
; to a certain size - you can use a maximum number of bytes instead of 'On', as
; a value for this directive (e.g., output_buffering=4096).
output_buffering = On

; You can redirect all of the output of your scripts to a function.  For
; example, if you set output_handler to "mb_output_handler", character
; encoding will be transparently converted to the specified encoding.
; Setting any output handler automatically turns on output buffering.
; Note: People who wrote portable scripts should not depend on this ini
;       directive. Instead, explicitly set the output handler using ob_start().
;       Using this ini directive may cause problems unless you know what script 
;       is doing.
; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler"
;       and you cannot use both "ob_gzhandler" and "zlib.output_compression". 
;output_handler =

; Transparent output compression using the zlib library
; Valid values for this option are 'off', 'on', or a specific buffer size
; to be used for compression (default is 4KB)
; Note: Resulting chunk size may vary due to nature of compression. PHP 
;       outputs chunks that are few hundreds bytes each as a result of 
;       compression. If you prefer a larger chunk size for better 
;       performance, enable output_buffering in addition.
; Note: You need to use zlib.output_handler instead of the standard
;       output_handler, or otherwise the output will be corrupted.
zlib.output_compression = On

; You cannot specify additional output handlers if zlib.output_compression
; is activated here. This setting does the same as output_handler but in
; a different order.
;zlib.output_handler =

; Implicit flush tells PHP to tell the output layer to flush itself
; automatically after every output block.  This is equivalent to calling the
; PHP function flush() after each and every call to print() or echo() and each
; and every HTML block.  Turning this option on has serious performance
; implications and is generally recommended for debugging purposes only.
implicit_flush = Off

; The unserialize callback function will be called (with the undefined class'
; name as parameter), if the unserializer finds an undefined class
; which should be instanciated.
; A warning appears if the specified function is not defined, or if the
; function doesn't include/implement the missing class.
; So only set this entry, if you really want to implement such a 
; callback-function.
unserialize_callback_func=

; When floats & doubles are serialized store serialize_precision significant
; digits after the floating point. The default value ensures that when floats
; are decoded with unserialize, the data will remain the same.
serialize_precision = 100

; Whether to enable the ability to force arguments to be passed by reference
; at function call time.  This method is deprecated and is likely to be
; unsupported in future versions of PHP/Zend.  The encouraged method of
; specifying which arguments should be passed by reference is in the function
; declaration.  You're encouraged to try and turn this option Off and make
; sure your scripts work properly with it in order to ensure they will work
; with future versions of the language (you will receive a warning each time
; you use this feature, and the argument will be passed by value instead of by
; reference).
allow_call_time_pass_reference = On

; Safe Mode
;
safe_mode = Off

; By default, Safe Mode does a UID compare check when
; opening files. If you want to relax this to a GID compare,
; then turn on safe_mode_gid.
safe_mode_gid = Off

; When safe_mode is on, UID/GID checks are bypassed when
; including files from this directory and its subdirectories.
; (directory must also be in include_path or full path must
; be used when including)
safe_mode_include_dir =								

; When safe_mode is on, only executables located in the safe_mode_exec_dir
; will be allowed to be executed via the exec family of functions.
safe_mode_exec_dir =

; Setting certain environment variables may be a potential security breach.
; This directive contains a comma-delimited list of prefixes.  In Safe Mode,
; the user may only alter environment variables whose names begin with the
; prefixes supplied here.  By default, users will only be able to set
; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
;
; Note:  If this directive is empty, PHP will let the user modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_

; This directive contains a comma-delimited list of environment variables that
; the end user won't be able to change using putenv().  These variables will be
; protected even if safe_mode_allowed_env_vars is set to allow to change them.
safe_mode_protected_env_vars = LD_LIBRARY_PATH

; open_basedir, if set, limits all file operations to the defined directory
; and below.  This directive makes most sense if used in a per-directory
; or per-virtualhost web server configuration file. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
;open_basedir =

; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_functions = dl

; This directive allows you to disable certain classes for security reasons.
; It receives a comma-delimited list of class names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_classes =

; Colors for Syntax Highlighting mode.  Anything that's acceptable in
; <font color="??????"> would work.
;highlight.string  = #DD0000
;highlight.comment = #FF9900
;highlight.keyword = #007700
;highlight.bg      = #FFFFFF
;highlight.default = #0000BB
;highlight.html    = #000000


;
; Misc
;
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header).  It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
expose_php = Off


;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 60
max_input_time = 60
memory_limit = 8M

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; error_reporting is a bit-field.  Or each number up to get desired error
; reporting level
; E_ALL             - All errors and warnings
; E_ERROR           - fatal run-time errors
; E_WARNING         - run-time warnings (non-fatal errors)
; E_PARSE           - compile-time parse errors
; E_NOTICE          - run-time notices (these are warnings which often result
;                     from a bug in your code, but it's possible that it was
;                     intentional (e.g., using an uninitialized variable and
;                     relying on the fact it's automatically initialized to an
;                     empty string)
; E_CORE_ERROR      - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING    - warnings (non-fatal errors) that occur during PHP's
;                     initial startup
; E_COMPILE_ERROR   - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR      - user-generated error message
; E_USER_WARNING    - user-generated warning message
; E_USER_NOTICE     - user-generated notice message
;
; Examples:
;
;   - Show all errors, except for notices
;
;error_reporting = E_ALL & ~E_NOTICE
;
;   - Show only errors
;
;error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR
;
;   - Show all errors except for notices
;
error_reporting  =  E_ALL & ~E_NOTICE

; Print out errors (as a part of the output).  For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below).  Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = Off

; Even when display_errors is on, errors that occur during PHP's startup
; sequence are not displayed.  It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off

; Log errors into a log file (server-specific log, stderr, or error_log (below))
; As stated above, you're strongly advised to use error logging in place of
; error displaying on production web sites.
log_errors = On;

; Set maximum length of log_errors. In error_log information about the source is
; added. The default is 1024 and 0 allows to not apply any maximum length at all.
log_errors = On;

; Do not log repeated messages. Repeated errors must occur in same file on same
; line until ignore_repeated_source is set true.
ignore_repeated_errors = Off

; Ignore source of message when ignoring repeated messages. When this setting 
; is On you will not log errors with repeated messages from different files or
; sourcelines.
ignore_repeated_source = Off

; If this parameter is set to Off, then memory leaks will not be shown (on
; stdout or in the log). This has only effect in a debug compile, and if 
; error reporting includes E_WARNING in the allowed list
report_memleaks = On

; Store the last error/warning message in $php_errormsg (boolean).
track_errors = Off

; Disable the inclusion of HTML tags in error messages.
;html_errors = Off
  
; If html_errors is set On PHP produces clickable error messages that direct 
; to a page describing the error or function causing the error in detail.
; You can download a copy of the PHP manual from http://www.php.net/docs.php 
; and change docref_root to the base URL of your local copy including the
; leading '/'. You must also specify the file extension being used including 
; the dot.
;docref_root = "/phpmanual/"
;docref_ext = .html
  
; String to output before an error message.
;error_prepend_string = "<font color=ff0000>"

; String to output after an error message.
;error_append_string = "</font>"

; Log errors to specified file.
error_log = /home/username/error_log;

; Log errors to syslog (Event Log on NT, not valid in Windows 95).
error_log = /home/username/error_log;


;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3

; The separator used in PHP generated URLs to separate arguments.
; Default is "&". 
;arg_separator.output = "&amp;"

; List of separator(s) used by PHP to parse input URLs into variables.
; Default is "&". 
; NOTE: Every character in this directive is considered as separator!
;arg_separator.input = ";&"

; This directive describes the order in which PHP registers GET, POST, Cookie,
; Environment and Built-in variables (G, P, C, E & S respectively, often
; referred to as EGPCS or GPC).  Registration is done from left to right, newer
; values override older values.
variables_order = "EGPCS"

; Whether or not to register the EGPCS variables as global variables.  You may
; want to turn this off if you don't want to clutter your scripts' global scope
; with user data.  This makes most sense when coupled with track_vars - in which
; case you can access all of the GPC variables through the $HTTP_*_VARS[],
; variables.
;
; You should do your best to write your scripts so that they do not require
; register_globals to be on;  Using form variables as globals can easily lead
; to possible security problems, if the code is not very well thought of.
register_globals = Off

; This directive tells PHP whether to declare the argv&argc variables (that
; would contain the GET information).  If you don't use these variables, you
; should turn it off for increased performance.
register_argc_argv = On

; Maximum size of POST data that PHP will accept.
post_max_size = 8M

; This directive is deprecated.  Use variables_order instead.
gpc_order = "GPC"

; Magic quotes
;

; Magic quotes for incoming GET/POST/Cookie data.
magic_quotes_gpc = On

; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
magic_quotes_runtime = Off    

; Use Sybase-style magic quotes (escape ' with '' instead of \').
magic_quotes_sybase = Off

; Automatically add files before or after any PHP document.
auto_prepend_file =
auto_append_file =

; As of 4.0b4, PHP always outputs a character encoding by default in
; the Content-type: header.  To disable sending of the charset, simply
; set it to be empty.
;
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"

; Always populate the $HTTP_RAW_POST_DATA variable.
;always_populate_raw_post_data = On


;;;;;;;;;;;;;;;;;;;;;;;;;
; Paths and Directories ;
;;;;;;;;;;;;;;;;;;;;;;;;;

; UNIX: "/path1:/path2"  
include_path = ".:/usr/lib/php:/usr/local/lib/php";
;
; Windows: "\path1;\path2"
;include_path = ".:/usr/lib/php:/usr/local/lib/php"   ;

; The root of the PHP pages, used only if nonempty.
; if PHP was not compiled with FORCE_REDIRECT, you SHOULD set doc_root
; if you are running php as a CGI under any web server (other than IIS)
; see documentation for security issues.  The alternate is to use the
; cgi.force_redirect configuration below
doc_root =

; The directory under which PHP opens the script using /~username used only
; if nonempty.
user_dir =

; Directory in which the loadable extensions (modules) reside.
extension_dir = "/"

; Whether or not to enable the dl() function.  The dl() function does NOT work
; properly in multithreaded servers, such as IIS or Zeus, and is automatically
; disabled on them.
enable_dl = Off

; cgi.force_redirect is necessary to provide security running PHP as a CGI under
; most web servers.  Left undefined, PHP turns this on by default.  You can
; turn it off here AT YOUR OWN RISK
; **You CAN safely turn this off for IIS, in fact, you MUST.**
; cgi.force_redirect = 1

; if cgi.nph is enabled it will force cgi to always sent Status: 200 with
; every request.
; cgi.nph = 1

; if cgi.force_redirect is turned on, and you are not running under Apache or Netscape 
; (iPlanet) web servers, you MAY need to set an environment variable name that PHP
; will look for to know it is OK to continue execution.  Setting this variable MAY
; cause security issues, KNOW WHAT YOU ARE DOING FIRST.
; cgi.redirect_status_env = ;

; cgi.fix_pathinfo provides *real* PATH_INFO/PATH_TRANSLATED support for CGI.  PHP's
; previous behaviour was to set PATH_TRANSLATED to SCRIPT_FILENAME, and to not grok
; what PATH_INFO is.  For more information on PATH_INFO, see the cgi specs.  Setting
; this to 1 will cause PHP CGI to fix it's paths to conform to the spec.  A setting
; of zero causes PHP to behave as before.  Default is zero.  You should fix your scripts
; to use SCRIPT_FILENAME rather than PATH_TRANSLATED.
; cgi.fix_pathinfo=0

; FastCGI under IIS (on WINNT based OS) supports the ability to impersonate
; security tokens of the calling client.  This allows IIS to define the
; security context that the request runs under.  mod_fastcgi under Apache
; does not currently support this feature (03/17/2002)
; Set to 1 if running under IIS.  Default is zero.
; fastcgi.impersonate = 1;

; cgi.rfc2616_headers configuration option tells PHP what type of headers to
; use when sending HTTP response code. If it's set 0 PHP sends Status: header that
; is supported by Apache. When this option is set to 1 PHP will send
; RFC2616 compliant header.
; Default is zero.
;cgi.rfc2616_headers = 0 
 

;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;

; Whether to allow HTTP file uploads.
file_uploads = On

; Temporary directory for HTTP uploaded files (will use system default if not
; specified).
;upload_tmp_dir =

; Maximum allowed size for uploaded files.
upload_max_filesize = 8M


;;;;;;;;;;;;;;;;;;
; Fopen wrappers ;
;;;;;;;;;;;;;;;;;;

; Whether to allow the treatment of URLs (like http:// or ftp://) as files.
allow_url_fopen = On

; Define the anonymous ftp password (your email address)
;from="john@doe.com"

; Define the User-Agent string
; user_agent="PHP"

; Default timeout for socket based streams (seconds)
default_socket_timeout = 60

; If your scripts have to deal with files from Macintosh systems,
; or you are running on a Mac and need to deal with files from
; unix or win32 systems, setting this flag will cause PHP to
; automatically detect the EOL character in those files so that
; fgets() and file() will work regardless of the source of the file.
; auto_detect_line_endings = Off


;;;;;;;;;;;;;;;;;;;;;;
; Dynamic Extensions ;
;;;;;;;;;;;;;;;;;;;;;;
;
; If you wish to have an extension loaded automatically, use the following
; syntax:
;
;   extension=modulename.extension
;
; For example, on Windows:
;
;   extension=msql.dll
;
; ... or under UNIX:
;
;   extension=msql.so
;
; Note that it should be the name of the module only; no directory information 
; needs to go here.  Specify the location of the extension with the
; extension_dir directive above.


;Windows Extensions
;Note that MySQL and ODBC support is now built in, so no dll is needed for it.
;
;extension=php_bz2.dll
;extension=php_cpdf.dll
;extension=php_crack.dll
;extension=php_curl.dll
;extension=php_db.dll
;extension=php_dba.dll
;extension=php_dbase.dll
;extension=php_dbx.dll
;extension=php_domxml.dll
;extension=php_exif.dll
;extension=php_fdf.dll
;extension=php_filepro.dll
;extension=php_gd2.dll
;extension=php_gettext.dll
;extension=php_hyperwave.dll
;extension=php_iconv.dll
;extension=php_ifx.dll
;extension=php_iisfunc.dll
;extension=php_imap.dll
;extension=php_interbase.dll
;extension=php_java.dll
;extension=php_ldap.dll
;extension=php_mbstring.dll
;extension=php_mcrypt.dll
;extension=php_mhash.dll
;extension=php_mime_magic.dll
;extension=php_ming.dll
;extension=php_mssql.dll
;extension=php_msql.dll
;extension=php_oci8.dll
;extension=php_openssl.dll
;extension=php_oracle.dll
;extension=php_pdf.dll
;extension=php_pgsql.dll
;extension=php_printer.dll
;extension=php_shmop.dll
;extension=php_snmp.dll
;extension=php_sockets.dll
;extension=php_sybase_ct.dll
;extension=php_w32api.dll
;extension=php_xmlrpc.dll
;extension=php_xslt.dll
;extension=php_yaz.dll
;extension=php_zip.dll


;;;;;;;;;;;;;;;;;;;
; Module Settings ;
;;;;;;;;;;;;;;;;;;;

[Syslog]
; Whether or not to define the various syslog variables (e.g. $LOG_PID,
; $LOG_CRON, etc.).  Turning it off is a good idea performance-wise.  In
; runtime, you can define these variables by calling define_syslog_variables().
define_syslog_variables  = Off

[mail function]
; For Win32 only.
;SMTP = localhost;
smtp_port = 25

; For Win32 only.
;sendmail_from = me@localhost.com;

; For Unix only.  You may supply arguments as well (default: "sendmail -t -i").
sendmail_path = /usr/sbin/sendmail -t -i;

[Java]
;java.class.path = .\php_java.jar
;java.home = c:\jdk
;java.library = c:\jdk\jre\bin\hotspot\jvm.dll 
;java.library.path = .\

[SQL]
sql.safe_mode = Off

[ODBC]
;odbc.default_db    =  Not yet implemented
;odbc.default_user  =  Not yet implemented
;odbc.default_pw    =  Not yet implemented

; Allow or prevent persistent links.
odbc.allow_persistent = On

; Check that a connection is still valid before reuse.
odbc.check_persistent = On

; Maximum number of persistent links.  -1 means no limit.
odbc.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
odbc.max_links = -1  

; Handling of LONG fields.  Returns number of bytes to variables.  0 means
; passthru.
odbc.defaultlrl = 4096  

; Handling of binary data.  0 means passthru, 1 return as is, 2 convert to char.
; See the documentation on odbc_binmode and odbc_longreadlen for an explanation
; of uodbc.defaultlrl and uodbc.defaultbinmode
odbc.defaultbinmode = 1  

[MySQL]
; Allow or prevent persistent links.
mysql.allow_persistent = Off

; Maximum number of persistent links.  -1 means no limit.
mysql.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
mysql.max_links = -1

; Default port number for mysql_connect().  If unset, mysql_connect() will use
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
; compile-time value defined MYSQL_PORT (in that order).  Win32 will only look
; at MYSQL_PORT.
mysql.default_port =

; Default socket name for local MySQL connects.  If empty, uses the built-in
; MySQL defaults.
mysql.default_socket =

; Default host for mysql_connect() (doesn't apply in safe mode).
mysql.default_host =

; Default user for mysql_connect() (doesn't apply in safe mode).
mysql.default_user =

; Default password for mysql_connect() (doesn't apply in safe mode).
; Note that this is generally a *bad* idea to store passwords in this file.
; *Any* user with PHP access can run 'echo get_cfg_var("mysql.default_password")
; and reveal this password!  And of course, any users with read access to this
; file will be able to reveal the password as well.
mysql.default_password =

; Maximum time (in seconds) for connect timeout. -1 means no limit
mysql.connect_timeout = 60

; Trace mode. When trace_mode is active (=On), warnings for table/index scans and
; SQL-Errors will be displayed.
mysql.trace_mode = Off

[mSQL]
; Allow or prevent persistent links.
msql.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
msql.max_persistent = -1

; Maximum number of links (persistent+non persistent).  -1 means no limit.
msql.max_links = -1

[PostgresSQL]
; Allow or prevent persistent links.
pgsql.allow_persistent = On

; Detect broken persistent links always with pg_pconnect(). Need a little overhead.
pgsql.auto_reset_persistent = Off 

; Maximum number of persistent links.  -1 means no limit.
pgsql.max_persistent = -1

; Maximum number of links (persistent+non persistent).  -1 means no limit.
pgsql.max_links = -1

; Ignore PostgreSQL backends Notice message or not.
pgsql.ignore_notice = 0

; Log PostgreSQL backends Noitce message or not.
; Unless pgsql.ignore_notice=0, module cannot log notice message.
pgsql.log_notice = 0

[Sybase]
; Allow or prevent persistent links.
sybase.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
sybase.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
sybase.max_links = -1

;sybase.interface_file = "/usr/sybase/interfaces"

; Minimum error severity to display.
sybase.min_error_severity = 10

; Minimum message severity to display.
sybase.min_message_severity = 10

; Compatability mode with old versions of PHP 3.0.
; If on, this will cause PHP to automatically assign types to results according
; to their Sybase type, instead of treating them all as strings.  This
; compatibility mode will probably not stay around forever, so try applying
; whatever necessary changes to your code, and turn it off.
sybase.compatability_mode = Off

[Sybase-CT]
; Allow or prevent persistent links.
sybct.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
sybct.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
sybct.max_links = -1

; Minimum server message severity to display.
sybct.min_server_severity = 10

; Minimum client message severity to display.
sybct.min_client_severity = 10

[dbx]
; returned column names can be converted for compatibility reasons
; possible values for dbx.colnames_case are
; "unchanged" (default, if not set)
; "lowercase"
; "uppercase"
; the recommended default is either upper- or lowercase, but
; unchanged is currently set for backwards compatibility
dbx.colnames_case = "unchanged"

[bcmath]
; Number of decimal digits for all bcmath functions.
bcmath.scale = 0

[browscap]
;browscap = extra/browscap.ini

[Informix]
; Default host for ifx_connect() (doesn't apply in safe mode).
ifx.default_host =

; Default user for ifx_connect() (doesn't apply in safe mode).
ifx.default_user =

; Default password for ifx_connect() (doesn't apply in safe mode).
ifx.default_password =

; Allow or prevent persistent links.
ifx.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
ifx.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
ifx.max_links = -1

; If on, select statements return the contents of a text blob instead of its id.
ifx.textasvarchar = 0

; If on, select statements return the contents of a byte blob instead of its id.
ifx.byteasvarchar = 0

; Trailing blanks are stripped from fixed-length char columns.  May help the
; life of Informix SE users.
ifx.charasvarchar = 0

; If on, the contents of text and byte blobs are dumped to a file instead of
; keeping them in memory.
ifx.blobinfile = 0

; NULL's are returned as empty strings, unless this is set to 1.  In that case,
; NULL's are returned as string 'NULL'.
ifx.nullformat = 0

[Session]
; Handler used to store/retrieve data.
session.save_handler = files

; Argument passed to save_handler.  In the case of files, this is the path
; where data files are stored. Note: Windows users have to change this 
; variable in order to use PHP's session functions.
; As of PHP 4.0.1, you can define the path as:
;     session.save_path = "N;/path"
; where N is an integer.  Instead of storing all the session files in 
; /path, what this will do is use subdirectories N-levels deep, and 
; store the session data in those directories.  This is useful if you 
; or your OS have problems with lots of files in one directory, and is 
; a more efficient layout for servers that handle lots of sessions.
; NOTE 1: PHP will not create this directory structure automatically.
;         You can use the script in the ext/session dir for that purpose.
; NOTE 2: See the section on garbage collection below if you choose to
;         use subdirectories for session storage
;session.save_path = /tmp
session.save_path = /home/username/tmp

; Whether to use cookies.
session.use_cookies = 1

; This option enables administrators to make their users invulnerable to
; attacks which involve passing session ids in URLs; defaults to 0.
session.use_only_cookies = 1

; Name of the session (used as cookie name).
session.name = PHPSESSID

; Initialize session on request startup.
session.auto_start = 0

; Lifetime in seconds of cookie or, if 0, until browser is restarted.
session.cookie_lifetime = 0

; The path for which the cookie is valid.
session.cookie_path = /

; The domain for which the cookie is valid.
session.cookie_domain =

; Handler used to serialize data.  php is the standard serializer of PHP.
session.serialize_handler = php

; Define the probability that the 'garbage collection' process is started
; on every session initialization.
; The probability is calculated by using gc_probability/gc_divisor,
; e.g. 1/100 means there is a 1% chance that the GC process starts
; on each request.

session.gc_probability = 1
session.gc_divisor     = 100

; After this number of seconds, stored data will be seen as 'garbage' and
; cleaned up by the garbage collection process.
session.gc_maxlifetime = 1440

; NOTE: If you are using the subdirectory option for storing session files
;       (see session.save_path above), then garbage collection does *not*
;       happen automatically.  You will need to do your own garbage 
;       collection through a shell script, cron entry, or some other method. 
;       For example, the following script would is the equivalent of
;       setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
;          cd /path/to/sessions; find -cmin +24 | xargs rm

; PHP 4.2 and less have an undocumented feature/bug that allows you to
; to initialize a session variable in the global scope, albeit register_globals
; is disabled.  PHP 4.3 and later will warn you, if this feature is used.
; You can disable the feature and the warning separately. At this time,
; the warning is only displayed, if bug_compat_42 is enabled.

session.bug_compat_42 = 1
session.bug_compat_warn = 1

; Check HTTP Referer to invalidate externally stored URLs containing ids.
; HTTP_REFERER has to contain this substring for the session to be
; considered as valid.
session.referer_check =

; How many bytes to read from the file.
session.entropy_length = 0

; Specified here to create the session id.
session.entropy_file =

;session.entropy_length = 16

;session.entropy_file = /dev/urandom

; Set to {nocache,private,public,} to determine HTTP caching aspects
; or leave this empty to avoid sending anti-caching headers.
; session.cache_limiter = nocache

; Document expires after n minutes.
session.cache_expire = 180

; trans sid support is disabled by default.
; Use of trans sid may risk your users security. 
; Use this option with caution.
; - User may send URL contains active session ID
;   to other person via. email/irc/etc.
; - URL that contains active session ID may be stored
;   in publically accessible computer.
; - User may access your site with the same session ID
;   always using URL stored in browser's history or bookmarks.
session.use_trans_sid = 0

; The URL rewriter will look for URLs in a defined set of HTML tags.
; form/fieldset are special; if you include them here, the rewriter will
; add a hidden <input> field with the info which is otherwise appended
; to URLs.  If you want XHTML conformity, remove the form entry.
; Note that all valid entries require a "=", even if no value follows.
url_rewriter.tags = "img=src,a=href,area=href,frame=src,input=src,form=,fieldset="

[MSSQL]
; Allow or prevent persistent links.
mssql.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
mssql.max_persistent = -1

; Maximum number of links (persistent+non persistent).  -1 means no limit.
mssql.max_links = -1

; Minimum error severity to display.
mssql.min_error_severity = 10

; Minimum message severity to display.
mssql.min_message_severity = 10

; Compatability mode with old versions of PHP 3.0.
mssql.compatability_mode = Off

; Connect timeout
;mssql.connect_timeout = 5

; Query timeout
;mssql.timeout = 60

; Valid range 0 - 2147483647.  Default = 4096.
;mssql.textlimit = 4096

; Valid range 0 - 2147483647.  Default = 4096.
;mssql.textsize = 4096

; Limits the number of records in each batch.  0 = all records in one batch.
;mssql.batchsize = 0

; Specify how datetime and datetim4 columns are returned
; On => Returns data converted to SQL server settings
; Off => Returns values as YYYY-MM-DD hh:mm:ss
;mssql.datetimeconvert = On

; Use NT authentication when connecting to the server
mssql.secure_connection = Off

; Specify max number of processes. Default = 25
;mssql.max_procs = 25

[Assertion]
; Assert(expr); active by default.
;assert.active = On

; Issue a PHP warning for each failed assertion.
;assert.warning = On

; Don't bail out by default.
;assert.bail = Off

; User-function to be called if an assertion fails.
;assert.callback = 0

; Eval the expression with current error_reporting().  Set to true if you want
; error_reporting(0) around the eval().
;assert.quiet_eval = 0

[Ingres II]
; Allow or prevent persistent links.
ingres.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
ingres.max_persistent = -1

; Maximum number of links, including persistents.  -1 means no limit.
ingres.max_links = -1

; Default database (format: [node_id::]dbname[/srv_class]).
ingres.default_database =

; Default user.
ingres.default_user =

; Default password.
ingres.default_password =

[Verisign Payflow Pro]
; Default Payflow Pro server.
pfpro.defaulthost = "test-payflow.verisign.com"

; Default port to connect to.
pfpro.defaultport = 443

; Default timeout in seconds.
pfpro.defaulttimeout = 30

; Default proxy IP address (if required).
;pfpro.proxyaddress =

; Default proxy port.
;pfpro.proxyport =

; Default proxy logon.
;pfpro.proxylogon =

; Default proxy password.
;pfpro.proxypassword =

[com]
; path to a file containing GUIDs, IIDs or filenames of files with TypeLibs
;com.typelib_file = 
; allow Distributed-COM calls
;com.allow_dcom = true
; autoregister constants of a components typlib on com_load()
;com.autoregister_typelib = true
; register constants casesensitive
;com.autoregister_casesensitive = false
; show warnings on duplicate constat registrations
;com.autoregister_verbose = true

[Printer]
;printer.default_printer = ""

[mbstring]
; language for internal character representation.
;mbstring.language = Japanese

; internal/script encoding.
; Some encoding cannot work as internal encoding.
; (e.g. SJIS, BIG5, ISO-2022-*)
;mbstring.internal_encoding = EUC-JP

; http input encoding.
;mbstring.http_input = auto

; http output encoding. mb_output_handler must be
; registered as output buffer to function
;mbstring.http_output = SJIS

; enable automatic encoding translation accoding to 
; mbstring.internal_encoding setting. Input chars are
; converted to internal encoding by setting this to On.
; Note: Do _not_ use automatic encoding translation for
;       portable libs/applications.
;mbstring.encoding_translation = Off

; automatic encoding detection order.
; auto means 
;mbstring.detect_order = auto

; substitute_character used when character cannot be converted
; one from another
;mbstring.substitute_character = none;

; overload(replace) single byte functions by mbstring functions.
; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(),
; etc. Possible values are 0,1,2,4 or combination of them.
; For example, 7 for overload everything.
; 0: No overload
; 1: Overload mail() function
; 2: Overload str*() functions
; 4: Overload ereg*() functions
;mbstring.func_overload = 0

[FrontBase]
;fbsql.allow_persistent = On
;fbsql.autocommit = On
;fbsql.default_database = 
;fbsql.default_database_password =
;fbsql.default_host =
;fbsql.default_password =
;fbsql.default_user = "_SYSTEM"
;fbsql.generate_warnings = Off
;fbsql.max_connections = 128
;fbsql.max_links = 128
;fbsql.max_persistent = -1
;fbsql.max_results = 128
;fbsql.batchSize = 1000

[Crack]
; Modify the setting below to match the directory location of the cracklib
; dictionary files.  Include the base filename, but not the file extension.
; crack.default_dictionary = "c:\php\lib\cracklib_dict"

[exif]
; Exif UNICODE user comments are handled as UCS-2BE/UCS-2LE and JIS as JIS. 
; With mbstring support this will automatically be converted into the encoding
; given by corresponding encode setting. When empty mbstring.internal_encoding 
; is used. For the decode settings you can distinguish between motorola and 
; intel byte order. A decode setting cannot be empty.
;exif.encode_unicode = ISO-8859-15
;exif.decode_unicode_motorola = UCS-2BE
;exif.decode_unicode_intel    = UCS-2LE
;exif.encode_jis = 
;exif.decode_jis_motorola = JIS
;exif.decode_jis_intel    = JIS

; Local Variables:
; tab-width: 4
; End:
extension=/etc/ixed/ixed.4.4.lin

; remove old version
;zend_extension=/etc/ioncube/ioncube_loader_lin_4.4.so
; add my version put your username here so you can find it easily
; we're upgrading the resources avaialble here
;zend_extension = /home/username/ioncube_loader_lin_5.2.so
[Zend]
zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.2.2
zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.2.2
zend_optimizer.version=3.2.2




zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so
zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so

WHERE IS THE TOS?
http://www.hostgator.com/tos.shtml - thanks to Jamyn's signature.

NOW Some questions/requests:
One of my packages is Aluminium, with WHMAutopilot. I tried to run THAT under php5 and it failed on account of Zend. I believe that Zend is not properly configured with php5 on that server - a Zend error screen appears, or else it just complains about an error on line zero of an unknown file. I might be mistaken in a big way but I would appreciate if Zend DEFINTIElY runs properly under php5 when it becomes default. I've just resorted (yech) to running php4 in the meantime. WHMAutopilot REQUIRES Zend. I don't know if the problem is what I think it is, or on what servers. IFF it's worth looking into, I'm on bluedevil.websitewelcome.com

I wouldn't mind having aspell and pspell so I can use the spellcheck in smf!? No worries if it can't/shouldn't be done

I also wouldn't mind ming.. I have a ming extension already compiled that should work for me.. In any event it's not the end of the world if this can't be done either. Yes, I do have a specific purpose for each of these things and I'm working around them right now.

xmlrpc-epi or whichever, and GD are switched on on at least one of my plans. I would hope for it to stay that way.

Most of my images from GD don't load properly in for Trident or KHTML based browsers, most of the time they come up as redexes or zero-byte files. This is a known issue with GD, but it is fixed in the latest version. I would appreciate it greatly if the latest version of GD could come with this upgrade.

AND
Thanks guys. Your support is great, I appreciate being told in advance although I expect no problems. I love having the latest versions of php, mysql, and Apache2 on a test server. There are a lot of things I want from Apache that I can't do on the Apache 1 servers I'm using at Hostgator at the moment, so if a move to Apache2 were planned, I would be the happiest guy on this side of the planet. Definitely eager to see php5 as default, mysql5, and hopefully someday soon Apache2 IF that's at all possible.

[Jordanlw]

Excellent little guide there!
Deserves a stickie!

[kmaw]

Originally Posted by Jordanlw

Excellent little guide there!
Deserves a stickie!

well, the thread is stickied... lol

[Jordanlw]

</sarcasm>

[GatorFord]

Originally Posted by minimalnet

Finally I used this option http://www.hostgator.com/php5opt-out/

I prefer continue with the current versions of php and mysql to avoid problems.

Jordanlw thanks for explain me the info about the tracert to can use this option, you are very nice.

Sorry my bad english, I am from Spain

This does not mean you will be on PHP4 and MySQL4. Your server will eventually be migrated to PHP5 and MySQL 5 regardless of if you opt out or not, what it does mean, is that we won't automatically try to fix any issues with your scripts or databases. Now you must do it manually.

[quietFinn]

Originally Posted by GatorFord

This does not mean you will be on PHP4 and MySQL4. Your server will eventually be migrated to PHP5 and MySQL 5 regardless of if you opt out or not, what it does mean, is that we won't automatically try to fix any issues with your scripts or databases. Now you must do it manually.

What opting out means is very badly explained in the email and in the 1st post of this thread.
I had to read it several times before I understood that opting out does not mean that you can continue using PHP4 and MySQL4.

[Jordanlw]

And the fact another Gator had miss-interrupted it and posted that Opting out would mean you can continue using the old services.
Which just made it even hard to understand it all in general.

[willow1872]

Originally Posted by GatorFord

This does not mean you will be on PHP4 and MySQL4. Your server will eventually be migrated to PHP5 and MySQL 5 regardless of if you opt out or not, what it does mean, is that we won't automatically try to fix any issues with your scripts or databases. Now you must do it manually.

Sadly this should also be pointed out to HG support staff who told me the complete opposite. Sadly i now have to look for a new host which is a great shame.

[codesight]

Originally Posted by willow1872

Sadly this should also be pointed out to HG support staff who told me the complete opposite. Sadly i now have to look for a new host which is a great shame.

According to a staff member on the cubecart forums, "Yes, currently the 4.0.0 betas run on PHP 4.3.0 or later, including PHP 5.x, and any version on MySQL later than 4.1".

I'm not sure which version of CubeCart you are on, but it seems you are fine.

[GatorDaveC]

Originally Posted by codesight

According to a staff member on the cubecart forums, "Yes, currently the 4.0.0 betas run on PHP 4.3.0 or later, including PHP 5.x, and any version on MySQL later than 4.1".

I'm not sure which version of CubeCart you are on, but it seems you are fine.

CubeCart 3.x also runs on PHP5/MySQL5 in our environment. CubeCart 3.x is one of the scripts I was testing ( http://gator380.hostgator.com/~davec/upload/ ). I'll be testing other functions in it tonight as well.


The current PHP5 use flags are listed below, and might be changed before the official launch.

'--enable-bcmath' '--enable-calendar' '--enable-ftp' '--enable-libxml' 
'--enable-magic-quotes' '--enable-mbstring' '--enable-pdo=shared' 
'--enable-soap' '--enable-sockets' '--enable-zip' '--prefix=/usr/local' 
'--with-curl=/opt/curlssl/' '--with-gd' '--with-gettext'
'--with-imap=/opt/php_with_imap_client/' '--with-imap-ssl=/usr' 
'--with-jpeg-dir=/usr' '--with-kerberos' '--with-libexpat-dir=/usr' 
'--with-libxml-dir=/opt/xml2' '--with-libxml-dir=/opt/xml2/' 
'--with-mcrypt=/opt/libmcrypt/' '--with-mhash=/opt/mhash/' 
'--with-mime-magic' '--with-mysql=/usr' '--with-mysql-sock=/var/lib/mysql/mysql.sock' '--with-mysqli=/usr/bin/mysql_config' 
'--with-pdo-mysql=shared' '--with-pdo-sqlite=shared'
 '--with-png-dir=/usr' '--with-pspell' '--with-sqlite=shared' 
'--with-tidy=/opt/tidy/' '--with-xmlrpc' '--with-xpm-dir=/usr/X11R6'
 '--with-xsl=/opt/xslt/' '--with-zlib' '--with-zlib-dir=/usr'

[codesight]

Dave,

Are you confirming all Fantastico scripts as well?

As a reseller, clients use them from time to time and I'd hate for them to break as they are standard installs.

I put a php5 addhandler in one of the accounts for coppermine and it seems to work, but obviously I didn't test mysql5, but I'd guess that should be ok as well.

[willow1872]

Originally Posted by codesight

According to a staff member on the cubecart forums, "Yes, currently the 4.0.0 betas run on PHP 4.3.0 or later, including PHP 5.x, and any version on MySQL later than 4.1".

I'm not sure which version of CubeCart you are on, but it seems you are fine.

PHP 5 is fine and there is support for MySQL 5 but CubeCart doesnt like it when you upgrade an existing database from 4 to 5. All of my customers are using CubeCart and i cannot take the risk of there being problems. I spoke to HG on the phone about this yesterday and they told me that by opting out i could continue to use MySQL 4 but Brent has stated that this information was wrong and that i have no choice in the matter.

If i was adding a new customer and started out on MySQL 5 then that wouldn't be a problem but i have a number of customers using older CubeCart versions who refuse to upgrade because of all their custom mods.

Theres no point in me harping on about it, it is what it is and such is life, i just would have prefered not to have to move them all again and would also have prefered that i wasnt miss informed by HG staff and that the email about the upgrades and opting out were a little clearer.

[IronWarrior]

I think php5 is not gonna work with the pafileDB mod am using on my site.

[codesight]

Originally Posted by IronWarrior

I think php5 is not gonna work with the pafileDB mod am using on my site.

Try it out... use the .htaccess addhandler for PHP5, this will allow you to see before the server gets the changes done.

[IronWarrior]

Originally Posted by codesight

Try it out... use the .htaccess addhandler for PHP5, this will allow you to see before the server gets the changes done.

How can something as simple as that, prove if it will work or not?

[Elijah]

Originally Posted by Elijah

Oh sorry, I guess the site move from reseller to shared somehow caused problems.

Whoa, whoa, whoa... it seems that the shared server I copied a script to is already php5!

From ticket:

The new server is PHP5 and the other server is php4. We will be migrating all of our servers to php5 as php4 has not been in development for some time, and now is no longer supported and is replaced with PHP5. Your function needs to be altered to adhere to PHP5 coding rules rather than php4 for this new server. We do not provide coding support as we are not developers, but system admins. I would advise contacting the script maintainer for support converting the script to work with php5.