Dynamic Value not working when published with Plasmic Hosting

I’ve made a component that has a single-select group of variants.

  • The active variant is based on a dynamic value(with some code) linked to the component variant field.
  • That dynamic value is from a state.
  • The component will switch variants depending on the interaction. e.g. when the ‘edit icon’ is clicked, it will open up a form to allow edit etc.

On a separate note, this project had some issues a few weeks back, where the new changes published to Plasmic Hosting don’t show up on the published site. That issue has since been resolved by the Plasmic Team.

The component worked fine before the issue mentioned above. Now, it works when ‘previewing’ in Plasmic Studio (i.e. clicking on the green play button, not just interactive mode.) But, it doesn’t work on the published site (I used Plamic Hosting).

This is the component, and the edit icon mentioned.

When clicked, it should change to the open variant. (which works in preview mode in Plasmic Studio)

To troubleshoot, I’ve test out a few things:

  1. The component uses the dynamic value from a state to update the variant. I’ve connected the variant state’s value to some text to see if they are being updated when the component’s interaction is fired. As you can see below, the interaction does update the state in the site published with Plasmic Hosting. But it doesn’t change the variant of the component.

  1. I’ve also tried creating a new test component and ‘wired’ it the same way (by linking the variant to a dynamic value from a state, and updating that state with an interaction). The new component works as intended in the live site published with Plasmic Hosting. Below is the screen capture of that.

  1. Finally, instead of directly adding the dynamic value to the variant field of the component, I tried creating a new prop in the component and set that as the value for ‘use dynamic value’ within the component variant(shown in the image below). That somehow works even when published with Plasmic Hosting. This workaround works, but is not desirable.

Summary: The component’s variant doesn’t change on the live site, but works in preview mode. Using a prop and linking that prop to the component variant’s ‘use dynamic value’ (internally) works. New components with variants work fine.

I hope someone can look into this, because the problems with publishing to Plasmic Hosting has really been delaying my progress on the project. Any help is greatly appreciated.

Relevant links:

  • My project: Plasmic
    please note, my project is set to private because my database is connected to it atm.

Hi, thanks for reporting the issue, we will be investigating it

1 Like

Great! looking forward to hearing from you soon. Thank you. :pray:

Good day @fmota, just following up on this. Sorry to bug you. Just wondering if you’ve been able to identify what’s causing this.

I’ve not made any changes to the project so you could check out the issue. Can I continue working on this project (and component), while waiting for the fix?

The component with the issue is the main component that I will be reusing throughout my app, so I’m kinda worried if I will be able to use it.

Hi, feel free to continue working on the project while we investigate the issue.

1 Like

Hi, do you remember if you used the following menu in your variant ? We are pushing a fix for this menu.

Captura de Tela 2024-05-21 às 15.20.19

Hi @fmota, I did play around with ‘read and write’ and ‘read only’ before(when I was building the component), but for the final version of the component, I’ve reverted to the default which was ‘private’.

Yes, that was the issue, we pushed a fix for it, if you try to reset the external access it should now work

1 Like

Got it! It works now. Thank you so much @fmota :blush: