Can't edit CW slots
Filter
Show Official Posts OnlyReplies
I have to edit a slot on a cw that is approved and I get a blank page and it doesn't change.
https://subeta.net/explore/custom_clothing_process.php is the address and a blank page shows up.
[edit]
I figured out it only happens when a slot has been rejected that you can't edit the slot.
Just letting you know this is on our radar. Sorry for the late response.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
no worries sweetie. Thanks for having it on your mile long list of things. <3
I'm back with a couple questions. I tried to get this error to show up, here is what we did:
- Another staff member slotted herself for 4 slots, and put me in the 5th slot, for an existing CW she owns.
- I rejected my slot.
After rejecting the slot, the slot was given to her. She edited the slot back to my username, and I got the payment ping again. We didn't encounter any errors.
Is this similar to what you did? Could you describe in more detail (if you remember) what happened when you ran into the error? For example:
- Were you editing the username, price, both?
- Were you editing just a single slot, or multiple slots at once?
- Were the other slots already paid?
- Did you run into this issue multiple times? (With multiple CWs?)
Thanks.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
So what happened from what I can remember....
1.username and price 2.just a single slot 3. not all slots were paid for yet 4. no, just with the one item
The item was also already approved and this was a new batch. What happened was I accidentally slotted someone twice, so when they rejected it, I was just trying to put in the next person on my list, and this is when I got this error.
(sorry it took me a couple days to get back to you, been crazy busy at my kids school and with my FIL passing)
I'm sorry this wasn't responded to earlier, ! Have you encountered this issue again since that one time?