Japan-Digital-Archives / Japan-Digital-Archive

Digital Archive of Japan's 2011 Disasters
6 stars 18 forks source link

Students at Tohoku University cannot make collections #1099

Open meeshmon opened 8 years ago

meeshmon commented 8 years ago

@jcuanm @horak Tohoku University has been trying to use our archive for their class but only 3 out of 20 students were able to build collections. The nature of the problem is the following. They can curate items into a collection box in the search page, but those curated items are not save once they move on to the collection page. Javier, could you please test this with a test account to see if you can replicate? I know there is some javascript related issue related to the archive not remembering an account information moving between pages. But also this could be a problem of the network when multiple users are trying to use the archive, or network port issue blocking access from a certain IP address.

jcuanm commented 8 years ago

I'll create a test account asap.

jcuanm commented 8 years ago

I created a test account, and as of right now, I can't even get to my collections page after adding items into the collection box. It redirects me to the following 404 error:

![Uploading image.png…]()

meeshmon commented 8 years ago

Can you tell with the developer's tool on Chrome what might be causing this? Also do you get the same message using different browsers?

horak commented 8 years ago

I'm not able to replicate this problem with either a new test account nor my own. I'd suggest the students do the following:

Mac:

  1. Log out of the archive
  2. View > Developer > Developer Tools
  3. Hold down the refresh button or right click it
  4. Click Empty Cache & Hard Reload
  5. Log back in and try again

Windows: I think instructions are similar enough to replicate, maybe @jcuanm can confirm (you have a windows machine right?)

meeshmon commented 8 years ago

@horak Thank you for the note. Some of the people who have the issue is Sebastien who you worked with last September when they can to Reischauer to present. I remember you working with his computer to try to find out a problem but no avail. I think they are well aware of the solution you have suggested both in mac and windows. The problem could be due to some network traffic issue or port issue 8080 for example. It is very annoying that the same issue keeps on coming up mostly with Japanese users oversea. I myself cannot replicate this issue like you could not. @jcuanm can you tell us what issue you had when you could not even get to the collection page?

horak commented 8 years ago

Ah it's the same issue. I remember having him send me some information, I'll dig that up and study it.

horak commented 8 years ago

unnamed unnamed-1 unnamed-2

horak commented 8 years ago

Ok, trying to organize a remote debug session soon.

jcuanm commented 8 years ago

I have the issue that doesn't let me even see my collections page both on Google Chrome and IE 11. I have yet to test Alex's recommendation.

horak commented 8 years ago

I spoke with Sebastien and I've got a number of items to investigate, I've noted those in my personal documentation. Will report back on what I find.

meeshmon commented 8 years ago

Thanks @horak for working with Sebastian. From what I can read in your personal documentation, there seems to be some identifiable issue for not being able to save/access the collection page. I hope you have some idea as to how to tackle this.. Since the Tohoku University is planning to use the archive again for their class on Aug 1st (July 30th here EST), could you point to a possible backdoor way to avoid this issue from affecting their class? Even if you cannot fix the problem, it would be sufficient for the time being to be able to provide a way for people to go around it and make a collection.

Thanks!

horak commented 8 years ago

@meeshmon, I see! Yes I will look into that ASAP.

horak commented 8 years ago

Worked on this a bunch today, I'm going to setup another call with Seb. I've isolated the main problem to the 401 that occurs on a PUT to the /items route. I think that users are just not getting properly logged in. I'm going to try to set something up with him ASAP. If I find a temporary fix i'll apply it but this is a very strange and tricky bug so investigating the heart of the matter is likely more fruitful. But my debugging session today was useful and I have a new thing to test with him.