RE: Upgrade 1.3.1 to 1.4 problem - Misao - com.mysql.lists.eventum-users

13 messages in com.mysql.lists.eventum-usersRE: Upgrade 1.3.1 to 1.4 problem

From	Sent On	Attachments
Misao	02 Feb 2005 13:15
Jame...@jdpa.com	02 Feb 2005 14:36
Misao	02 Feb 2005 14:48
Jame...@jdpa.com	02 Feb 2005 14:51
Misao	02 Feb 2005 14:59
Jame...@jdpa.com	02 Feb 2005 15:09
Jame...@jdpa.com	02 Feb 2005 15:11
Misao	02 Feb 2005 15:26
Bryan Alsdorf	02 Feb 2005 16:23
Misao	03 Feb 2005 21:48
Misao	08 Feb 2005 10:35
Bryan Alsdorf	08 Feb 2005 14:06
Misao	08 Feb 2005 14:26

Subject:	RE: Upgrade 1.3.1 to 1.4 problem
From:	Misao (misa...@speakeasy.net)
Date:	02/03/2005 09:48:05 PM
List:	com.mysql.lists.eventum-users

I ran all scripts in order. It still messed up.

-----Original Message----- From: Bryan Alsdorf [mailto:bry...@mysql.com] Sent: Wednesday, February 02, 2005 7:24 PM To: Misao Cc: even...@lists.mysql.com Subject: Re: Upgrade 1.3.1 to 1.4 problem

Did you run all the scripts in misc/upgrade/v1.3.1_to_v1.4/ ? Specifically fix_setup_file.php? This script should have update the format of the file.

If for some reason that script didn't work, the format of the file should be '<?php $eventum_setup_string='<encoded string here>'; ?>', as James mentioned.

/bryan

Misao wrote:

Ah, I'll need to remember that trick. Turns out that not only did the script butcher the setup.conf.php, but somehow my permissions needed changed back as well. Looks like it is happy now. Thanks.

-----Original Message----- From: Jame...@jdpa.com [mailto:Jame...@jdpa.com] Sent: Wednesday, February 02, 2005 6:09 PM To: even...@lists.mysql.com Subject: RE: Upgrade 1.3.1 to 1.4 problem

The blank page indicates that there is a PHP error that is being suppressed by configuration settings.

Change the appropriate lines in config.inc.php to the below: ini_set("display_errors", E_ALL); error_reporting(E_ALL);

Those two (redundant) lines should display any errors PHP is encountering. If that doesn't work, again, try to run the page at a shell prompt (php login.php) and see what output you get.

The file only had that string it in, no other stuff. I tried to edit it manually with that, but now the pages are just blank. Looks like the upgrade script did something nasty.

-----Original Message----- From: Jame...@jdpa.com [mailto:Jame...@jdpa.com] Sent: Wednesday, February 02, 2005 5:52 PM To: even...@lists.mysql.com Subject: RE: Upgrade 1.3.1 to 1.4 problem

Well, it looks like the file should contain: <?php $eventum_setup_string='<encoded string here>'; ?>

Is this the case? Or is it just the string by itself (with no "<?php", etc.)? If it was not contained between the php tags, that would explain why it's being printed out and not processed...

On further exploration, I find that the gibberish that displays is actually the contents of the setup.conf.php file. Isn't there supposed to be something else in there? If so, then the upgrade scripts broke it. Any idea how to restore the file?

-----Original Message----- From: Jame...@jdpa.com [mailto:Jame...@jdpa.com] Sent: Wednesday, February 02, 2005 5:37 PM To: even...@lists.mysql.com Subject: RE: Upgrade 1.3.1 to 1.4 problem

The only thing that I would imagine would be encoded like that is cookie data...why you are seeing it, I don't know. Developers could confirm whether any encoded data is stored in cookies.

Try running one of those php pages at a shell prompt and see what happens - perhaps something is dying after headers are sent but before page body is sent.

-----Original Message----- From: Misao [mailto:misa...@speakeasy.net] Sent: Wednesday, February 02, 2005 1:16 PM To: even...@lists.mysql.com Subject: Upgrade 1.3.1 to 1.4 problem

