# Manifest ignored on plugin publish

**URL:** <https://forums.creativeclouddeveloper.com/t/manifest-ignored-on-plugin-publish/1282>\
**Category:** UXP Plugin API\
**Tags:** api-feedback\
**Created:** [October 4, 2019, 3:32pm UTC](https://forums.creativeclouddeveloper.com/t/manifest-ignored-on-plugin-publish/1282 "2019-10-04T15:32:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gdreyv](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/gdreyv/32/358_2.png) [@gdreyv](https://forums.creativeclouddeveloper.com/u/gdreyv)\
**Post date:** [October 4, 2019, 3:32pm UTC](https://forums.creativeclouddeveloper.com/t/manifest-ignored-on-plugin-publish/1282/1 "2019-10-04T15:32:48Z")

</div>

When I published plugin all description fields were populated from manifest.json.  
Now on plugin release manifest.json is ignored and old values are used instead. Specifically for plugin description, name and so on.  
Expected behavior - like it was in very beginning, read manifest.json and populate all fields correctly.

---

<div class="post-metadata">

**Author:** ![cpryland](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/cpryland/32/1172_2.png) [@cpryland](https://forums.creativeclouddeveloper.com/u/cpryland)\
**Post date:** [October 5, 2019, 10:22pm UTC](https://forums.creativeclouddeveloper.com/t/manifest-ignored-on-plugin-publish/1282/2 "2019-10-05T22:22:37Z")

</div>

I have the impression that they now want you to fill most of those values in the console.

But, I agree, if you don’t provide them, they should come from the manifest, not default to the old values.

---

<div class="post-metadata">

**Author:** ![kerrishotts](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/kerrishotts/32/8_2.png) [@kerrishotts](https://forums.creativeclouddeveloper.com/u/kerrishotts)\
**Post date:** [October 9, 2019, 3:33pm UTC](https://forums.creativeclouddeveloper.com/t/manifest-ignored-on-plugin-publish/1282/3 "2019-10-09T15:33:22Z")

</div>

So, we’ve separated metadata from the manifest due to the increased amount of content (screenshots), future plans, and also because there are publishers who want to be able to update metadata without having to dig into the dev’s JSON.

If you keep this metadata in your plugin, you’ll start to notice soon that XD will warn in the console that these fields are no longer required. This will simplify the manifest greatly (keeping it more functional rather than full of user-facing data).

If you’re submitting an update to a plugin, we should pull the previously submitted data in the console – but a new plugin won’t have existing data to pull from.

FYI – should you copy and paste from the manifest, watch for escaped characters. “\n” and friends won’t render as you might expect (as in, they’ll render verbatim, not as a newline).