You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Links in tables in Volto do not use resolveuid.
When creating a link a full url is stored (which will break when deploying since the full url includes the domain).
When rendering a (e.g. imported or manually created) link that uses resolveuid it is not transformed to a path and is also broken.
Especially annoying: When migrating text in tables from classic to volto the links are correctly migrated to use resolveuid but since the transforms are not applied these links are all broken.
To Reproduce
Steps to reproduce the behavior:
Create a table block with a link and a stale-block with a link
Inspect the raw block and see that the link in the text uses "data": {"url": "../../resolveuid/39e4910bd5404b00a0e58bb55cc90c5c"} whereas the link in the table uses "data": {"url": "http://localhost:3000/ziel"}
Expected behavior
Both should use resolveuid.
Software:
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Volto 16.12.0-dev (current master)
Plone 6.0.1
Plone REST API Version 8.33.3
The text was updated successfully, but these errors were encountered:
Links in tables in Volto do not use resolveuid.
When creating a link a full url is stored (which will break when deploying since the full url includes the domain).
When rendering a (e.g. imported or manually created) link that uses resolveuid it is not transformed to a path and is also broken.
Especially annoying: When migrating text in tables from classic to volto the links are correctly migrated to use resolveuid but since the transforms are not applied these links are all broken.
To Reproduce
Steps to reproduce the behavior:
"data": {"url": "../../resolveuid/39e4910bd5404b00a0e58bb55cc90c5c"}
whereas the link in the table uses"data": {"url": "http://localhost:3000/ziel"}
Expected behavior
Both should use resolveuid.
Software:
The text was updated successfully, but these errors were encountered: