Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • ianhoughton 281 posts 605 karma points c-trib
    Jun 09, 2021 @ 06:52
    ianhoughton
    2

    Discount rules not working

    We've recently upgraded our Umbraco instance to 8.14.0 (Vendr 1.3) and when adding a discount Rule the browser window now freezes. There are no console errors, no requests waiting for completion and no errors in the umbraco logs. The only way to get the browser to respond is by refreshing the page. (I'm using chrome 91.0.4472.72, but the client also has this issue on different browsers)

    Thinking it was something in our custom installation, I checked by upgrading my demo Umbraco / Vendr setup locally from an earlier working version of umbraco to 8.14.0. The adding of rules to discounts then stopped working again.

  • Matt Brailsford 4124 posts 22215 karma points MVP 9x c-trib
    Jun 09, 2021 @ 08:02
    Matt Brailsford
    0

    Hi Ian,

    Hmm, without some kind of error I'm not entirely sure what it would be. Best I could guess would maybe be some cached JS?

    Do you see any network request during this "freeze"?

    Matt

  • ianhoughton 281 posts 605 karma points c-trib
    Jun 09, 2021 @ 08:35
    ianhoughton
    0

    Yeah, it's very strange, I can see no waiting requests in the console / network tab.

    I have the clients site running Umbraco 8.14.0 & Vendr 1.83 and my local demo site (vanilla installation) running 8.14.0 & Vendr 1.3.

    The issue only started when we upgraded to 8.14.0. I might try a fresh install of 8.14.0 and latest Vendr and see if it still happens.

  • ianhoughton 281 posts 605 karma points c-trib
    Jun 09, 2021 @ 13:50
    ianhoughton
    0

    Hi Matt,

    I've just rolled my local instance back to 8.13.1 and the Discount Rule picker started working again. Then re-installed 8.14.0 and its stopped again.

    Tested in Chrome and Firefox.

  • Conor Dunk 1 post 21 karma points
    Jul 18, 2021 @ 16:46
    Conor Dunk
    0

    Hi Matt/Ian,

    Did you find a reason for the issue above, I am also having the same problem after upgrading from 8.13 to 8.15 with vendr 1.8.3?

    Conor

  • Matt Brailsford 4124 posts 22215 karma points MVP 9x c-trib
    Jul 18, 2021 @ 16:54
    Matt Brailsford
    0

    I’ll be taking a look Tomorrow. My guess is something changed in Umbraco that is causing a conflict.

  • Matt Brailsford 4124 posts 22215 karma points MVP 9x c-trib
    Jul 19, 2021 @ 08:24
    Matt Brailsford
    2

    Ok, so i've looked into this and it appears to be a bug in Umbraco core.

    They seem to have introduced the adding of an "inert" attribute onto the main editor area when you open an dialog, and this should get removed when you close the dialog, but there seems to be a problem when using editorService.closeAll() that it's not removing the inert attribute and so the UI remains unresponsive.

    I'm trying to hunt down where this should be happening and why it's not and I'll then report it on the issue tracker, but as this is a core issue, my suggestion right now is to roll back to 8.13 which looks like the version prior to this addition.

    UPDATE:

    I've now confirmed this as a core regression and not a Vendr issue. This is due to new changes in core as described above. I've raised an issue on cores issue tracker here https://github.com/umbraco/Umbraco-CMS/issues/10708 and have submitted a PR fix for it here https://github.com/umbraco/Umbraco-CMS/pull/10710

    My suggestions right now would be to either roll back to 8.13, or, manually apply the fix in the PR which is just a one liner and hope it gets included in 8.15.1

    Here is an example of what you need to change in a general Umbraco project https://github.com/vendrhub/vendr-demo-store/commit/0262081c4b79a388f6ccccfbc4eda44744220151

  • ianhoughton 281 posts 605 karma points c-trib
    Jul 19, 2021 @ 18:11
    ianhoughton
    0

    Thanks Matt, yes we've rolled back to 8.13 for the time being.

    I just started looking at an issue on my own Youtube picker package, and it looks like this bug affects that as well.

Please Sign in or register to post replies

Write your reply to:

Draft