Dev Tracker

@Aust @Eve @ReZonancE @ArcaneShadows @Semirhage @CrystalBones

We just made a change that will hopefully address some of these problems. In most cases, instead of getting "Already Logged In" you will instead get a page that will automatically refresh your session for the non-www1 half of the site.

Please let me know if this improves anything for you -- I am sorry for the frustration you have been experiencing in the mean time!

@Stariceling @Nightshades @Inudoragon23 @Coalesce

We just made a change to try to address these problems. In most cases, instead of getting "Already Logged In" you will instead get a page that will automatically refresh your session for the non-www1 half of the site.

Please let me know if this improves anything for you -- I am sorry for the frustration you have been experiencing in the mean time!

@Ergo @mekakucitypkmn @flufflesauce @OerbaYunFang

I'm sorry for the frustration the login changes have caused! We just added a new feature that should fix one of the major problems with the changes. Now, if you try to log in from the non-www1 side of the site (e.g., Lair, Hoard, etc), instead of taking you to "Already Logged In" you should now be taken to a page which will refresh your session automatically, and you should be properly logged into both halves of the site afterward.

If that is still not working for you, please ping me so I can help track down what is occurring.

Hello @Keiene,

This is occurring every time you log in from your tablet with the new system? Can you let me know what browser and OS your tablet runs?

Hi @0scar123456789,

I'm sorry about the crash -- it appears that the error message you received is related to re-submitting a form from an old session. So that error should hopefully not happen frequently, it is possible it was just a result of Safari caching the login page.

That aside, though, were you able to finally get fully logged in, or are you still having issues?

@Atlantahammy --

Sorry for the difficulty you're experiencing. Our official troubleshooting steps are:

• Log out
• Clear your cache
• Close your browser
• Open new browser window
• Log in

Clearing cache and closing/opening browser window are often not necessary, but they are there for thoroughness.

If that is not working for you, may I ask what you see when you try to visit your lair after logging in? Are you able to view your lair briefly and then get logged out again, or does it never truly work?

Hi @Kincee,

Does visiting your lair/hoard/etc work briefly after logging out and logging in, and then stop working, or does it never work for you even after logging in?

Also, could you confirm what OS/device you are using Chrome on? Thanks!

@Nightshades

Sorry for the frustration! We're monitoring feedback, in the end we want this to be smooth for everyone. There may be more we can work on to accomplish that.

@Nightshades

Try logging out and logging back in without clearing cache, the cache clear step is an extra precaution -- in typical cases logging out & back in should fix it.

Hi @Nightshades and @Celestria,

Have you tried logging out, clearing your browser cache, and logging back in?

That is the first troubleshooting step we usually suggest.

Hi @Minxx,

Have you tried logging out, clearing your cache, and logging back in? That is usually the first troubleshooting step for this sort of situation.

At 06:00 Server Time on Friday, April 7, Flight Rising will be moving to a single login page, rather than allowing username/password entry from any page on the site. This change is one of the next steps in our full site optimization efforts and recode process.

Details:

The "Login" button will still be available from every page while you are logged out, but clicking it will take you to a single secure page that you can use to log in.

Additionally, if you arrive at the login page when you are already logged in on the www1 half of the site, you will receive troubleshooting instructions to assist with some common login problems.

The move to a single login page will also allow us to address login/logout bugs more easily by centralizing the login code, and focusing on a single login path.

Some changes have also been made to streamline the login process:

• If you fail to log in, you will no longer have to re-enter your username.
  
  
• Login error messages are now inline in the page rather than being modal dialogs. For example, if you mistype your password, you will not have to click twice to dismiss the dialog and then focus the password field.
  
  
• We have taken steps to ensure that the login page will receive a secure classification by your browser.

Thank you for your patience as we make this change to our login system. We realize that the additional page load is an inconvenience, but this is an important change for us to make going forward.

NOTE: Customer Support staff can only provide account assistance to the account owner. Please take this time to make sure the email address registered to your Flight Rising account is both valid and accessible should you run into any login problems after the change.

The future is now. Site optimization has been going so well, we've decided to test some visual upgrades!





As we continue down the road of optimizing Flight Rising's underlying codebase, we've found some places where we can make visual improvements as well. Starting today, we will begin beta testing phase 1 of Flight Rising HD, a brand-new version of Flight Rising, designed for high-fidelity computers and devices. Every dragon now has a native resolution of 700x700 pixels, making it really pop on 4k and retina screens.

