You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When excluding items from appearing in the Map marker, the conditions are not applied to the Proflile page marker.
To Reproduce
Steps to reproduce the behavior:
Add Shortcode for Map or Directory using attributes
[pmpro_membership_maps show_level="false" show_avatar="false" show_startdate="false" show_email="false"] or
[pmpro_member_directory show_level="false" show_avatar="false" show_startdate="false" show_email="false"]
Click on Directory: Map Marker will exclude the avatar etc
Click on View Profile: Map Marker on profile shows avatar etc
Screenshots
Directory View
Profile View
Expected behavior
Markers on both maps should match
Isolating the problem (mark completed items with an [x]):
I have deactivated other plugins and confirmed this bug occurs when only Paid Memberships Pro plugin is active.
[ x] This bug happens with a default WordPress theme active, or Memberlite.
[ x] I can reproduce this bug consistently using the steps above.
Please share non-sensitive information about your hosting environment such as WordPress version, PHP version, Paid Memberships Pro and any related plugins versions.
The text was updated successfully, but these errors were encountered:
Describe the bug
When excluding items from appearing in the Map marker, the conditions are not applied to the Proflile page marker.
To Reproduce
Steps to reproduce the behavior:
[pmpro_membership_maps show_level="false" show_avatar="false" show_startdate="false" show_email="false"] or
[pmpro_member_directory show_level="false" show_avatar="false" show_startdate="false" show_email="false"]
Screenshots
Directory View
Profile View
Expected behavior
Markers on both maps should match
Isolating the problem (mark completed items with an [x]):
WordPress Environment
WP 6.4.3
PMPro 3.0.1
PMPro Map 0.7.1
The text was updated successfully, but these errors were encountered: