907814 - Submit event button not clicking through to event confirmation

Status: RESOLVED WONTFIX

(Webmaker Graveyard :: Events, defect)

Description

[Amira]

Multiple events and people not knowing that their events are being uploaded due to this bug. User inputs event info and clicks submit but nothing happens. Each time they click submit another event is being added but they don't know it. 

Here is a user's experience laid out:

    "I had MAJOR problems with the http://webmaker.org/events  page  when I was using it on Google Chrome – it didn't look like the  event  was being submitted at all (there was literally no movement on  the  page) so I pressed load many, many times and… now there are a  million  (give or take) MaRS Energy Hackathon event listings, and I have  no way  to erase even one of them because the account info  says I  don't have any makes. I tried using the contact email address  for  assistance, but then got a notification that my email was being held   for review before it went out to a whole list? I have since erased   that, thank goodness, so my embarrassment is not  Complete.  :( Please  Help!"

Comment 1

[sookramsaroop]

Attachment: Event open but submit button not working

Comment 2

[sookramsaroop]

Attachment: multiple entries of coderdojo event

Comment 3

[sookramsaroop]

Just attempted to add the codor dojo event for august 25th. I hit the submit button and nothing happened. I hit it a second time, still nothing. At that time, knowing there were issues, I decided to check the backend and saw the four entries. 

I'm using a chromebook with the latest chrome os. 
I was entering events as well as browsing the web/csol site for events to enter.

Comment 4

[Chris DeCairos (:cade)]

I cannot seem to reproduce this using Firefox 25 or Chrome 29.. A couple questions:

What version of what browser causes this behaviour?

Does it happen every time you create a new event?

If not, do you notice that a certain bit of data entered makes it happen?

Are there any intermediate steps causing this to happen? i.e switching to different tabs, creating an event registration page, minimizing the browser, etc.

One possible reason this is happening might be due to the SSO bug that logs accounts in and out when they use an email that has an identity bridge (like a mofo email or a gmail account) but I have yet to confirm this is the case.

Comment 5

[sookramsaroop]

Here's the info on my chromebook
Version 28.0.1500.95
Platform 4100.89.0 (Official Build) stable-channel lumpy
Firmware Google_Lumpy.2.111.0
I see an update on the chromebook that I haven't updated to yet, so this should be the same build as when I had the problems.

I was switching between the Chicago Summer of Learning site (http://chicagosummeroflearning.org/explore) and the events page. I was logged on to the mozteach account. There were other tabs open as well, but I wasn't switching between them on a regular basis (gmail, a couple etherpads, hootsuite, G+, facebook, swag request page and possibly a couple other). I wasn't doing any minimizing of browsers.

It does not happen all the time. I've been adding events all day today and it hasn't happened once, although I have noticed today it will freeze and nothing will happen. I have had to log out and in and resubmit the event. Previously, when it froze, if you kept hitting submit, the event would go through each time.

Comment 6

[Chris DeCairos (:cade)]

This is almost certainly being caused by the iframe SSO problem reported in Bug 894860

Comment 7

[Chris DeCairos (:cade)]

I don't think this is an issue anymore, as I've not heard problems assiciated with it in months. We can re-open it if the problem comes back.

Comment 8

[Matt Thompson (@OpenMatt :OpenMatt)]

@ Amira: are you able to confirm that this bug has been fixed? 
and/or: is it a dupe?

Comment 9

[Amira]

(In reply to Matt Thompson (@OpenMatt :OpenMatt) from comment #8)
> @ Amira: are you able to confirm that this bug has been fixed? 
> and/or: is it a dupe?

Well, the volume of people adding events to our site is no where near what it was in the summer so we don't see many bug reports these days but with that being said, there are no event duplicates in the backend for the past month to support that this still exists. I also just did a test and it worked for me.