Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

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

  • 3 svar
  • 19 har detta problem
  • 1 visning
  • Senaste svar av 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.

Ändrad av DeanCAI

Alla svar (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?