Help for update/upgrade from 1.2.6 to 1.2.8

Balubaer · Post by **Balubaer** » Wed 23. Aug 2006, 00:28

Hi ladies and gents,

I was searching for a update how-to in the 1.2.8 archive desperately. Without success.

Can anyone give me some hints what traps I have to pay attention to?

I think it cannot be so simple to just overwrite the archive content to my webdir, can it? I mean what's with the configuration files on the server? And maybe other files?

I found the upgrade-script in the setup dir but I was a litte bit to unsafe for me just to start the script.

The first two steps of an upgrade a quite clear:

1. make a backup of the database (what I did so far, puh)
2. make a backup of the webdir (I did this too, wow)
3. ... ugh what now?

Thanks guys (and ladies),
Dennis

P.S. I hope I will be able to give something back to the community later.

Pappnase · Post by **Pappnase** » Wed 23. Aug 2006, 00:43

hallo

hast du das schon gelesen

http://www.phpwcms-docu.de/update_1.x.x_de.phtml

Balubaer · Post by **Balubaer** » Wed 23. Aug 2006, 00:52

werd ich mal machen.... wusste nicht, dass die so "universell" einsetzbar ist.

danke erstmal. melde mich ggf. nochmal.

gruß
dennis

Balubaer · Post by **Balubaer** » Thu 24. Aug 2006, 16:01

Hi guys,

I want to give a litte report of my experiences I got while upgrading from version 1.2.6 to 1.2.8 (incl. all patches [last patchC]).

1. I backuped all files and the db... you really don't know what can happen.

2. I copied the files into my webdir and re-configured manually changed files (just a few, like frontend.css, conf.inc.php etc.)
3. I started setup/upgrade.php and selected entry no. 14 (1.2.6-dev to 1.2.7-dev). With this I got an error warning because this script wanted to create the table phpwcms_formtracking which still existed. But I found a difference and maybe a possible error:

the upgrade sql says:

Code: Select all

CREATE TABLE `phpwcms_formtracking` (
  `formtracking_id` INT NOT NULL AUTO_INCREMENT,
  `formtracking_hash` VARCHAR( 50 ) NOT NULL default '',
  `formtracking_ip` VARCHAR( 20 ) NOT NULL default '',
  `formtracking_created` TIMESTAMP(14) NOT NULL,
  `formtracking_sentdate` VARCHAR( 20 ) NOT NULL default '',
  `formtracking_sent` INT( 1 ) NOT NULL DEFAULT '0',
  PRIMARY KEY  (`formtracking_id`)
) TYPE=MyISAM;

but the still existing table says:

Code: Select all

 formtracking_created	timestamp(14)	NULL default NULL

this means, that the existing table allow a NULL value, the new table doesn't, but gives no default value! Maybe an error, Oliver? And what is the better setting? I think it will be the new table (but WITH default value!).

4. After this the upgrade procedure seems to be done. But I detected another error. My sites weren't shown correctly and I found the problem:
in the templates were code lines like

Code: Select all

<!------ Haupt --------------------------------------- //-->

These were parsed in the old version correcly because the old site where coded as

Code: Select all

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

and not as

Code: Select all

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

this is more restrictive so that the comments have to be edited to the form

Code: Select all

<!-- comment text -->

or

Code: Select all

<!-- comment text
over more lines //-->

(I'm not quite sure with this, but it works. Correct me if I'm wrong)

So, hope this helps.

Greetings,
Dennis

ADDITION!!!!
The template for my home sitestructure changed to another one and cannot be changed in the backend! What happens here? (I have to change it in the db by myself!)

Redirected it to a new post:
-> http://www.phpwcms.de/forum/viewtopic.php?p=71212#71212