Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Plenigo

开发者 Sebastian Dieguez
更新时间 2021年3月24日 16:51
PHP版本: 7.0 及以上
WordPress版本: 5.7
版权: GPLv2 or later
版权网址: 版权信息

标签

widget plugin media donate payment e-commerce newspaper paywall subscriptions pay money visa transaction Ecommerce mastercard card give credit debit bank pay what you want paid content software pay-per-read plenigo

下载

1.1.18 1.1.19 1.1.20 1.1.21 1.1.22 1.1.23 1.1.24 1.1.25 1.1.26 1.1.27 1.1.28 1.1.29 1.1.30 1.1.31 1.10.0 1.11.0 1.12.0 1.2.0 1.2.1 1.2.2 1.2.3 1.3.0 1.4.0 1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6 1.4.7 1.4.8 1.4.9 1.5.0 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.5.6 1.5.7 1.5.8 1.6.0 1.6.2 1.6.3 1.6.4 1.6.5 1.7.1 1.7.2 1.7.3 1.7.4 1.7.5 1.7.6 1.7.7 1.7.8 1.7.9 1.8.0 1.8.1 1.8.2 1.8.4 1.8.5 1.8.6 1.8.7 1.8.9 1.9.0 1.9.1 1.9.2

详情介绍:

What do I get with plenigo? Basically plenigo includes all you need to run your paid content offer. No matter if your offer is a Video on Demand subscription or a pay-per-view live stream, a metered model for your digital news page or magazine. With plenigo you can run any offer you like, created just with a few mouse clicks. Don’t believe it? Just try our BASIC account, with € 0 monthly fee. What are the basic features? The plenigo team aims to include all necessary functionality you need to create the best possible platform for paid content offers. This does include a user-friendly checkout process that does not derive your users but keeps them on your page. Currently six different payment methods are included and can be integrated just by clicking a checkbox. In the penigo backend you can easily create your offer and just add e.g. „Premium“ to the tag box while managing your posts - now you have created your offer. There is much more, please have a look at „features" below. 定价 plenigo offers four different pricing plans starting with 0 € fix fee, so it is risk free to test. You can easily upgrade once your offer is established. If you what to start with even more features, just pick one. What do I need? Beside your Wordpress account, your plenigo merchant account and the offer you created, you need to sign up with the payment method you would like to use, e.g. PayPal. Why do you have to sign up for your own account: This way you can be 100% sure nobody but you has access to your earnings. plenigo only handles transfer, access, clients etc. but never has access to the money you earn. Currently plenigo offers credit card payments, SEPA direct debit, PayPal, Sofortueberweisung and bill payments. Are there any restrictions? plenigo highly values author’s rights, so we have to make sure only people sell through plenigo who are allowed to. I addition, we respect all legal requirements and ask you to confirm that you are not violating any laws. Data protection Data security is of highest value for plenigo, so we do anything in our power to keep data save. For detailed questions pls. contact our data security team at dataprotection@plenigo.com. "Who owns the customer" Your customer is your customer. You have full access to all information we gather for you and you can export this information any time. Once a customer signs in with plenigo, he approves plenigo can hand over the customer data to you as a publisher. This does, off course, include only data collected in context of your account. These are plenigo’s basic features Access Management User Management Product Management 付款 支付 分析

安装:

For installation instructions visit help pages. Pre Requirements General Section Test Mode Use the test mode for testing the integration and production mode for real payments. Company ID The company id provided to you by the plenigo backend after registration of a company account. Company Private Key The company private key provided to you by the plenigo backend after registration of a company account. Notify non-JavaScript user If you are using metered views or using the plenigo user login users with deactivated JavaScript can get negative site impressions. In case of metered views deactivated JavaScript means there is no paywall at all for metered view article so the user can access them without limit. We recommend to enabled this setting. non-JavaScript overlay title Title that is shown to the user in the overlay that is shown to users with deactivated JavaScript. non-JavaScript overlay message Message that is shown to the user in the overlay that is shown to users with deactivated JavaScript. Google Analytics ID If you insert your Google Analytics ID here you will get events about the delivered curtains, etc. OAuth2 Login Section Use OAuth2 Login This is the base decision about your usermanagement. If you decide to use plenigo as OAuth2 Login provider all users are managed by the plenigo plugin and shadow users are created in WordPress. This way all users already registered at plenigo can login without new registration. Also the users can use the same account for payments and for writing comments, etc. After enabling this you also need to insert the plenigo widget into your page. Enable Wordpress Login If you select plenigo as your authentication provider you can decide if users should still see the regular WordPress login link or only see the login button via plenigo. (The later is recommended.) Override WP Profile data Decide which system is the leading system. If you allow users to modify their data also within WordPress the user data can vary and you won't get the latests data from the plenigo system transfered into your WordPress system. OAuth redirect URL This url should be set to identify the page that should handle the OAuth2 redirect result. In theory every page can do this, but after processing the user will be redirected again. So it is recommended to select a page here that can be rendered very fast, e.g. the wp-login page. URL After Login If you want the user to get redirected to a special URL after login you can define it here. If you don't insert an URL here the user will stay on the same page after login. Premium Content Section The plenigo plugin controls which article is paid content by the use of WordPress tags. So before you add mappings in this section you have to
  1. Create WordPress tags that identify your payments.
  2. Create a product within the plenigo product section. (This step is optional if you only want to sell single articles.)
Premium Content Products The tag field offers auto completion for all existing WordPress tags. The product ids can be obtained by the plenigo backend product management. You can add multiple product ids to a single tag by separating them with a ','. In case of the screenshot the tag payment is associated with a monthly subscription represented by its product id. Premium Content Categories The tag field offers auto completion for all existing WordPress tags. The category ids can be obtained by the plenigo backend product management. You can add multiple category ids to a single tag by separating them with a ','. In case of the screenshot the tag buyButton is associated with a plenigo category that has a price of 2.99€. So every article that this tag is associated with will be buyable as a single product for the price of 2.99€ Prevent Payment Tag If you add a tag here and add this tag to an article that is already marked with a tag that marks the article as paid content this decision will be reverted and the article will be free available again. Metered Views Section Metered Views switch Metered views can be managed within the plenigo backend. If you disable metered views in the plenigo backend you should also disable them here to prevent some useless redirects that could happen to a user. Metered explain URL Metered views are often new to users. So you can provide an URL here where you explain the principle to them. This URL will automatically added to the metered view flag. Metered exemption tag With the tag defined here you can exclude articles from metered views so that the content is only available to paying customers. Curtain Customization Section The curtain is "the heart" of your paywall. It will be shown to the user to motivate him paying. In this section you can modify the curtain. If you are an advanced user you can also overwrite the curtain template to get a completely customized curtain. Curtain Title The title of your curtain shown to the user. Curtain Message The message of your curtain shown to the user. Curtain Title (for memebers) This curtain title is shown to users that are already logged in but don't have paid yet. Curtain Message (for memebers) This curtain message is shown to users that are already logged in but don't have paid yet. Curtain Button Scheme This button scheme is used within the curtain if a product tag is added to an article. Curtain Button Scheme (Category tag) This button scheme is used within the curtain if a category tag is added to an article. If a product and a category tag is added to an article this scheme will be used. BUY Button Text Text that is shown on the buy button. LOGIN Button Text Text that is shown on the login button. This button can be used to provide existing users that already bought the content an easy way to log in. CUSTOM Button Text The custom button is a button that doesn't have logic implemented within. It only contains a link. This way you can redirect the user e.g. to a subscription selection page. In this field you set the title for this button. CUSTOMER Button URL The URL the custom button should link to. CUSTOM Button Text (Category tag) In this field you set the title for the button within the category scheme. CUSTOM Button URL (Category tag) The URL the custom button in the category scheme should link to. Buy Button Text (based on tag) You can define different button texts for the buy button defined by the tags provided. If two tags with different button texts are provided for the same article the first tag is choosen. WooCommerce Section Use WooCommerce Payment Gateway Enable/Disable the WooCommerce functionality of the plenigo plugin Order Title Format Order title format to use. Product Type Type of the product going to be sold. This is important for the tax rate that will be selected.

屏幕截图:

  • Extensive configuration options
  • Freely configurable curtain

常见问题:

幫助

To get help visit help pages.

可用简码

