Forums / Setup & design / fatal error importing contentclass package

fatal error importing contentclass package

Previous topic

Setup & design

Next topic

Author	Message
Alessandro Cipriani	Monday 04 October 2004 3:20:56 am hi all i have two instances of my site, one on a developping server and the other on the production server. both of the instances have the class 'myclass', but now i've modified it on the developping server and i'd like to export the package in order to import it on the second server and overwrite the old 'myclass'. i can export without problem the package and import on the second server, but when i press the 'install' button i get the following error: Fatal error: Call to a member function on a non-object in c:\programmi\ezpublish\ezpublish\kernel\classes\ezcontentclassattribute.php on line 233 i'm using ezp version 3.4.0 any hint? best regards alessandro
Gunnstein Lye	Monday 11 October 2004 5:13:02 am I don't think overwriting classes is supported. But it should give a warning instead of crashing, of course, or it should be implemented. Please submit a bug report.

Author

Message

Alessandro Cipriani

Monday 04 October 2004 3:20:56 am

hi all
i have two instances of my site, one on a developping server and the other on the production server.
both of the instances have the class 'myclass', but now i've modified it on the developping server and i'd like to export the package in order to import it on the second server and overwrite the old 'myclass'.

i can export without problem the package and import on the second server, but when i press the 'install' button i get the following error:
Fatal error: Call to a member function on a non-object in c:\programmi\ezpublish\ezpublish\kernel\classes\ezcontentclassattribute.php on line 233

i'm using ezp version 3.4.0

any hint?
best regards
alessandro

Gunnstein Lye

Monday 11 October 2004 5:13:02 am

I don't think overwriting classes is supported. But it should give a warning instead of crashing, of course, or it should be implemented. Please submit a bug report.