DB Update release 1.3.3 - 1.5

Alle installationsbezogenen Probleme hier posten. Dies sollte die erste Anlaufstelle bei Problemen sein.
User avatar
Nobbes
Posts: 10
Joined: Mon 18. Feb 2008, 09:33
Location: Leimen / St Ilgen

DB Update release 1.3.3 - 1.5

Post by Nobbes »

Hallo zusammen....
Ich habe auf meinem Lokalen (Xampp bzw. Lampp unter Linux) Testserver eine Testinstallation aufgesetzt und dann ein DB Update wie unter http://forum.phpwcms.org/viewtopic.php?f=16&t=17104 beschrieben durchgeführt.
Folgende Fehlermeldungen sind aufgetreten..... Kann ich diese Fehlermeldungen ignorieren bzw. was ist zu tun???
Ich will demnächst eine neue Installation auf einem Webserver mit allen Updates durchführen ..... die sollte wenn möglich fehlerfrei funtzen .... denn von SQL hab ich bisher leider noch wenig Ahnung. :roll:
Danke im voraus für eure Hilfe!!!

Code: Select all

Update Log:
--------------------------------------------
Upgrade release 1.3.3 to 1.3.4
Fehlermeldung:
 
Keine Fehler festgestellt...........

--------------------------------------------
Upgrade release 1.3.4 to 1.3.5
Fehlermeldung:

ERROR: Duplicate column name 'acat_overwrite' -> #
#


ALTER TABLE `phpwcms_articlecat` ADD `acat_overwrite` VARCHAR( 255 ) NOT NULL;
ERROR: Duplicate column name 'acontent_paginate_page' -> ALTER TABLE `phpwcms_articlecontent` ADD `acontent_paginate_page` INT( 5 ) UNSIGNED NOT NULL;
ERROR: Duplicate column name 'acontent_paginate_title' -> ALTER TABLE `phpwcms_articlecontent` ADD `acontent_paginate_title` VARCHAR( 255 ) NOT NULL;
ALTER TABLE `phpwcms_articlecontent` ADD INDEX ( `acontent_paginate_page` );

--------------------------------------------
Upgrade release 1.3.5 to 1.3.5.1
Fehlermeldung:

ERROR: Table 'cms_test.phpwcms_categories' doesn't exist -> #
#


