Force users to login THEN restrict base on role

  • I figure I need 2 restrictions to deal with users who are not logged in when accessing a specific page:

    1. Logged-out users, Redirect Login & Back, selected page
    2. Logged-in users without specific role, Replace Content with my own page, selected page

    But I created 2 before 1, so now I need to change Priority so that 1 is the 1st restriction – correct?

    But I can’t change Priority: clicking the Up arrow in the Priority column for the Restriction does nothing. Should it? I was expecting it to move up in the list of Restrictions.

    Clue: When I do Click, the Developer Console complains about “MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead.” – which is coming out of tinymce. Tried current versions of Chrome & Firefox.

Viewing 1 replies (of 1 total)
  • Plugin Author Daniel Iser

    (@danieliser)

    @flymike – Sorry to hear you had issues.

    1. Your correct, priority does matter, mainly for performance of the handling. We stop processing after we find a match.

      If you don’t have a lot of restrictions you can use a snippet of code to check all restrictions and bypass priority to some degree. Not the ideal solution, just something you can do.

    2. The error is likely coming from another plugin/theme causing interference. You can try the Health Check & Troubleshooting plugin’s “Troubleshooting Mode” to test just our plugin then activate others one by one to find the culprit, but while you have only our plugin active, might as well go ahead and update your priority order to.

      There is very little we can do on our end if some other code is globally hooking into the TinyMCE editor and extending it. We enqueue it the WP way, and don’t have any code related to MouseEvent.mozPressure, our build tools would automatically generate compliant modern replacement or flag it in our code editors with highlighting and build time error notices, sl highly likely it comes from something else.

      We also have a guide from one of our other plugin’s docs on using error notices in the console to try and find the problem JS file (plugin/theme): https://docs.wppopupmaker.com/article/373-checking-javascript-errors

    Let us know.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.

Tags