#bks_unexpected
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1377444710037323919
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- bks_error, 1 day ago, 37 messages
hello! Can you share the link to your site where we can see the Element? Please share the test login credentials (if any) and steps to navigate to the page where the Element is displayed.
Here is the link. There is no creds needed. https://scodemo.digitallabsllc.com/checkout.html?email=c7220780-71d3-46df-a23c-e1f30cc46dcc
A demo of a payment on Stripe
taking a look, gimme a while
you have a request to your own server https://scodemo.digitallabsllc.com/create-checkout-session/create-checkout-session that is returning list index out of range
there's no client secret being returned which is probably what is causing that issue
from the code side, nothing has changed. It is the same code that is working on the local. Can you guide me what should I change so it will work on the server?
you need to go through your own code
i wouldn't know why your server is returning list index out of range. You should add additional logging at each line in the section of code that is handling that request to identify the exact line of code that is getting that error first