Does scheduled content work in preview mode?

[fmota]

I can see the issue related to the /_next issue, but after bypassing it, I already see the content, anyway, sorry for the inconvenience, going to improve the docs about it

[efficient_pelican]

so my schedule is called 11/25 - an in my root provider I have:

<PlasmicRootProvider
          loader={PLASMIC}
          prefetchedData={plasmicData}
          skipFonts={true}
          variation={variation}
          globalVariants={[{ name: "Schedule", value: "11/25" }]}
        >

But it’s still rendering the base component

[efficient_pelican]

i set up a sandbox that replicates what I’m seeing. that top banner should be the one attached, but instead it’s Base https://codesandbox.io/s/elated-dhawan-13excz?file=/pages/[[...catchall]].tsx

[fmota]

In the sandbox there’s an issue with the CatchallPage not receiving the variation prop which is not being returned in the getStaticProps .

For forcing a variant it should actually be

<PlasmicRootProvider
      loader={PLASMIC}
      prefetchedData={plasmicData}
      globalVariants={[
        {
          name: "_1125",
          value: "override",
        },
      ]}
    >

ideally the name should be 11/25 but currently we adapt this names under the hood, so we end up requiring _1125 which is not the same reference as you would expect, a component like name wouldn’t be affected by this