Avatar for Username

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Kjo rrjedhë është arkivuar. Ju lutemi, bëni një pyetje të re, nëse keni nevojë për ndihmë.

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

  • 3 përgjigje
  • 19 e kanë hasur këtë problem
  • 2 parje
  • Përgjigjja më e re nga AyesRambler

DeanCAI
DeanCAI
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.

Ndryshuar nga DeanCAI

Krejt Përgjigjet (3)

DeanCAI
DeanCAI I zoti i pyetjes
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/

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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/"}
AyesRambler
AyesRambler
more options

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