Upgradeproblem...

tellus · Post by **tellus** » Sat 30. Jun 2007, 20:12

I have a little upgradeproblem, after I have upgraded a page from 1.2.6DEV to the latest version. When I try to add a contentpart, I got this error message:

error while creating new article content: Unknown column 'acontent_created' in 'field list'

How do I fix that?

/Anders

Post by **flip-flop** » Sat 30. Jun 2007, 20:40

Hi tellus,

please use the search function.

-> http://www.phpwcms.de/forum/viewtopic.php?p=85460#85460

Knut

Jensensen · Post by **Jensensen** » Sat 30. Jun 2007, 20:41

Hi tellus,

http://www.phpwcms.de/forum/viewtopic.p ... entcreated

or try search - there r some entires to b found (in german, too)

greetz

PS: happy mitsommar til sverige. hope you have fine weather --> more than we in germany

tellus · Post by **tellus** » Mon 2. Jul 2007, 13:36

thanks, problem solved. the midsummer was very nice, the sun was not shinning, but it was no reign either. (exuse me for my bad english).

One oher thing, after I upgraded the page all symbols in articlelistning was replaced whith bullets http://www.jrtc.se/index.php?klubben
how do to change it back?

/Anders

Jensensen · Post by **Jensensen** » Mon 2. Jul 2007, 14:36

don't know, but check html output AND adjust CSS!!

be sure to edit your templates, which are used for CPs since v1.1.3 very often.

have a look for the files in
/template/

especially in
/template/inc_cntpart/
/template/inc_default/

and
/config/phpwcms/conf.template_default.inc.php
/template/inc_settings/template_default/custom_settings.php

one thing at least:
better use NAV_LIST_UL as your replacement tag (RT) for menus anywhere

greetz

tellus · Post by **tellus** » Mon 2. Jul 2007, 20:54

Another error, all contents in filelist are gone, only the ones who is put there after the upgrade are visible...

/Anders

http://www.jrtc.se/index.php?aid=21

wastl · Post by **wastl** » Fri 27. Jul 2007, 09:02

I guess this has to do with the database update you just run the DB update again and it is hopefully solved.

Pappnase · Post by **Pappnase** » Fri 27. Jul 2007, 09:20

wastl wrote:I guess this has to do with the database update you just run the DB update again and it is hopefully solved.

hello

one question did you run all database updates from 1.2.6 to 1.3.3 via the upgrade script ?

Code: Select all

14__1.2.6-DEV_to_1.2.7-DEV.sql
15__1.2.7-DEV_to_1.2.9.sql
16__1.2.9-DEV_to_1.3.0.sql
17__1.3.0_to_1.3.2.sql
18__1.3.2_to_1.3.3.sql

Post by **flip-flop** » Fri 27. Jul 2007, 09:37

Important: Please have a look into the generated output during the DB update.

Is/was there any error message (Scrolling the window of the output field)?

This very important check is the most unattended job by user.

Knut

Upgradeproblem...

Upgradeproblem...

Upgrade

Re: Upgrade