Replies

Dec 15, 2020 5 years ago
If ever a whiz there was
Georgie
is a whiz because
User Avatar
Holly Daze

It would be great if there were a link to the regular site from the CW shops.

Dec 15, 2020 5 years ago Official
Bug
User Avatar
Segfault

We are hoping to add a "Back" button in general. See related suggestion: Easy Link back to Subeta site, please?

🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights

Dec 15, 2020 5 years ago
usagi
has some electric moves!
User Avatar
Josie

ran off to look up most wanted cw on site ...

"WAREHOUSED"

me: oh okay that maybe means I have hope, idk?? need to look up what warehoused means

opening up "View More Info"

Layer: Head Number Sold: 0

and user inactive

me: .. I guess .. there is no hope after all ;___;

(lol ty subeta for giving me realistic expectations through this very useful cw system)

[sup]"We are like the dreamer who dreams and then lives inside the dream."[/sup] [sup]art by [/sup] [sup]cute gallery[/sup]

Dec 15, 2020 5 years ago
Valiska
is wicked but sweet
User Avatar
Ravage

the spoiler tags aren't broken, they just take up hella space on the page. I took all the spoilers out but when I get a chance I'll put them in


Slotting | CW Shop | Owned List | Releases
[KISS=Valiska] * [DANCE=Valiska] [Flower=Valiska] * [tot=Valiska] * [egg=Valiska] * [tp=Valiska]

Dec 15, 2020 5 years ago
Disasters
User Avatar

Funny now they’re working... but

I am only able to put them on unlimited IF I have the number counter over zero maybe that was the issue I was having?

another screenie here

Dec 15, 2020 5 years ago
If ever a whiz there was
Georgie
is a whiz because
User Avatar
Holly Daze

Thanks for the link, Bug/ Not pinging you because I think you have enough!

Dec 15, 2020 5 years ago Official
Bug
User Avatar
Segfault

Enough people have asked about it that I just added a tooltip to the little "Warehoused" label, haha. Now, if you hover over it, it will explain briefly what Warehoused means. That should help people who are just browsing the directory, I totally get the confusion if you're seeing it there for the first time!

However, we really tried to make it clear in several places. The warehouse is also explained in the Transition Guide, the Manage Shop Items page, the Warehouse page itself, various staff posts prior to release, and also in this very news announcement :P

I highly recommend that all CW releasers read the Transition Guide in its entirety. It may be long, but it will tell you all the information you need to know about this update as a CW releaser, so it is worth sitting down and reading through it. We worked really hard to make sure it is clear and covers everything :)

🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights

Dec 15, 2020 5 years ago
usagi
has some electric moves!
User Avatar
Josie

I realise, I looked it up later, sorry if it sounded like I was complaining, I was too excited to see the cw database so I skimmed through the transition guide, thanks

[sup]"We are like the dreamer who dreams and then lives inside the dream."[/sup] [sup]art by [/sup] [sup]cute gallery[/sup]

Dec 15, 2020 5 years ago
Disasters
User Avatar

Not gonna ping you Bug but adding that some items that are in my shop don’t appear in shop search while others do.

https://subeta.net/user_shops.php/search/shops/Festive+Blow-Up+Snowman

Vs

https://subeta.net/user_shops.php/search/shops/Funky+ferret+vest

Both items I added today but one shows in shop search and one doesn’t.

Dec 15, 2020 5 years ago
shylarah
is a Time Lord
User Avatar
Yahrzeit

sorry for the delay; I'd gone to bed. Yes, now the add to/remove from wishlist button clearly works! Huzzah!

The way some people spell makes me wonder about their pronunciation. My CW shop, and my ping group

Dec 15, 2020 5 years ago
jensen
rolled snake eyes
User Avatar
RM

I'm not sure if I should put this here or somewhere else, but I was trying out the new cw directory and it turns out that it (or maybe new.subeta as a whole?) doesn't display frozen usernames with a line through it like the current site does :0

I don't know if that is intentional, or just something you guys might've overlooked? If it's intentional, it would be nice if the strikethrough came back to make it easier to differentiate inactive users vs frozen ones when browsing the directory ^^


Also, I am having problems with the "all" category directory filter.

I filtered for companions and then tried to go back to seeing everything by changing the filter to "all" and then hitting search, and it just shows no results.

