Relevanssi compatibility: users don't get indexed

  • Hi, it seems Relevanssi doesn’t notice when users are created by User Role Editor. Relevanssi attaches itself to following WordPress action hooks in order to index user profiles. It seems User Role Editor is not triggering any of these, and for compatibility reasons it probably should.

    profile_update, edit_user_profile_update, user_register

    Firing any of these action hooks after creating a new user profile would be enough to make Relevanssi able to index user profiles created by User Role Editor.

    https://www.ads-software.com/plugins/user-role-editor/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Vladimir Garagulya

    (@shinephp)

    Hi Miko,

    Thank you.
    I will look at it and add needed do_action(...).

    Plugin Author Vladimir Garagulya

    (@shinephp)

    Hi Mikko,

    I made a quick run through my code. URE does not create new users. If did not skip something…

    The only place, where URE adds new users, is an existing user (and his permissions) replication to all subsites or the network. It’s included into a Pro version. It calls add_user_to_blog(), which itself fires add_user_to_blog action. After that URE fires added_existing_user action.

    When URE adds to the user a secondary role via user profile, URE’s code itself is linked to the ‘profile_update’ action with a default 10 priority.

    I’m ready to help with issue fix, but do not see a right place to fire the listed actions.

    Is it critical for your plugin when URE directly updates user’s capabilities or re-assign him the user role(s)?

    Thread Starter Mikko Saari

    (@msaari)

    I’m not sure what exactly is the issue here. I don’t use URE myself, my client just said “I used the ‘User Role Editor’ plugin to create those two user.” and had some issues getting the users indexed.

    If URE doesn’t create users, then I’m not sure what exactly is the problem… It may matter to Relevanssi what capabilities user has, as that may be a criteria for indexing the user or not, so firing profile_update after any changes is helpful. But that should be well enough.

    It seems to me URE is working as it should.

    Plugin Author Vladimir Garagulya

    (@shinephp)

    Thanks.

    If a client changes capabilities included to the role after assigning that role to a user, then Relevanssi may miss such user permissions change, as it definitely done not with user but with role data.

    I added do_action('profile_update',... to the user permissions update, made directly by URE. I plan to publish version 4.25.2 at May, 1st.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Relevanssi compatibility: users don't get indexed’ is closed to new replies.