It is probably that some of the template override definitions still refers to the old class ID. You could try looking for your old class ID in override.ini for your siteaccess.
If you use the admin interface you can go the template list, find node/view/full.tpl, there your old class ID should be listed in the <i>Match conditions</i> column, edit that file.
- Make a copy of the text content (e.g. paste it into a text browser)
- Remove the file for that given ID
- Create a new file and select your new class. - Edit the new file and paste the text content you copied earlier.
This questions remembers me about a problem i have upgrading a site to a new ezpublish version. The problem is the the class number conflict. Assuming you have intslled ezp with the orignal 10 internal classes. And you create one more, the new class number 11.
Then you upgrade to new ezp version witch comes with more internal classes. The new version have 20 classes. This generates conflits.
Why not have reserved class numbers only for internal classes coming with default ezp instalation and another range to user created classes ?
example: 1...100 - internal classes 101 ...nnnn - user created classes ?
what you thing ? somene have any better sugestion ?
I don't think that reserving IDs is needed. With the latest eZ publish versions you can use the identifier on a class to create overrides or otherwise relate to a class, that way it doesn't matter what the ID is.
