langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

dummy #446

New Issue
Closed
opened 2026-02-16 10:19:26 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:19:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @ghost on GitHub (Jul 14, 2025).

Originally created by @ghost on GitHub (Jul 14, 2025).
yindo closed this issue 2026-02-16 10:19:26 -05:00
yindo commented 2026-02-16 10:19:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 14, 2025):

The error you're seeing means Dify expects the plugin identifier to follow a strict format: $organization/$plugin_name/$provider_name (all lowercase, separated by slashes). For example, if your plugin is just called gemma, Dify will expand it to langgenius/gemma/gemma. The identifier gemma/manifest.json does not match this format, so the plugin fails to load and triggers the error you see.

The backend does not directly parse manifest.json or modelfile—instead, it expects plugin metadata to be structured according to its internal schema, and the identifier must be valid for the plugin to be recognized and loaded. File permissions or the presence of Modelfile/model.modelfile alone won't resolve this if the identifier is wrong.

To fix this, make sure your plugin's unique identifier matches the required format, and that your plugin metadata (manifest) is structured as expected by Dify's plugin system. If you are packaging the plugin yourself, double-check the identifier and the manifest fields. If you need an example, the identifier should look like langgenius/gemma/ollama or similar, not gemma/manifest.json source.

If you have control over the manifest, update the id and related fields to match this format. If you still have issues, please share the exact structure and content of your plugin directory and manifest so we can help further.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 14, 2025): <!-- Answer --> The error you're seeing means Dify expects the plugin identifier to follow a strict format: `$organization/$plugin_name/$provider_name` (all lowercase, separated by slashes). For example, if your plugin is just called `gemma`, Dify will expand it to `langgenius/gemma/gemma`. The identifier `gemma/manifest.json` does not match this format, so the plugin fails to load and triggers the error you see. The backend does not directly parse `manifest.json` or `modelfile`—instead, it expects plugin metadata to be structured according to its internal schema, and the identifier must be valid for the plugin to be recognized and loaded. File permissions or the presence of `Modelfile`/`model.modelfile` alone won't resolve this if the identifier is wrong. To fix this, make sure your plugin's unique identifier matches the required format, and that your plugin metadata (manifest) is structured as expected by Dify's plugin system. If you are packaging the plugin yourself, double-check the identifier and the manifest fields. If you need an example, the identifier should look like `langgenius/gemma/ollama` or similar, not `gemma/manifest.json` [source](https://github.com/langgenius/dify/blob/b27c540379c43a4dda72a8684ceb1249b42c6e37/api/core/plugin/entities/plugin.py). If you have control over the manifest, update the `id` and related fields to match this format. If you still have issues, please share the exact structure and content of your plugin directory and manifest so we can help further. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/05d6a04c-72b2-48a2-b741-75436b04672d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/05d6a04c-72b2-48a2-b741-75436b04672d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/05d6a04c-72b2-48a2-b741-75436b04672d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/05d6a04c-72b2-48a2-b741-75436b04672d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/05d6a04c-72b2-48a2-b741-75436b04672d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/05d6a04c-72b2-48a2-b741-75436b04672d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/05d6a04c-72b2-48a2-b741-75436b04672d?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/22336)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#446
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?