Package export from 3.8.6 to 4.0 failed

Previous topic

Install & configuration

Next topic

Author	Message
Sébastien Antoniotti	Friday 08 February 2008 1:54:30 am Hi, I'm trying to export all classes and content object from my existing 3.8.6 website to a clean install of a 4.0. I made the content classes package on the 3.8.6, and imported him into the 4.0, but when I click on the install button, I get this error : Fatal error: Call to a member function unserializeContentClassAttribute() on a non-object in D:\wamp\www\ezp4\kernel\classes\packagehandlers\ezcontentclass\ezcontentclasspackagehandler.php on line 364 Do you think that is a bug or rather an error of configuration ? eZ Publish Freelance web : http://www.webaxis.fr
Xavier Serna	Monday 11 February 2008 12:54:02 am Hi Sébastien, I believe that you should follow the upgrade process in order to use 4.0 as the contentclasses management (among other things, of course) has changed since 3.8.x so I think the better way is to follow the upgrade process fro 3.8.x -> 3.9.x -> 3.10.x and then finally 4.0 hth! -- Xavier Serna eZ Publish Certified Developer Departament de Software Microblau S.L. - http://www.microblau.net +34 937 466 205
Sébastien Antoniotti	Monday 11 February 2008 7:08:52 am Ok thanks I'll try this ;) eZ Publish Freelance web : http://www.webaxis.fr

Author

Message

Sébastien Antoniotti

Friday 08 February 2008 1:54:30 am

Hi,

I'm trying to export all classes and content object from my existing 3.8.6 website to a clean install of a 4.0.

I made the content classes package on the 3.8.6, and imported him into the 4.0, but when I click on the install button, I get this error :

Fatal error: Call to a member function unserializeContentClassAttribute() on a non-object in D:\wamp\www\ezp4\kernel\classes\packagehandlers\ezcontentclass\ezcontentclasspackagehandler.php on line 364

Do you think that is a bug or rather an error of configuration ?

eZ Publish Freelance
web : http://www.webaxis.fr

Xavier Serna

Monday 11 February 2008 12:54:02 am

Hi Sébastien,

I believe that you should follow the upgrade process in order to use 4.0 as the contentclasses management (among other things, of course) has changed since 3.8.x so I think the better way is to follow the upgrade process fro 3.8.x -> 3.9.x -> 3.10.x and then finally 4.0

hth!

--
Xavier Serna
eZ Publish Certified Developer
Departament de Software
Microblau S.L. - http://www.microblau.net
+34 937 466 205

Sébastien Antoniotti

Monday 11 February 2008 7:08:52 am

Ok thanks I'll try this ;)

eZ Publish Freelance
web : http://www.webaxis.fr

eZ debug

Timing:	Jan 18 2025 11:01:09
Script start
Timing:	Jan 18 2025 11:01:09
Module start 'layout'
Timing:	Jan 18 2025 11:01:09
Module start 'content'
Timing:	Jan 18 2025 11:01:09
Module end 'content'
Timing:	Jan 18 2025 11:01:09
Script end

Main resources:

Total runtime	0.0171 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0067	588.0547	152.6406
Module start 'layout'	0.0067	0.0030	740.6953	39.4766
Module start 'content'	0.0097	0.0049	780.1719	89.3984
Module end 'content'	0.0146	0.0025	869.5703	34.3047
Script end	0.0170		903.8750

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	14.8036	14	0.0002
Check MTime	0.0011	6.5371	14	0.0001
Mysql Total
Database connection	0.0008	4.6204	1	0.0008
Mysqli_queries	0.0026	14.9644	3	0.0009
Looping result	0.0000	0.0937	1	0.0000
Template Total	0.0021	12.2	1	0.0021
Template load	0.0009	5.1475	1	0.0009
Template processing	0.0012	7.0306	1	0.0012
Override
Cache load	0.0006	3.4769	1	0.0006
General
dbfile	0.0002	1.4539	8	0.0000
String conversion	0.0000	0.0419	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs