Replies

Oct 19, 2020 5 years ago Official
Bug
User Avatar
Segfault

Programmer Update: Upcoming Changes


Hello! This update is to give you a heads up on some changes we're making to new.subeta.net's coding this week. We are upgrading some of our tools and making some changes to how things are hooked together behind-the-scenes. These updates are meant to make new.subeta.net a little bit speedier, a little more robust, and easier for us to build moving forward!

We are splitting these into two updates: one we're aiming for tonight (hopefully in a few hours, if we can get it all ready by then - we're so close!!), and one more we are aiming for later this week if all goes well. We hope these updates will roll out smoothly, and we will be around watching each deployment to make sure. If there are any problems, rest assured we will be here working to resolve them as quickly as we can.

To clarify, these are changes to the user interface only, which means this does NOT affect any of the code that actually changes your account data. These changes are to the JavaScript, HTML, and CSS of new.subeta.net only. These changes will not affect the main site or Morostide-related code.

The first update (the one we hope to roll out today) requires a change to how we deploy new.subeta.net; while we hope it goes smoothly, if there are issues then new.subeta.net may have to go offline for a few minutes while we debug it. We of course do not want to take the wardrobe offline any more than absolutely necessary, so if this happens, please rest assured we'll be working to resolve it as fast as possible!

All right, that's all for now - thank you and happy Morostide! We'll keep you updated in this thread :) You'll also be able to see all the updates in admin post highlights!

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

Oct 19, 2020 5 years ago Official
Bug
User Avatar
Segfault

We took this into account, and we considered the option of waiting until Morostide was over, but we decided against it. These updates need to be done now because they solve some problems that were blocking me on important new.subeta.net work that can't be delayed. They are highly unlikely to break any wardrobe functionality, since we've made sure to test the wardrobe every step of the way, but in the case of unforeseen issues we are standing by ready to resolve things as soon as possible. We definitely don't want the wardrobe to be unusable during Morostide either!

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

Hey everyone, that took a few hours longer than we hoped, but we made it! The first update has just been deployed. We were as thorough as possible with testing this before deployment, and we're watching it carefully now that it's up for real :) # siteupdate

[edit] If you notice any new issues on new.subeta.net please let us know on this thread! I'm not seeing anything so far but we're camping out a bit longer to watch.

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

It's unrelated; that one is a known issue since July, but feel free to add to the report: Non-Wearables Appearing in Wardrobe

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

No worries, thanks for mentioning it! Night mode has always been a bit glitchy, and it's possible the update today made it glitchier. But our second planned update is actually meant to address the glitches with night mode (among other things) - so I'll check in with you again once that is deployed, and see if that fixes it for you!

Technical details, if you're curious: Basically, the library that powers our new night mode (and the rest of our user interface!!) came with a few glitches of its own, but has fixed them in the newest version, so we are planning to upgrade the version we use to the newest one! It is involved work, though, since the new version breaks backwards-compatibility in major ways, so we have to manually smooth out and refactor whatever needs it.

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

<3 <3 <3 On the main site, we've been chipping away at the myriad causes of lag/errors for years and it's so nice to see it really start to pay off. There was never a single cause of lag/errors, so it has been (and continues to be) a bit of a grueling process, where we try to isolate factors and improve on them, and each improvement might only make a small difference by itself.

has been doing a lot of heavy lifting on the infrastructure side especially, and we are really set up for success now; I think we have better server and development infrastructure now than ever. It took a lot of costly trial-and-error with different hosting providers to get to this point. So we're super excited about where we are at, and we're enthusiastic about continued improvements and all the great visions we have for Subeta's future!

