Disney World Reservation System -POST 1 FOR LINKS

I'm exhausted but afraid that as soon as I let myself fall asleep, the AP glitch will be fixed and well miss out on park reservations for our other 3 resort stays. Has anyone had any luck yet with booking park reservations for days they'd previously gotten the message about reaching the limit before?
Not yet. I almost wish we had a little Dis alerts system that could alert every one when it's fixed.
 
Has anyone been able to make reservations in the last 30 minutes? Do we know if the site is down, or just overloaded?
 
Hi, thank you for all the info. I canceled our current trip as Disney was not accepting new reservations at that time, and being nice, I decided to cancel to give them a better head count (August). Are they currently not booking new trips (2021) so I'm out of luck with the park reservations or have to wait until Sunday? We know when we want to go next year, we've just been unable to book it. I can't get another reservation
 

I don’t remember reading this on the website - do you happen to have a link? I’m in the same situation, with a November AP expiration and an on-site December trip that I can’t reserve parks for. Very frustrating!
Whenever I can access the site again, I will send the link.
 
I'm going to get on my soap box here for a moment. Bear with me. :mic:

When you go live with a huge new system or huge new set of changes like this to a major application such as MDE, there are different types of testing required. For example:
  • Testing the overall load of web users hitting the web app all at once. This can be done in a simulated way...to mimic tens of thousands of users all clicking the same buttons at the same time to try to get to the new park reservation part of MDE.
  • Testing various iterations of non-AP users - For example, option #1 might be where all the people in the reservation are staying in ONE resort hotel room and everybody ONLY has regular tickets. No AP people. #2 - regular ticket holders but people in multiple hotel rooms under different reservation #s but their tickets are all linked. #3 - User accidentally clicks the check box for child <age 3, so they should have set up an automated error message telling the user what to do instead. #4 - Everyone has regular tickets and all tickets are the same # of days. #5 - All regular tickets, but variations on # of days on those tickets. #6 - All regular tickets, but they're 14 day tickets and user wants to schedule the park days over a month, not over 14 consecutive days. Etc, etc.
  • Testing AP users - #1 - local AP'ers who only want one day at a time. #2 - AP'ers from out of town who only have ONE resort stay scheduled. #3 - AP'ers who have multiple resort stays scheduled. #4 - APers who have a couple of resort stays scheduled in 2020 and want to schedule consecutive days at various times in 2021 through late Sept.
  • Testing a combo of reg ticket holders & AP'ers together in 1 set of park reservations.
  • Testing a combo of reg ticket holders & AP'ers together when the entire party has 2 or more scheduled/booked on site resort stays between now and 12/31/2020.
  • Failure testing - this basically means that you TRY to get the system to fail. This is important so you can validate that the error messages and error screens, etc. that you've coded are actually going to show up and display like you expected them to. Ideally, you'd have documentation in place for your Customer Service team to access so when the horde of angry users calls on Monday morning to complain about how come they have the pink castle still or the Millennium Falcon on their screen, you can tell them what that means and what to do next.
It's unacceptable. For a company as large as this to have this sort of application disaster is an unacceptable nightmare. And they don't have the option of rolling back the changes and going live on a different date. Their only option is to fix it in place and continue moving forward. From a project management perspective, this could be considered a massive failure.

Please screenshot this and tweet it at Disney. Cause you win in everything right now.
 
If you go back through this thread, you will find lots of people (myself included) got through this way;
  • Open an incognito window in Chrome (Firefox seems to work too)
  • Open a link to add a restaurant reservation. Choose any restaurant.
  • Cancel that when you get to the next window. You should now either already be in your MDE account or have the ability to log in
  • Once in your MDE account, you should now be able to add a park reservation
Done. If you don't have tickets or an AP, or you don't have a hotel or DVC reservation, it will not work.

This is no longer working as simply as it did earlier this morning; now if you aren't logged in yet you get taken to the Millennium Falcon queue/holding page when trying to go to the Dining Reservation page(s)
 
O.....M....G.......!! I just got all the way through again, and Sept 1-7, no available parks for 3 people....?????????? Yet, plenty of availability on the WDPRD Availability Calendar. I am going to have a breakdown. An hour on chat, and she didn't "hear" my issue, nor correct it. 😢😢😢😭😿
 
OMG I finally got through and booked my other days!!! My Edge browser came through first, Chrome and Firefox are still on the Castle. So I would highly recommend that you open windows in multiple browsers so you have a better chance of one of them getting through.
 
I'm going to get on my soap box here for a moment. Bear with me. :mic:

When you go live with a huge new system or huge new set of changes like this to a major application such as MDE, there are different types of testing required.

It's unacceptable. For a company as large as this to have this sort of application disaster is an unacceptable nightmare. And they don't have the option of rolling back the changes and going live on a different date. Their only option is to fix it in place and continue moving forward. From a project management perspective, this could be considered a massive failure.

