PlugUpp Live Pricing for Freemius
| 开发者 | plugupp |
|---|---|
| 更新时间 | 2026年9月27日 22:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- A Freemius pricing card block is a whole card in one go: insert it and it arrives holding the plan's name, its price, its description, its features list and a full-width buy button, every figure and every word of it live and every one of them still its own block. The card itself has a width, a position, a border, a radius, padding, a background and the space between the blocks inside it, all from its own panels, on every theme, including the themes where WordPress leaves those panels switched off.
- A Freemius price block renders any plan, licence tier and billing cycle, picked from dropdowns that offer only the combinations your product sells. Freemius buy button, Freemius plan text, Freemius plan features, Freemius currency toggle, Freemius billing cycle toggle, Freemius release and Freemius money-back sit beside it, all nine under Widgets in the inserter.
[pflp_card]is the same box as a shortcode, wrapping whatever you put between its tags. A row of cards side by side stays an ordinary Columns or Grid block, because WordPress is already good at that.- The plan's own words come from Freemius too.
[pflp_plan]renders its title, its description or its free trial, and[pflp_features]renders its feature list, so nothing on a pricing card is typed twice. [pflp_price]does the same thing as a shortcode, for page builders, the classic editor, widget areas and template files. The blocks and the shortcodes are the same code, so the two can never drift apart, and an existing shortcode converts to a block in one click.[pflp_button]renders a buy button linking to the hosted checkout for that same row, built the way WordPress builds its own Button block so your theme's button styling applies to it. It comes in two kinds, Filled and Outlined, the same two the core Buttons block offers and built the same way, and each kind has its own colours on the Settings screen.[pflp_cycle]renders a billing cycle toggle and[pflp_currency]a currency toggle, each with five styles, a size, a gap and an active colour, and each rendering nothing at all where there is only one option to offer.- The cycle toggle can carry the saving on the yearly option. It is computed from your own prices rather than typed, so a price change moves it, and it is not shown at all when there is no saving to claim.
- A price can print your own text after the figure,
/monthand/yearset once on the Settings screen and following the toggle, or your own words. It is off unless you ask for it, so nothing already published changes. - A plan that does not sell the cycle on show says so, "Yearly only", built from the cycles it does sell. A price never falls back to a nearby figure and never prints a zero.
- Every attribute is optional.
[pflp_price]and[pflp_button]with nothing at all render your headline price and the checkout that sells it, so the shortest thing you can type is already the right one. - A webhook receiver refetches within seconds of a price or plan change in the dashboard, and registers itself: there is nothing to paste. A staleness check is the backstop, and a daily job is the backstop for that.
- Every price carries all of its currencies and all of its billing cycles, so a visitor sees theirs through a swap in their own browser. No request comes back to your site, which means a page cache or a CDN can never serve one visitor's currency to another.
- Buy buttons stay ordinary links to the hosted checkout and gain the visitor's currency, whether the plugin rendered them or your theme did. One setting opens the checkout in an overlay instead.
- If the Freemius API is ever unreachable, the last good prices stay on the page and an admin notice tells you. Nothing goes blank, and no figure is ever invented or shown as zero.
- A shortcode builder on each product's screen writes any of it for you, says what it will render, and lists every price the product sells. Pick Pricing card and it writes the whole card, all six lines at once, ready for a page builder's shortcode widget or the classic editor. A second row of dropdowns offers whatever named choices the element has: a price's format and its suffix, a button's style and width, a toggle's look, the saving badge, a card's featured state and its button style, and a features list's descriptions.
- Card defaults set the border, radius, padding, background and shadow of every pricing card on the site at once. They start empty, so nothing changes until you fill one, and anything set on a card itself always wins.
- The version is live too. Freemius release and
[pflp_release]show the latest release Freemius holds for the product: its version, what it requires and what it is tested up to, and its release date if you ask for it. Freemius money-back and[pflp_moneyback]show the money-back guarantee set in the dashboard. Both show nothing at all where Freemius holds nothing, rather than a typed stand-in that would go stale.
安装:
- Install the plugin through Plugins, Add New, or upload the plugin folder to
wp-content/plugins/, then activate it. - Open Freemius Pricing in the WordPress admin menu. It lands on Products.
- Press Add product and fill in the numeric Freemius product ID and its API Bearer Authorization Token, from the Freemius dashboard under the product, then Settings, then Keys. Nothing else is typed: the product's name arrives with the prices, and the product secret key, which signs webhooks, is read with the token. Both the token and the secret come from the Freemius dashboard, under the product, then Settings, then Keys.
- Press Test token to check it, then Add product to save.
- You are now on the product's own screen, and the webhook is already registered with Freemius: the save did it, and the Status card says so. If it could not be, the same line says why, and Show webhook URL beneath it opens the URL and the events to paste into the Freemius dashboard, under the product, then Webhooks, then Listeners, yourself.
- The same screen has a Shortcode builder: pick the element, the plan, the licence tier and the billing cycle, and it writes the shortcode and says what it renders. Copy it into a page. In the block editor, insert any of the nine Freemius blocks from the inserter under Widgets instead, or drop in the Freemius pricing card from the Patterns tab, and pick the row from dropdowns.
- Freemius Pricing, then Settings holds the site-wide choices: under Display the default currency, whether a visitor's currency choice is remembered, hosted or overlay checkout and how stale prices may get before a background refresh; under Billing cycle the default cycle, the three toggle labels and the three texts that can follow a price; under Buttons the default label, CSS classes and hover effect. Freemius Pricing, then Logs shows what the plugin has been doing.
屏幕截图:
常见问题:
Does this slow my pages down?
No. Pages read the prices from your own database, and your server never calls Freemius while a visitor is waiting. A stale copy renders as it is and schedules a background refresh.
How quickly does a price change appear?
With the webhook registered, within seconds. Without it, within the Refresh after interval on the Settings screen, which starts at 15 minutes, and at worst within a day on a page nobody visits.
What happens if Freemius is down, or my token stops working?
The last prices fetched stay on your pages indefinitely, and an admin notice tells you the refresh is failing. Nothing goes blank and nothing invents a figure.
Do I have to set up the webhook?
No. Saving a product with a working token registers it with Freemius for you, and every later save checks it. Where Freemius has not enabled webhooks for a product yet (it reserves them until a product is actively selling), the save is still complete and the Status card says so rather than blaming the token; every later save tries again.
Do I need Freemius's own WordPress plugin as well?
No. This plugin talks to the Freemius API directly and depends on no other plugin. The two run side by side happily. The only thing this one does to the rest of your page is add the visitor's currency to links pointing at the Freemius checkout, whoever made them, and open them in the overlay if you have chosen it.
Where do I get the API Bearer Authorization Token, and is it safe?
In the Freemius dashboard: the product, then Settings, then Keys. It is stored in your site's settings, shown masked, never written to the log, and sent nowhere but api.freemius.com over HTTPS from your server. The product secret key, which proves a webhook genuine, is read with it, so there is nothing else to copy.
Which currencies are supported?
The ones the Freemius pricing API returns: USD, EUR and GBP. The plugin never converts a price, so a currency a plan has no row in is never offered for it, and the currency toggle does not render at all where there is only one.
Do I have to write out every attribute?
No. Every attribute on every shortcode is optional, and the shortest form is the right one: [pflp_price] renders your headline price and [pflp_button] links to the checkout that sells it. Left out, plan means the plan Freemius marks as featured, licenses means that plan's lowest numbered tier, and cycle means your default cycle where the tier sells it. An attribute you do write is never second-guessed.
Can I show prices for more than one product?
Yes. Add each one under Freemius Pricing, Products, then name one with product="12345", or with its Freemius slug or name. The first product configured is used when a shortcode names none.
The product was renamed in Freemius. When does the site follow?
The name comes with the prices on every fetch, and Freemius sends no webhook for a rename, so it follows on the next refresh, or straight away if you press Refresh now or save the product.
What about the free plan?
Nothing from this plugin: a plan with no price has no figure to show and no checkout to link to, so the block's Plan dropdown does not offer it and a shortcode naming it renders nothing. For the free tier of a pricing table, use an ordinary button, the core Buttons block or your theme's, linking to the plugin's download page. That link is a fixed fact rather than a live price, so there is nothing to keep current.
Are there blocks, or only shortcodes?
Both, and they are the same code, so they can never disagree. Nine blocks under Widgets in the inserter (Freemius pricing card, price, buy button, plan text, plan features, currency toggle, billing cycle toggle, release and money-back), and the pricing card again under Freemius in the Patterns tab, ready sized and bordered. Each block renders your headline row as soon as it is inserted, and its dropdowns offer only the combinations your product sells. A Shortcode block converts to the matching block in one click, and the block type menu converts it back; styling set in the editor's own panels is inline CSS and cannot travel to a shortcode, which the editor says once.
Does it work with a page cache?
Yes, and it is built for it. Every price is written into the page in all of its currencies and all of its billing cycles, and both swaps happen in the visitor's own browser with no request back to your server, so a cached page is the same page for everyone.
Does it replace my buy buttons?
Only if you want it to. [pflp_button] renders one for any plan, licence tier and billing cycle, with four widths, two kinds of button, Filled and Outlined, and the wp-element-button class WordPress gives its own buttons. A button you built yourself works just as well: the plugin adds the visitor's currency to any link pointing at the Freemius checkout, and can open it in an overlay.
Can it show the current version and the money-back guarantee?
Yes. The Freemius release block, or [pflp_release], shows the latest version released on Freemius, what it requires and what it is tested up to, and the Freemius money-back block, or [pflp_moneyback], shows the guarantee set in the dashboard, named after its refund policy. Both update when you release or change them, the same way prices do. A product with no releases on Freemius, such as an app, shows no release line at all, and a product with no money-back period shows no guarantee: there is no typed fallback, because a typed version is the copy that goes stale.
What happens if a plan does not sell the billing cycle on show?
The price says so, "Yearly only", built from the cycles that tier does sell in your own words for them, and the buy button keeps its shape and says the same rather than linking to a checkout that cannot sell it. It never falls back to a nearby figure and never prints a zero. missing="hide" prints nothing instead, and cycle="annual" pins a card to its own figure so a toggle leaves it alone.
What external services does this plugin use?
The Freemius platform. Your server reads your prices from https://api.freemius.com/v1/products/{product ID}/pricing.json, with the money-back period in the same answer, and the latest release from .../tags/latest.json, sending the product ID and your API Bearer Authorization Token and nothing else, and only when you refresh, test a token, receive a webhook or a scheduled refresh runs. The visitor's browser calls https://checkout.freemius.com/geo.json to work out which currency to show, sending nothing beyond the request itself, and caching the answer for an hour. If you turn on overlay checkout, the visitor's browser also loads the checkout script from https://checkout.freemius.com/js/v1/; with the default hosted checkout it does not. Webhooks run the other way, inbound from Freemius to your site, and each one is verified by both a generated URL key and a body signature. Nothing about your visitors is ever sent to Freemius by your server. Freemius terms: https://freemius.com/terms/ . Freemius privacy policy: https://freemius.com/privacy/ .
更新日志:
- Changed: the settings screens are easier to read and quicker to use. A setting that is on or off is now a switch. A choice of two to five is a row of buttons, with every option in view and the chosen one filled. Longer lists stay lists. Each tab's settings sit on one card, in groups under headings, with Save under the card.
- Changed: each product's screen works the same way. The Featured plan override is a switch. In the shortcode builder, the choices for each element are rows of buttons and switches, and the release line's Show is four tick boxes.
- Changed: shorter words on the controls. The badge positions read Strip, Tab, Inside, Corner and None. Checkout reads Hosted page or Overlay. The builder's first choices read Headline plan, Headline tier and Headline cycle, and the line under the code box says what they work out to for your product.
- Changed: the log level on the Logs tab is a row of five buttons: Off, Errors, Warnings, Info and Debug.
- Changed: nothing you have saved changes. Every setting keeps its value.
- Fixed: the Freemius blocks were missing from the block editor in 1.4.0. A mistake in the editor script stopped all nine from loading. They load again.
- Fixed: turning off a product's own featured styling always keeps that product's own values for next time.
- Fixed: a product with no released version yet, such as a plugin still in testing, no longer logs a failed release check on every refresh. It shows no release line, the same as a product Freemius has no releases for.
- Added: a release line, read from Freemius. The Freemius release block and [pflp_release] show the product's latest released version, what it requires and what it is tested up to, such as "Version 1.4.0 · Requires WordPress 6.2 and PHP 7.4 · Tested up to 7.1", with the release date as a fourth part you can add. Choose the parts and their order, the text between them and the date format. Only a released version shows, never a beta. A product Freemius has no releases for, such as an app, shows nothing at all, and the editor, the shortcode builder and the product's Status card each say why. A part Freemius holds nothing for is left out, and there is no fallback text, because a version typed as a fallback is exactly the copy that goes stale.
- Added: the money-back guarantee, read from Freemius. The Freemius money-back block and [pflp_moneyback] show the guarantee from the period and refund policy set in the Freemius dashboard, named the way Freemius names the policy, such as "30-day satisfaction guarantee" for its Moderate policy, or your own words with %d where the number of days goes. It shows nothing while Freemius holds no period, your own words included, so a page can never promise a guarantee the checkout does not give.
- Added: the product's Status card shows the release and the money-back period it holds, and Refresh now fetches both with the prices. The shortcode builder offers Release line, with a Show list of the four parts, and Money-back guarantee.
- Changed: a refresh now reads the latest release from Freemius as well as the prices, and the money-back period arrives with the prices. Each is kept on its own terms: if one read fails, what it last fetched stays and the other still updates. Refresh now says so when the prices came back and the release did not.
- Changed: the webhook this plugin registers with Freemius now also listens for a version being released, deployed, updated or deleted, and for a release being suspended, so a new release reaches your pages within seconds and a withdrawn one leaves them. A site updated from an earlier version brings its existing webhook up to date by itself, once, in the background; a site that had no webhook registered is not given one.
- Added: the look of every currency and billing cycle toggle can be set once, under Toggles on the Appearance tab: a Style, and a Colours grid with a Normal column and an Active one for the text and the background. Leave the style Unchanged and a colour empty and your theme's own stays, exactly as before. A toggle that names its own style in the editor or in a shortcode still keeps it, and so does one given a colour in the editor's own panel. Size and Gap stay on each toggle, because they are layout rather than look.
- Added: buy button colours, site-wide, for each kind of button. The Appearance tab has two Colours grids, Filled buttons and Outlined buttons, each with the same shape as the one on the Featured plan tab: the text, the border and the background that kind of button takes Normal and On hover. An outlined button's background is empty to start with, which is what makes it outlined; set one for a tint at rest or a fill under the pointer. Leave a colour empty and your theme's own stays, as before. A colour set on a button itself, in its block panel or its shortcode, still wins, and a featured card's button keeps its own. The two kinds are called Filled and Outlined everywhere now, including the block's own Styles panel. Each kind of button has a Border width too, and the Buttons settings are three groups now: Buttons for what both kinds share, then Filled buttons and Outlined buttons, each a Border width and a Colours grid. A button shows a border only when it has a width, set here, on the button itself, or by your theme, and 0 means none; a Border colour never creates a width, it colours a border the button already has, and an outlined button keeps its 2px outline while its width is empty. There is no width on hover, because a border that changed under the pointer would move the page, so the On hover Border colour paints the border the button already has. An outlined button's border follows its Text colour until you give Border one of its own. The featured card's button has the same Border width on the Featured plan tab; a width set on the button itself, in its own Border panel, wins over it, as it wins over the site-wide ones.
- Changed: an outlined buy button now takes your theme's own outline style wherever that style can reach it. Its 2px border and its padding were WordPress's own, fixed, and overrode the theme's, so it matched an outlined WordPress Button block on 2 of the 10 themes we test against; it matches on 5 now, Twenty Twenty-One, GeneratePress and Kadence joining Neve and Hello Elementor. WordPress's own outline look stays as the fallback wherever the theme's cannot reach: a theme that keeps its outline style for the core Buttons block, as Astra and Blocksy do, or that sets it through theme.json, as Twenty Twenty-Five and Twenty Twenty-Four do. On Astra the outlined button takes the theme's general button padding and border colour. The Border width and colours on the Appearance tab, and the block's own panels, still win over all of it.
- Changed: a filled buy button on a theme that styles no buttons is now padded the way WordPress pads its own button, so a filled and an outlined button side by side are the same size, in the Appearance tab's preview too. On a theme that styles its buttons, which all ten we test against do, nothing changes.
- Changed: a featured card's button with a Border colour and no Border width keeps the 1 pixel border it has had since 1.2.0, and its Border width now says so. That border came from the colour alone, and a colour no longer creates a width, so the first run after the update writes the width for you: 1, on the Featured plan tab and on every product's own Featured plan, wherever a Border colour is set and the width is empty. It runs once, and a width you have set, 0 included, is never changed.
- Changed: the Settings screen has a new Appearance tab, between Settings and Featured plan, with an entry of its own in the sidebar. Settings keeps what a price says and how it behaves: Display, Billing cycle and the Button label, saved with Save settings. How every toggle, card and buy button looks moved to Appearance, in Toggles, Cards, Buttons, Filled buttons and Outlined buttons, saved with Save appearance, with the live preview beside it. Saving either tab never changes a value on the other. Both are laid out like the rest of the plugin's screens, with their fields in one titled panel and the Save button at its foot rather than adrift below it. Every field that means the same thing on more than one screen is now called the same thing, every colour that can be left empty says Unchanged, and every number box is the same size.
- Added: the Appearance tab previews what you are setting. A live pricing card, two buy buttons, one filled and one outlined, and both toggles sit beside the fields and follow every change, drawn with your own theme and your own settings rather than a picture of them. Point at the card or a button to see its hover, or tick Hold hover to pin the hover on while you pick a colour. The figures are placeholders and no product is needed.
- Changed: the Freemius pricing card pattern now has 16 pixel corners in place of 8, which is the card as it looks on our own pricing pages. A card already on one of your pages keeps the corners it was given: a pattern is copied when you insert it, so changing it never reaches a page you have already built.
- Changed: a site installing this plugin for the first time now starts with the Card defaults filled in from the Freemius pricing card pattern: a 1 pixel #e0e0e0 border, a 16 pixel corner radius and 2rem of padding, with no background and no shadow. A card written as a shortcode then looks like a card inserted from the inserter with nothing to match up by hand. A site updating from an earlier version is not touched: its Card defaults start empty, so not one card on it moved. Empty fields now say what empty means, so a length left blank reads "Theme's own" rather than sitting there looking unset.
- Fixed: a pricing card written as a shortcode into a page builder's widget, alongside other content in the same widget, stretched to the full height of that widget and hung over whatever came next. Measured in an Elementor text widget: 425 pixels tall for 189 pixels of content, overlapping the section below by 236. A card now fills its container only when it is the whole of that container, which is what a row of cards is, so cards side by side are still all the same height with their buy buttons on one line.
- Added: the shortcode builder on a product's screen can now write a whole pricing card. Choose Pricing card as the element and the box gives you the six lines a card is made of, ready to paste into a page builder's shortcode widget or a classic editor: the card, the plan name, the price, the features list and the buy button. The four shortcodes inside name no product, plan or licence tier, because they follow the card, so changing the plan means changing one line. The Billing cycle choice is switched off for a card on purpose: naming a cycle fixes the price, and the billing toggle on the page would then leave that card behind. One card per plan, each in its own column of your page builder.
- Added: a second row of choices in the shortcode builder, so the settings you would otherwise have to look up are on the screen. A price can be written with a currency code instead of a symbol, and with the site-wide text after the figure. A buy button can be Filled or Outlined, and sized to the content or to a quarter, a half, three quarters or the full width. Either toggle can take any of the five looks. A billing cycle toggle can carry the saving badge. A features list can show each feature's description. A card can be forced to stand out or forced not to, and its buy button can be Outlined. Every one of them is a choice of words rather than a value to type, anything left at its default is left out of the shortcode, and the sentence under the box says what the choice changes.
- Added: Card defaults, under Cards on the Appearance tab: a border colour and width, a corner radius, padding, a background and a shadow for every pricing card on the site. They start empty, and empty means unchanged, so nothing on your site moves when you update: a card still takes whatever your theme gives a plain box until you fill a field. Anything set on a card itself always wins, whether it came from the block's own panels or from a shortcode attribute, including a background chosen from your theme's palette. The Cards section's Shadow colour now colours both a card's resting shadow and its hover shadow, because they are one card's shadow. Older versions are in the full changelog.