As for Subeta v2 (new.subeta.net), the update earlier should have made it a tad faster! :) (Though I'm not sure how noticeable it is - maybe slightly?)

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

If you've been using the wardrobe, you've been using new subeta! We are building it at https://new.subeta.net, so by "Subeta v2" or "New Subeta" we refer to everything at that URL.

Custom CSS - as we know it today - won't be possible on the new site, because of how it is written. However,

  1. Night mode / day mode is currently a huge, huge WIP, and not even the colors you see for them are final. The update planned for later this week should get rid of the glitches we've had with it, after which I will be working on making the Night Mode colors a lot better, bit by bit! Thanks for telling me the hex code you use; it gives me a better idea of what is most helpful.
  2. We're not against allowing you to customize the colors; and once we have Day Mode and Night Mode hooked up to work correctly, it will be set up to add other kinds of modes as well - including ones you might be able to customize ;) That said, we have a LOT of work we need to prioritize before we add something like that, but I want you to know we do see the value of having these customization options and would ideally like to still provide that in the future.

As for the Subeta v2 forums; those were highly experimental and we intended to remove the link in the navigation bar; I actually had done the code to remove them last-minute, for this update, and just.. failed to actually save it lol. The link has been removed now. (You could still see them with a direct link, but I'm not sure why you'd want to xD)

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

Your issue is mostly unrelated to this update, since you had the same issue prior to the update and it is affecting pages outside of new.subeta.net as well. Your other bug report is on my radar and I'll work with you there when I can get to it :)

Since Opera is not one of our officially supported web browsers, I am not sure when I'll be able to help you. If everything works for you on Firefox, I suggest just using that to play Subeta for now - sorry for the inconvenience.

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

Good morning! We rolled out the first update last night, and it went very smoothly! ^^

There are two(ish) known issues post-update:

  1. Some of you have mentioned Night Mode got a bit glitchier; there are a few other little CSS kinks here and there as well. We are hoping to resolve these in our second update later this week, which is an major upgrade to the part of the code that handles all of those things - so hang on tight!

  2. When you are not logged in and viewing new.subeta.net, you see a blank white page. I've identified the cause and am working on a fix.

Most of you will not have encountered this issue, since, if you are logged in on Subeta, those login cookies should work for new.subeta.net as well. However, some players on older browsers have this issue despite being logged in on subeta.net; something cookie-related is not working correctly on older browsers. I will look into this issue next. I do recommend updating your browser if possible, as new versions may come with important security updates as well.

individual pings I think that last part is the issue you ran into.

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

The other Opera users in this thread do not have these issues, so I think it is specific to your Opera settings. The info you shared so far gives some hints. I'll post more details on your topic since it is really unrelated to this update. Meet you there- Wardrobe and forums not working on Opera :)

[edit] Pinging in case you want to follow the Opera issue in the topic linked above.

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

Quote
When you are not logged in and viewing new.subeta.net, you see a blank white page.
This issue is now fixed :)

If you are logged in on subeta.net, and the wardrobe currently gives you an error about "you must be logged in to view this page", please post on this thread with your browser, specific browser version, and if you see any errors in the browser console. We only had I think 3 users report this so far, and it seems to be related to browser versions or browser settings, so I will work with you individually to try and pinpoint and resolve the issue. <3

(By the way - if the frequent siteupdate pings bother you, you can mute the ping group and just check Admin Post Highlights whenever is best for you.)

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

Please see my post on your bug report topic, as I think your issue is a bit more specific. Reply to me there, I want to help you out :)

Could you please let me know your browser and browser version? (Apologies if you already said it somewhere and I missed it!) Could you also go to https://new.subeta.net, open the browser console, refresh the page, and let me know if it says anything in the console after that refresh? That would help me a lot. I can give more detailed instructions about how to open the console and stuff if you'd like, just let me know.

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

Thank you, that helped me pinpoint the issue. Your error is due to an older Firefox bug, which has been fixed in newer versions of Firefox. The solution is to update your browser to a newer version. The particular glitch that I think is causing the issue was fixed in Firefox 51, but I recommend updating to the newest Firefox version if possible - version 50 is four years old :o

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

Quote by Trubble
How come it worked before your latest update?

