Description of problem: Camden migration scripts did not migrate image ids correctly. The same image in the 5.2 box has a different id in the migrated APLAWS+ box: http://camden.aplaws.org.uk/cms-service/stream/image/?image_id=160775 http://youth.aplaws.org.uk/ccm/cms-service/stream/image/? image_id=12551& How reproducible: Always
IDs for images & all objects within WAF are installation specific & as such it is not possible to maintain the same IDs across differnet installs. What situation have you got that would require IDs to be the same across both installs ? All styling should be using the ID specified in the XML, not hardcoding it, so I can only think its relevant if there were hardcoding <img> tags in the body text for some articles.
That's exactly the case. There is no solution for this?
There isn't any solution - we don't support/recommend entering of <img> tags directly into HTML for this exact reason. You'll have to edit the HTML to fix the image ids.
I understand that. Just to get to the bottom of this ticket, the "migrated" image repository in our production instance is a lot smaller than the 5.2 one. Is that because the items that were loaded into the image repository were then accessed from the html in the body text instead of using the add image authoring step? I understand that we may need to change the ids of the images if we want to access them from the html in the body text but it seems that we also have to re-upload more than half of the images as well.
If the images weren't referenced in the 'image' authoring step then there is no way for the systme to tell that they were in use, so they won't have been migrated. The issue wrt missing images has previously been entered as bug 117196.