This channel is not moderated by Netlify staff. For staff and peer support, please head to 👉 community.netlify.com
I could not deploy my production. status is building since yesterday. this site is simple static contents.
deploy log is end with this.
6:47:43 PM: Preparing Git Reference refs/heads/master
6:47:44 PM: No build command found, continuing to publishing
6:47:45 PM: Finished processing build request in 2.982765884sIs there something that is considered to be the cause of that?
Anyone seen this kind of error in the CMS admin UI before?
react_devtools_backend.js:2430 TypeError: Failed to fetch
{type: "ENTRIES_FAILURE", error: "Failed to load entries", payload: "TypeError: Failed to fetch", meta: {…}}
error: "Failed to load entries"
meta: {collection: "config"}
payload: "TypeError: Failed to fetch"
type: "ENTRIES_FAILURE"
__proto__: Object
Step to host site:
1) Add to archive files css folder, img folder and index.html.
2) Upload the archive to Netify
3) Open the site URL
ACT>> page not found message((
logs from deploy details.
12:38:15 PM: Creating deploy upload records
12:38:15 PM: Starting post processing
12:38:15 PM: Post processing - HTML
12:38:15 PM: Post processing - header rules
12:38:16 PM: Post processing - redirect rules
12:38:16 PM: Post processing done
12:38:16 PM: Site is live ✨
deankayton How everyone. Can anyone see what is wrong with my admin/config.yml? It doesn't produce the correct filename as I would expect (it always creates a .md file, so it is as if the slug does not exist at all).
https://gitlab.com/dnk8n/research_db_docs/-/blob/master/mkdocs/docs/admin/config.yml
You can see by history I have tried many things.
Anyone else had this error with ncms.
Warning: Failed prop type: invariant is not defined
at x (http://localhost:3000/_next/static/chunks/1.js:468:66487)
at l (http://localhost:3000/_next/static/chunks/1.js:460:53996)
at http://localhost:3000/_next/static/chunks/1.js:426:189812
at Connect(Component) (http://localhost:3000/_next/static/chunks/1.js:305:26272)
at c (http://localhost:3000/_next/static/chunks/1.js:305:24194)I'm totally loast as to how to debug this efficiently given everything is obscured/minified.
Hi, I'm using Netlify functions to send aws ses emails. The function fires locally perfectly and I get the email as expected but once I get this into production or into build the email does not get sent the first time but upon trying again it sends the previous email that I should have got, it feels like the functions fire but they are out of step and only ever sends the previous request not that current request.
The gist is that a user enters their email, it sends the email to the lambda function, we then check it and send an AWS email with a magic sign in link to that email. Like I said above locally fine works as normal but in build env it only fires the second time and it is a step out each time
(nextjs,custom widget) So, cms custom widget editor, i register a custom editor widget with cms.registerEditorComponent(BannerBlockEditorComponent); in its toPreview i return 'return <BannerBlock data={obj}></BannerBlock>' where banner block is basically a div with a button and an useCallback handler.
In the cms preview the buttons callback doesn't work. So my question is, is it? or should it be possible to have a custom components javascript work? Its like the javascript for the preview iframe isn't being embedded.
[[redirects]]
from = '*'
to = 'https://example.com'
status = 301
This works for https://mywebsite.com/anything but not for https://mywebsite.com.
Does anybody knows how to stop deploying to the main domain?, for obvious reasons I want my client to see the changes just in the default subdomain (someword.netlify.app), after the reviews I can deploy to the main domain. (www.whatever.com).
Does anybody found any docs for that? It seems simple but I can't find the documentation.
Thanks in advance
dev branch that deploys, that you then merge into the main branch, which is what deploys to the main domain and the default netlify subdomain... So you would end up sending dev--someword.netlify.app to the client, which is probably the easiest way to do it.
...name inside the encode function. Where is that coming from? Doc typo?
const handleSubmit = (event) => {
event.preventDefault()
fetch("/", {
method: "POST",
headers: { "Content-Type": "application/x-www-form-urlencoded" },
body: encode({
"form-name": event.target.getAttribute("name"),
...name
})
}).then(() => navigate("/thank-you/")).catch(error => alert(error))
}
Hi, I'm struggling to get netflify deploy previews to work with hugo. Either, links to posts are not clickable with this config:
[context.deploy-preview]
command = "hugo --gc --minify --buildFuture"Or, the theme doesn't render with this config
[context.deploy-preview]
command = "hugo --gc --minify --buildFuture -b $DEPLOY_PRIME_URL"I'm having the same settings for [context.branch-deploy] and pushing to a branch to look at the deploy preview.
I'm using HUGO_VERSION = "0.87.0" and the ezhil theme
Any help would be appreciated.
