Bug: It seems there’s a bug where the `content` field becomes empty when the number of `attachment` images is set to 10?

[Jiwoon-Kim]

It seems there’s a bug where the content field becomes empty when the number of attachment images is set to 10?
Also, the featured image is being displayed as the very first image, which is not the expected behavior.

https://browser.pub/https://kimjiwoon96.wordpress.com/2025/10/23/251023-domoheon/

https://kimjiwoon96.wordpress.com/2025/10/23/251023-domoheon/
https://mastodon.social/@kimjiwoon96.wordpress.com@kimjiwoon96.wordpress.com/115464300983817149
https://sajin.life/i/web/post/889564112032357328
https://misskey.io/notes/ae5sli2w6pof01xw

• Consistency between Actor icon handling and post image federation #2382 (reply in thread)
• Add image attachment selection control for ActivityPub posts #2138

[Jiwoon-Kim]

I tested whether it’s possible to attach all 41 images, but it seems the number is being forcibly limited to 10.

[Jiwoon-Kim]

Summary (what I observed)
I set the maximum number of attachments to 10, but selected the 11th image the featured image. Image #10 was dropped, and image #1 was replaced by image #11. This looks like a bug related to the image-object count / indexing.

However, I personally think that since the Article’s attachment should include all attached files,
the logic should be fully revised to control attachments specifically within the preview property instead.

lifting the attachment image limit for Article objects would likely be a prerequisite for proper inline image support.

[Jiwoon-Kim]

🔧 Requirements Summary

1. Media Library and Block Editor (Image Block)

Implement a “Sensitive” checkbox option within:

• The WordPress Media Library
• The Block Editor’s Image Block settings panel

---

2. Inline Images (<img>)

❌ Do not apply CW (Content Warning) directly to inline <img> elements.
✅ Instead, define the sensitivity status through the attachment property.

Each attachment should be a Link object containing:

{
  "type": "Link",
  "mediaType": "image/jpeg",
  "href": "https://example.com/wp-content/uploads/2025/10/sample.jpg",
  "sensitive": true
}

---

3. source Property

Must reference the image object ID (e.g., ?attachment_id=123)

Indicates that the image belongs to an isolated media object in the WordPress Media Library

Used for federated object linkage (e.g., in ActivityPub-compatible JSON-LD)

---

4. preview Property

Include a Note-type object representing a summary or preview of the article.
This can act as a lightweight representation for feed visibility.

Example:

"preview": {
  "type": "Note",
  "name": "Post title or preview summary",
  "summary": "Short description or excerpt",
  "attachment": [
    {
      "type": "Link",
      "mediaType": "image/jpeg",
      "href": "https://example.com/?attachment_id=101",
      "source": "https://example.com/?attachment_id=101"
    }
  ]
}

---

5. content Property

The content should be a single-line HTML string that includes:

Custom emoji inside

Two inline elements

One of them marked as sensitive: true, and the other as sensitive: false in the attachment list.

Example:

"content": "<p>Custom emoji 🪶 with inline images <img src='?attachment_id=123'/> and <img src='?attachment_id=124'/>.</p>"

---

Summary:
This structure ensures a clear separation between inline display (content) and media metadata (attachment), while supporting CW/sensitivity labeling and lazy loading based on locally federated media objects.

---

Example: WordPress Article Object in JSON-LD (with Sensitive Attachments)

This example demonstrates how a WordPress Article object can represent
attachments and inline images using JSON-LD / ActivityStreams format.

It includes:

• Inline images in content
• sensitive flag for each attachment
• source property referencing the local media object via ?attachment_id=
• A preview object for rich link cards
• Custom emoji tags

---

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://schema.org",
    {
      "sensitive": "as:sensitive",
      "source": "as:source",
      "preview": "as:preview"
    }
  ],
  "id": "https://travel-in-busan.com/articles/123",
  "type": "Article",
  "name": "Autumn Scenery and Camellias in Busan",
  "summary": "A short post with inline images and custom emoji for ActivityPub testing.",
  "published": "2025-10-31T12:00:00+09:00",
  "attributedTo": "https://travel-in-busan.com/@jiwoon",

  "preview": {
    "type": "Note",
    "name": "Preview of Autumn Scenery and Camellias",
    "summary": "A brief preview: autumn sky and camellias at Gwangalli Beach.",
    "attachment": [
      {
        "type": "Link",
        "mediaType": "image/webp",
        "href": "https://travel-in-busan.com/media/preview-001.webp",
        "source": {
          "id": "https://travel-in-busan.com/?attachment_id=321"
        }
      }
    ]
  },

  "content": "<p>🍁 Strolling around Gwangalli Beach 🌊 <img src=\"https://travel-in-busan.com/wp-content/uploads/2025/10/beach.webp\" alt=\"Gwangalli Beach\"> <img src=\"https://travel-in-busan.com/wp-content/uploads/2025/10/camellia.webp\" alt=\"Camellia flower\"></p>",

  "attachment": [
    {
      "type": "Link",
      "mediaType": "image/webp",
      "href": "https://travel-in-busan.com/wp-content/uploads/2025/10/beach.webp",
      "sensitive": false,
      "source": {
        "id": "https://travel-in-busan.com/?attachment_id=201"
      },
      "name": "Gwangalli Beach"
    },
    {
      "type": "Link",
      "mediaType": "image/webp",
      "href": "https://travel-in-busan.com/wp-content/uploads/2025/10/camellia.webp",
      "sensitive": true,
      "source": {
        "id": "https://travel-in-busan.com/?attachment_id=202"
      },
      "name": "Camellia Close-up"
    }
  ],

  "tag": [
    {
      "type": "Emoji",
      "name": "🍁",
      "icon": {
        "type": "Image",
        "mediaType": "image/png",
        "url": "https://travel-in-busan.com/wp-content/uploads/emojis/maple.png"
      }
    }
  ]
}

---

🧩 Key Design Notes

Property Description

attachment[].sensitive Boolean flag to indicate whether an image should be hidden behind a content warning (CW).
source.id Uses a WordPress-style media endpoint: ?attachment_id=123, allowing direct linkage to media metadata.
preview Provides a small Note object for link previews (summary + thumbnail).
content Contains inline tags and custom emoji, with no direct CW markup applied.
tag Includes custom emoji definition via Emoji object.

---

💡 Usage

This JSON-LD representation can be embedded in the <script type="application/ld+json"> of a WordPress post or exposed via REST API for ActivityPub federation.

It enables:

Fine-grained content moderation (sensitive flag)

Local media caching and reference consistency

Structured previews for external platforms

---

Author: Jiwoon Kim
License: CC0 / Public Domain for interoperability documentation.

When attaching remote image objects, it should follow a license and consent compliance model.

[pfefferle]

I am sorry, but I can not reproduce the issue. Even with way more then 10 images, I can see the full content and the first 10 images as attachments.

Is it maybe an issue with the Korean characters, that the plugin can't handle properly? Can you verify that, by adding the same content, but without any images?

I set the maximum number of attachments to 10, but selected the 11th image the featured image. Image 10 was dropped, and image 1 was replaced by image 11. This looks like a bug related to the image-object count / indexing.

The featured image will always be set as the first image. That is a feature and not a bug.

[Jiwoon-Kim]

I’ll check later today when I publish a new post to see if I can reproduce the issue.