-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Next.js draft mode #502
Comments
Draft mode is also recommended for pages too https://nextjs.org/docs/pages/building-your-application/configuring/draft-mode but the implementations are slightly different which would need to be taken into account. Also there doesn't seem to be a replacement for |
@dottodot Thanks so much for the link! Somehow I had missed that Draft Mode was recommended for pages router. That simplifies what next-drupal needs to support when a website is only partially migrated from pages router to app router. |
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Issue #502 BREAKING CHANGE: The options to the DrupalClient.preview() method were previously ignored. The options are now passed to the NextApiResponse.setDraftMode() method and their TypeScript definition have now changed to match the options parameter of the setDraftMode method.
Fixed with #670 |
The new App Router feature of Next.js 13.4 doesn't work with the old Preview Mode API. Instead Next.js apps that use the App directory need to use the new Draft Mode feature.
Here's a blog post mentioning the Draft Mode feature (under "other improvements") included with Next.js 13.4: https://nextjs.org/blog/next-13-4#other-improvements
And here is Next.js' Draft Mode documentation
This request is related to #442, but that issue specifically mentions the Server Components part of the App Router feature and Draft Mode isn't related to Server Components.
The text was updated successfully, but these errors were encountered: