Click here to create a new issue on GitHub

U4-8060 - Angular cache not cleared during installs can lead to inability to edit content

Created by Chriztian Steinmeier 22 Feb 2016, 23:47:28 Updated by Shannon Deminick 18 Mar 2016, 09:22:05

What did you do?

  • Installed a blank Umbraco 7.4.1 with no starter kit.
  • Created a "Splash Page" Document Type (with Template)
  • Allowed the document type in the root

And then I Clicked the "Content" label to create a page in the Content section, and the flyout showed me the Splash Page type as expected, so I clicked that one...

What did you expect to happen?

  • To get the usual editors for creating a page

What actually happened?

  • I got an empty pane on the right, with no signs of editing facility. No errors in the console either - and not a single clue in the Log file.

Comments

Sebastiaan Janssen 23 Feb 2016, 07:28:03

Weird, have you tried a different browser? If you can zip up the site + db and email it me (Dropbox/WeTransfer link) then we can have a look.
Sebastiaan Janssen 23 Feb 2016, 07:28:47

May be related? https://our.umbraco.org/forum/using/ui-questions/75292-black-pages-in-admin-site
Chriztian Steinmeier 23 Feb 2016, 08:01:33

Alright - that forum post is exactly the same issue - just tried in Chrome instead (which has never been to that site) and that doesn't show a blank page (thank God! :-)

I know I tried wiping the ClientDependency folder in App_Data/ and reloading all sorts of combinations before logging the issue, but apparently something must be stuck...
Sebastiaan Janssen 23 Feb 2016, 08:05:38

Clear browser cache?
Chriztian Steinmeier 23 Feb 2016, 08:22:41

Really weird - reloading without caches didn't do it; had to specifically empty the cache, which I have never had to do before...

Thanks anyway :-)

Just for any future scrutinizing: This was a "clean" install - ''but on a site I'd just wiped from an older install'' - so the browser obviously had some cached stuff.

I bet it's an Angular issue, because of the code-applied style attribute...
Sebastiaan Janssen 23 Feb 2016, 08:27:12

Yeah, it is, because the browser was still holding on to Angular cache (at least that's what I've hear Shannon mutter about). So it had the cache from the previous site. We can do some extra cache busting for the next release!
Shannon Deminick 14 Mar 2016, 13:10:24

All angular views (html) are cache busted now
Shannon Deminick 17 Mar 2016, 10:33:46

I'm 98% sure this issue is fixed in 7.4.2 with the views being cache busted
Shannon Deminick 18 Mar 2016, 09:21:55

I tested upgrading from 7.3 to 7.4.2 without clearing any browser cache and had no problems so closing this issue

Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty: Normal

Category: Editor

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.4.1

Due in version: 7.4.2

Sprint: Sprint 11

Story Points:

Cycle: