Upgrade to 2.0 RC1.2 at Step 4th,it prompt me to download the upgrade.php's file

Started by mrich1, August 28, 2009, 05:09:40 AM

Previous topic - Next topic

mrich1

 :-*  Hi,

Please advise.
I still never success to upgrade from 1.1.10 to 2.0 RC1.2, everytime I struck at step 4th, always prompt me to download upgrade.php file. And it is blank file.

This what I miss. Please advise.

Thanks

mrich1

 ;) When retry to upgarde with IE8 at the same step it show blank page.

Please advise.

Thanks.

Norv

Hello there!
It sounds like the PHP engine on your host's server crashes.
Please try looking in your cpanel for the webserver logs, or ask your host in case you don't find them, and attach here the webserver error log.
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker


Also known as Norv on D* | Norv N. on G+ | Norv on Github

mrich1

Crashed, I run well with the 1.1.8 -> 1.1.9 and 1.1.10.  now it has more than 3000 posts. I checked in the error log but nothing.


Please advise.

Thanks





[PHP]

;;;;;;;;;;;;;;;;;;;
; 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 overriden 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 ;
;;;;;;;;;;;;;;;;;;;;

engine = On
short_open_tag = On
asp_tags = Off
precision = 14
y2k_compliance = Off
output_buffering = On
                     ; even after you send body content, in the price of slowing PHP's
                     ; output layer a bit.
                     ; You can enable output buffering by in runtime by calling the output
                     ; buffering functions, or enable output buffering for all files
                     ; by setting this directive to On.
implicit_flush = Off
                     ; 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.
allow_call_time_pass_reference = On
                              ; 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, 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).

; Safe Mode
safe_mode = Off
safe_mode_exec_dir =
safe_mode_allowed_env_vars = PHP_
                                       ; 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_protected_env_vars = LD_LIBRARY_PATH
                                       ; 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.


disable_functions =
                                       ; functions for security reasons.  It receives
                                       ; a comma separated list of function names.
                                       ; This directive is *NOT* affected by whether
                                       ; Safe Mode is turned on or off.
                                       

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

; Misc
expose_php = On
                  ; 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.



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

max_execution_time = 30
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:
error_reporting = E_ALL & ~E_NOTICE
; error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR   ; show only errors
;error_reporting   =   E_ALL & ~E_NOTICE      ; Show all errors except for notices
display_errors = On
                  ; 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_startup_errors = Off
                           ; PHP's startup sequence are not displayed.  It's strongly
                           ; recommended to keep display_startup_errors off, except for
                           ; when debugging.
log_errors = On
                  ; As stated above, you're strongly advised to use error logging in place of
                  ; error displaying on production web sites.
track_errors = Off
;error_prepend_string = "<font color=ff0000>"   ; string to output before an error message
;error_append_string = "</font>"                ; string to output after an error message
error_log = error_log
;error_log = error_log;
warn_plus_overloading = Off


;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3
variables_order = "EGPCS"
                        ; 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.
register_globals = Off
                        ; 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_argc_argv = On
                        ; variables (that would contain the GET information).  If you
                        ; don't use these variables, you should turn it off for
                        ; increased performance
post_max_size = 55M
gpc_order = "GPC"

; Magic quotes
magic_quotes_gpc = On
magic_quotes_runtime = Off
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-11"

;;;;;;;;;;;;;;;;;;;;;;;;;
; Paths and Directories ;
;;;;;;;;;;;;;;;;;;;;;;;;;
include_path = ".:/usr/lib/php:/usr/local/lib/php"
doc_root =
user_dir =
extension_dir = "/usr/local/lib/php/extensions/no-debug-non-zts-20020429"
zend_extension = "/usr/local/IonCube/ioncube_loader_lin_4.4.so"
zend_extension = On
zend_extension_ts = "/usr/local/IonCube/ioncube_loader_lin_4.4_ts.so"
zend_extension_ts = On
enable_dl = On
                           ; The dl() function does NOT properly work in multithreaded
                           ; servers, such as IIS or Zeus, and is automatically disabled
                           ; on them.


;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;
file_uploads = On
;upload_tmp_dir   =                   ; temporary directory for HTTP uploaded files (will use system default if not specified)
upload_max_filesize = 15M


;;;;;;;;;;;;;;;;;;;;;;
; Dynamic Extensions ;
;;;;;;;;;;;;;;;;;;;;;;
; if you wish to have an extension loaded automaticly, use the
; following syntax:  extension=modulename.extension
; for example, on windows,
;extension = "ffmpeg.so"
; or under UNIX,
; 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.
;


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

[Syslog]
define_syslog_variables = Off
                        ; 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()


[mail function]
;SMTP = localhost
;sendmail_from = [email protected]
sendmail_path = "/usr/sbin/sendmail -t -i"

[Debugger]
debugger.host = "localhost"
debugger.port = 7869
debugger.enabled = "False"

[Logging]
; These configuration directives are used by the example logging mechanism.
; See examples/README.logging for more explanation.
;logging.method    = db
;logging.directory = /path/to/log/directory

[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]
;uodbc.default_db      =   Not yet implemented
;uodbc.default_user      =   Not yet implemented
;uodbc.default_pw      =   Not yet implemented
uodbc.allow_persistent = On
uodbc.check_persistent = On
uodbc.max_persistent = -1
uodbc.max_links = -1
uodbc.defaultlrl = 4096
uodbc.defaultbinmode = 1
; See the documentation on odbc_binmode and odbc_longreadlen for an explanation of uodbc.defaultlrl
; and uodbc.defaultbinmode

[MySQL]
mysql.allow_persistent = On
mysql.max_persistent = -1
mysql.max_links = -1
mysql.default_port =
                        ; mysql_connect() will use the $MYSQL_TCP_PORT, or the mysql-tcp
                        ; entry in /etc/services, or the compile-time defined MYSQL_PORT
                        ; (in that order).  Win32 will only look at MYSQL_PORT.
mysql.default_socket =
                        ; MySQL defaults
mysql.default_host =
mysql.default_user =
mysql.default_password =
                        ; Note that this is generally a *bad* idea to store passwords
                        ; in this file.  *Any* user with PHP access can run
                        ; 'echo cfg_get_var("mysql.default_password")' and reveal that
                        ; password!  And of course, any users with read access to this
                        ; file will be able to reveal the password as well.

[mSQL]
msql.allow_persistent = On
msql.max_persistent = -1
msql.max_links = -1

[PostgresSQL]
pgsql.allow_persistent = On
pgsql.max_persistent = -1
pgsql.max_links = -1

[Sybase]
sybase.allow_persistent = On
sybase.max_persistent = -1
sybase.max_links = -1
;sybase.interface_file   =   "/usr/sybase/interfaces"
sybase.min_error_severity = 10
sybase.min_message_severity = 10
sybase.compatability_mode = Off
                           ; 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 compatability mode will probably not stay around
                           ; forever, so try applying whatever necessary changes to your code,
                           ; and turn it off.

[Sybase-CT]
sybct.allow_persistent = On
sybct.max_persistent = -1
sybct.max_links = -1
sybct.min_server_severity = 10
sybct.min_client_severity = 10

[bcmath]
bcmath.scale =

[browscap]
;browscap   =   extra/browscap.ini

[Informix]
ifx.default_host =
ifx.default_user =
ifx.default_password =
ifx.allow_persistent = On
ifx.max_persistent = -1
ifx.max_links = -1
ifx.textasvarchar =
ifx.byteasvarchar =
ifx.charasvarchar =
                  ; of Informix SE users.
ifx.blobinfile =
                  ; keeping them in memory
ifx.nullformat =
                  ; NULL's are returned as string 'NULL'.

[Session]
session.save_handler = files
session.save_path = "/tmp"
                                    ; in the case of files, this is the
                                    ; path where data files are stored
session.use_cookies = 1
session.name = PHPSESSID
                                    ; name of the session
                                    ; is used as cookie name
session.auto_start =
session.cookie_lifetime =
                                    ; or if 0, until browser is restarted
session.cookie_path = "/"
session.cookie_domain =
session.serialize_handler = php
                                    ; php is the standard serializer of PHP
session.gc_probability = 1
                                    ; 'garbage collection' process is started
                                    ; on every session initialization
session.gc_maxlifetime = 1440
                                    ; data will be seen as 'garbage' and
                                    ; cleaned up by the gc process
session.referer_check =
                                    ; externally stored URLs containing ids
session.entropy_length =
session.entropy_file =
; session.entropy_length    = 16
; session.entropy_file      = /dev/urandom
session.cache_limiter = nocache
                                    ; determine HTTP caching aspects
session.cache_expire = 180
session.use_trans_sid = 1
                                    ; by compiling with --enable-trans-sid

[MSSQL]
mssql.allow_persistent = On
mssql.max_persistent = -1
mssql.max_links = -1
mssql.min_error_severity = 10
mssql.min_message_severity = 10
mssql.compatability_mode = Off

[Assertion]
;assert.active            =   On   ; assert(expr); active by default
;assert.warning            =   On   ; issue a PHP warning for each failed assertion.
;assert.bail            =   Off   ; don't bail out by default.
;assert.callback         =   0   ; user-function to be called if an assertion fails.
;assert.quiet_eval         =   0   ; eval the expression with current error_reporting(). set to true if you want error_reporting(0) around the eval().

[Ingres II]
ingres.allow_persistent = On
ingres.max_persistent = -1
ingres.max_links = -1
ingres.default_database =
ingres.default_user =
ingres.default_password =

[Verisign Payflow Pro]
pfpro.defaulthost = "test.signio.com"
pfpro.defaultport = 443
pfpro.defaulttimeout = 30

; pfpro.proxyaddress      =      ; default proxy IP address (if required)
; pfpro.proxyport         =      ; default proxy port
; pfpro.proxylogon         =      ; default proxy logon
; pfpro.proxypassword      =      ; default proxy password

; Local Variables:
; tab-width: 4
; End:



[Zend]
;zend_optimizer.optimization_level=15
zend_extension_manager.optimizer = "/usr/local/Zend/lib/Optimizer-2_6_2"
zend_extension_manager.optimizer_ts = "/usr/local/Zend/lib/Optimizer_TS-2_6_2"



allow_url_fopen = On

Norv

Are you your own host?

Please make a phpinfo file and tell a link to it.  (What is a phpinfo() file?)
Also, you might try re-uploading the upgrade package files, to make sure none was missed during upload.
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker


Also known as Norv on D* | Norv N. on G+ | Norv on Github

mrich1

Yes, it is my own host.


I will try to ftp to the server again.


Norv

Ah well. PHP 4.4 is an old PHP version, there isn't even support for it anymore if I remember well, and that for a few years.
Though SMF should work, but the problem is that if there's an error, new versions of PHP, more robust, should simply tell the error, while old unmaintained versions might ... crash.
If possible, try upgrading it, to 5.1 at least.
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker


Also known as Norv on D* | Norv N. on G+ | Norv on Github

mrich1


Norv

Please keep us informed, if you wish. :)

EDIT: Ah, I just noticed... mysql API version 3.23, this is not supported by MySQL itself anymore for a long time now, also I'm afraid nobody tests SMF on it anymore... (if I remember well, is not even available for download at mysql.com, at least I searched for it for exactly the purpose of testing SMF installation/upgrade on a few MySQL versions and couldn't find it).
5.0 and 5.1 are MySQL versions to look at, if possible...
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker


Also known as Norv on D* | Norv N. on G+ | Norv on Github

mrich1

 ;) It is to upgrade my server.

I will back to inform you whatever happen.  :D

mrich1

Hi,
I resolved this.

My server has old version of PHP and Mysql so this mak everything hard to upgrade which is
PHP version     4.4.6
MySQL version    4.1.22-standard


But I still need to work on the current machine.

I backup all DB and file and move to another machine which has

PHP version     5.2.10
MySQL version    4.1.22-standard

And make upgrade from 1.1.8 to 1.1.9 to 1.1.10 by easy, and make big upgrade to SMF 2.0 RC1.2 also by easy just one time and finish.


Now I have fresh files and working DB. I backup DB and files then restore to the first machine. Now it works.


I will show you the link in a few day after I finish fix some theme and special tag. My site has size medium-big.

Thanks Norv, just one word about my old MySQL version.

Sorry about my English I will come back to inform you later soon after all online.





Norv

Okay, great! Then you're quite set, including for 2.0 (hopefully), good to hear things worked out! :)
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker


Also known as Norv on D* | Norv N. on G+ | Norv on Github

Advertisement: