Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter susanwrotethis

    (@susanwrotethis)

    Additional info: the rest_forbidden_who and rest_forbidden_context errors do not appear when all plugins other than Smush are deactivated, so I am looking elsewhere in regards to those. The querySelector error remains, however.

    Plugin Support Kris – WPMU DEV Support

    (@wpmudevsupport13)

    Hi @susanwrotethis

    I hope you are doing well today.

    Thank you for all the details.

    Can you let us know which plugin you use to create that custom role so that we can be on the same page to replicate this in the first place and we could share that with our developers for review?

    Kind Regards,
    Kris

    Thread Starter susanwrotethis

    (@susanwrotethis)

    Hi Kris, I found last night that it doesn’t even have to be a custom role (we roll our own, BTW — no pun intended). An Author or Contributor role experience the same issue. This is re the original querySelector issue. As regards the additional info I sent, I’m investigating further, but I’m increasingly convinced this isn’t related to Smush and was coincidental that it came up at the same time.

    Thanks!

    Susan

    Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    Hi @susanwrotethis

    Thanks for response!

    I checked it again closer and you were right from the start – it actually is related to Smush.

    The good news is that it will not affect any features of the plugin or cause any issues with how it works. It’s not a matter of any conflict either. You can safely ignore it for now but I am reporting it to our developers to get it fix with one of future releases – it shouldn’t be happening anyway.

    As for what it is and why it happens:

    It’s related to the upselling notificaitons in the free version of plugin. We do show some upsell notifications to promote the Pro version of the plugin. Currently those notifications are only:

    – a modal upon first install of the plugin (or after plugin reset to factory settings) and it only shows in the plugin (not in other areas of back-end)

    – and a dedicated menu “Upgrade” section in the plugin.

    In the past we also used to also show sort of a banner at the top of the backend pages and the script that is cauing that error is related to it.

    That banner is no longer there (we do not use that kind of upsell anymore) but apparently the script was missed and left there. In any case, all the upsell messages were also showing up only to the admins, hence no no error for admin users.

    As mentioned, I already reported it to our developers to be fixed in future releases (not sure if it will be in nearest one or one of the later ones) but you can also safely ignore that error for now.

    Thank you for reporting it!

    Best regards,
    Adam

    Thread Starter susanwrotethis

    (@susanwrotethis)

    That’s really helpful and informative. Thanks so much. Sometimes I give demos to executives who know just enough to want to go down rabbit holes over irrelevant details. The fewer “why is that showing an error?” questions I need to field, the shorter our meetings are. 🙂

    Appreciate all you folks do. Thanks again!

    Susan

    Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    Hi @susanwrotethis

    I hope you’re well today!

    It seems we have accidentally missed notification about your response. I’m sorry about that!

    Anyway, I’m glad I could help and thank you for response.

    I’m marking this as resolved then but if you have any additional/follow-up questions on this subject, let us know and we’ll get back to you.

    Best regards,
    Adam

    Came here to report the same issue: getting error Uncaught TypeError: Cannot set properties of null (setting 'target') on seemingly all admin pages. Would be nice to have this fixed to make debugging other issues easier. @wpmudev-support8

    Plugin Support Jair – WPMU DEV Support

    (@wpmudevsupport15)

    Hi @enfueggo,

    I understand your frustration, and I apologize for not being able to provide you with a specific timeframe for a fix. However, please rest assured that our Smush team strives to fix each bug as quickly as possible.

    Kind regards,
    Zafer

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘document.querySelector null Error’ is closed to new replies.