https://twill.io logo
Join Discord
Powered by
# ❓questions
  • r
    ah ok
  • h
    Thank you for the advice. If I have question I will be back. Appreciate the assistance
  • i
    no it's actually to be able to preview content that isn't saved yet @User
  • r
    Yeah that's a good idea 😄
  • i
    we put it in cache with the token, and then the API request can pull from it
  • i
    Copy code
    public function previewData($item)
{
    Cache::put($previewToken, $item, 60);
    return [
        'previewUrl' => $item->preview_url,
        'previewToken' => $previewToken,
    ];
}
  • i
    and in the API:
    Copy code
    $previewing = request()->has('previewToken');

if ($previewing) {
    $item = Cache::pull(request('previewToken'));
}
  • r
    Yeah in my case I have a api route that get draft && published item by slug
  • r
    and in the front a preview route with a ServerRednering
  • i
    since you're using next, did you look into generating at build time? we do that too by listening Twill/model events to trigger a static rebuild. your site seems to be in SPA mode right now.
  • i
    as in, it does API requests on the client side
  • i
    oh no it seems like you're doing SSR, but there are still a couple of client side requests for things like the menu?
  • i
    your SEO meta are rendered server side though, which is the most important bit I guess
  • r
    yeah we use StaticProps
  • r
    for the ssr
  • i
    👍
  • i
    but not staticPaths, right?
  • r
    both 😄
  • i
    ok ok nice. that menu request is what confused me
  • r
    You can't use staticPath without StaticProps
  • i
    correct, it would be getServerSideProps without
  • r
    yeah but no caching 😦
  • i
    yeah
  • r
    and we use vercel for the front
  • i
    nice
  • r
  • r
    and when a "module" is publish or updated an event is fire to the hook for rebuild the cache
  • d
    Try install capsule
  • d
  • d
    for route: 'route' => 'admin.homepages.landing', but where we set "landing" ?
1...567...484Latest