🐛 Bug - Unable to edit specific rule in TinaCMS due to unexpected error #2690

Activity

1. tiagov8

   self-assigned this

   on Jul 30, 2026
2. tiagov8

   added

   YakShaver

   Needs Refinement

   on Jul 30, 2026
3. tiagov8

   removed their assignment

   on Jul 30, 2026
4. github-actions commented on Jul 30, 2026

   

   github-actionsBot

   on Jul 30, 2026 – with GitHub Actions

   Contributor

   More actions

   🔍 Research Findings

   Thanks for the detailed report. I've investigated the codebase and here are my findings.

   ---

   Summary

   The TinaCMS "unexpected error while fetching your content" is almost certainly caused by invalid or unsupported content in the MDX files for those two specific rules in the SSW.Rules.Content repo — not in the SSW.Rules frontend code.

   ---

   Relevant Files (this repo)

   File	Role
   tina/collection/rule.tsx	TinaCMS schema definition for rules
   tina/config.tsx	TinaCMS global config (branch, search, etc.)
   components/embeds/index.ts	Registered embed templates
   components/embeds/imageEmbed.tsx	Image embed (includes normalizeSrc logic)

   ---

   Registered TinaCMS Embed Templates

   Only these five components are registered in the TinaCMS schema (components/embeds/index.ts):

   export const embedTemplates: Template[] = [
     endIntroTemplate,
     emailEmbedTemplate,
     imageEmbedTemplate,
     boxEmbedTemplate,
     youtubeEmbedTemplate,
   ];

   If either rule's MDX body uses any other JSX component (e.g. a <Figure> standalone, <TwitterEmbed>, <Iframe>, or any previously-supported but now-removed component), TinaCMS will fail with exactly this kind of "unexpected error" because it can't parse the unknown component against the schema.

   ---

   Potential Causes

   1. Unregistered MDX component — The rule uses a JSX component in its body that is not in embedTemplates. TinaCMS can't deserialise it → fetch error.
   2. Invalid/corrupted frontmatter — A YAML parsing issue in the rule's frontmatter would cause TinaCMS's GraphQL API to fail when fetching that document.
   3. Schema mismatch after a recent change — If a field was renamed or removed from the TinaCMS schema but still exists in the MDX frontmatter, the API would return an error.
   4. File too large — TinaCMS has size/timeout limits; unusually large rules can occasionally hit this.

   ---

   Broken Image (Acceptance Criteria #6)

   The broken image at (www.ssw.com.au/redacted) is also a **content issue** — the srcvalue inside an(imageEmbed)(or raw(img)`) in the MDX file is pointing to a missing/deleted image URL.

   Note: imageEmbed.tsx has a normalizeSrc function that strips a duplicated `(assets.tina.io/redacted) prefix — a double-URL is one known pattern that can result in a broken image.

   ---

   Recommended Next Steps (for a developer)

   1. Open the affected MDX files in SSW.Rules.Content:

      • rules/chewing-the-fat/rule.mdx
      • rules/get-data-to-your-ai/rule.mdx

   2. Check the body for any JSX components that are NOT in the list above (endIntro, emailEmbed, imageEmbed, boxEmbed, youtubeEmbed).

   3. Check the frontmatter for any malformed YAML or fields that don't match the current TinaCMS schema in tina/collection/rule.tsx.

   4. Check the broken image src — look for a double URL, a deleted blob URL, or a GitHub attachment URL that's no longer accessible.

   5. If a previously-supported component was removed and is still used in these rules, it will need to be either:

      • Re-added to the TinaCMS schema (in components/embeds/ and index.ts), or
      • Replaced with a supported alternative in the content MDX.

   ---

   Confidence: Low — the root cause requires inspecting the actual content files in SSW.Rules.Content, which is a separate repository. The SSW.Rules frontend code appears correct.

   Note

   🔒 Integrity filter blocked 2 items

   The following items were blocked because they don't meet the GitHub integrity level.

   • #2249 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #2368 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

   To allow these resources, lower min-integrity in your GitHub frontmatter:

   tools:
     github:
       min-integrity: approved  # merged | approved | unapproved | none

   Generated by Issue Triage for issue #2690 · ● 462.9K · ◷
5. tiagov8 commented on Jul 30, 2026

   

   tiagov8

   on Jul 30, 2026

   MemberAuthor

   More actions

   Update: I found there was a change to the rule URL which caused the mess up

   the latest is:
   https://www.ssw.com.au/rules/feed-data-to-ai

   ...but the Form was still linking to:
   https://www.ssw.com.au/rules/get-data-to-your-ai

   --

   ✅ Done - I fixed the link in the form: 2026-07-31 - From RAG to Riches (long context) - Chewing the Fat 📈 – Fill out form

   --

   PENDING - Still need to figure out how and why the old URL is still live
6. Aibono1225 commented on Jul 31, 2026

   

   Aibono1225

   on Jul 31, 2026

   Contributor

   More actions

   PENDING - Still need to figure out how and why the old URL is still live

   RESOLVED - Found out why the old URL is still live.
   The old link still works after the rename because redirects.json only gets updated once a day. So the old link will keep working until the next scheduled deployment

   This is a known limitation that could be improved, PBI: #2513

   👍React with 👍1Reacted by Tiago Araújo [SSW]
7. Aibono1225

   closed this as completedon Jul 31, 2026