Netroxen
September 25, 2017, 12:44pm
4
OK, it turns out this issue was coming from images that were included in the RichText fields of the item. These images had broken image paths (not handled in the migration) and required manually checking the fields and updating the image 'resolveuid' paths with the corresponding updated image path format used in Plone 5. In this case something like '/@@images /image/thumb' or the sorts...fix image scales from archetypes scales to dx scales, old scale names to new scale names · GitHub
References:
@seanupton recently put a lot of effort into plone.app.widgets 1.x (https://github.com/plone/plone.app.widgets/pull/144 ).
this made us give plone.app.widgets 1.x in plone4.3 another spin.
for sites with existing content (especially for images inserted into richtextfields) some migration has to be done:
the markup for images in richtext fields changed from Tiny3 (Products.TinyMCE) to tinymce4 (plone.app.widgets 1.x)
image inserted with Products.TinyMCE look like this:
<img class="image-inl…
opened 06:55PM - 04 Nov 16 UTC
01 type: bug
Today I tested an upgrade from Plone 3.1 to 4.3 and then on to 5.0.6.
When I ed… it a page and want to search for an image, I get a traceback:
```
Traceback (innermost last):
Module ZPublisher.Publish, line 138, in publish
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 48, in call_object
Module plone.app.content.browser.vocabulary, line 101, in __call__
Module plone.app.content.browser.vocabulary, line 323, in get_vocabulary
Module plone.app.vocabularies.catalog, line 594, in __call__
Module plone.app.vocabularies.utils, line 7, in parseQueryString
Module plone.app.querystring.queryparser, line 29, in parseFormquery
Module plone.registry.registry, line 38, in __getitem__
KeyError: u'plone.app.querystring.operation.list.contains.operation'
```
Looking in the configuration registry, I see lots of things starting with `plone.app.querystring.operation`, but nothing starting with `plone.app.querystring.operation.list`.
Going to `portal_setup` and applying the `plone.app.querystring:default` profile, fixes it. But it should work out of the box after an upgrade.
I don't know where this exactly goes wrong. There were no unapplied upgrade steps.
opened 06:36AM - 07 Dec 15 UTC
99 tag: migration
I am upgrading a 4.0.10 site to 5.0, and was able to migrate all default AT type… s using @@atct_migrator. However, all images in the richtext body fields that have a `src="resolveuid/..` are broken. Is there any way to make sure that the images keep working after migration?