Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Buscar en Ayuda

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

Unresponsive Script Error when Saving Changed Set in Flickr Organizer

  • 1 respuesta
  • 7 tienen este problema
  • 2 visitas
  • Última respuesta de blazer869608

more options

I'm getting an unresponsive script error when saving a changed set in the Flickr organizer.

The problem started when using Firefox 3.6.8 or maybe an earlier version. It persists in Firefox 3.6.12

I've noticed the error only appears in the Organizer and only when saving a changed set or saving after deleting a set.

It does indeed save the changed set correctly before crashing.

It is not intermittent and happens every time I perform this save.

The error does not occur in Chrome or Safari.

Examples of the error messages can be found at

http://www.flickr.com/photos/blazer8696/4897580573/

and

http://www.flickr.com/photos/blazer8696/4897656175/

I'm getting an unresponsive script error when saving a changed set in the Flickr organizer. The problem started when using Firefox 3.6.8 or maybe an earlier version. It persists in Firefox 3.6.12 I've noticed the error only appears in the Organizer and only when saving a changed set or saving after deleting a set. It does indeed save the changed set correctly before crashing. It is not intermittent and happens every time I perform this save. The error does not occur in Chrome or Safari. Examples of the error messages can be found at http://www.flickr.com/photos/blazer8696/4897580573/ and http://www.flickr.com/photos/blazer8696/4897656175/

Modificadas por blazer869608 el

Todas las respuestas (1)

more options

Upgrading to 4.0.1 has corrected this problem.