Dashboard and RTE slideouts not loading

Questions
1

V13.7.1

When developing locally I’m finding that dashboards and panels aren’t loading when navigating via the content tree. Also in Block Grids, if I try to edit an RTE, the slide out doesn’t load the RTE. This is only happening since upgrading from 13.6.0 to 13.4.1. This is the console result from navigating to one page, the dashboard didn’t load so had to refresh the whole page, then trying to edit an RTE, and then trying to save (it shows an X on the Save button)

image
image1646×545 180 KB

Any advice or suggestions would be appreciated.

Thanks

2

Are you sure it’s not browser cache that is messing around?

3

Don’t think so. I’ve cleared all the browser cache from the browser and I’ve killed all the site caches with God Mode and restarted the site several times. :frowning:

4

Had a browser update and it all works now! So frustrating.

Thanks for all the suggestions.

5

Oh wow, that is weird… although it your own answer, mark it as solved please :slight_smile:

6

Unfortunately this issue is happening again. So it wasn’t anything to do with a new browser update:(

Any time I try to open a block with an RTE in it, all I see is a slideout with three moving dots where the RTE should be and the console errors shown in previous post :frowning:

… (Edit an hour later)… and now it’s working. This only happens locally and appears to be intermittent. Very frustrating not knowing what causes it and therefore how to fix it on demand, so to speak.

7

This is happening so often now I can’t work locally, which is devastating when you have to deliver. It must be some package interaction, but the only thing that the console error alludes to is the Block Grid Preview package.

I also get images showing low res on the site front and back ends. it’s really, really odd.

Does anyone have a clue what this might be to do with because I don’t? :frowning:

angular.min.js?d=638792836200000000:114 
            
            
 GET https://localhost:44337/umbraco/backoffice/umbracoapi/stylesheet/GetRulesByName?name=%2Fcss%2Frte.css 417 (Expectation Failed)

Possibly unhandled rejection: {"errorMsg":"Failed to retrieve stylesheets ","data":{"Type":null,"Title":null,"Status":417,"Detail":null,"Instance":null,"Extensions":{"traceId":"00-a721403a445be9a419d4dd8356ab2860-02e355e74bde746e-00"}},"status":417,"xhrStatus":"complete"}
            
 GET https://localhost:44337/umbraco/backoffice/umbracoapi/richtextprevalue/GetConfiguration 417 (Expectation Failed)
8

I don’t have much of a clue myself, but investigating the error from older Umbraco (waaay older tho so dunno how relevant they are >.<) forum posts this seems to be consistently related to cookie states. Is there any custom cookie stuff going on in the project to inspect?

Otherwise… since the main complaints shown in your errors seem to be related to the RTE stylesheets (/css/rte.css path)…

  • Does this only happen on content nodes with an RTE? Or anywhere?
  • Is there a stylesheet available at that path?
  • If you suspect any packages are related as you mentioned…
    • … are you able to temporarily remove them to see if the issue goes away?
    • … when Umbraco was updated were all the packages compatible with the new minor version &/or updated as well?
      • If so, have you tried downgrading any suspected packages to their previous version to see if that fixes the problem?
  • Do you have any custom RTE or TinyMCE plugin/settings?
    • If so, have you tried just temporarily removing them to see if that fixes it?
    • If not, could you create a custom RTE stylesheet and apply it and see if that changes anything?
9

It doesn’t just happen with RTE’s. It’s also happening with an Image Block as well. The image never loads in the slide out. Have also tried using Firefox instead of my normal Brave. No different. It’s becoming unuseable locally.

Having said all that I’ve now tried removing packages. It seems it’s the Umbraco.Community.AccessibilityReporter that’s the issue, or at least it may be interacting with another package that provides critical services which I can’t take out or the site won’t build. So the answer has been to remove it.

The other package that I “suspect” but can’t prove is DocumentFormat.OpenXml which I need for handling text replacements in docx files, so can’t do without it.

10

Nice! Now at least you have an idea of where things are going wrong ^^

Accessibility Reporter package looks like it’s being maintained and doesn’t have anyone else reporting such a severe issue on their repo so I’d concur with that suspicion it’s an interaction issue.

At this point you’ve just gotta nail down which ones don’t like each other and either fiddle with versions, find a replacement, or put in a new issue in a relevant repo.