(WARNING: If you do not have a beefy monster computer or tablet or phone, we don't recommend enabling this test feature.)

Not without its challenges, this feature required that all existing artwork be revamped from the ground up. The artists rebelled, but the engineering team knew that we could bring this feature to you even without their help at all!

For now, only dragons are available in HD resolution, but over the coming decade we plan on painstakingly rolling out new artwork across the site in the resolution that this generation of hardware really demands.

Phase 1: HD Dragon Image Toggle

Starting today, we've enabled HD art for all dragons on the website. When you visit Flight Rising dragon profiles, you'll be met with a much more vibrant, much more bodacious, much more extreme visual experience. Again, we recommend exercising caution with using this mode if you feel you don't have the totally-not-cost-prohibitive device hardware to support it.

We understand that some may wish to revert back to the normal boring versions for dragon artwork (though, heh, we don't know why you would), so we have opted to include an HD toggle button, which will do just that. Simply visit a dragon profile, click the toggle button in the top right corner of the screen, and you'll be browsing again in normal super-duper-low-fidelity-mode once again.




(DISCLAIMER: Stormlight Workshop, LLC is not responsible for damage to user devices or minds--in the event that they are TOTALLY BLOWN).


Additional Updates

• An issue that affected logging in from non-www1 pages a few days ago has been resolved.
• Spring is in the air! Winter Wind and Winter Vista have been cycled out, while our Spring's Breath apparel and the Spring Vista have been cycled in!

@HowlingGale @CyrinaLuna @kyofanatic1 @MaccabeusTheMad

We just made a change a moment ago that may have fixed this issue for you.

Can you please try logging out and logging in again from the front page to test?

Thanks for your continued patience while we work through this!

@CyrinaLuna @kyofanatic1 @MaccabeusTheMad

I have a question, based on what @Truth posted. Previous to today, were you having to log in a second time for www pages, even after logging in to www1 to the front page?

If that is a commonality between people having this issue, that may help narrow things down.

Hello all -- if any of you are still having issues, can you please take a look at the troubleshooting steps here and reply to that thread with your results?

If you have already performed those steps as part of your troubleshooting and it is still not working, I would still like to hear from you.

Thanks!

Hello all -- if any of you are still having issues, can you please take a look at the troubleshooting steps here and reply to that thread with your results?

If you have already performed those steps as part of your troubleshooting and it is still not working, I would still like to hear from you.

Thanks!

Hello all -- if any of you are still having issues, can you please take a look at the troubleshooting steps here and reply to that thread with your results?

If you have already performed those steps as part of your troubleshooting and it is still not working, I would still like to hear from you.

Thanks!

Hello all -- if any of you are still having issues, can you please take a look at the troubleshooting steps here and reply to that thread with your results?

If you have already performed those steps as part of your troubleshooting and it is still not working, I would still like to hear from you.

Thanks!

Hello everyone! I'm sorry for the frustrations you are experiencing.

For those of you that are logged in to www1 pages correctly, but getting logged out when viewing non-www1 pages such as Lair, Hoard, Faire/Coliseum, etc., may I request that you try the following steps and then let me know if the problem is still persisting?

1. Log out from the front page
2. Clear your browser's cache
3. Log in from the front page again
4. Try visiting various portions of the site

If you are still having issues after these steps, it would also be very helpful if you could include your Operating System and Browser information in your reply.

Also, just to clarify, the login issue we fixed earlier today was a fix to a temporary degradation in the ability to log in from non-www1 pages. It was not a comprehensive fix for all www/www1 login issues.

Thank you!

Yes, it's definitely correct for them to show those warnings -- the way we are looking at addressing this short term is to create a dedicated HTTPS-only login page, because unless the site is 100% HTTPS-only this concern will always exist (since there is a login form on every page.)

Improving our HTTPS support is something we are definitely interested in. There are a number of behind-the-scenes details we need to sort out before it is feasible to force HTTPS on 100% of pages.

At the moment, our servers do support HTTPS, and we do require it for certain key parts of the site. For example, our login form submits your username and password over HTTPS. Firefox and Chrome are displaying increasingly verbose warnings when logging in from the home page when the surrounding page is not HTTPS, and that is something we are looking at addressing.

In general, we do not forcefully redirect you to HTTPS pages. The most likely path is that we would gradually require HTTPS on incrementally more portions of the site rather than turning it all on at once, across the full site.

@Sherlocked

You will have received private messages for any business relating to the previous version of the Auction House, but you should not receive private messages for any business relating to the revamped Auction House. We did a bulk expiration of every item that was on the old Auction House around 22:00 on March 18th, so you may have received several "final" private messages from the old Auction House around then.

@adenar

If you want to name any unnamed dragons that are currently on auction, you can cancel their oustanding auctions and rename the dragons while they are not in the Auction House. Then you can relist them.

For the purposes of the new Auction House search, every parameter you can search for ideally needs to be unchanging (or very predictable) while the dragon is on auction. For example, we let you search for a dragon based on whether it is named or not, so if you were able to name the dragon while it was on auction, we would have to re-index it in order for it to still operate correctly in searches. More generally, though, since some players may be searching for dragons that they can initially name themselves, we need to ensure that the dragons are not given a name by the seller between when the prospective buyer encounters them on the Auction House and when they complete the purchase.

@JennySigma @blossombranch

Just in case you were not aware -- the revamped Auction House deposits items directly into your hoard, rather then sending them via a private message. If you are not seeing the items in your Hoard, please try clearing your cache, and if that does not make them appear, please send us a ticket via Contact Us!

@Vitalani

Auction House purchases are now deposited directly into your hoard! Sorry for the confusion.

@RedWillia

The fact that new Auction House alerts (such as the "You have X sold auctions to review" alert) disappear from the alerts dropdown if you address them in the Auction House is intentional.

The alert count badge won't automatically decrease, you will still have to view the alert popup for that. Still, the Auction House alerts themselves will disappear from the alerts dropdown if you have no sold, expired or pending private auctions.

@LotusCandy

Based on that size, it seems likely that you are either uploading a file that is not 350x350 pixels or that has not been saved out to PNG-24 (for example, you may be uploading the PSD file.) Our Skin Tutorial page has all the details about how to get it in the exact format we like. Hope that helps!

Hi @LotusCandy , how big is the file you are attempting to upload?

@shnoonigans Can you please send a ticket via Contact Us, including approximately when you edited your profile? We will look into what we can do about this.

Hi @chyannethewolf, I'm sorry for the frustration you had with this. We will need to look at what we can do to improve this part of the site.

If I am reading correctly, it looks like you were able to recover your profile text once you removed the "<3"?

If you were not able to recover all of your profile, please send us a ticket via Contact Us and we will see if we can restore it from a backup.

Again, sorry for the frustration and thank you for your patience with this issue.