U4-4508 - Save causes content to vanish in IE

Created by Asbjørn Riis-Knudsen 23 Mar 2014, 19:44:26 Updated by Shannon Deminick 24 Mar 2014, 23:45:03

When editing content, I frequently use the Save feature to save when editing, but avoid publishing. In Umbraco 7.1 RC this is badly broken. When creating a new item and then pressing Save (not Save and Publish), I'm redirected to the root Content view (the dashboard). The content I just created has vanished without a trace. It also happens when editing an existing item. Obviously, this should not happen. Save and Publish works as expected.

This appears to only occur in IE11 (haven't tested other IE versions). In Firefox it works as expected.

Comments

Asbjørn Riis-Knudsen 23 Mar 2014, 21:24:17

Some initial observations: When this issue occurs, no traffic to the server is generated. No errors are logged in the Console. It behaves pretty much as if the Save link has no js handler attached and just handles the href="#".


Shannon Deminick 24 Mar 2014, 05:30:32

I cannot replicate this in IE11 or other browsers. What properties do you have defined on your doc type? No JS errors are seen?


Asbjørn Riis-Knudsen 24 Mar 2014, 07:52:49

I can reproduce this in IE11 on a blank install of Umbraco 7.1 RC with the following steps:

  1. Install Umbraco 7.1 RC (this will install the TXT Starter Kit)
  2. In the backend, click the three dots next to Home and create a new Text Page.
  3. Give the page a title
  4. Press the arrow next to Save and publish and select Save.

The first two times, this works correctly - i.e. the content is saved and no redirect occurs. Try repeating the steps a few times (create new content, set the title and click Save). For me, the error happened on the third try. This is on a completely fresh default install of 7.1 RC.


Shannon Deminick 24 Mar 2014, 08:03:14

yup, i can reproduce now.


Shannon Deminick 24 Mar 2014, 08:04:25

luckily there is a JS error:

TypeError: Unable to get property 'indexOf' of undefined or null reference at Anonymous function (http://localhost:7100/umbraco/js/umbraco.directives.js:2657:21) at $broadcast (http://localhost:7100/umbraco/lib/angular/1.1.5/angular.min.js:94:235) at Anonymous function (http://localhost:7100/umbraco/lib/angular/1.1.5/angular.min.js:62:25) at $eval (http://localhost:7100/umbraco/lib/angular/1.1.5/angular.min.js:92:261) at $digest (http://localhost:7100/umbraco/lib/angular/1.1.5/angular.min.js:90:140) at $apply (http://localhost:7100/umbraco/lib/angular/1.1.5/angular.min.js:92:429) at Anonymous function (http://localhost:7100/umbraco/lib/angular/1.1.5/angular.min.js:61:114) at dispatch (http://localhost:7100/umbraco/lib/jquery/jquery-2.0.3.min.js:10:11716) at handle (http://localhost:7100/umbraco/lib/jquery/jquery-2.0.3.min.js:10:7809)


Asbjørn Riis-Knudsen 24 Mar 2014, 08:07:24

I get this error too, but I don't seem to get it every time, though, so I'm not sure if it is related. Worth checking out, though ;) Glad you can reproduce, though (sorry for the incomplete report)


Shannon Deminick 24 Mar 2014, 08:24:00

unfortunately that error isn't the cause, still need to investigate more tomorrow.


Asbjørn Riis-Knudsen 24 Mar 2014, 19:21:18

From brief testing it appears that pressing Unpublish causes the same issue sometimes.


Shannon Deminick 24 Mar 2014, 23:45:00

This is all fixed in rev: ab586a49ce3a3dc8278a796d5243ac915d4f4a8f Due to a rogue ng-disabled directive, not sure why it was there.


Priority: Critical

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.1.0

Due in version: 7.1.0

Sprint:

Story Points:

Cycle: