开发者 |
strangerstudios
kimannwall andrewza dlparker1005 paidmembershipspro |
---|---|
更新时间 | 2024年10月13日 05:52 |
PHP版本: | 5.6 及以上 |
WordPress版本: | 6.6.2 |
版权: | GPLv2 |
版权网址: | 版权信息 |
"PMPro is very user-friendly, affordable and scalable. It has all the features you would need to run a fully-functioning membership site." Katie Prescott, Founder, Abridge Academy28 Types of Content Restrictions
"Recommended to anyone from beginner to experienced coders. I tried MemberMouse and MemberPress and they both lacked critical features that I wanted for my member site. PMPro has all the features I need (Social Login, ability to gift, multiple membership levels, works with BuddyPress) and more. I can easily customize to make it look great too. If I have questions, which is often since I am a beginner in WordPress and know nothing about coding, they are quick to respond and always find a way for me to do exactly what I want. Super happy. Would recommend to anyone from beginner to experienced coders!" @efsluys via WordPress.org 5-star ReviewDocumentation, Support, Localization Access free support here on WordPress.org or reach out on our contact form. Refer to our information on premium support if you would like more help. Our website has extensive documentation to assist you in building your membership site. We also offer unique content hubs, which explore the 8 most popular membership site use cases and how to build a successful membership site on WordPress. Developer Friendly Open source, REST API support, extensive hooks, and tools for easy customization. Our website offers over 340 examples on how to use our action and filter hooks to customize your membership site. Free WordPress Theme Our official theme, Memberlite, is built specifically for membership sites. Memberlite has deep integration with Paid Memberships Pro to offer advanced features for logged-in/out users and works alongside your favorite page builders, like the Block Editor and Elementor. Popular Add Ons Extend the features of your membership site or integrate with third-party services through our library of over 65 Add Ons. Some of the most popular features include:
No, Paid Memberships Pro does not require any coding knowledge. The plugin is designed to meet all levels of WordPress experience. At the same time, our plugin is very developer-friendly and extendible.
Yes. PMPro will work with any properly coded theme. However, some themes may cause conflicts with the plugin. If you find a styling issue with your theme please create a post in the community forum.
Absolutely. We have a complete guide on using a caching plugin or your host's caching methods with Paid Memberships Pro on our website if you want to explore this topic more.
PMPro does not restrict access to the wp-login.php page when active. This allows your administrator users to leverage advanced security plugins, like Two-Factor and more, so that you can keep your membership site secure. We do include a frontend login page for your members to use for logging in and resetting their password.
"Supporting multisite" means different things to different people. This guide covers the three primary ways you can use Paid Memberships Pro in a network. Out of the box PMPro will basically act as a stand alone plugin for each site. Each site has its own list of membership levels, members, payment settings, etc. Our Member Network Sites Add On allows members to choose a site name and title at checkout and will set up a network site at checkout. Our Multisite Membership Add On allows you to manage memberships at the 'Main' Network site and provide or restrict access on other Network Subsites. If you would like more help using PMPro on a network install, reach our via our contact page.
Please visit our support site for more documentation and our support forums.
Please post it in the WordPress support forum and we'll fix it right away. Thanks for helping.
Not sure? You can find out by doing a bit a research.
pmpro_checkout_checks
, pmpro_checkout_user_creation_checks
, and pmpro_checkout_order_creation_checks
. #3137 (@dparker1005)pmpro_build_order_for_checkout()
function in favor of inline logic. #3129 (@dparker1005)process()
method instead of on actions that are being deprecated. #3116 (@dparker1005)process()
method instead of during the pmpro_checkout_before_change_membership_level
hook. #3104 (@dparker1005)pmpro_checkout_oldemail
, pmpro_new_user
, pmpro_require_billing
, and pmpro_checkout_confirmed
. #3137 (@dparker1005)getGatewaySubscriptionStatus()
, getGatewayTransactionStatus()
, and confirm()
MemberOrder methods as deprecated. #3129, #3116 (@dparker1005)PMProGateway
class and marked sample helper methods as deprecated. #3129 (@dparker1005)pmpro_get_ip()
function. #3113 (@andrewlimaza)pmpro_set_curent_user()
is now only called in the pmpro_clear_level_cache_for_user()
function if we are clearing the cache for the current user. #3127 (@mircobabini)pmpro_skip_account_fields
filter to skip the account fields for new users. #3135 (@kimcoleman)code_id
may not reflect the discount code ID that was used at checkout. #3138 (@dparker1005)getDiscountCode()
on a blank MemberOrder object. #3120 (@dparker1005)CardType
JavaScript not being present in the update billing form. #3108 (@dparker1005)pmpro_stripe_card_element_style
to allow developers to customize the Stripe card element style. #3099 (@kimcoleman)CardType
field not being present in the payment form. #3102 (@JarrydLong)pmpro_set_expiration_date()
function to allow null
as a valid value for the $enddate
parameter. #3098 (@ZebulanStanphill)pmpro_lost_password_before_submit_button
. #3090 (@dioliviers, @dparker1005)aria-required
attribute. #3076 (@kimcoleman)$local_time
was set to true
. #3069 (@mircobabini)pmpro_subscription_cost_text
for updating how the subscription cost is displayed. #3021 (@dparker1005)pmpro_dashboard_meta_boxes
to allow developers to hide dashboard widgets and add their very own widgets to the PMPro dashboard area. #3019 (@andrewlimaza)/membership/
slug. #2927 (@MaximilianoRicoTabo)pmpro_complete_checkout()
function. #2937 (@dparker1005)print.css
file from the plugin. These styles are now in frontend.css
. #2940 (@dparker1005)pmpro_longform_address
filter. Address fields will always be shown in longform format. #2990 (@kimcoleman)