[MGNLSLOCK-8] Error message on client in spite of 200 HTTP response code Created: 10/Jan/11  Updated: 24/Jan/11  Resolved: 10/Jan/11

Status: Closed
Project: Magnolia Soft Locking Module
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0.1

Type: Bug Priority: Critical
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7, FF 3.6.13, Chrome 8.0.552.22


Attachments: PNG File softlocking.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

This issue was reported by Kees de Koning from MediaCatalyst (see MGNLSLOCK-6). It does not seem to happen on IE8. Besides losing the soft locking functionality
the browser's window soon becomes cluttered with error messages which make the application unusable. On a first glance, it looks like jQuery.ajax()'s onError callback treats the 200 response as an error, whereas when handling "real" errors the page stops polling the server so that only one error message is shown instead of having it replicated endlessly.
I tried to reproduce this bug on a windows 7 box with FF 3.6.13, Chrome 8.0.552.224, IE7 and IE8 but everything seems to work fine. However, it actually happened to me a few times while developing this feature to have the same problem which apparently disappeared overnight without doing anything special and never occurred again.



 Comments   
Comment by Federico Grilli [ 10/Jan/11 ]

Hi Kees,

I just committed a few changes. Can you see if with the latest 1.0.1-SNAPSHOT (http://nexus.magnolia-cms.com/index.html#nexus-search;quick~soft%20locking) the problem has gone? Also, the firebug console messages should have gone.

Comment by kees de koning [ 10/Jan/11 ]

Hi Federico,

I tested it and the problem is gone indeed! Thanks a lot!

Comment by Federico Grilli [ 10/Jan/11 ]

Sure!

Comment by Boris Kraft [ 24/Jan/11 ]

typo

Generated at Mon Feb 12 07:14:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.