eZ Community » Forums » Install & configuration » eZp 2013.6 - Could not get instance...
expandshrink

eZp 2013.6 - Could not get instance of datatype: - Problem

eZp 2013.6 - Could not get instance of datatype: - Problem

Monday 01 July 2013 8:55:50 am - 12 replies

Hi there,

after upgrading from eZp 2013.5 to eZp 2013.6 there are no images, text, etc. displayed. Not on the prod site, not on the dev site, not in the admin area. Templates are loaded, because I can see the structure and CSS stuff.

Any hints? I can't find the problem by myself.

Just get those errors...

Could not get instance of datatype:ezstring

Could not get instance of datatype: ezobjectrelation

Could not get instance of datatype: ezxmltext

Could not get instance of datatype: ezkeyword

Could not get instance of datatype: ezimage

 

Regenerated autloads already.

Dirk

Monday 01 July 2013 12:06:41 pm

Hi Dirk,

this maybe related to this issue?

https://jira.ez.no/browse/EZP-19411

and corresponding fix:

https://github.com/ezsystems/ezpublish-legacy/commit/1e27fa165cb20e26ae63ac3ccf621f0eee277356

Wednesday 17 July 2013 9:31:57 am

Quote from Edi Modrić :

Hi Dirk,

this maybe related to this issue?

https://jira.ez.no/browse/EZP-19411

and corresponding fix:

https://github.com/ezsystems/ezpublish-legacy/commit/1e27fa165cb20e26ae63ac3ccf621f0eee277356

 Hi Edi,

I am trying to upgrade to 2013.6 and am having the same problem as Dirk. I do not understand your answer:

I checked a few of the files mentioned in the fix you point to and it seems that the changes are already there in 2013.6 (community).

Do you mean that the fix does not work and needs to be rolled back ? Does 2013.6 as shipped not work at all with ez4 content ?

I don't know what to do now and any help would be greatly appreciated.

 

Thanks

Francesco

Wednesday 17 July 2013 10:44:30 am

Hi Francesco,

yes, sorry, I meant that the fix was not working correctly and probably needs to be reverted. But, I didn't try it myself yet.

Wednesday 17 July 2013 1:39:43 pm

Quote from Edi Modrić :

Hi Francesco,

yes, sorry, I meant that the fix was not working correctly and probably needs to be reverted. But, I didn't try it myself yet.

 Thanks!

I reverted the fix and now it seems to work.

Wednesday 17 July 2013 1:51:15 pm

Quote from Francesco Nardone :
Quote from Edi Modrić :

Hi Francesco,

yes, sorry, I meant that the fix was not working correctly and probably needs to be reverted. But, I didn't try it myself yet.

 Thanks!

I reverted the fix and now it seems to work.

Hi Francesco,

I'm glad to hear it worked for you. You should also report a bug on http://jira.ez.no for it to be fixed.

Tuesday 23 July 2013 12:51:13 pm

I created the Jira a while ago blunk.gif Emoticon

https://jira.ez.no/browse/EZP-21285

Tuesday 20 August 2013 6:40:54 pm

Do you by any chance have settings that clears the AvailableDataTypes setting and sets it to old style values maybe? this will not work after the change, the datatypes that have been changed to not register them self unfortunately *must* be loaded using the new autoload way, ref AvailableDataTypes[type]=class

Tuesday 20 August 2013 7:25:16 pm

Hi there. As i was the creator of that commit, i double checked it upgrading from 2013.5 to 2013.6 and found no issues.

@Andre: Even if for any reason the AvailableDataTypes was set to the old style, whole thing should be working too. The only difference is that with old style we still need those file_exists calls.

As a test, if you have 2013.07 installed and check ezflow, you will notice AvailableDataTypes is still defined in the old way but still working too.

Edit: Obviously it will help to have another testers. Please let me know if you find issues with this. 

Modified on Tuesday 20 August 2013 7:59:23 pm by Carlos Revillo

Wednesday 21 August 2013 1:45:25 pm

I was updating from 4.6 following the 4.6 -> 4.7 and 4.7 -> 5.1 procedure.

Wednesday 21 August 2013 1:58:08 pm

I don't understand... why are you following the 4.7 -> 5.1 procedure if you were upgrading from 2013.05 to 2013.06? 

Wednesday 21 August 2013 2:08:50 pm

Quote from Carlos Revillo :

I don't understand... why are you following the 4.7 -> 5.1 procedure if you were upgrading from 2013.05 to 2013.06? 

Dirk (the original poster) was upgrading from 2013.5 to 2013.6

I was updating from 4.6 and tagged along on the thread because I found the same error message.

Wednesday 21 August 2013 2:17:12 pm

Ok. but that improvement was added to 2013.06, indeed. but in enterprise versions it will be available since 5.2... so, it should be something in your case... 

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from