Exactly the same as this issue; Component props duplicated
When connected localhost:3000/plasmic-host (dev environment), this is fine.
I then have a “Production” and “Staging” environment in Plasmic, both pointed to the same site’s /plasmic-host.
For some reason, one component shows duplicate props on Production, whereas the Staging environment reads the props absolutely fine.
I was able to fix this by duplicating the block (changing its name). Its functionally identical except for the change in name, but its props are simply no longer duplicated. The original is still in the environment, with its props duplicated. If a member of the Plasmic team wants to further investigate, I can share the Project ID in a private message
Hi @angelo_hague, sorry for the late reply! If your project app host is localhost, we probably won’t be able to use it to debug.
If possible, can you provide the code component registration/meta before and after the fix? Also, can you confirm that you mean you have two different projects, “Production” and “Staging”?
Finally, when you say “duplicating the block”, do you mean the component instance in the studio/editor?
Hi @samuel_pullman,
Sorry for the late reply here.
When I say duplicating the block, I meant I duplicated the files for the Component and Meta that were being imported, and simply changed the component’s name, display name and the export names of the component and meta object, then re-importing.
Both components still exist in the client’s environments (three separate projects, one for dev (localhost), one for staging, and one for production). So we essentially have the old erroneous component, and the new working one (despite them being functionally identical).
The staging and production projects no longer point to the same site’s /plasmic-host, but the issue still occurs for that erroneous component in both projects.
Here’s a snapshot of the broken components. I haven’t included its dependencies, but this is the structure we use and you can see these are functionally identical
@angelo_hague Thanks for the example, and sorry for the late follow up as well. I’ll see if we can reproduce it this week.