WIP Update netlify-cms plugin to work in v2. #6056
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Deploy preview for using-drupal ready! Built with commit 9aef740 |
|
Deploy preview for gatsbygram ready! Built with commit 9aef740 |
This currently works fine when using "gatsby develop" but fails in production when using "gatsy build". In a production site the cms code is affected by the webpackJsonP wrappings and dynamic loading. I added a template to specify the config file location and define a page context to make the script loader happy.
|
Is there any update on the progress of this PR? This is a blocker on me upgrading my project to V2. |
|
There's another PR (#6292) that apparently works, though I haven't tried it myself yet. |
This was referenced Dec 27, 2023
This was referenced Dec 27, 2023
This was referenced Dec 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This currently works fine when using "gatsby develop" but fails in production when using "gatsy build".
In a production site the cms code is affected by the webpackJsonP wrappings and dynamic loading.
I added a template to specify the config file location and define a page context to make the script loader happy.
@erquhart Can you please look at this. I think there is a little more work to make this work in production mode along with the other webpackJsonP modules.