Webhooks en cache wissen (Next.js en Frappe)

On-demand ISR begrijpen

Marketora vermijdt de trage herbouwcyclus van traditionele statische sitegeneratoren door Next.js On-Demand ISR (incrementele statische regeneratie) met Frappe Document Event Hooks.

Hoe de revalidatieloop werkt

1. Frappe doc_events: Whenever a content document (e.g., MK Help Article or MK Blog Post) is created, updated, or trashed, Frappe triggers marketora_cms.revalidate.on_content_change.
2. Tagresolutie: The CMS calls doc.revalidation_tags() to gather the precise cache tags affected. For an article with slug welcome-to-marketora, the tags include help-article:welcome-to-marketora and help-articles.
3. Veilige POST-webhook: Frappe sends a POST request to your Next.js application at /api/revalidate containing the tags and the shared secret:

{
  "secret": "YOUR_REVALIDATE_SECRET",
  "tags": ["help-article:welcome-to-marketora", "help-articles"]
}

4. Timingveilige validatie: Next.js verifies the secret using a timing-safe equality check, calls revalidateTag(tag) for each tag, and confirms revalidation with HTTP 200.

Cacheproblemen oplossen

Als updates niet direct zichtbaar zijn, controleer dan dat:

• The marketing_url and revalidate_secret keys are present in site_config.json on your Frappe bench.
• The Next.js environment has the matching REVALIDATE_SECRET variable set.