Fix event list ajax issues

[mikehand]

So far noticed:

• people "signed up" when not actually
• if event is not members only says need to log in
• asks to add some events to gcal even though should be done automatically

Data appears to be all correct.

[patosai]

Any ETA on when this will be fixed?

[mikehand]

No. Problem is complicated, low incidence, and difficult to reproduce. If you have information that is useful in ascertaining the root cause, please make it known.

ETAs are not a thing for website bugs, as a rule.

On Wednesday, October 7, 2015, Patrick Tsai notifications@github.com wrote:

Any ETA on when this will be fixed?

— Reply to this email directly or view it on GitHub https://github.com/tbpmig/mig-website/issues/185#issuecomment-146300668.

Michael Hand Electrical Engineering/Control Systems M.S.E. The University of Michigan mikehand@umich.edu

[patosai]

The ETA was to figure out if anyone was working on it, since the issue was created many moons ago. I'm noticing a lot of the "need to log in" bug.

Also on the Schlumberger info session, the div to edit/delete shows (though the actions don't go through).

[mikehand]

You don't have those permissions. Screenshots or the info is useless

On Wednesday, October 7, 2015, Patrick Tsai notifications@github.com wrote:

The ETA was to figure out if anyone was working on it, since the issue was created many moons ago. I'm noticing a lot of the "need to log in" bug.

Also on the Schlumberger info session, the div to edit/delete shows (though the actions don't go through).

— Reply to this email directly or view it on GitHub https://github.com/tbpmig/mig-website/issues/185#issuecomment-146303842.

Michael Hand Electrical Engineering/Control Systems M.S.E. The University of Michigan mikehand@umich.edu

[patosai]

These are just some of the events that have those options showing up.

[mikehand]

I'll also need your current position/role. Also browser. Also if you've done anything abnormal like turn JavaScript off

On Wednesday, October 7, 2015, Patrick Tsai notifications@github.com wrote:

[image: screen shot 2015-10-07 at 3 39 05 pm] https://cloud.githubusercontent.com/assets/5304405/10348874/9a744c06-6d09-11e5-8d8c-fc7df814744b.png [image: screen shot 2015-10-07 at 3 39 12 pm] https://cloud.githubusercontent.com/assets/5304405/10348875/9a79172c-6d09-11e5-89c7-f8898298d644.png

These are just some of the events that have those options showing up.

— Reply to this email directly or view it on GitHub https://github.com/tbpmig/mig-website/issues/185#issuecomment-146305854.

Michael Hand Electrical Engineering/Control Systems M.S.E. The University of Michigan mikehand@umich.edu

[patosai]

Electee, Firefox 38.0.5, everything running as normal (no AdBlock, no NoScript, nothing). Sometimes those buttons will show up on some events, then some time later they'll show up on others and the original ones are gone, and the cycle repeats.

edit: same issue in fresh Chrome 45. I'm pretty sure it's a backend problem.

[mikehand]

Ducking Firefox. Making I.E. Look sane

On Wednesday, October 7, 2015, Patrick Tsai notifications@github.com wrote:

Electee, Firefox 38.0.5, everything running as normal (no AdBlock, no NoScript, nothing).

— Reply to this email directly or view it on GitHub https://github.com/tbpmig/mig-website/issues/185#issuecomment-146313312.

Mike Hand

[mikehand]

Patrick, can you test in another browser and see if the problem repeats?

On Wednesday, October 7, 2015, Mike Hand mikehand89@gmail.com wrote:

Ducking Firefox. Making I.E. Look sane

On Wednesday, October 7, 2015, Patrick Tsai <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

Electee, Firefox 38.0.5, everything running as normal (no AdBlock, no NoScript, nothing).

— Reply to this email directly or view it on GitHub https://github.com/tbpmig/mig-website/issues/185#issuecomment-146313312 .

Mike Hand

Mike Hand

[patosai]

Opera and Safari both have the same problem.

[mikehand]

@dadrian Did the above referenced commit do anything to fix the issue? It looks like it's a misnumbering

[dadrian]

I'm confused as to how this commit numbering happened. I'll take a look after quals (e.g. after Tuesday)