Checkout Button Creates a checkout button with optional title and optional css class. If the product is bought, the button won't e shown and the contents will be shown instead. Note: You can use shortcodes and all formatting inside the button shortcode [pl_checkout prod_id="{{PRODUCT ID}}" title="{{BUTTON TITLE}}" class="{{CSS CLASS}}"]{{DISPLAY TEXT AFTER PURCHASE}}[/pl_checkout] Checkout Button (persistent) Same as pl_checkout but it will show the checkout button even if the product is bought. [pl_checkout_button prod_id="{{PRODUCT ID}}" title="{{BUTTON TITLE}}" class="{{CSS CLASS}}"][/pl_checkout_button] Failed Payments button Same as pl_checkout_button but it will trigger the failed payments list instead of checking out a particular product. [pl_failed title="{{BUTTON TITLE}}" class="{{CSS CLASS}}"][/pl_failed] Subscription renewal button Same as pl_checkout but it will set the "Subscription Renew" flag for this purchase. [pl_renew prod_id="{{PRODUCT ID}}" title="{{BUTTON TITLE}}" class="{{CSS CLASS}}"]{{DISPLAY TEXT AFTER PURCHASE}}[/pl_renew] Show content or Hide content based on purchases PRO TIP: What if you want to do a Welcome page that knows what the customer purchased and/or refer to other product that may be interested in? No problem! Just create a page and use this neat shortcodes (superpowers if you ask me) to show content if the product has been bought! We do the rocket science. TO SHOW CONTENT: [pl_content_show prod_id=""]This content is shown if the Product has been bought. Thank your customer and encourage to buy other products[/pl_content_show] TO HIDE CONTENT: [pl_content_hide prod_id=""]We don't show and invitation to buy the product if it has been already purchased. Don't annoy your customers [/pl_content_hide] Ok, combine this with purchase buttons and the sky is the limit! Plenigo User Profile replacement To render a complete user profile with the current data from plenigo, just create a nuew Page (i.e.: /PlenigoProfile ) and put the Shortcode below to render a nice (and customizable) user profile. [pl_user_profile]Sorry the user is not logged in to plenigo[/pl_user_profile] After that copy the URL of the newly cerated page and paste it in the Profile URL setting at the Plenigo Login section. Separator vs More tag This hidden HTML tag will let plenigo know where the plugin should trim the contents of the post and show the payment curtain. This allows to manually slice the post without interferring with the "More..." separator, native Wordpress tag.

更新日志:

= 1.12.0 - WP updated plenigo URLs = 1.11.0 - WP updated plenigo URLs = 1.10.0 - WP version compatibility = 1.8.0 - Added Analytics Support = 1.7.8 - Fixed Displaying Categories with quotes = 1.7.7 - Fixed Translations 1.7.6 - Updated dependencies 1.7.5 - Updated dependencies 1.7.4 - Updated dependencies 1.7.3 - Updated dependencies 1.7.2 - Improved stability 1.7.1 - Improved stability 1.7.0 - Added new snippet types 1.6.5 - New parameters on checkout button 1.6.4 - Fix incorrect snippet button 1.6.3 - Fix incorrect snippet calls 1.6.2 - Embed plenigo on your site 1.6.1 - App ID Administration 1.6.0 - Time for some updates 1.5.8 - Bug fixes 1.5.7 - plenigo in a language near you 1.5.6 - Bug fixes 1.5.5 - Bug fixes 1.5.4 - Bug fixes 1.5.3 - Bug fixes 1.5.2 - Improvements (and new year's resolutions) 1.5.1 - Fixed version number 1.5.0 - Some presents for this holidays! 1.4.9 - Awesome Greetings for your awesome new users! 1.4.8 - Paving the road of the future and covering some road bumps too! 1.4.7 - To provide better support for you! 1.4.6 - To provide better support for you! 1.4.5 - Swifty and in shape 1.4.4 - Where is my missing image? 1.4.3 - Get help! 1.4.2 - It's MY order you got there! 1.4.1 - Beware of advanced features! 1.4.0 - New Product types! 1.3.0 - Sorry Sir, your credit card was rejected.... 1.2.3 - Peek A Boo, I see you . . . and you 1.2.2 - Lover for category of products 1.2.1 - Don't want to forget 1.2.0 - A new hope 1.1.32 - WooCommerce Payment Gateway 1.1.31 - Fixed deployment script 1.1.30 - Fixed release problems 1.1.29 - Fixes and Improvements 1.1.28 - Validation problems 1.1.27 - Hot fix release 1.1.26 - Google bot magic 1.1.25 - no-Javascript overlay 1.1.24 - Teaser customization 1.1.23 - New cool freebie tag! 1.1.22 - Aesop and other plugin support 1.1.21 - Fixes for URL redirect 1.1.20 - Bug fixes and improvements 1.1.19 - Allow no redirection 1.1.18 1.1.17 1.1.16 - New curtain 1.1.15 - Disable Metered 1.1.14 - Category support