Last modified: 2014-02-12 23:38:11 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T29497, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 27497 - IE get "Webpage expired" when using back button in RunQuery pages
IE get "Webpage expired" when using back button in RunQuery pages
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Yaron Koren
http://www.parentvoice.info/en/Specia...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-17 15:23 UTC by Neill Mitchell
Modified: 2014-02-12 23:38 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Neill Mitchell 2011-02-17 15:23:06 UTC
Hi.

I'm using Special:RunQuery's and you hit a problem with IE 6/7/8 that 
when you press the Back button you get a "Webpage has expired"
screen. I guess this is because of the Additional Query section of the 
result screen.

Example:

Using IE 7/8 go to 

http://www.parentvoice.info/en/Special:RunQuery/EventQuery

Choose All, All Hampshire. At the calendar, click on an event.
In the event screen click browser back button.
You get page expired screen.

I've been digging around and got advised that this could be a jquery issue. This is what I was told:

"This probably happens when POST request page has javascript that tries to modify html while it has not yet loaded until the end. For example if you have thickbox component call that is not inside jQuery's document.ready block."

Of course this might not be it ;)

This is really causing issues with my users. I can't simply tell them not to press their browser's back button unfortunately. 

Thanks
Neill.
Comment 1 Neill Mitchell 2011-03-08 10:02:05 UTC
Hi.

Do the changes in SF 2.1 fix this issue? I saw that some jquery work was done in this area.

Thanks
Neill.
Comment 2 Yaron Koren 2011-03-08 17:58:04 UTC
Hi, I don't know - I didn't try it.
Comment 3 Neill Mitchell 2011-03-17 11:58:45 UTC
Still does it I'm afriad. This one is actually quite serious. It makes RunQuery virtually unusable in IE :(
Comment 4 Neill Mitchell 2012-01-27 09:50:35 UTC
Unfortunately, I'm getting complaints about this again. It also does it with IE9, so I can't just tell people to upgrade their browser. Any chance of taking a look? 

Many thanks
Neill.
Comment 5 Neill Mitchell 2012-01-27 09:53:46 UTC
Sorry, an example would help wouldn't it ;)

http://www.parentvoice.info/en/Special:RunQuery/EventQuery

Choose any parameters or leave blank. You then  get taken to a calendar of events. Click the little grey + symbol on any event to go to the details page. Then click the back button in IE8/9. You get a page expired error.

Cheers
Neill.
Comment 6 Yaron Koren 2012-01-27 15:02:13 UTC
Hi - I just finally looked into this. It looks like there's a server-side change you can do to fix the problem - see here:

http://bitkickers.blogspot.com/2010/03/apache-fix-for-ie-webpage-has-expired.html
Comment 7 Neill Mitchell 2012-01-27 18:15:40 UTC
Okay, I'll check that out and let you know if it fixes it. 

Thanks Yaron :)
Comment 8 Neill Mitchell 2012-01-27 20:17:19 UTC
Hmmm. RunQuery stops working completely with IE 8 when that is enabled. It just hangs :(
Comment 9 Yaron Koren 2012-01-27 22:20:51 UTC
Oh well, that's too bad.
Comment 10 Neill Mitchell 2012-01-28 00:12:10 UTC
Oh how I hate IE. Unfortunately 52% of the world's population disagrees with me :(
Comment 11 Neill Mitchell 2012-03-16 14:59:08 UTC
This also now happens with Firefox 10.0.2 and SF 2.4.1. So that is now about 90% of all users affected. Even simple runQuery pages now have this problem.

The suggested server side change does not fix this. I am getting a lot of complaints now. To the point where runQuery is not very popular at all with the users now :(
Comment 12 Yaron Koren 2012-03-16 15:09:01 UTC
How many complaints would you say you've gotten, out of curiosity?
Comment 13 Neill Mitchell 2012-03-16 17:32:36 UTC
Over the last week, I have had 3 of my major clients complain that their users are getting in touch about this problem. They are not happy. These people have taken a risk and invested in SMW technology. Money that I am now putting back into the SMW project. Without these people I can't sponsor work. It's that simple.

The sites are used by a lot of people. One is up for wiki of the month. People really like the sites and they are good advocacy for SMW.

Come on Yaron, this needs sorting out. We can't sweep this under the carpet. You know it is not right and we can't expect users to try to work around or put up with this problem. Not being able to use the browser back button is really bad news. 

There must be a way to fix this :) I will pay for time spent on it. It will make a lot of people happy and benefit the community.
Comment 14 Yaron Koren 2012-03-16 17:40:12 UTC
I have no idea what you mean by "not right" in this context, but in any case, if you want to pay for it, feel free to contact me (or some other developer) separately.
Comment 15 Neill Mitchell 2012-03-16 18:29:17 UTC
Okay, will do :)
Comment 16 Yaron Koren 2012-10-02 17:30:02 UTC
Marking as "normal" severity, given that no one else has remarked on the issue.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links