brianol

hmmm I may try again then, though I do have it working. The filter 100% works in theory.

Hi @mikes41720
The option I’m talking about is at the bottom of each individual user in the user editor.

https://drive.google.com/file/d/1zxfZ2kwcHb0OG3dE4tPps5DyroXi2gVd/view?usp=sharing

It would appear, no one knows about this option!

Hi @champsupertramp
In my case, the UM role is “Sport Organization” and the slug is “um_sport-organization”

Using wither of those, the filter does nothing.

And in the end, I am going to have two… “Facility” / “um_facility”

• This reply was modified 3 years, 3 months ago by brianol.

That works excellently.

The hook doesn’t quite work, but the edit to the plugin does.

It’s weird. In my case, I have 3 site users, 2 admins, and 1 editor and then a series of “Sport Organizations” in ultimate member as a custom role.

If I tick “Do not allow search engines to show this author’s archives in search results” in the 1 editor, on both admin users, the author sitemap breaks and throws a 404. I need to leave one exposed, the editor in my case.

I believe something here is at play with the fact that the UM users have 0 posts attributed to them (by wordpress User panel)

But at least now, my admin users are not public!

Thank you!

• This reply was modified 3 years, 3 months ago by brianol.

Hi @champsupertramp
OK, this is all working now. Thank you.

It wasn’t, even after installing the plugin, but once I un-ticked the “Do not allow search engines to show this author’s archives in search results.” in the main wordpress user editor for one single user, it all popped into place.

Sadly, though, I don’t want those users indexed (the admin users) but now they are showing by default. haha. You can’t win.

With this plugin, it would be great if it respected the “Do not allow search engines to show this author’s archives in search results.” but still produced the sitemap.

But I am most grateful. I believe my problem is solved at the moment!

Hi @mikes41720
I think I have it working.

In the user menu, on the admin users, I had disabled the inclusion of the admin users in the sitemap. Once I include them, it all pops to life.

For the record, I think the admin users should be removed from this, but that’s another debate.

Thanks

Thank you.

I agree – what at play here is only part Yoast. Ultimate Member uses the main site user table to create users. Looking back, I may have not selected them for this, as it muddies the main site admin, but what appears to happen is you create a custom user role and the directory uses that.

Indexing the site is the main issue, but I am sorting that with Ultimate Member Support. What I can’t figure out is why Yoast doesn’t pick up the custom user roles.

Hi Thanks,
“Do not allow search engines to show this author’s archives in search results.” is located in the User Editor.

I am checking this on the ADMIN users to exclude them from any lists or sitemaps.

What I think is the real issue at heart is that the Ultimate Member user roles aren’t showing up in the sitemap.xml author archives.

THe member directory shows in the sitemap, but the list of users does not show (in the author sitemap).

What I really want to do is make sure the actual listings in the directory are getting properly indexed. Having them show in the author sitemap is logical, as they are in the user database.

Aside from this, I am unhappy that the general site search does not seem to pick up Ultimate member info.

But for now, What I am trying to ensure is best-case SEO indexing.

For reference, Ultimate Member builds a User Directory by adding users directly to the main user table, and then adding content via user_meta.

It’s weird actually… you basically are running these complex member directories without any additional tables.

SO… I can’t quite figure out why Yoast wouldn’t pick up the users, because they are in the user table anyway.

see attached screenies:

https://drive.google.com/file/d/1j27w8chdFU_oU-obGuaIRSbCF0fqmFyF/view?usp=sharing
Yoast archive settings with “Show archives for authors without posts in search results?” toggled to ON

https://drive.google.com/file/d/1I2YYbcqru__ZvPCIM93MuLccUhP5umxe/view?usp=sharing
UM settings showing the site is visible to everyone.

https://drive.google.com/file/d/1zxfZ2kwcHb0OG3dE4tPps5DyroXi2gVd/view?usp=sharing
ADMIN user settings removing them from the sitemap – the other user classes are shared, but they have 0 posts attributed to them. They are also a custom role. in this case, “Sport Organization”

So in theory, My user sitemap should have just ultimate member “Sport Organization” users. But it’s not.
https://drive.google.com/file/d/1fkD7DKwSW35frQNAh-J-R9HAcPwOs2eD/view?usp=sharing

So I can make the user sitemap appear if I reveal the admin users in the main admin user editor, but either way, it’s not picking up the other user classes.

If I uncheck the “Do not allow search engines to show this author’s archives in search results.” from the admin accounts, they indeed will show up, but I don’t want that. What I want is the directory users to appear.

Thank you

They should be public now

Thanks @champsupertramp
see attached screenies:

https://drive.google.com/file/d/1j27w8chdFU_oU-obGuaIRSbCF0fqmFyF/view?usp=sharing
Yoast archive settings with “Show archives for authors without posts in search results?” toggled to ON

https://drive.google.com/file/d/1I2YYbcqru__ZvPCIM93MuLccUhP5umxe/view?usp=sharing
UM settings showing the site is visible to everyone.

https://drive.google.com/file/d/1zxfZ2kwcHb0OG3dE4tPps5DyroXi2gVd/view?usp=sharing
ADMIN user settings removing them from the sitemap

So in theory, My user sitemap should have just ultimate member users.

If I uncheck the “Do not allow search engines to show this author’s archives in search results.” from the admin accounts, they indeed will show up, but I don’t want that. What I want is the directory users to appear.

Thank you

thank you.

I did get it working, I just created a simple draft post, created the short code and copied it into a code module in divi. super easy and works great. Will check out the plugin – thank you!

• This reply was modified 4 years, 10 months ago by brianol.

I works fine as long as I don’t use the Divi builder (if I use the WP stock editor, it’s fine)

you need to connect the trigger with the cookie. Edit the trigger and then select the cookie “to disable this trigger”