I don’t disagree with your post at all, it’s just that, in my experience having been through lots of Disney IT launches and issues, this is (unfortunately) pretty typical SOP for them.

I can only imagine how much more frustrating it is for you as someone with inside knowledge of how it should be and could be better!
 
OMG I finally got through and booked my other days!!! My Edge browser came through first, Chrome and Firefox are still on the Castle. So I would highly recommend that you open windows in multiple browsers so you have a better chance of one of them getting through.

Did you refresh? Did you wait? What did you do?!
 
If you go back through this thread, you will find lots of people (myself included) got through this way;
  • Open an incognito window in Chrome (Firefox seems to work too)
  • Open a link to add a restaurant reservation. Choose any restaurant.
  • Cancel that when you get to the next window. You should now either already be in your MDE account or have the ability to log in
  • Once in your MDE account, you should now be able to add a park reservation
Done. If you don't have tickets or an AP, or you don't have a hotel or DVC reservation, it will not work.
I tried - multiple times - did not work for me
 
I'm going to get on my soap box here for a moment. Bear with me. :mic:

When you go live with a huge new system or huge new set of changes like this to a major application such as MDE, there are different types of testing required. For example:
  • Testing the overall load of web users hitting the web app all at once. This can be done in a simulated way...to mimic tens of thousands of users all clicking the same buttons at the same time to try to get to the new park reservation part of MDE.
  • Testing various iterations of non-AP users - For example, option #1 might be where all the people in the reservation are staying in ONE resort hotel room and everybody ONLY has regular tickets. No AP people. #2 - regular ticket holders but people in multiple hotel rooms under different reservation #s but their tickets are all linked. #3 - User accidentally clicks the check box for child <age 3, so they should have set up an automated error message telling the user what to do instead. #4 - Everyone has regular tickets and all tickets are the same # of days. #5 - All regular tickets, but variations on # of days on those tickets. #6 - All regular tickets, but they're 14 day tickets and user wants to schedule the park days over a month, not over 14 consecutive days. Etc, etc.
  • Testing AP users - #1 - local AP'ers who only want one day at a time. #2 - AP'ers from out of town who only have ONE resort stay scheduled. #3 - AP'ers who have multiple resort stays scheduled. #4 - APers who have a couple of resort stays scheduled in 2020 and want to schedule consecutive days at various times in 2021 through late Sept.
  • Testing a combo of reg ticket holders & AP'ers together in 1 set of park reservations.
  • Testing a combo of reg ticket holders & AP'ers together when the entire party has 2 or more scheduled/booked on site resort stays between now and 12/31/2020.
  • Failure testing - this basically means that you TRY to get the system to fail. This is important so you can validate that the error messages and error screens, etc. that you've coded are actually going to show up and display like you expected them to. Ideally, you'd have documentation in place for your Customer Service team to access so when the horde of angry users calls on Monday morning to complain about how come they have the pink castle still or the Millennium Falcon on their screen, you can tell them what that means and what to do next.
It's unacceptable. For a company as large as this to have this sort of application disaster is an unacceptable nightmare. And they don't have the option of rolling back the changes and going live on a different date. Their only option is to fix it in place and continue moving forward. From a project management perspective, this could be considered a massive failure.

I'm a software developer and I agree with your testing plans. I would like to add that even thought this is a new reservation system, they have had inherent problems with the design of their entire site. I don't know if it is because it is designed more with Mobile in-mind, or if it is just poor flow design, but the system is junk. I see that especially in the Fastpass system, in particular, where you have to go through multiple steps to select a fast pass that starts with selecting your party, hitting apply, then going to park, then finding a fast pass, and God forbid you decided on a different park or different ride and you have to start alllllll the way from the beginning.

Even the most basic Login system is so poorly coded that it boggles the mind - it disconnects you for no reason, it doesn't maintain your login state well. I was surprised by how poor this system was a few years ago, and I am now just disappointed that it continues to be in an even worse state now. I mean, this site is pretty much the first thing people see when they want to go to your park - the park is second. Make the first experience better, Disney!!!
 
I go to this page and I see a calendar but no colors that say anything is open, closed, or some parks available.

that's how it was for me on Edge. When opened in Google Chrome and the resort guests tab is selected, it is interactive and shows the colors.
 












Save Up to 30% on Rooms at Walt Disney World!

Save up to 30% on rooms at select Disney Resorts Collection hotels when you stay 5 consecutive nights or longer in late summer and early fall. Plus, enjoy other savings for shorter stays.This offer is valid for stays most nights from August 1 to October 11, 2025.
CLICK HERE







New Posts







DIS Facebook DIS youtube DIS Instagram DIS Pinterest

Back
Top