Gift Registry Widget Not Working

  • Profile Image
    ddunlavy
    Asked on August 05, 2016 at 10:36 AM

    Hello -

    The gift registry widget is running extremely slow and is not tracking submissions and updating the numbers of available items left properly. It is not recognizing past submissions as it should be.

    Please advise.

  • Profile Image
    Charlie
    Answered on August 05, 2016 at 12:44 PM

    Apologies for the inconvenience. 

    I went ahead and opened your widgets and clicked the "Update Widget" button:

     

    I checked the form again and it seems like the widgets are now working. 

     

    It does seem to take a couple of seconds to finish loading the items, but I presume it is because you have a lot of items listed and you have around 800 submissions. The widgets needs to check if the available items are present in your submissions. 

    Let us know if it is still extremely slow in your end and if you are getting any error messages.

  • Profile Image
    ddunlavy
    Answered on August 09, 2016 at 02:45 PM
    I am having the same issue again – the widget has now been loading (wheel spinning) for close to 5 minutes now and will not populate the choices. Earlier, when it populated the choices it seemed to not recognize previous submissions.
    Please advise.
    Dustin
    Dustin A. Dunlavy, M.A.
    Manager, Admissions
    [COTC logo_45 email]
    [cid:image001.jpg@01D0ACE6.097DF690]
    www.cotc.edu
    ...
  • Profile Image
    Jim_R
    Answered on August 09, 2016 at 04:24 PM

    Hello Dustin, I also noticed the widget indeed loads a bit slower from my end, however it still loads (I had to wait a few seconds give or take). I'm guessing it's loading longer than usual because of the number of entries you have on the Gift Registry widget. To get an idea of how long it takes to load them, here's a short screencast:

    I wasn't able to replicate the same experience you described (waiting for 5 minutes or longer). Can you please give it another try and let us know if you're still experiencing this same issue up until now?

    If possible, if there is anything unique that you do on your end that will allow us to replicate the problem, please let us know so we can have a better look.