this got kinda long sorry Experienced issue on both Safari Version 14.0.1 (I am apparently short one security update so I uh. will be downloading that shortly and going to 14.0.2) / Firefox 84.0 (64-bit)

load page filter: layer "all", category "companions" https://new.subeta.net/cws/directory?category=48&layer=0&availability=all&page=1 returns results change category filter: layer "all", category "all" https://new.subeta.net/cws/directory?category=all&layer=0&availability=all&page=1 no results change layer filter: layer "arms", category "all" https://new.subeta.net/cws/directory?category=all&layer=2&availability=all&page=1 no results

However, starting from https://new.subeta.net/cws/directory?page=1 and clicking search (not changing anything from layer all / category all) does return results https://new.subeta.net/cws/directory?category=0&layer=0&availability=all&page=1

And I can't seem to dupe the issue with the layer filter?

load page filter: layer "ankles", category "all" https://new.subeta.net/cws/directory?category=0&layer=1&availability=all&page=1 returns results change category filter: layer "all", category "all" https://new.subeta.net/cws/directory?category=0&layer=all&availability=all&page=1 returns results change category filter: layer "all", category "bottoms" https://new.subeta.net/cws/directory?category=27&layer=all&availability=all&page=1 change category filter: layer "all", category "all" https://new.subeta.net/cws/directory?category=all&layer=all&availability=all&page=1 no results

So I am specifically having problems with the "all" category filter, while using Safari or Firefox.

oh sacred spork, smite mine enemies

Dec 15, 2020 5 years ago Official
Bug
User Avatar
Segfault

First off, just letting you guys know, I have a second job nowadays so I will have to get to these fixes a bit later in the day. Everything will be dealt with in a timely manner still <3

Yes, I think you might be right, that it's happening in the specific case where unlimited is checked and stock is 0. The shop search page on the main site is still trying to find things in the old CW shops; I will update it to the new ones and let you know.

User hover: neither intentional nor overlooked; the item and user hovers are both works-in-progress; we didn't want to delay the CW update any further just to add details like that, so unfortunately we had to make the call to release with some things like that being unfinished, and hope that people understand. The birthday icon and the frozen user strikethrough are top priorities to add to that though!