I guess our changes introduced code which Firefox 50 was unable to run correctly, but I can't tell you what exactly - and it's not important, because the message in your console is not coming from our code, it's coming from the code that runs Firefox itself, and causing it to not run the JavaScript code correctly even though the JavaScript itself is valid and correct. As long Javascript code is correct, the browser should be able to run it, which is why Firefox recognized this as a bug in their browser and got it fixed in the next version.

I know it is frustrating, but please understand, we also cannot try to avoid writing specific patterns of correct, valid code just to avoid triggering browser glitches that were fixed 4 years ago. The problem is in the browser, it was fixed in the next version, and the only solution is to update it (so you get their fix) or use a different browser.

Getting a newer browser is a good idea in general, since it is not just bugfixes and improvements you are missing out on, but also four years of important security updates. Website programming languages, like JavaScript, are also getting updated with improvements themselves on a regular basis, and browsers need to make regular updates too, to keep up.

I understand your tools only work in Firefox 50 so you don't really have a choice. In that case, would it be possible to keep Firefox 50 around for those tools, and use a different browser for everything else so you can keep getting those important browser updates?

If you really like Firefox, and can't get two Firefox versions running, you can try searching for "Firefox derivatives" to find browsers that are based on Firefox's code so it'll be more like what you are used to. I think WaterFox might be a good alternative. I hope this helps!

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

Oct 20, 2020 5 years ago Official
Bug
User Avatar
Segfault

If you click this link, it is the wardrobe? https://new.subeta.net/

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

Oct 21, 2020 5 years ago Official
Bug
User Avatar
Segfault

Hm... this sounds like it may be a browser cache issue. Could you please try clearing your browser cache and loading it again, and see if that helps?

If that does not fix the issue, could you please let me know what browser and browser version you are using, and could you open the browser console and copy-paste any errors you see there (if you are on Firefox or Chrome, you can press Ctrl+Shift+J to open the console)

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

Oct 21, 2020 5 years ago Official
Bug
User Avatar
Segfault

Hm.. that error message comes from a browser extension, though I am not sure which one. Have you made changes to any of your browser extensions lately? You can try to disable browser extensions and see if that makes a difference. It could be completely unrelated, I'm not sure.

When it takes you to your wardrobe, could you please copy and paste for me what it says in the address bar of your browser? Does it still say new.subeta.net (the link you clicked) or has it changed to new.subeta.net/wardrobe, or something else?

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

Oct 21, 2020 5 years ago Official
Bug
User Avatar
Segfault

At the moment, we're still kinda finding our footing with Subeta v2, so nothing you see there is final just yet! There isn't really an official feedback thread for it since we are not actively seeking that at the moment, but thank you nonetheless. I've brought it up with along with some ideas for how having a sidebar could work in the newer code, and we agreed that we can try it :)

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

Oct 21, 2020 5 years ago Official
Bug
User Avatar
Segfault

Quote by Senti
I haven&;t made any changes in anything. I clicked that link again and this is what it says in the address bar
<a href="https://new.subeta.net/">https://new.subeta.net/</a>

And when it said that, did the page still load the wardrobe or a blank white page for you? You should see something like this screenshot (this is an image link) https://i.imgur.com/bru8L58.png

Is that not what you see?

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

Oct 21, 2020 5 years ago Official
Bug
User Avatar
Segfault

Yup, it sounds like you're good to go!

Let me try and clear up the confusion about new.subeta.net. We are gradually building a new website for Subeta there, and everything on the current site will be moved over bit by bit. At the moment, "new Subeta" (we also call it "Subeta v2") only has a few things on it, like the wardrobe, avatar borders, and cash shop subscriptions.

Eventually, the goal is for the new website to replace the current one, but we still have a LOT of work to do before it is ready for that; New Subeta is still in the baby stages! We'll have a lot more updates, testing, and opportunities for players to give feedback first along the way. When we are ready to fully move from the current site, it will be a BIG announcement, so you don't have to worry about missing the news.

🐝 ☕ 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.