Potential conflict with the Plugin UAM

  • Resolved pilotspelman

    (@pilotspelman)


    1 year, 4 months ago

    After a lot of testing, I have discovered a potential conflict with the plugin User Access Manager (UAM) and a possible workaround (at least for now). However, this conflict did not exist with earlier versions of WordPress and/or the plugins.

    The conflict arises when associating UAM user groups with categories. Associating UAM user groups with specific categories was a way of controlling access to certain posts. However, though this worked well earlier, it now creates a conflict between UAM and Postie. Postie does not assign categories at all with this setup. However, when removing all associations between UAM user groups and categories, Postie works as expected again.

    A possible workaround is associating UAM user groups with tags instead of categories. The tags can thereby be a way of controlling access to certain posts instead of using specific categories. There is no conflict with Postie’s tag function (at least not for now).

    Actual versions:
    WordPress: 6.1.1
    PHP: 8.0.26
    Postie: 1.9.62
    User Access Manager (UAM): 2.2.19

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter pilotspelman

    (@pilotspelman)

    1 year, 4 months ago

    Additional information:
    This conflict only arises when Postie is set to run the check mail script automatically (at set intervals). Postie works as expected (regarding categories) when running the check mail script manually (by clicking the button “Process Email”).

    Plugin Author Wayne Allen

    (@wayneallen-1)

    1 year, 4 months ago

    I don’t have any particular knowledge about UAM but you could try setting Force User Login to yes (on the Postie Settings User tab)

    • This reply was modified 1 year, 4 months ago by Wayne Allen.
    Thread Starter pilotspelman

    (@pilotspelman)

    1 year, 4 months ago

    Thanks for the suggestion Wayne, which I have now tested! Unfortunately, the problem persists even with the force user login setting to Yes.

    Interestingly, the problem only arises when Postie runs the check mail script automatically (at set intervals). When forcing the mail script to run (before the set interval) by clicking the button “Process Email,” Postie works as expected, even with UAM user groups associated with categories. What is the difference? Is it not the same check mail script but with different triggers?

    A follow-up question is whether something else could trigger the script, e.g., when a specific page loads (e.g. via a shortcode on that page)?

    Plugin Author Wayne Allen

    (@wayneallen-1)

    1 year, 3 months ago

    The difference is that the scheduled mail check is run via WordPress Cron and no user is logged in.

    I expect that UAM has some dependency on a logged in user.

    >A follow-up question is whether something else could trigger the script, e.g., when a specific page loads (e.g. via a shortcode on that page)?

    No, cron is the process.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Potential conflict with the Plugin UAM’ is closed to new replies.