After running the upgrade, all I get at the login and main.php pages is this:

YToyMjp7czoxMjoidG9vbF9jYXB0aW9uIjtzOjg6ImVDUk0gVGl4IjtzOjEzOiJzdXBwb3J0 X2Vt YWlsIjtzOjg6ImRpc2FibGVkIjtzOjEwOiJkYWlseV90aXBzIjtzOjg6ImRpc2FibGVkIjtz OjEz OiJzcGVsbF9jaGVja2VyIjtzOjg6ImRpc2FibGVkIjtzOjE2OiJpcmNfbm90aWZpY2F0aW9u Ijtz Ojg6ImRpc2FibGVkIjtzOjIzOiJhbGxvd191bmFzc2lnbmVkX2lzc3VlcyI7czoyOiJubyI7 czo2 OiJ1cGRhdGUiO3M6MToiMSI7czo2OiJjbG9zZWQiO3M6MToiMSI7czo1OiJub3RlcyI7Tjtz OjY6 ImVtYWlscyI7czoxOiIxIjtzOjU6ImZpbGVzIjtzOjE6IjEiO3M6NDoic210cCI7YTo2Ontz OjQ6 ImZyb20iO3M6MTc6InVtZ2NybUB1bXVzaWMuY29tIjtzOjQ6Imhvc3QiO3M6MjU6Ik1BSUxE Uk9Q LnVzZnNoLlVNVVNJQy5jb20iO3M6NDoicG9ydCI7czoyOiIyNSI7czo0OiJhdXRoIjtzOjE6 IjAi O3M6MTk6InNhdmVfb3V0Z29pbmdfZW1haWwiO3M6MzoieWVzIjtzOjEyOiJzYXZlX2FkZHJl c3Mi O3M6MjM6IkNocmlzLnBydWl0dEB1bXVzaWMuY29tIjt9czoxNToic2NtX2ludGVncmF0aW9u Ijtz Ojg6ImRpc2FibGVkIjtzOjEyOiJjaGVja291dF91cmwiO047czo4OiJkaWZmX3VybCI7Tjtz OjEx OiJvcGVuX3NpZ251cCI7czo4OiJkaXNhYmxlZCI7czoxNzoiYWNjb3VudHNfcHJvamVjdHMi O047 czoxMzoiYWNjb3VudHNfcm9sZSI7TjtzOjEzOiJlbWFpbF9yb3V0aW5nIjthOjE6e3M6Njoi c3Rh dHVzIjtzOjg6ImRpc2FibGVkIjt9czoxMjoibm90ZV9yb3V0aW5nIjthOjE6e3M6Njoic3Rh dHVz IjtzOjg6ImRpc2FibGVkIjt9czoxMToiZW1haWxfZXJyb3IiO2E6Mjp7czo2OiJzdGF0dXMi O3M6 NzoiZW5hYmxlZCI7czo5OiJhZGRyZXNzZXMiO3M6MjM6ImNocmlzLnBydWl0dEB1bXVzaWMu Y29t Ijt9czoxODoiZG93bmxvYWRpbmdfZW1haWxzIjtOO30=

I don't see any error messages, so I'm at a loss as to what to do.

*****************************************************************

This e-mail and any files transmitted with it are confidential

and intended solely for the use of the individual or entity to

which they are addressed. If you have received this in error,

you must not use or disseminate any information contained in it.

Please send it back to the person who sent it to you and delete

it from your system. This footnote also confirms that this e-mail

message has been swept by Sybari's Antigen for the presence of

computer viruses. However, we cannot guarantee that this trans-

mission is virus free, nor can we guarantee that this e-mail is

secure or error-free as information could be intercepted,

corrupted, lost, destroyed, or arrive late or incomplete. J.D.

Power and Associates therefore does not accept liability for loss

or damage suffered as a result of this transmission or for any

errors or omissions in the contents of this e-mail.

*****************************************************************

Are you MySQL certified? www.mysql.com/certification