I just downloaded and installed the core plugin; it explicitly states on the page “It also supports all of our extensions.”
However, when I go to any of the extension pages, it tells me I need to pay for a plan to access them.
Which is it? Why would you state it supports extensions if you can’t actually download extensions with the core plugin alone?
]]>Hi, I have installed the plugin and no matter what I do I just cant get it to work. I have set up all the pages with the shortcodes and assigned them, set the Digital Access subscription to forever duration and unlimited number allowed. I edited one of the pages of content and set the visibility to Always visible to Digital Access and no matter what I do I can still see the full page when not logged in.
And then I had a thought, does this work with custom fields? The page content is not in a WYSIWYG, it is an ACF repeater field – can this not be hidden?
]]>When you hit the 3 article limit and you should be prompted with the “nag”, you instead get a blank screen that shows nothing but the header. If you refresh, the nag starts to work like it should from that point forward.
]]>I’m currently using your free plugin for a project and have been experiencing some issues related to its functionality with dynamically populated posts.
The issue arises when trying to apply the paywall to a regular post that is populated dynamically (via js) by entries from custom post types. While the paywall operates as expected on regular post types and posts, it fails to do so when the content of a post is dynamically generated from custom post types.
Specifically, we are trying to implement the following:
So far, we have been unable to implement these features due to the aforementioned issue. We have gone through your documentation and FAQs, but could not find a solution that fits our case.
Could you please provide some insight or guidance on how we can get Leaky Paywall to recognize and function correctly with our dynamically populated posts?
]]>Hi,
I’m testing PHP 8.1.13 on my development server and I’m getting some deprecated notices from your plug-in:
Deprecated Return type of Stripe\Util\CaseInsensitiveArray::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Util/CaseInsensitiveArray.php:44
Plugin: leaky-paywall
Deprecated Return type of Stripe\Util\CaseInsensitiveArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Util/CaseInsensitiveArray.php:57
Plugin: leaky-paywall
Deprecated Return type of Stripe\Util\CaseInsensitiveArray::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Util/CaseInsensitiveArray.php:34
Plugin: leaky-paywall
Deprecated Return type of Stripe\Util\CaseInsensitiveArray::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Util/CaseInsensitiveArray.php:51
Plugin: leaky-paywall
Deprecated Return type of Stripe\Util\CaseInsensitiveArray::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Util/CaseInsensitiveArray.php:24
Plugin: leaky-paywall
Deprecated Return type of Stripe\Util\CaseInsensitiveArray::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Util/CaseInsensitiveArray.php:29
Plugin: leaky-paywall
Deprecated Return type of Stripe\Util\Set::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Util/Set.php:40
Plugin: leaky-paywall
Deprecated Return type of Stripe\StripeObject::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/StripeObject.php:202
Plugin: leaky-paywall
Deprecated Return type of Stripe\StripeObject::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/StripeObject.php:212
Plugin: leaky-paywall
Deprecated Return type of Stripe\StripeObject::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/StripeObject.php:197
Plugin: leaky-paywall
Deprecated Return type of Stripe\StripeObject::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/StripeObject.php:207
Plugin: leaky-paywall
Deprecated Return type of Stripe\StripeObject::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/StripeObject.php:218
Plugin: leaky-paywall
Deprecated Return type of Stripe\StripeObject::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/StripeObject.php:424
Plugin: leaky-paywall
Deprecated Return type of Stripe\Collection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice +
wp-content/plugins/leaky-paywall/include/stripe/lib/Collection.php:119
Plugin: leaky-paywallIt doesn’t stop the plug-in from working, but is it possible to fix this? Thank you!
]]>May I know how this works with search engine bots.
If I set free 3 views, what happens with Google Bot, Bing Bot, do they also see 3 posts only for a period of time, or they are somehow filtered and have unlimited posts view possibility?
]]>I like to use this plugin, but it doesnt support my current wordpress and php. Hoping you can expand it for wider wordpress users.
]]>While testing the plugin with PHP8 these deprecated notices are showing. I’m assuming the plugin would still work but can confirm that it will. Also, do you have plans to remedy these deprecated issues?
Level: Deprecated
Message: Required parameter $email follows optional parameter $hash
Count: 1
Location: wp-content/plugins/leaky-paywall/functions.php:699
Plugin: leaky-paywall
Level: Deprecated
Message: Required parameter $customer_id follows optional parameter $hash
Count: 1
wp-content/plugins/leaky-paywall/functions.php:0
Plugin: leaky-paywall
Level: Deprecated
Message: Required parameter $meta_args follows optional parameter $hash
Count: 1
wp-content/plugins/leaky-paywall/functions.php:0
Plugin: leaky-paywall
Level: Deprecated
Message: Required parameter $email follows optional parameter $hash
Count: 1
wp-content/plugins/leaky-paywall/functions.php:820
Plugin: leaky-paywall
Level: Deprecated
Message: Required parameter $customer_id follows optional parameter $hash
Count: 1
wp-content/plugins/leaky-paywall/functions.php:820
Plugin: leaky-paywall
Level: Deprecated
Message: Required parameter $meta_args follows optional parameter $hash
Count: 1
wp-content/plugins/leaky-paywall/functions.php:820Hi
I realized that the new registration emails to new subscribers dont send by the system. I also tried wp mail smtp with mailgun but doesnt work either..
Please help.
Under Settings > Payments beside the Stripe Webhooks Enabled checkbox. There’s a link to documentation that 404s. v4.18.9
https://zeen101.helpscoutdocs.com/article/120-leaky-paywall-recurring-payments
]]>We’ve had a couple reports from subscribers that they are still being charged after their subscription has been cancelled. We’re using Stripe as our payment processor and have had to manually cancel the subscriptions in Stripe as well.
]]>I accidentally deleted my 1 subscription level that comes with the core plugin. How can I get it back?
Thanks!
]]>Hi there,
a content-restricted post seems to loose all formatting and pictures. By formatting I mean paragraphs, headers, blockquotes. Every post turns into an undistinguishable stream of text.
Can you help?
Regards
]]>Hi,
Is there a recommended solution for hiding (or displaying previews) paid articles in RSS feeds?
Thanks!!
]]>Suppose “Plan A” includes all content, except for the Category: News.
“Plan B” includes all categories.
If a subscriber already has “Plan A” and they want to upgrade to “Plan B,” does Leaky Paywall have a means to pro-rate what they already paid for “Plan A”?
]]>I’ve been using Leaky Paywall for a year or so with no issues. But suddenly new subscribers have stopped being added when they pay for a subscription. The payment goes through PayPal just fine, and their user account is created just fine, but they’re not being added to the Leaky Paywall subscriber list. I am having to manually add them as paid subscribers.
I did make some changes to the website but I cannot pinpoint anything that would have caused a change. I did install the Ultimate Member plugin to see if it would work with Leaky Paywall, but I’ve since deleted it.
Any ideas??
]]>Hello, in the “restrictions” tab, the “subscription” section does not appear as shown in the tutorial documentation.
I cannot set any option such as price or duration of subscription. I can only click on “collapse all/expand all” which obviously doesn’t produce many results.
Theme, WP version and plugin are all up to date; I tried uninstalling and reinstalling the plugin as well.
Thank you in advance
]]>Hi there
I hope you are well.
I am using the Coupon plugin add-ons. I create two coupons one is Monthly and the second is Yearly. When I try to use the Monthly coupon on the yearly subscription it’s throwing an error and it’s correct but when I use the Yearly coupon on the Monthly subscription it’s applied but does not deduct the price and it’s wrong. Yearly coupons should not be applied to Monthly Subscriptions. Also, I create another Coupon with a max usage limit is one and I can still use this coupon more than one time with different accounts
Thanks
]]>Greetings,
A recent update seems to have eliminated the Paypal logo image from the file package. On the registration form, only the Alt text “PayPal logo” is shown and there is no image in the plugin folder. The code says it be at the following location:
/wp-content/plugins/leaky-paywall/images/PP_logo_h_150x38.png
Thanks,
Tony
MY client’s site is having a problem with Stripe. Multiple charges for fraud subscriptions are being executed at Stripe, while the subscriber and transactions do not show in Leaky Paywall.
Stripe logs;
Source
Stripe/v1 PhpBindings/6.43.1 WordPress Leaky Paywall/4.16.12
Please advise.
]]>Hi,
We are currently using Leaky Paywall with PubCare. Everything has been working well so far but we have just came across a major issue that might result in having to switch to an alternative plugin.
It seems like only admin users are able to use Leaky Paywall and this simply will not work for us as a long-term paywall solution.
We are using PublishPress Capabilities to manage and grant capabilities/permissions to non-admin users. Usually, upon installation, other plugins would create additional capabilities that would allow us to assign to specific user roles. However, for Leaky Paywall, this doesn’t seem to be the case.
Is it possible to create new capabilities/permissions for Leaky Paywall that we can then assign to non-admin users? If so, any advice on how best to get this done will be much appreciated.
Thanks!
]]>Hi,
I was wondering if leaky paywall offeres other access possibilities except of paying money. I would like to grant access to all my newsletter subscribers.
Is that possible to set up?
]]>Keen to integrate Leaky Paywall with Klaviyo and Zapier. Any chance you are likely to release these integrations sometime soon?
]]>What does this mean?
]]>Hello,
I’m trying to use this pllugin to restrict content for logged out users. Logged out users can see upto a limited number of posts. Once a user logs in or signs up to the website (free) they can see all content.
Is this possible with leaky paywall?
How do I set all the existing users to my free subscription plan as well as upcoming new sign ups added to the free subscription plan?
]]>Hi!
Leaky paywall’s ability to meter the amount of articles a user can view before they are required to create an account fits my use case. But does leaky paywall work with the extension ultimate member?
My ideal flow is that a user can read 3-5 articles and once they hit their article cap they need to create an account to view the rest of the articles for free.
]]>I am interested in using this plugin to require users to register on the site, but I don’t need the paywall functionality.
As such, I don’t want the Stripe script to load, since it’s completely unnecessary overhead.
How do I disable the Stripe script?
]]>How do I make certain pages only visible to non-logged-in users?
For example, once a user subscribes, how do I stop showing them the subscribe/register pages?
Right now they can access the pages in the menu. It will be confusing for them to subscribe and then see a page that still says to subscribe.
Thanks
]]>Hi everyone…I’m being hacked for my payments with this app. I’ve checked and I don’t have a new user, I’m not showing anyone logging in but the payments keep being change to this new hacker.
Please help and thank you in advance!
]]>Hi,
I changed my theme to “Responsive Blogger”. Didn’t change any settings on my Leaky Pawyall plug-in (and all the settings on the backend are intact). But, the paywall doesn’t seem to be working with the new themes. Pages that were behind the paywall (premium category) are now visible to non-subscribers. I have removed and re-uploaded the plugin but that hasn’t helped.
Please advice.
]]>