ALTER TABLE `phpwcms_categories` ADD `cat_pid` INT( 11 ) NOT NULL AFTER `cat_type`;
ERROR: Table 'cms_test.phpwcms_categories' doesn't exist -> ALTER TABLE `phpwcms_categories` ADD INDEX ( `cat_pid` );
ERROR: Table 'phpwcms_log' already exists -> CREATE TABLE `phpwcms_log` (
  `log_id` int(11) NOT NULL auto_increment,
  `log_type` varchar(255) NOT NULL,
  `log_timestamp` timestamp NOT NULL,
  `log_message` text NOT NULL,
  `log_ip` varchar(50) NOT NULL,
  `log_userid` varchar(255) NOT NULL,
  PRIMARY KEY  (`log_id`)
) TYPE=MyISAM;
ALTER TABLE `phpwcms_guestbook` CHANGE `guestbook_created` `guestbook_created` INT(11) NOT NULL;
ALTER TABLE `phpwcms_userlog` CHANGE `logged_change` `logged_change` INT(11) DEFAULT '0' NOT NULL;
ALTER TABLE `phpwcms_userlog` CHANGE `logged_start` `logged_start` INT(11) DEFAULT '0' NOT NULL;
ALTER TABLE `phpwcms_articlecat` CHANGE `acat_alias` `acat_alias` VARCHAR(255) NOT NULL;
ALTER TABLE `phpwcms_articlecat` DROP INDEX `acat_alias`, ADD INDEX `acat_alias` (`acat_alias`);
ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE `phpwcms_file` DROP INDEX `f_shortinfo`, ADD INDEX `f_shortinfo` (`f' at line 2 -> ALTER TABLE `phpwcms_file` DROP INDEX `f_name`, ADD INDEX `f_name` (`f_name`)
ALTER TABLE `phpwcms_file` DROP INDEX `f_shortinfo`, ADD INDEX `f_shortinfo` (`f_shortinfo`);

-------------------------------------------------
Upgrade release 1.3.5.1 to 1.5


#
#


ALTER TABLE `phpwcms_articlecat` ADD `acat_archive` INT( 1 ) NOT NULL DEFAULT '0';
ALTER TABLE `phpwcms_articlecat` ADD INDEX ( `acat_archive` );
ALTER TABLE `phpwcms_article` ADD `article_archive_status` INT( 1 ) NOT NULL DEFAULT '1';
ALTER TABLE `phpwcms_article` ADD INDEX ( `article_archive_status` );
ALTER TABLE `phpwcms_articlecontent` ADD `acontent_category` VARCHAR( 255 ) NOT NULL;
ALTER TABLE `phpwcms_file` CHANGE `f_cat` `f_cat` VARCHAR( 255 ) NOT NULL;
ALTER TABLE `phpwcms_file` CHANGE `f_changed` `f_changed` INT NOT NULL DEFAULT '0';
ALTER TABLE `phpwcms_file` CHANGE `f_created` `f_created` INT NOT NULL DEFAULT '0';
ALTER TABLE `phpwcms_file` DROP `f_log`;
ALTER TABLE `phpwcms_file` CHANGE `f_longinfo` `f_longinfo` TEXT NOT NULL;
ALTER TABLE `phpwcms_file` ADD `f_copyright` VARCHAR( 255 ) NOT NULL;
ALTER TABLE `phpwcms_file` ADD `f_tags` VARCHAR( 255 ) NOT NULL;
ALTER TABLE `phpwcms_file` CHANGE `f_size` `f_size` INT( 15 ) UNSIGNED NOT NULL DEFAULT '0';
ERROR: Table 'cms_test.phpwcms_calendar' doesn't exist -> ALTER TABLE `phpwcms_calendar` ADD `calendar_lang` VARCHAR( 255 ) NOT NULL;
ERROR: Table 'cms_test.phpwcms_calendar' doesn't exist -> ALTER TABLE `phpwcms_calendar` ADD INDEX ( `calendar_lang` );
ALTER TABLE `phpwcms_file` ADD `f_granted` INT NOT NULL DEFAULT '0';
ALTER TABLE `phpwcms_file` ADD INDEX ( `f_granted` );
ALTER TABLE `phpwcms_articlecontent` ADD `acontent_granted` INT NOT NULL DEFAULT '0';
ALTER TABLE `phpwcms_articlecontent` ADD INDEX ( `acontent_granted` );
ERROR: Table 'cms_test.phpwcms_calendar' doesn't exist -> ALTER TABLE `phpwcms_calendar` ADD `calendar_teaser` TEXT NOT NULL AFTER `calendar_where`;
Meine mit phpwcms erstellten Webseiten:
http://stv-stilgen.de/cms - http://www.tv-st-ilgen.de/cms
Linux - Ubuntu 8.04 LTS & Win XP
phpwcms - v1.3.3 aufwärts
User avatar
juergen
Moderator
Posts: 4556
Joined: Mon 10. Jan 2005, 18:10
Location: Weinheim
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by juergen »

Mach mal folgendes extra:

Code: Select all

CREATE TABLE `phpwcms_calendar` (
  `calendar_id` int(11) NOT NULL auto_increment,
  `calendar_created` datetime NOT NULL default '0000-00-00 00:00:00',
  `calendar_changed` datetime NOT NULL default '0000-00-00 00:00:00',
  `calendar_status` int(1) NOT NULL default '0',
  `calendar_start` datetime NOT NULL default '0000-00-00 00:00:00',
  `calendar_end` datetime NOT NULL default '0000-00-00 00:00:00',
  `calendar_allday` int(1) NOT NULL default '0',
  `calendar_range` int(1) NOT NULL default '0',
  `calendar_range_start` date NOT NULL default '0000-00-00',
  `calendar_range_end` date NOT NULL default '0000-00-00',
  `calendar_title` varchar(255) collate latin1_german1_ci NOT NULL default '',
  `calendar_where` varchar(255) collate latin1_german1_ci NOT NULL default '',
  `calendar_teaser` text collate latin1_german1_ci NOT NULL,
  `calendar_text` mediumtext collate latin1_german1_ci NOT NULL,
  `calendar_tag` varchar(255) collate latin1_german1_ci NOT NULL default '',
  `calendar_object` longtext collate latin1_german1_ci NOT NULL,
  `calendar_refid` int(11) NOT NULL default '0',
  `calendar_lang` varchar(255) collate latin1_german1_ci NOT NULL,
  PRIMARY KEY  (`calendar_id`),
  KEY `calendar_status` (`calendar_status`),
  KEY `calendar_start` (`calendar_start`),
  KEY `calendar_end` (`calendar_end`),
  KEY `calendar_tag` (`calendar_tag`),
  KEY `calendar_refid` (`calendar_refid`),
  KEY `calendar_range` (`calendar_range`),
  KEY `calendar_lang` (`calendar_lang`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_german1_ci AUTO_INCREMENT=1 ;

Code: Select all

CREATE TABLE `phpwcms_categories` (
  `cat_id` int(10) unsigned NOT NULL auto_increment,
  `cat_type` varchar(255) collate latin1_german1_ci NOT NULL default '',
  `cat_pid` int(11) NOT NULL default '0',
  `cat_status` int(1) NOT NULL default '0',
  `cat_createdate` datetime NOT NULL default '0000-00-00 00:00:00',
  `cat_changedate` datetime NOT NULL default '0000-00-00 00:00:00',
  `cat_name` varchar(255) collate latin1_german1_ci NOT NULL default '',
  `cat_info` text collate latin1_german1_ci NOT NULL,
  PRIMARY KEY  (`cat_id`),
  KEY `cat_type` (`cat_type`,`cat_status`),
  KEY `cat_pid` (`cat_pid`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 COLLATE=latin1_german1_ci AUTO_INCREMENT=1 ;
Und vergiss nicht das mit deinem cms_dingsda prepend noch hinein zu editieren.

Du hast zwei Möglichkeiten:

Es geht, oder es geht nicht .. passieren kann dir eigentlich wenig, insbesondere dann, wenn es eine Versuchsinstall ist.

Mach das update nochmal, wenn du die beiden Tabellen händisch da rein getan hast. DUPLICATE heisst in etwa dass das zu ergänzende Feld schon vorhanden ist ...

Achja .. diese Version ist für Standard deutsch latin1 Installationen ....
User avatar
Nobbes
Posts: 10
Joined: Mon 18. Feb 2008, 09:33
Location: Leimen / St Ilgen

Re: DB Update release 1.3.3 - 1.5

Post by Nobbes »

Vieeelen Dank für die schnelle Nachbarschaftshilfe....
Ich werde mir das ganze über das Wochenende mal ansehen.
Bin leider kurzfristig mit Terminen abgedichtet worden.
Wenn ich noch Fragen habe oder nicht klar komme Poste ich hier noch mal.

Gruß und Danke!
Nobbes
Meine mit phpwcms erstellten Webseiten:
http://stv-stilgen.de/cms - http://www.tv-st-ilgen.de/cms
Linux - Ubuntu 8.04 LTS & Win XP
phpwcms - v1.3.3 aufwärts
User avatar
StudioZ
Posts: 802
Joined: Fri 28. May 2004, 19:57
Location: Québec, Canada
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by StudioZ »

HeY Ho! :roll:
Could anyone translate the essence of this thread.
I have the feeling that it has something to do with my problem ugrading 1.3.3 to the latest dev :shock:

Thanks ! :wink:
Image
PhpWCMS Evangelist, -- iRoutier.com Running phpWCMS 1.4.2, r354 -> Great Version!!!!
User avatar
Jensensen
Posts: 3000
Joined: Tue 17. Oct 2006, 21:11
Location: auf der mlauer

Re: DB Update release 1.3.3 - 1.5

Post by Jensensen »

Hi StudioZ,

nothing dramatic, so far. Well, we all wait for an answer of Nobbes who obviously tried an update from v1.3.3 to v.1.3.9 (DEV r_xyz).

btw: Version 1.5 does not exist! (typo)

abstracts in brief:
MySQL update scripts
v1.3.3 to v1.3.4 --> no prob
v1.3.4 to v1.3.5 --> errors...!

see code boxes above.

DF6IH suggestions was to do/try this MySQL inserts additionally: (see above)
http://forum.phpwcms.org/viewtopic.php? ... 49#p103408

but, which are for "COLLATE=latin1_german1_ci" ONLY!!! (can/must be changed for your needs)

Still we have no feedback whether DF6IH's tip could solve it or whether the problem was related to Nobbes' server settings or else....?
{so_much} | Knick-Knack. | GitHub
Umlaute im URL sind meistens immer Kacke.
User avatar
StudioZ
Posts: 802
Joined: Fri 28. May 2004, 19:57
Location: Québec, Canada
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by StudioZ »

Thank you Jensensen for this much appreciated translation and summary 8)

Cheers,
Image
PhpWCMS Evangelist, -- iRoutier.com Running phpWCMS 1.4.2, r354 -> Great Version!!!!
User avatar
Jensensen
Posts: 3000
Joined: Tue 17. Oct 2006, 21:11
Location: auf der mlauer

Re: DB Update release 1.3.3 - 1.5

Post by Jensensen »

Jensensen wrote:...nothing dramatic, so far...
Hey, Nobbes got stuck on the half way - during update! Everyone who experienced similar problems know: THIS IS extremely DRAMATIC!
Sorry, don't get me wrong!

I used this expression only, because we don't know if Nobbes could solve meanwhile or why the errors occurred, generally vs. just in the case of...???
Otherwise there would be a solution like: upon the advice of ... for an update of v1.3.3 always use ... do this but not...

i mean
"nothing dramatic" = since there is no evidence (commonly) of ....
Last edited by Jensensen on Fri 9. May 2008, 10:30, edited 1 time in total.
{so_much} | Knick-Knack. | GitHub
Umlaute im URL sind meistens immer Kacke.
User avatar
juergen
Moderator
Posts: 4556
Joined: Mon 10. Jan 2005, 18:10
Location: Weinheim
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by juergen »

Nobbes wrote: Ich werde mir das ganze über das Wochenende mal ansehen.
:idea: de->en Wochenende-> Weekend .. stay tuned :mrgreen:
User avatar
update
Moderator
Posts: 6455
Joined: Mon 10. Jan 2005, 17:29
Location: germany / outdoor

Re: DB Update release 1.3.3 - 1.5

Post by update »

en: ROFLMAO --> de: Ich schmeiss' mich weg :mrgreen:

PS: not to be tahen seriously, please --> bitte nicht ernst nehmen, bitte
en: Since this forum tends to become more and more some german show (what a pity !!) there indeed is a need for more transparency for english speaking people
de: guess what ;)
It's mostly all about maintaining two or three customer's sites Still supporter for the band Mykket Morton. Visit Mykket Morton on FB. Listen Mykket Morton and live videos on youtube.
Now building a venue for young artists to get wet on stage, rehearsal rooms, a studio, a guitar shop - yes I'm going to build some guitars.
User avatar
juergen
Moderator
Posts: 4556
Joined: Mon 10. Jan 2005, 18:10
Location: Weinheim
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by juergen »

Jensensen wrote:Hi StudioZ,

nothing dramatic, so far. Well, we all wait for an answer of Nobbes who obviously tried an update from v1.3.3 to v.1.3.9 (DEV r_xyz).

btw: Version 1.5 does not exist! (typo)

abstracts in brief:
MySQL update scripts
v1.3.3 to v1.3.4 --> no prob
v1.3.4 to v1.3.5 --> errors...!

Code: Select all

#####################################################
#
#  PHPWCMS SQL Update
#  
#  Upgrade release 1.3.4 to 1.3.5
#
#####################################################


ALTER TABLE `phpwcms_articlecat` ADD `acat_overwrite` VARCHAR( 255 ) NOT NULL ;
ALTER TABLE `phpwcms_articlecontent` ADD `acontent_paginate_page` INT( 5 ) UNSIGNED NOT NULL ;
ALTER TABLE `phpwcms_articlecontent` ADD `acontent_paginate_title` VARCHAR( 255 ) NOT NULL ;
ALTER TABLE `phpwcms_articlecontent` ADD INDEX ( `acontent_paginate_page` ) ;
May be done by hand as well
Jensensen wrote: see code boxes above.

DF6IH suggestions was to do/try this MySQL inserts additionally: (see above)
http://forum.phpwcms.org/viewtopic.php? ... 49#p103408

but, which are for "COLLATE=latin1_german1_ci" ONLY!!! (can/must be changed for your needs)

Still we have no feedback whether DF6IH's tip could solve it or whether the problem was related to Nobbes' server settings or else....?
Yes, if other standard collations (where servers settings equal wcms settings) no need so leave this blank.....

and ! you can easily do all the steps in phpmyadmin and see what are the problems . ...

So you can go through 1.3.3 ----> 1.5 in any case... where sql is not so old.,..

Alors Yves .. c*est ca :oops:
User avatar
Nobbes
Posts: 10
Joined: Mon 18. Feb 2008, 09:33
Location: Leimen / St Ilgen

Re: DB Update release 1.3.3 - 1.5

Post by Nobbes »

Ach du lieber Himmel, habe ich da was losgetreten? :oops:
Ich komme wie gesagt erst am Wochenende dazu die og. Änderungen zu testen.
Ob ich das letztlich hin bekomme ist noch fraglich da ich generell php und SQL Anfänger bin.... leider ich muss noch sehr viel lernen.
Also bitte bitte nicht schlagen wenn ich mich bezüglich der SQL und Release- Versionen eventuell verhaspelt habe.
Auch das muss ich anscheinend erst noch mal prüfen.
Ich werde die ganze Installation noch mal sauber auf meinem Web- Server aufsetzen und alle Updates durchführen.
Genauere Infos bezüglich der php und SQL Version von meinem Webserver werde ich dann auch mitteilen..... versprochen!
Ich hoffe ich habe kein Chaos angerichtet....

P.s. Leider ist mein Englisch eher mittelmäßig. Vermutlich brauche ich demnächst dann auch mal nen Dolmetscher :(
Meine mit phpwcms erstellten Webseiten:
http://stv-stilgen.de/cms - http://www.tv-st-ilgen.de/cms
Linux - Ubuntu 8.04 LTS & Win XP
phpwcms - v1.3.3 aufwärts
User avatar
axelko
Posts: 138
Joined: Mon 27. Feb 2006, 22:51
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by axelko »

Hi,

I saw that OG posrted in svn r171 which has the description: Some optimizations to handle upgrade from 1.3.3 in the better way'.
I tried the upgrade from v1.3.3 and the good news is that the database upgrades were ok except 2 index errors (upgrade 20_1.3.5_to_1.3.5.1), but the indexes were created when I checked in phpMyadmin

Code: Select all

ERROR: Can't DROP 'acat_alias'; check that column/key exists -> ALTER TABLE `phpwcms_articlecat` DROP INDEX `acat_alias`, ADD INDEX `acat_alias` (`acat_alias`);
ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE `phpwcms_file` DROP INDEX `f_shortinfo`, ADD INDEX `f_shortinfo` (`f' at line 2 -> ALTER TABLE `phpwcms_file` DROP INDEX `f_name`, ADD INDEX `f_name` (`f_name`)
The only problem I have now is that no articles are shown and in the backend under articles I get this error

Code: Select all

 {STATUS_MESSAGE} 
  error while browsing related articles  
and in the frontend articles with categorie aliasses (aka index.php?category_whatever) aren't shown, I just get the phpwcms template with an empty article. The only way to access an article is to go via the 'Home Centre' and click on the last edited pages and then preview it (aka index.php?id=571,880,0,0,1,0), editing is possible but I'am not able to save.

I'll now try a new fresh install and import the database and see what it brings. And I know that the svn version isn't supported, but reading this thread I thought this could be helpfull.

Greetz,

Axel
-------------------------------
User avatar
axelko
Posts: 138
Joined: Mon 27. Feb 2006, 22:51
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by axelko »

Hi, I wasn't paying attention, but this thread is continued here http://forum.phpwcms.org/viewtopic.php?f=1&t=17163

Greetz,

Axel
-------------------------------
User avatar
StudioZ
Posts: 802
Joined: Fri 28. May 2004, 19:57
Location: Québec, Canada
Contact:

Re: DB Update release 1.3.3 - 1.5

Post by StudioZ »

This issue is now solved.
Thanks to Oliver for quickly integrating it.
[SQL] Upgrade from 1.3.3 to 1.3.9 r170 -> TESTED
http://forum.phpwcms.org/viewtopic.php?f=1&t=17163

Cheers,

Yves
Image
PhpWCMS Evangelist, -- iRoutier.com Running phpWCMS 1.4.2, r354 -> Great Version!!!!
User avatar
Nobbes
Posts: 10
Joined: Mon 18. Feb 2008, 09:33
Location: Leimen / St Ilgen

Re: DB Update release 1.3.3 - 1.5

Post by Nobbes »

Hallo....
Ich habe inzwischen witziger weise die selbe Erfahrung wie von Axel beschrieben gemacht.
Siehe: http://forum.phpwcms.org/viewtopic.php? ... 49#p103534
Ich habe eine neue saubere Installation auf meinem Webserver mit den geänderten Datensätzen aus r171.
Soweit alles wunderbar verlaufen. Jedoch bei Upgrade release 1.3.5 to 1.3.5.1 wie bei Axel folgender Fehler:

Code: Select all

ALTER TABLE `phpwcms_articlecat` DROP INDEX `acat_alias`, ADD INDEX `acat_alias` (`acat_alias`);
ERROR: You have an error in your SQL syntax.  Check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE `phpwcms_file` DROP INDEX `f_shortinfo`, ADD INDEX  -> ALTER TABLE `phpwcms_file` DROP INDEX `f_name`, ADD INDEX `f_name` (`f_name`)
ALTER TABLE `phpwcms_file` DROP INDEX `f_shortinfo`, ADD INDEX `f_shortinfo` (`f_shortinfo`); 
OK. der Fehler ist mitlerweile erkannt und wie von Studio Z beschrieben geändert.
Frage:
Kann ich das korrigierte DB Setup "Upgrade release 1.3.5 to 1.3.5.1" einfach noch mal komplett durchführen oder muss man wirklich in php admin die Änderung von Hand ausführen.
Wenn ja wäre das übel, da trau ich mich noch nicht wirklich ran...... :cry:
Ach ja. Ich brauchs zwar nicht.... aber das Shop- Modul ist anscheinend auch nicht mehr funktionsfähig.
Diverse andere Fehler (und da hab ich schon was...) melde ich dann im phpwcms Support Deutsch.

Hier noch mal zur Info meine Server Einstellungen:
system: Linux infong 2.4 #1 SMP Wed Sep 26 00:19:50 CEST 2007 i686 GNU/Linux
server: Apache/1.3.34 Ben-SSL/1.55
php: v4.4.8
mysql: 5.0.32 (is just client information, server might be different)
path: ############################
php.ini: register_globals = On -> should always be set Off because of security risks
safe_mode = Off -> good when you want to use ImageMagick, may have some security risks
GD = On -> bundled (2.0.28 compatible)

Gruß
Nobbes
Meine mit phpwcms erstellten Webseiten:
http://stv-stilgen.de/cms - http://www.tv-st-ilgen.de/cms
Linux - Ubuntu 8.04 LTS & Win XP
phpwcms - v1.3.3 aufwärts
Post Reply