Udate from S-1.3.1 / PHP 5.2.14 to 1.5.5

[BerlinOS]

Hi,

first of all - thank you for the great blog system !

I have to update from 1.3.1 on PHP 5.2.14 to 1.5.5.

For securety reasons i have created a copy of the complete system for update.

Are there any changes to the database structure ? Because the moderators will post some news in the original blog and i want to import the changes to the updated copy after the update. Are there differences between the Database in 1.3.1 and 1.5.5 ?

If so, can i copy only the entries table from the 1.3.1 version to 1.5.5 ?

Thank you for any help.

Oliver

[Timbalu]

I have to update from 1.3.1 on PHP 5.2.14 to 1.5.5.

Whow this has quite a museal character.

For securety reasons i have created a copy of the complete system for update.

good. Did you make a dump of the database and safed your template too?

Are there any chnages to the database structure ? Because the moderators will post some news in the original blog and i want to import the changes to the updated copy after the update. Are there differences between the Database in 1.3.1 and 1.5.5 ?

I am sure there are. But in most common cases the update will do everything you need to keep the old and then updated database tables.

If so, can i copy only the entries table from the 1.3.1 version to 1.5.5 ?

This depends on the changes. I would be careful doing it this way.

[BerlinOS]

Yeah, i am updating a few year old blog. I hope everything will work after that (is a friends blog).

I have copied the complete php structure on the server to a second folder (including the templates).
I have set up a new database with a complete DUMP of the DB (wow... the Spam section was 900 MB big). After some configuration the copy is now functional.

From your Update note:

Notes on updating from 0.8 / 0.9 / 1.0 / 1.1 / 1.2 and above

No specific tasks are required to update Serendipity versions after 0.8 to the current ones. The complete upgrade path is automatted and can be performed with a single mouse click.

When I upload the new files of S 1.5.5 - do i have to start the update process by doing something ? Do I need to log into the admin area and start the update (the "single mouse click")?

[Timbalu]

No, no need. Just copy the new over old and open your normal blog url.
Do not forget write access to some dirs and files, see DOCS & FAQ.
Then you will be asked to upgrade.

Is there any need to have a new db, version update or similar?
If not, keep the old and run the update. Just truncate the spamlog.

[BerlinOS]

Hi,

On my save copy of the blog everything worked fine and the update was a one click experience.

Now I updated the original blog and have a problem:

I uploaded all files to the server and have write access to all needed files and folders.
I visited the blog startpage and the YOU NEED TO UPDATE... message was there.
I deleted the blog-cockie.
I visited the admin area and came to the new styled admin area, named like the blog = there is database access.
No Errors where reported on the Install Check page, all folders where writable.

THE PROBLEM: I can not log in with the Admin user name / password.
It says that it is a wrong pass or user name. On different browsers (Firefox & Safari).

I have tested two Admin accounts, both seem to be defect.
They are still in the DB under _s.._authors.

The blog is visible again and all entries are visible,
but i think i got stuck in the update process because I can not log in to the system.

What can be the problem and how do I get it to work ? I hope you can help me out.

Update:

I have created the test.php as mentioned here

http://board.s9y.org/viewtopic.php?f=3& ... #p10424763

I get following message ( .... part):

Found user with password: 854aecd0......cfdd30a25 and hashtype:
Expected password: e386e2e69......9d1053ba26cf1a

Can I create a new Admin Pass in the DB or should I run the script mentioned here ?

http://board.s9y.org/viewtopic.php?f=1&t=17712&start=15

Greetings

Oliver

[garvinhicking]

Hi!

Yes, you should run that fixlogin script!

Regards,
Garvin

[BerlinOS]

Dear Garvin,

thank you for answering.
I run the fixlogin.php and got following message (....... part):

UPDATE serendipity_authors SET password = 'e386e2e69a4a1.......1053ba26cf1a', hashtype=1 WHERE username = 'Admin'
/ Unknown column 'hashtype' in 'field list'Password changed.

Sadly I still can not log into the system, I used the old password and I get again WRONG PASS OR NAME.

I used the original password that was chosen by the first Admin and the password is including brackets like= (mypassword)

Can this special character ( ) cause the problem ?

The update seems to be partial done, I have Serendipity 1.5.5 und PHP 5.2.17 mentioned on the Admin login page. At which point the DB gets updated ? Is the DB update done:

# when I click on the blog startpage the YOU NEED TO UPDATE YOUR BLOG link,
# when I see the NO ERRORS Message on the admin area or
# after I log into the Admin area (what I can not since the Update).

Can I check if the DB is already updated and how can I create a working Admin Password ?
Thank you for any help.

Kind regards,
Oliver

[garvinhicking]

Hi!

When the "hashtype" column is not in the "serendipity_authors" DB table, that means the DB upgrade either failed or was not executed.

Please check if the sql/ subdirectory contains all the .sql files that come with s9y 1.5.5. Then edit your serendipity_config_local.inc.php and set versionInstalled to "1.3.1" again. Then go to the admin area. There you should see the upgrader. Confirm the upgrader, which should properly execute the DB upgrades.

The upgrade is only executed if you click the "Yes, perform updates" button on the admin-like page you see.

After that is done, you can try to use the fixlogin.php script properly.

HTH,
Garvin

[BerlinOS]

Dear Garvin, you made my day! I am back in the Admin area. The second time the update was executed complete, I did not need to use the fixlogin.php.

The spamlog in the original DB is 950 MB big - can I empty the table without getting into trouble ?

The book "Peacocks Manifest. Roadnovel" is on the way to you, I found it on your wishlist.

Also many thanks to Ian for the initial help. You´r great guys.

Oliver

[garvinhicking]

Hi!

Great to hear that! Yes, you can empty the spamlog table without problems. It's only for logging, so as long as you don't want to look inside the log, you don't need it anymore

Thanks a lot for taking a look on my wishlist! I'm eagerly waiting and hope it's a nice read

Best regards,
Garvin

[BerlinOS]

cheers, have fun reading. but...

wowowow... NOW i got a problem...

I have German blog language in front- and backend.
I was creating a static page with the "static page plugin" and i called it Aktivitäten in the title.
Then I created a link in the head navigation menu called Aktivitäten (with German Umlaut) at style options in admin area, I use the bulletproof template.

After reloading the blog ALL ENTRIES AND DATABASE STORED TEXT is encrypted to something like this:

Unter dem Motto "Freilichtkino an Originalschauplätzen" startet Potsdam nach einem verregneten Juli im August neu durch. Die Meteorologen kündigen besseres Wetter an und die Nächte werden früher dunkel, was für open-air Filmvorführungen von Vorteil ist.

Heres the blog: http://www.baf-berlin.de/blog/

What has happened, is there a Bug inside the static pages plugin or at the navigation options of bulletproof template options? I am sure it happened by creating the Umlaute page or navigation. Please help me out, the blog owner gets crazy about it.

Yours, (in panic) Oliver

[garvinhicking]

Hi!

You most probably have done one of these things:

* You changed in your global configuration the charset to native instead of UTF-8
* You disabled the "Use database charsets" option

Changing back one of these configuration variables should again fix it for you. Most probably, you changed the first thing...

Regards,
Garvin

[BerlinOS]

Hi,

The "Use database charsets" aka "Datenbank-Zeichensatzkonvertierung aktivieren" option was ON.
After switch to OFF it worked as usual.

I am happy to have it working again. Your book is on the way since Friday. Have fun!

Oliver, (reaxed again)