WYSIWYG link tool inserts the first-version inode for dotAssets and images (/dA/<inode>), so links show an outdated version after the asset is edited

未关闭 适合新手
#38,546 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
java, javascript

调研方向

从dotCMS/src/main/webapp/html/portlet/ext/contentlet/field/edit_field_js.jsp开始,阅读addFileCallback,它根据file.path为dotAssets和Images构建链接。将此行为与基于标识符的图像按钮URL进行比较,然后检查旧版WYSIWYG链接流程。当浏览对话框为dotAssets和Images插入/dA/<identifier>/<name>,且现有File Asset和页面链接仍能正常工作时,即为完成。

由索引模型根据 Issue 内容生成。

描述

OKR : Customer Support Team : Maintenance Type : Defect
Problem Statement

In the legacy WYSIWYG field (the legacy edit-contentlet screen), the Insert link dialog's file browser builds the href for dotAssets and images as /dA/<inode>/<name>. This covers every content type of base type dotAsset: the DotAsset content type and the Image content type (an Image asset is a dotAsset). In addFileCallback (dotCMS/src/main/webapp/html/portlet/ext/contentlet/field/edit_field_js.jsp), the id is taken from file.path.split(".")[1], and a dotAsset's (or Image's) path/url field keeps the inode of its first version (/content.<first inode>) for the lifetime of the asset. The link is therefore pinned to the first version instead of to the asset's identifier. Images stored as File Assets are different: they get the Site Browser path (see Out of scope).

Impact

  • After any new version of the dotAsset or Image is saved (a new file, or even a metadata-only save), the link keeps resolving to the first version, so authors and visitors see an outdated file or image. If the asset was edited before it was inserted, the link is outdated from the start.
  • Depending on permissions, a non-live version may instead redirect to login or return 404 (BinaryExporterServlet serves live versions only to users without read access).
  • The image button in the same editor inserts /dA/<shortyId>/<name>?language_id=… (identifier-based), which always shows the latest version. The docs say dotAssets are accessed by their identifier (Image is a dotAsset type), and describe the inode form as the version at the time the link is inserted; the link tool uses neither (it uses the first version).
  • WYSIWYG_IMAGE_URL_PATTERN does not influence the link tool (tested with the default pattern and with {path}{name}; addFileCallback never reads the property), so there is no configuration workaround. Interim workaround: type /dA/<short identifier>/<file name> in the URL field.
  • Reported by a customer whose authors rely on the Link tool (hundreds of authors; an inconvenience, not blocking). Not browser-specific (JavaScript in the legacy JSP).

History: the dotAsset branch was added by commit 5b26570851 (Aug 2020, fix for #19041, a JavaScript error when adding a link; first in 5.3.7).

Related: File Assets (same tool, different behavior; a product decision, not part of this defect)

For File Assets, including images stored as File Assets, the Link tool inserts the Site Browser path (file.path, for example /files/report.pdf). Unlike the dotAsset case, this is not new:

  • Before 2015 the file browser inserted /contentAsset/raw-data/<identifier>/fileAsset, which was reported as an invalid URL. #7729 changed it to the path, and #8229 fixed follow-up cross-site link problems.
  • From 2015 to 2020 every file got path + name. The 2020 change (5b26570851) kept the path for File Assets and added the /dA/ branch for dotAssets only.
  • At no point did the Link tool insert a /dA/ URL for a File Asset.

The docs say File Assets can be reached by path or by identifier. The result is an inconsistency inside the same editor: a path link breaks when the file is renamed or moved, while the image button inserts /dA/<shortyId>/<name>?language_id=… for the same File Asset. The customer who reported this expects the Link tool to behave like the image button. Product to decide whether the Link tool should insert /dA/<identifier> for File Assets too.

Steps to Reproduce

Video screencast: https://drive.google.com/file/d/1J9QHbskwX748kPmhjhRWpYU2PtbEclBb/view?usp=drive_link (dotCMS internal)

Or detailed steps:

  1. Use a content type with a WYSIWYG field on the legacy editor (content type metadata CONTENT_EDITOR2_ENABLED=false).
  2. Create and publish a dotAsset (content type DotAsset), for example red.png.
  3. In the WYSIWYG field, select some text, click Link, click the browse button next to the URL box and pick the dotAsset. Switch the field to Code view: href="/dA/<inode>/red.png".
  4. Save the content. Replace the dotAsset's file with blue.png (new version) and publish it.
  5. Open the saved link: it still serves red.png (the first version).

Repeat with an asset of the Image content type (for example photo.png): same result, href="/dA/<inode>/photo.png", and the saved link still shows the first version after the image is replaced.

Variant: give the dotAsset or Image two versions before inserting it. The inserted id is still the first version's inode, not the current one.

Tested on 26.10.13-01 (Docker image) through the UI and the API for both the DotAsset and Image content types, including assets placed in folders. Also seen on a customer's dev environment with an Image-type asset.

Acceptance Criteria
  • Inserting a dotAsset or an Image asset with the Link dialog's file browser writes /dA/<identifier>/<name> (same identifier form as the image button), not an inode.
  • After a new version of the dotAsset or Image is saved and published, the saved link shows the new version.
  • A dotAsset or Image that already had several versions before insertion also produces an identifier-based link.
  • Works for dotAssets and Images in folders, and for any content type of base type dotAsset.
  • Existing File Asset and page link behavior is unchanged (unless product decides otherwise, see Related: File Assets).
dotCMS Version

26.10.13-01 (dotCMS Cloud dev environment and local Docker image). The dotAsset branch dates from 5.3.7, so older versions are affected too.

Severity

Medium - Some functionality impacted

Links
主要语言
Java
星标
972
派生
493
平均合并
2 天 12 小时
30 天内合并 PR
237

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dotCMS/core 的其他 Issue

查看 dotCMS/core 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。