-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
500 (Internal Server Error) #26
Comments
@Pannu786 is it only happening when you click the Buy Now button in the banner or any product on the home page? |
|
It's more than likely an issue with the product slug that the banner points too. Either the product doesn't exist in Sanity or there is no image published for the product. |
Hmm, I will have a look. Thank for the help tho. |
I think i found the problem, you imported capital Product from components when it should have been lower case product and i think this is the reason all four properties of lowercase product is null. Import product instead and let me know if this helps. |
@dmr019 I wish I could say it worked but it did not. |
Its the problem with ur sanity database, u have to go to banner section (open localhost:3333) and there u have "product" field. There u have to change it to a slug that is already existing in the database of any product u wanna display. |
Oh thank you for pointing that out.. I might have a look some day again
into this but I appreciate you took a look. Thanks again to all of you.
…On Sat, 1 Oct 2022, 21:33 Pradhan1999, ***@***.***> wrote:
@dmr019 I wish I could say it worked but it did not.
bro you've not write logic for *Buy Now* button. Add code for that in
HerroBanner.jsx.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKO6XDUGQCK65S36JMYWNCLWBBOFVANCNFSM5WU3YOQA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi
I almost finished this project, but I face this one issue and need help here.
My slug file
The text was updated successfully, but these errors were encountered: