Hi @cmspencer99
Please try adding the following code snippets to enable the Title, Content and Excerpt:
add_filter( 'um_ignore_restricted_title', '__return_true' );
add_filter( 'um_ignore_restricted_excerpt', '__return_true' );
add_filter( 'um_ignore_restricted_content', '__return_true' );
You can add the code to your theme/child-theme’s functions.php file or use the Code Snippet plugin to run the code.
Regards,
Hi,
Thanks for you reply, unfortunately this hasn’t helped, we also have two other sites with the issue – one has “E-mail is empty” and the other has both Title and E-mail.
The issue seems to be mostly around the ultimatemember_account and the member directory form shortcodes as the other forms seem to be ok.
Neither of these should be an issue and should be filled in for each user.
Kind regards,
Charlene
Hi,
After some debugging I think it’s related to a plugin conflict with Pods (which allows us to add custom meta data to users etc)
Any ideas why this would cause UM shortcodes to completely fail however?
Kind regards,
Charlene
UM fails because if it detects get_user_meta() returns any value for normal user object fields, it will attempt to delete that meta value (saving as empty to Pods).
Because Pods supports object fields through meta functions (only when called directly, versus a get_user_meta( $id ) to get all of the meta) — when it attempts to delete that value, it tries to save the object field (user_email, etc) as empty which fails validation in core WP APIs for that functionality. An error is thrown onto the page at that point.
Pods 2.8.8 will turn this functionality off and it can be re-enabled through a new filter being introduced. That resolves the conflict we’ve seen here.
Ahh I see this makes sense. Thank you for the update, how long will it be for 2.8.8 to be released?
Kind regards,
Charlene
Pods 2.8.8 went out yesterday to resolve your issue here.
Hi @cmspencer99
Could you please confirm?
Hi @sc0ttkclark Thanks for letting us know.
Regards,
Hi both,
Apologies I’m on WP Engine and the plugin only updated for us this morning.
It appears to have resolved the issue.
Thank you so much for the update!
Kind regards,
Charlene
