# Plugin Working in Local Instance, Breaking on Deployed **URL:** \ **Category:** Development\ **Created:** [December 13, 2024, 3:01pm UTC](https://meta.discourse.org/t/plugin-working-in-local-instance-breaking-on-deployed/342293 "2024-12-13T15:01:33Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![jafab](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@jafab](https://meta.discourse.org/u/jafab)\ **Post date:** [December 13, 2024, 3:01pm UTC](https://meta.discourse.org/t/plugin-working-in-local-instance-breaking-on-deployed/342293/1 "2024-12-13T15:01:33Z")
Hello! This is primarily a question for @angus but if anyone has any suggestions I would be very grateful! I had been working on a variation of @angus Topic Custom Field Plugin and had it working as desired in my locally hosted instance of discourse (version 3.4.0.beta3-dev). Once I installed it on our deployed instance of discourse (also version 3.4.0.beta3-dev), something strange is happening. When a user writes a new post and puts an input into the custom field, it doesn’t save it or render it when the user makes the post. BUT if the user edits the post and then adds the input, it saves it and renders it. So this points me to it breaking somewhere in the connectors (presumably the composer connector), but I can’t figure out why as it works perfectly in my local instance. I have some regex that filters inputs, maybe this could be the culprit? Any suggestions are greatly appreciated, Thank you! [https://github.com/jacksnnn/discourse-topic-custom-fields/blob/main/assets/javascripts/discourse/connectors/composer-fields/topic-custom-field-composer.js](https://github.com/jacksnnn/discourse-topic-custom-fields/blob/main/assets/javascripts/discourse/connectors/composer-fields/topic-custom-field-composer.js) --- _[View the full topic](https://meta.discourse.org/t/plugin-working-in-local-instance-breaking-on-deployed/342293)._