I'll look into those search filters later for sure; thank you so much for the detailed report, that will make it so much easier to debug on my end. At first glance, I think the issue might specifically be with category=all; I think that's the one thing all the broken links have in common? (Let me know if I'm mistaken please)

🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights

Dec 15, 2020 5 years ago
feral
will always find their way
User Avatar

Okay I finally had the time to read through everything / experience the whole system and all it's steps and everything.

A+, you guys did seriously amazing. I'm blown away, I'm moved to happy tears. This feels like an unbelievable achievement you guys are sharing with us. Thank you so very much. I'm so happy, and so thrilled to see what the future holds.

Please take care of yourselves, don't let us spread you too thin. ILU all. TY. I'm so happy to have a place to come back to again. ❤️

Dec 15, 2020 5 years ago
jensen
rolled snake eyes
User Avatar
RM

oh, i must've missed the news about the hovers on new.subeta! thanks for letting me know :D

& yeah, as far as i can tell, it's just category=all that's having problems! so hopefully whatever's hiccuping is something simple :0

oh sacred spork, smite mine enemies

Dec 15, 2020 5 years ago
Emyon
would tap that
User Avatar
Glacial

just coming here to say amazing work, aside from the lag that was to be expected, i haven't had any issues and everything is super clear and easy to follow ♥

Dec 15, 2020 5 years ago
Truffula
is quali-tree company
User Avatar
Daryonka

I really love the new system. I want to look through the item directory. However, when I try, the entire page goes blank. I'm not sure at what point it happens, but it was on page 2 earlier and now it's on page 3. So maybe there's a particular item triggering it to happen on the page where it goes blank?

Note: this is the same behavior we've seen before with errors in the new wardrobe, where the whole page displays for a while then blanks out on an error. Just that now it's happening while paging through the custom wearable item directory.

Dec 15, 2020 5 years ago Official
Bug
User Avatar
Segfault

Any javascript error that crashes the page will look like a blank white page to users. If I can reproduce it on my end (not on the real website, but on the version on my computer that I work on) it will show an actual error message to me that gives a hint where the error is happening - then it is usually a quick fix.

The next time it happens to you, could you please copy-paste the exact URL that's in the address bar when it goes blank? Could you also let me know your browser, OS, and device information? Thank you. I have the same line of thought as you - that it's a specific item that the page is not handling correctly. But since no one who reported this has given a URL so far, I don't know where to start pinpointing which item it could be. Even if that is not the issue, I still need a URL as a starting point to investigate it :)

🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights

Dec 15, 2020 5 years ago Official
Bug
User Avatar
Segfault

Also, please read the second post on this topic - there are a few things there that you should try on your end, just to rule out possible factors on your end that might be affecting things. Please let me know when you've done this so I can rule those out :)

🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights

Dec 16, 2020 5 years ago
Truffula
is quali-tree company
User Avatar
Daryonka

It was this page when it happened: https://new.subeta.net/cws/directory?page=3 but that page is fine now. So now I think it was something else, not the specific page...

Chrome, Windows 10, desktop machine. I'll check the js console for errors if I can recreate the whitescreen issue.

ok, finally reproduced here: https://new.subeta.net/cws/directory?page=11

js errors in spoiler:

js errors ailed to load resource: the server responded with a status of 404 () /cws/directory?page=8:1 Access to fetch at 'https://sapi.subeta.net/v1/user/Cathii' from origin 'https://new.subeta.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. sapi.subeta.net/v1/user/Cathii:1 Failed to load resource: net::ERR_FAILED /cws/directory?page=8:1 Uncaught (in promise) TypeError: Failed to fetch sapi.subeta.net/preview/225354.png:1 Failed to load resource: the server responded with a status of 504 () /cws/directory?page=2:1 Access to fetch at 'https://sapi.subeta.net/v1/user/Ava' from origin 'https://new.subeta.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. sapi.subeta.net/v1/user/Ava:1 Failed to load resource: net::ERR_FAILED /cws/directory?page=2:1 Uncaught (in promise) TypeError: Failed to fetch img.subeta.net/items/undefined:1 Failed to load resource: the server responded with a status of 404 () lib-index-d53bc1a3.d74550466559f6d7117e.js:1 Error: Minified React error ; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at ka (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Object.off (lib-react.bf635cd670ee877630d3.js:2) at lib-react.bf635cd670ee877630d3.js:2 at co (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at _u (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at t.unstable_runWithPriority (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Yl (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Cu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at su (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) ao @ lib-index-d53bc1a3.d74550466559f6d7117e.js:1 lib-index-d53bc1a3.d74550466559f6d7117e.js:1 Uncaught (in promise) Error: Minified React error ; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at ka (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Object.off (lib-react.bf635cd670ee877630d3.js:2) at lib-react.bf635cd670ee877630d3.js:2 at co (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at _u (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at t.unstable_runWithPriority (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Yl (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Cu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at su (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) 225211.png:1 Failed to load resource: the server responded with a status of 504 ()

Ew, it's a CORS error. I hate those! Sympathies to you, Bug. 💙 You're doing great at this.

As for the suggestions: I didn't clear my cache again after your post above, but I had done that before. I can try it again, but this looks like it's caused

I don't have ad blocker, user scripts like tampermonkey or what have you, or browser add ons, it's just Chrome as it is out of the box (I use it for testing my own stuff, those things would be in the way). I don't have cookies whitelisted but I haven't seen that being an issue; I can go whitelist cookies but the problem seems to be something else, given how long it takes to make it happen (about 10 minutes this most recent time).


edited to add:

whitelisted cookies from the 3 domains.

reproduced on https://new.subeta.net/cws/directory?page=2

js error this time 225361.png:1 Failed to load resource: the server responded with a status of 504 () Failed to load resource: the server responded with a status of 404 () lib-index-d53bc1a3.d74550466559f6d7117e.js:1

Error: Minified React error ; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at ka (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Object.off (lib-react.bf635cd670ee877630d3.js:2) at lib-react.bf635cd670ee877630d3.js:2 at co (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at _u (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at t.unstable_runWithPriority (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Yl (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Cu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at su (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) ao @ lib-index-d53bc1a3.d74550466559f6d7117e.js:1 lib-index-d53bc1a3.d74550466559f6d7117e.js:1 Uncaught (in promise)

Error: Minified React error ; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at ka (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Object.off (lib-react.bf635cd670ee877630d3.js:2) at lib-react.bf635cd670ee877630d3.js:2 at co (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at _u (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at t.unstable_runWithPriority (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Yl (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Cu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at su (lib-index-d53bc1a3.d74550466559f6d7117e.js:1)

Reactjs.org says:

Quote
Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

Also it had these warnings:

jswarnings [DOM] Found 3 elements with non-unique id : (More info: https://goo.gl/9p2vKq) <input class=​"chakra-radio__input" id=​"availability" type=​"radio" name=​"availability" value=​"all" checked aria-describedby=​"availability-helptext" style=​"border:​ 0px;​ clip:​ rect(0px, 0px, 0px, 0px)​;​ height:​ 1px;​ width:​ 1px;​ margin:​ -1px;​ padding:​ 0px;​ overflow:​ hidden;​ white-space:​ nowrap;​ position:​ absolute;​">​ <input class=​"chakra-radio__input" id=​"availability" type=​"radio" name=​"availability" value=​"stocked" aria-describedby=​"availability-helptext" style=​"border:​ 0px;​ clip:​ rect(0px, 0px, 0px, 0px)​;​ height:​ 1px;​ width:​ 1px;​ margin:​ -1px;​ padding:​ 0px;​ overflow:​ hidden;​ white-space:​ nowrap;​ position:​ absolute;​">​ <input class=​"chakra-radio__input" id=​"availability" type=​"radio" name=​"availability" value=​"retired" aria-describedby=​"availability-helptext" style=​"border:​ 0px;​ clip:​ rect(0px, 0px, 0px, 0px)​;​ height:​ 1px;​ width:​ 1px;​ margin:​ -1px;​ padding:​ 0px;​ overflow:​ hidden;​ white-space:​ nowrap;​ position:​ absolute;​">​ /cws/directory:1 [DOM] Found 3 elements with non-unique id : (More info: https://goo.gl/9p2vKq)

Cleared cache again, logged out and back in, browsed again and this time error happened on

https://new.subeta.net/cws/directory?page=4

JS error this time (after cache clear/ login/logout, with cookies whitelisted from sapi.subeta.net, subeta.net and new.subeta.net in chrome settings. Still windows 10 / chrome with no plugins or userscripts or adblock / desktop pc.

this set of console errors is very similar to the previous one.

last set of javascript errors Failed to load resource: the server responded with a status of 404 () lib-index-d53bc1a3.d74550466559f6d7117e.js:1 Error: Minified React error ; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at ka (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Object.off (lib-react.bf635cd670ee877630d3.js:2) at lib-react.bf635cd670ee877630d3.js:2 at co (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at _u (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at t.unstable_runWithPriority (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Yl (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Cu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at su (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) ao @ lib-index-d53bc1a3.d74550466559f6d7117e.js:1 lib-index-d53bc1a3.d74550466559f6d7117e.js:1 Uncaught (in promise) Error: Minified React error ; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at ka (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Object.off (lib-react.bf635cd670ee877630d3.js:2) at lib-react.bf635cd670ee877630d3.js:2 at co (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at _u (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at t.unstable_runWithPriority (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Yl (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at Cu (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) at su (lib-index-d53bc1a3.d74550466559f6d7117e.js:1) 225351.png:1 Failed to load resource: the server responded with a status of 504 ()

Dec 16, 2020 5 years ago Official
Bug
User Avatar
Segfault

Thank you so much! That helps a lot.

And uh, thanks for the sympathies haha. CORS errors are always really hairy. However, just since you brought it up - I am pretty certain it is not actually a CORS error. It is a really annoying thing (that has tripped me up before) but that CORS error you see there is often a red herring - which I believe is the case here too, because our CORS is.. definitely fine. All that's required for the browser console will report it as a CORS error is if the response is missing the Access-Control-Allow-Origin header. It makes you think it is an improper CORS configuration, but a missing header could be caused by much more than improper CORS setup; there's a lot a web server issues that could cause the header to not get set, such as a timeout at certain parts of the pipeline. The browser console cannot access the error details, however, because it does not have permission, due to the missing CORS header.

[edit] TYSM for the extra information! This is super helpful!

🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights

Please log in to reply to this topic.