This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Latest FireFox update (v15.0.1) breaks sorting on Google Sites

  • 3 biyano
  • 19 eza na bankokoso oyo
  • 1 view
  • Eyano yasuka ya AyesRambler

more options

When using Google Sites feature in Google Apps, the sort feature in the list template page does not work. If you try to sort a list, you get a "server error" message which displays at the top of the page.

This problem is new to v15.0.1 of FireFox. Older versions of FireFox, Internet Explorer 8, and Chrome do not currently have this problem.

When using Google Sites feature in Google Apps, the sort feature in the list template page does not work. If you try to sort a list, you get a "server error" message which displays at the top of the page. This problem is new to v15.0.1 of FireFox. Older versions of FireFox, Internet Explorer 8, and Chrome do not currently have this problem.

Ezalaki modifié na DeanCAI

All Replies (3)

more options

I have setup a temporary Google Apps test site where you can see this error for yourself:

https://sites.google.com/a/cascadeservices.org/intraweb-test/

more options

Looks like a problem with the script that sends a sort request to the server.
I see a sorting message followed by a server error message.

If you check the HTTP request and response header with the Live Http Headers extension then you see that the "sortCol" and "sortBy" params are empty.

json={"path":"/home","sortCol":"","sortBy":"","hasWriteAccess":false,"requestPath":"/a/cascadeservices.org/intraweb-test/"}

more options

This problem still seems to exist in v16.0.2. How long does this sort of problem normally take to get rectified?