mitchell_neill wrote:

Hi.

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

Thanks
Neill.

Hi, I don't know - I didn't try it.

mitchell_neill wrote:

Still does it I'm afriad. This one is actually quite serious. It makes RunQuery virtually unusable in IE :(

mitchell_neill wrote:

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.

mitchell_neill wrote:

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.

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

mitchell_neill wrote:

Okay, I'll check that out and let you know if it fixes it.

Thanks Yaron :)

mitchell_neill wrote:

Hmmm. RunQuery stops working completely with IE 8 when that is enabled. It just hangs :(

Oh well, that's too bad.

mitchell_neill wrote:

Oh how I hate IE. Unfortunately 52% of the world's population disagrees with me :(

mitchell_neill wrote:

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 :(

How many complaints would you say you've gotten, out of curiosity?

mitchell_neill wrote:

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.

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.

mitchell_neill wrote:

Okay, will do :)

Marking as "normal" severity, given that no one else has remarked on the issue.