Errors after Upgrade to 1.1

[lillebror]

Hey everybody,
I upgraded my Serendipity blog to 1.1, but the update failed. The index.php page is just blank. However, I can access the serendipity_admin.php page. There, it seems everything ok, all articles are still there. In addition, I noticed that the style of the plugin section doesn't appear correctly. Only the first 5 or 6 plugins are shown.

Can anybody tell me what went wrong?

Lillebror

[garvinhicking]

Hi!

When you get a blank page this usually means a fatal PHP error. Can you check your error logs from PHP, or contact your provider and ask him to see the setting for PHP.ini "display_errors" and "error_log" is set?

This would help us to trace the problem. In many cases it's just missing read/write privileges or often also a PEAR library inclusion problem.

Sometimes it might also be a .htaccess issue or if you've turned on URL rewriting that URLs can't be found.

HTH,
Garvin

[lillebror]

I tried to write over the files with the last release, 1.0.4. Then, everything functioned and the blog was shown as usual. However, there was still shown that I use version 1.1.

Which read/write privileges are necessary? And how do I check PHP errors?

Lillebror

[garvinhicking]

Hi!

Read-privileges need to be set for all files in the s9y directory, and write privleges are required for the "templates_c" directory.

You can usually check your PHP errors if you have a "logs" subdiretory somewhere on your site, or else you'd need to ask your server provider.

HTH,
Garvin

[magnum80]

Dear Forum members,
last summer I installed my first s9y Blog (1.00). Today I upgraded to 1.1. Although I asked previous to the Upgrade, I did not have proper SQL rights. Here are two screenshots: Before the Upgrade and after the Upgrade. How shall I continue now? I made a SQL dump and a backup of my webspace before the Upgrade.

I haven't changed anything after the failed upgrade yet. I haven't logged in to the admin menu yet, as I am afraid to touch it after the upgrade error messages. The blog itself looks ok on the first look.

I would be very happy and thankful, if someone could help me. Sadly I am a bit of a PHP and SQL noob.

Many thanks and best regards
magnum80

Serendipty kicks butt!

EDIT: I followed the FAQ tip "If you haven't made the backup or want to make it faster, you can do that by:"
I followed the 3 steps for the fast way and changed serendipity_config_local.inc.php back to "1.0".
Now, I see the Upgrade screen again. I am now waiting for my provider to make sure that this time I have the SQL rights.

One question is left:
In the FAQ the following is mentioned:
"However, some providers might not think about that and thus deny you access to your own files. In those cases you also need the script above to change file permissions if you need to manually edit/delete a special file. Note that plugins copied by spartacus and images uploaded via the Serendipity Admin suite are affected by the same problem. You can change the default file/directory of the Spartacus plugin though by it's configuration."

Do I have to do more than only changing the serendipity_config_local.inc.php file (which I did already) before I restart the Upgrade process again?

EDIT2: Got the SQL permissions. Applied the Upgrade again. This is the resulting screen. Are those errors normal for my situation? Or do I need to fix anything?

Thank you so much for any help!

[garvinhicking]

Hi magnum!

You did all things right.

Note that the "INDEX" things are non-critical, so you did not really need to backgrade to 1.0 - instead you could simply execute those SQL queries later via phpMyAdmin, and leave your s9y blog upgraded at 1.1!

The errors you show in your last upgrade are just because some things of the first try had already been executed. But all is well, don't mind those errors. You have the tables now, and that's the important thing.

Best regards,
Garvin

[magnum80]

@Garvin: Thank you so much for your reply! I was so afraid that I screwed up. Man, am I happy to read those lines.

Thanks a lot!!!

[lillebror]

So this is what I got when I again triedto upgrade to version 1.1.

Code: Select all

Bei der Einrichtung der Installation traten einige Fehler auf:

-

CREATE INDEX pluginretr_idx ON serendipity_plugins (placement, sort_order);

/ Duplicate key name 'pluginretr_idx'

create table serendipity_mediaproperties (
  mediaid int(11) not null,
  property varchar(128) not null,
  property_group varchar(50) not null default '',
  property_subgroup varchar(50) not null default '',
  value text
) /*!40100 CHARACTER SET utf8 COLLATE utf8_unicode_ci */;

/ Table 'serendipity_mediaproperties' already exists

CREATE INDEX mediapropid_idx ON serendipity_mediaproperties (mediaid);

/ Duplicate key name 'mediapropid_idx'

CREATE UNIQUE INDEX media_idx ON serendipity_mediaproperties (mediaid, property, property_group, property_subgroup);

/ Duplicate key name 'media_idx'

create table serendipity_options (
  name varchar(255) not null,
  value text not null,
  okey varchar(64) not null default ''
) /*!40100 CHARACTER SET utf8 COLLATE utf8_unicode_ci */;

/ Table 'serendipity_options' already exists

CREATE INDEX options_idx ON serendipity_options (okey);

/ Duplicate key name 'options_idx'

ALTER TABLE serendipity_images ADD COLUMN realname varchar(255) not null default '';

/ Duplicate column name 'realname'

ALTER TABLE serendipity_references ADD COLUMN type varchar(128) not null default '';

/ Duplicate column name 'type'

CREATE INDEX reftype_idx ON serendipity_references (type);

/ Duplicate key name 'reftype_idx'

Die Serendipity-Installation ist nun auf die Version 1.1 aktualisiert!

Here you can see my blog, it shows a blank page again: http://www.lillebror.beeven.de/blog

With previous installations, all went fine, and I even upgraded once. Everything was fine again. Even the first (this was the second one) upgrading to 1.1 passed without errors. But this 1.1 doesn't seem to work, I get a blank page.

About the logs: I have a rewrite log and an access log, which is relevant? I would be pleased if you could help me, too.

Lillebror

[garvinhicking]

Hi!

the error messages indicate that you installed and performed the upgrade twice (because required tables are already existing!)

When you get a blank page, please try to view your apache/php error logs or ask your provider for those logs - this usually means a fatal PHP error happens. Mostly this is caused by missing write privileges to templates_c or missing files that might not have been properly uploaded via FTP.

The rewrite log is irrelevant for this kind of trouble, and access logs only show the accesses to pages but usually no errors...

HTH,
Garvin

[lillebror]

Could it be possible that it is the template which i was using (competition)? However, I asked the sys. administrator for the logs now...