* docs: revamp develop-plugin section
Fixes critical content bugs that broke setup paths (wrong Linux binary
name, conflicting `REMOTE_INSTALL_URL` env var, full duplicate of
release-overview where GitHub-publishing steps should be, broken Flomo
provider YAML, depot-only `runs-on` in the auto-publish workflow,
unverified imports in reverse-invocation examples, wrong
`TextEmbeddingModelConfig` type) and restructures the section around the
developer's mental model.
Sidebar reorg: Publishing now reads release-overview -> Standards ->
Marketplace (with auto-publish nested) -> GitHub Repository -> Local
File -> FAQ. A new choose-plugin-type decision page sits between the
landing page and the CLI in Getting Started.
Major rewrites: release-to-individual-github-repo (full),
remote-debug-a-plugin (50 -> 160 lines with troubleshooting),
multilingual-readme (added template), faq (2 -> 10 entries), Flomo
walkthrough YAML to canonical credentials_for_provider shape. Quick
Decision callouts on model-schema and model-designing-rules. Backfilled
missing frontmatter `description` on 7 pre-existing pages for
CLAUDE.md compliance.
All edits in en/ only; translation pipeline handles zh/ja.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: fix TOC, tighten Standards, move signature verification
TOC: promote leading h3 -> h2 (and h4 -> h3) on 17 pages whose
right-rail TOC had no top-level entries because every section started
at h3. Hierarchy is preserved; subsections that were h4 now sit
correctly as h3 under their parent h2.
Standards section: rewrite contributor-covenant-code-of-conduct
(now properly titled "Plugin Development Guidelines") and
privacy-protection-guidelines for tighter prose, scannable lists, and
correct heading levels. The privacy page used h4 manual numbering
which broke its TOC entirely; now uses h2/h3 with an Accordion FAQ.
Reclassify third-party-signature-verification: it is a Community
Edition install-time feature, not a Marketplace standard. Moved from
Publishing > Standards to Publishing > Local File (alongside the
release-by-file `.difypkg` flow).
Also strip a stray `# Endpoint` h1 from endpoint.mdx (the title is
already in frontmatter) and replace a self-referencing link.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: subgroup walkthroughs, shorten titles, widget-ize publishing
Walkthroughs sidebar: split the 12-page flat list into Cheatsheet +
'By Plugin Type' subgroup (tool/oauth/model/agent-strategy/datasource/
trigger/endpoint) + 'Full Walkthroughs' subgroup (flomo/slack-bot/
md-exporter/multimodal). Shortened the worst sidebar offenders:
- 'Build Tool Plugins for Multimodal Data Processing in Knowledge
Pipelines' -> 'Multimodal Tool'
- '10-Minute Guide to Building Dify Plugins' -> 'Flomo Tool (10-min)'
- 'Dify Plugin Development Cheatsheet' -> 'Cheatsheet'
- 'Develop A Slack Bot Plugin' -> 'Slack Bot'
- 'Build a Markdown Exporter Plugin' -> 'Markdown Exporter'
- 'Add OAuth Support to Your Tool Plugin' -> 'Tool OAuth'
- 'Neko Cat Endpoint' -> 'Endpoint Plugin'
Publishing pages: rewrite around Mintlify widgets and bake in the
actual reviewer process from the pr-review-helper skill:
- release-to-dify-marketplace.mdx: full rewrite with a Tabs-based
pre-submission checklist, the exact 12-check reviewer table the
automated workflow runs, a Steps submit flow, AccordionGroup FAQ,
CardGroup related resources, and a PR-lifecycle table.
- release-overview.mdx: replace prose with a CardGroup chooser and a
comparison table (audience / review / install path / versioning /
best for).
- release-by-file.mdx: Steps for both packaging and installing,
CardGroup for next-step distribution methods.
- third-party-signature-verification.mdx: scenario CardGroup,
three-Step generate/sign/verify flow, three-Step daemon-enable flow.
- faq.mdx: add 'Why was my Marketplace PR rejected?' entry covering
the most common automated-check failures from the skill.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: add free Mintlify components (mermaid, check, icon)
- release-to-dify-marketplace.mdx: replace the static PNG submission
flowchart with a Mermaid diagram (renders dark-mode-friendly,
diff-friendly, no CDN dependency). Add Check callout confirming
auto-publish on merge.
- tool-oauth.mdx: add a Mermaid sequence diagram contrasting the
admin-side OAuth client setup with the per-user authorization flow,
matching the existing "two separate flows" narrative.
- release-overview.mdx: add inline `<Icon>` to the comparison table
header so each column reads as Marketplace/GitHub/Local at a glance.
- remote-debug-a-plugin.mdx, release-by-file.mdx,
release-to-individual-github-repo.mdx: add `<Check>` confirmations
after the verify-install step on each install path, so the reader
knows what "success" looks like and when they can stop following.
Snippets deferred — the translation pipeline operates on en/zh/ja
trees, so a root-level `snippets/` directory needs coordination with
tools/translate before adoption.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix: address correctness gaps in develop-plugin pages
* docs: align plugin type catalog and tighten heading case
* style: drop em dashes and tidy formatting in develop-plugin docs
* fix: address Copilot follow-up comments on develop-plugin docs
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: RiskeyL <7a8y@163.com>
* docs: sync App Toolkit with dify#35442 follow-up settings (#757)
* docs: sync App Toolkit page with follow-up settings PR and UI labels
* fix: correct CJK format linter false positives
* chore: broaden post-writing audit scope to whole documents
* docs: address Copilot review on PR #754
Restore the Tab titles rule in formatting-zh.md, which had been trimmed
to a stub. Drop the First-Mention Rule entry from the terminology-check
skill's Output Format so the report sections match the Checks to
Perform sections (the corresponding check was removed earlier).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: document workflow collaboration feature (#758)
* docs: add workflow collaboration user guide
* docs: tighten style and formatting guides
* docs: avoid "please" in zh refer-to phrases
* fix: add CJK-Latin spacing in translation notice templates
* docs: add env var coordination to dify-docs-guides skill
* docs: document collaboration environment variables
* style: trim collaboration env var descriptions for consistency
* docs: add zoom menu tip for hiding comments and cursors
* docs: sync collaboration UI labels after upstream localization
* docs: rewrite orchestration logic for cross-workflow node copy-paste (#759)
* docs: rewrite orchestration logic and extend workflow-chatflow overview
* translate: update zh and ja for orchestration logic and overview
* docs: refine orchestration logic node reuse section
* docs: clarify MAX_TREE_DEPTH env var description
* fix: align zh title and body references with the glossary UI label
* fix: align EN node reuse text with zh/ja translations (User Input exception)
Agent-Logs-Url: https://github.com/langgenius/dify-docs/sessions/00e54676-8a43-4b6f-99f8-fef2495b054f
Co-authored-by: RiskeyL <36894937+RiskeyL@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
* docs: note HTTPS requirement for cross-workflow node paste (#761)
* docs: HITL Service API polish and 1.14 release follow-ups (#760)
* feat: add env var ignore-list consumed by the verifier
* docs: add 1.14 env vars and correct drifted defaults
* fix: correct knowledge pipeline datasource-plugins response in api references
* chore: record 1.14 env var traces in deep-dive
* docs: update HITL Service API documentation
* docs: clarify /api-reference/ link convention in formatting guide
* docs: update marketplace publish flow
* fix: drop duplicate workflow_run_id from HITL event data schemas
The three HITL event schemas (StreamEventHumanInputRequired,
StreamEventHumanInputFormFilled, StreamEventHumanInputFormTimeout)
declared `workflow_run_id` inside `data.properties`, but
`HumanInputRequiredResponse` in `api/core/app/entities/task_entities.py`
defines `workflow_run_id` only as a top-level field on the response
(alongside `event` and `task_id`); its inner `Data` class doesn't carry
one. The OpenAPI spec already provides top-level `workflow_run_id` via
the `$ref: StreamEventBase` in the `allOf` composition, so the inline
duplicate was a phantom field that doesn't exist in the actual payload.
Remove the inline `workflow_run_id` from `data.properties` in all three
HITL event schemas across all six spec files. This relies on
`StreamEventBase` to provide `workflow_run_id` at the top level via
composition, matching how every other event schema in this spec handles
it (e.g., `StreamEventWorkflowStarted`).
Reported by Copilot on PR #756.
* fix: address Copilot's review comments
* feat: skip api-reference paths in internal link checker
The /api-reference/... URL convention (no language prefix, derived
from OpenAPI tag/summary) generates pages that Mintlify auto-builds
rather than from filesystem MDX files, so the existing filesystem
resolution logic flags every such link as broken.
Skip both filesystem-existence and anchor validation for any URL
containing /api-reference/, mirroring the existing
anchor_check_skipped behaviour. The convention is documented in
writing-guides/formatting-guide.md.
Caveat: typos in tag or summary slugs will now pass silently. A
follow-up could parse the OpenAPI specs to validate against the
real tag/summary kebab pairs if hand-written api-reference links
become common enough to warrant it.
* fix: correct CORS anchor in ja environments page
Inline link [CORS設定](#cors 設定) used a literal space, but the
heading "CORS 設定" slugifies to "cors-設定" (whitespace replaced
with hyphen). Update the anchor to #cors-設定.
* fix: align datasource-plugins is_published and 200 description with node framing
* fix: clarify chatflow stream workflow events task_id origin
* docs: address HITL Service API reader-test feedback
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
* Batch update service apis
* final check and add zh/ja docs
* add temporary redirects for changed api links embedded in the product
* Restore original operationIds to preserve SDK compatibility
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* complete the missing descriptions
* correct the human input terminology
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: remove href from language blocks to preserve page on language switch
Mintlify's language switcher navigates to the explicit href when set,
instead of doing smart path prefix replacement. Removing href lets the
switcher stay on the current page when switching languages.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Revert "fix: remove href from language blocks to preserve page on language switch"
This reverts commit b74b1b8291.
* fix: restructure navigation from versions>languages to languages>versions
Mintlify's language switcher only preserves the current page when
languages are the top-level navigation partition. Previously, versions
were the top level with languages nested inside, causing the switcher
to redirect to the introduction page instead of the same page in the
target language.
Also removes explicit href from language blocks and fixes ja having
default=true incorrectly in the 3.2.x version config.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: align zh/ja API spec operationIds with en for language switching
Mintlify generates page URL slugs from operationId. When operationIds
differ between languages (e.g., en: sendChatMessage vs zh:
sendBasicChatMessageCn), the language switcher can't find the
equivalent page and falls back to the introduction page.
This aligns all zh/ja operationIds to match en for endpoints that
share the same HTTP method and path.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: align OpenAPI tags across languages for consistent URL slugs
Mintlify uses OpenAPI tags to generate URL category paths (e.g., tag
"Chat" → /chat/). When zh uses "对话消息" and ja uses "チャットメッセージ",
the generated URLs differ from en's, breaking language switching.
This aligns all zh/ja OpenAPI spec tags to match en, ensuring
identical URL structures across languages.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: add x-displayName to preserve translated tag names in sidebar
Tags use English names for URL slug generation (consistent across
languages) but x-displayName holds the translated names for display
in the sidebar, so Chinese/Japanese users still see localized labels.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use x-mint href to align API reference URLs across languages
Mintlify generates API page URLs from the tag name + summary, both of
which are translated in zh/ja specs. This produces different URL slugs
(e.g., en: /chat/send-chat-message vs zh: /对话消息/发送对话消息),
making language switching impossible.
Instead of changing the visible content (tags, summaries), this adds
x-mint: { href: ... } to each endpoint in zh/ja specs, explicitly
setting the URL path to match en. All translated content (tags,
summaries, descriptions) is preserved as-is for readers.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: add language prefix to x-mint href to prevent cross-language conflicts
Without the language prefix, zh/ja endpoints claimed the same absolute
URL as en (e.g., /api-reference/chat/send-chat-message), causing ja
content to appear on en pages. Now each language has its own prefixed
href (e.g., /zh/api-reference/chat/send-chat-message), keeping content
correctly scoped while enabling language switching.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* revert: remove all API spec changes (x-mint href, operationId, tag alignment)
These changes are breaking and need careful coordination with the dev
team before implementation. Only the navigation restructure
(versions>languages → languages>versions) is kept for this PR.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* remove all enterprise versions
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* draft
* revise based on hands-on testing
* modify based on feedback
* add zh and ja translation
* Update tip for referencing text output variable
Clarify the default behavior of the reasoning model output.
* Add translation note
Added a note about AI translation accuracy and referenced the English version for discrepancies.
* Update human-input.mdx with translation note
Add a note about AI translation accuracy and reference to the English version.
* Apply suggestion from @Copilot
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update wording for clarity on model output display
---------
Co-authored-by: Riskey <riskey47@dify.ai>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* 🌐 Initial translations for PR #665
Auto-generated translations for documentation changes in PR #665.
Last-Processed-Commit: fe61cffd6d
Original-PR: #665
Languages: Chinese (zh), Japanese (ja)
🤖 Generated with GitHub Actions
* 🔄 Update translations for commit fe61cffd
Auto-generated translations for changes in commit fe61cffd6d.
Last-Processed-Commit: fe61cffd6d
Original-PR: #665
Languages: Chinese (zh), Japanese (ja)
🤖 Generated with GitHub Actions
* 🔄 Update translations for commit d37bc6b5
Auto-generated translations for changes in commit d37bc6b5589e629eac03feb0b7278cba6e75bb0f.
Last-Processed-Commit: d37bc6b5589e629eac03feb0b7278cba6e75bb0f
Original-PR: #665
Languages: Chinese (zh), Japanese (ja)
🤖 Generated with GitHub Actions
* fix the zh link
* fix ja links
* align with en doc
* align with en doc
Remove unnecessary URLs and email addresses for better text cleaning.
* Fix formatting for URL and email removal section
* Fix formatting for URL and email removal section
* align the doc title
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Riskey <36894937+RiskeyL@users.noreply.github.com>
Co-authored-by: RiskeyL <7a8y@163.com>
* create 3.4.x navigation
* add content related to multi-credential management and load balancing for 3-5-x
* add content related to knowledge pipeline for 3-6-x
* add content related to trigger, multimodal embedding, and json object for 3-7-x
* changes upon review
* remove unnecessary links
---------
Co-authored-by: Riskey <riskey47@dify.ai>
* 🌐 Initial translations for PR #636
Auto-generated translations for documentation changes in PR #636.
Last-Processed-Commit: 3f204fbd9d
Original-PR: #636
Languages: Chinese (zh), Japanese (ja)
🤖 Generated with GitHub Actions
* 🔄 Update translations for commit 623b346a
Auto-generated translations for changes in commit 623b346a77.
Last-Processed-Commit: 623b346a77
Original-PR: #636
Languages: Chinese (zh), Japanese (ja)
🤖 Generated with GitHub Actions
* Fix pricing link for batch upload information
Updated the link for the paid plan pricing page.
* Update maintain-knowledge-documents.mdx
* Update link text for knowledge base creation
* Update pricing link in readme for batch upload
* Update setting-indexing-methods.mdx
* Update knowledge-retrieval.mdx
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Riskey <36894937+RiskeyL@users.noreply.github.com>
* recover the original agent strategy docs from old docs repo
* Adjust the navigation order of the plugin dev docs
---------
Co-authored-by: Riskey <riskey47@dify.ai>
* draft
* migrate from old docs repo
* adjust content based on experiencing the feature
* Improvements
* changes upon feedback
* refinements
* zh draft
* add plugin dev docs
* update old links
* add jp docs
* change the position of variables related to multimodal embedding in the environment variable doc
---------
Co-authored-by: Riskey <riskey47@dify.ai>
* fix redirect language code prefixes
* rename: cn -> zh, jp -> ja
* remove hardcoded ja / zh references
* remove hardcoded 'english' references
* renamed variable names and dict keys to language agnostic names
* fix: add missing language helper methods to PRAnalyzer
- Add get_language_directory() method
- Initialize source_language and target_languages from config
- Fixes AttributeError when generating mixed PR errors
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* test: kitchen sink workflow validation v2
This PR validates the translation workflow after config-driven refactoring:
Changes:
- Add new test file: test-workflow-validation.mdx
- Modify existing file: introduction.mdx
- Update docs.json navigation
Tests:
- New file translation (add workflow)
- Existing file translation (update workflow)
- Navigation sync across languages
- Config-driven language codes (zh/ja instead of cn/jp)
- Source language abstraction (no hardcoded "English")
Expected workflow behavior:
1. Detect changes in en/ directory
2. Translate new file to zh and ja
3. Update modified file translations
4. Sync docs.json for all language sections
5. Commit translated files automatically
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* fix: update workflow paths to use zh/ja instead of cn/jp
Aligns workflow trigger paths with the zh/ja language directory rename.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Revert "fix: update workflow paths to use zh/ja instead of cn/jp"
This reverts commit 9587b7cc5d.
* Revert "test: kitchen sink workflow validation v2"
This reverts commit 4abdd69fd2.
* fix: update workflow paths in doc analyze workflow to use zh/ja instead of cn/jp
* Refactor/language codes (#240)
* test: kitchen sink workflow validation v2
This PR validates the translation workflow after config-driven refactoring:
Changes:
- Add new test file: test-workflow-validation.mdx
- Modify existing file: introduction.mdx
- Update docs.json navigation
Tests:
- New file translation (add workflow)
- Existing file translation (update workflow)
- Navigation sync across languages
- Config-driven language codes (zh/ja instead of cn/jp)
- Source language abstraction (no hardcoded "English")
Expected workflow behavior:
1. Detect changes in en/ directory
2. Translate new file to zh and ja
3. Update modified file translations
4. Sync docs.json for all language sections
5. Commit translated files automatically
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* fix: update workflow paths to use zh/ja instead of cn/jp
Aligns workflow trigger paths with the zh/ja language directory rename.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Revert "fix: update workflow paths to use zh/ja instead of cn/jp"
This reverts commit 9587b7cc5d.
* Revert "test: kitchen sink workflow validation v2"
This reverts commit 4abdd69fd2.
* fix: update workflow paths in doc analyze workflow to use zh/ja instead of cn/jp
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: update workflow files to use 'source' instead of 'english'
After refactoring the PR analyzer to use 'source' for source language
PRs (instead of hardcoded 'english'), the workflow files need to match.
Changes:
- sync_docs_analyze.yml: pr_type == 'source' (was 'english')
- sync_docs_update.yml: PR_TYPE != 'source' check
- Updated all comments from "English" to "source language"
- Updated all pr_type values in JSON from "english" to "source"
This ensures the workflows trigger correctly with the refactored
config-driven language system.
Related: language code refactoring (cn/jp → zh/ja)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Fix/workflow source language references (#245)
* test: kitchen sink workflow validation v2
This PR validates the translation workflow after config-driven refactoring:
Changes:
- Add new test file: test-workflow-validation.mdx
- Modify existing file: introduction.mdx
- Update docs.json navigation
Tests:
- New file translation (add workflow)
- Existing file translation (update workflow)
- Navigation sync across languages
- Config-driven language codes (zh/ja instead of cn/jp)
- Source language abstraction (no hardcoded "English")
Expected workflow behavior:
1. Detect changes in en/ directory
2. Translate new file to zh and ja
3. Update modified file translations
4. Sync docs.json for all language sections
5. Commit translated files automatically
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* fix: update workflow paths to use zh/ja instead of cn/jp
Aligns workflow trigger paths with the zh/ja language directory rename.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Revert "fix: update workflow paths to use zh/ja instead of cn/jp"
This reverts commit 9587b7cc5d.
* Revert "test: kitchen sink workflow validation v2"
This reverts commit 4abdd69fd2.
* fix: update workflow paths in doc analyze workflow to use zh/ja instead of cn/jp
* fix: update workflow files to use 'source' instead of 'english'
After refactoring the PR analyzer to use 'source' for source language
PRs (instead of hardcoded 'english'), the workflow files need to match.
Changes:
- sync_docs_analyze.yml: pr_type == 'source' (was 'english')
- sync_docs_update.yml: PR_TYPE != 'source' check
- Updated all comments from "English" to "source language"
- Updated all pr_type values in JSON from "english" to "source"
This ensures the workflows trigger correctly with the refactored
config-driven language system.
Related: language code refactoring (cn/jp → zh/ja)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix
* fix docs.json language codes
* rename previous version docs: cn -> zh, jp -> ja
* rm duplicate redirect entires
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: new version docs about node redirect supplement
* fix: replace some uncorrect destination
* docs: improve redirect just like main branch
---------
Co-authored-by: crazywoola <100913391+crazywoola@users.noreply.github.com>
* draft
* draft
* draft
* refine dev docs
* almost
* update
* remove sys.file and sys.query; add sys.timestamp
* update the end node to output
* modify the introduction section of variable
* fix typo
* adjust image size
* remove unnecessary list
* feedback fix
* remove example
* feedback fix & add en/ja dev docs
* correct description
* fix typos
* replace UI text
* refinements & add zh-ja translation
* feedback fixes
* fix punctuation
* refine heading-reference
* typo
* adjust casing & remove sys.timestamp from chatflow
* Docs tools: 2 succeeded, some failed
Rename operation failed: - Lang 'zh': File 'dify-docs/plugin-dev-zh/0211-getting-started-dify-tool.mdx' - Renaming error: Unexpected error: 'str' object has no attribute 'get'
- Lang 'zh': File 'dify-docs/plugin-dev-zh/0222-datasource-plugin.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
- Lang 'zh': File 'dify-docs/plugin-dev-zh/0222-tool-oauth.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
- Lang 'zh': File 'dify-docs/plugin-dev-zh/0222-trigger-plugin.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
- Lang 'en': File 'dify-docs/plugin-dev-en/0211-getting-started-dify-tool.mdx' - Renaming error: Unexpected error: 'str' object has no attribute 'get'
- Lang 'en': File 'dify-docs/plugin-dev-en/0222-datasource-plugin.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
- Lang 'en': File 'dify-docs/plugin-dev-en/0222-tool-oauth.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
- Lang 'en': File 'dify-docs/plugin-dev-en/0222-trigger-plugin.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
- Lang 'ja': File 'dify-docs/plugin-dev-ja/0211-getting-started-dify-tool.mdx' - Renaming error: Unexpected error: 'str' object has no attribute 'get'
- Lang 'ja': File 'dify-docs/plugin-dev-ja/0222-datasource-plugin.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
- Lang 'ja': File 'dify-docs/plugin-dev-ja/0222-trigger-plugin.mdx' - Skipped (non-compliant):
Missing/empty critical frontmatter fields for renaming: dimensions.type.primary, dimensions.type.detail, dimensions.level, standard_title, language (expected for metadata, though not used in filename suffix anymore).
---------
Co-authored-by: Riskey <riskey47@dify.ai>
Co-authored-by: alterxyz <88554920+alterxyz@users.noreply.github.com>
RiskeyL