Dear Newspaper
The Leaky Paywall plugin no longer takes Stripe payments since NP 10.4 was issued (and I installed) end of last month.
The plugin takes card details but hangs on initiating payment.
LP’s developer says the problem is with tagDiv Composer. Can you say what has changed with 10.4 to cause this so that I can relay the information to him?
Thanks
Mark Gilbert
Correct. Downgrade asap.
Any feedback on when an update with tagDiv will be available???
Is this a known problem with 10.4 then? Leaky Paywall have suggested disabling tagDiv Composer. That would be pretty major. Is Stripe hanging with other plug-ins?
Hello,
At the moment we did not test those plugins with the theme and we had no way of knowing that these cannot work with the theme.
In some cases this can be a problem related to some plugins or even WordPress (latest updates), to check this please try to do a test on a default theme to see if the problem persists.
Indeed, for the latest version of WordPress and the theme, some issues related to payments have been reported. Our developers have been informed about this issue.
A solution is to revert to the previous version, v10.3.9.1
Thank you for your understanding!
I see there is a problem with Stripe in other plugins. I think it’s established from other posts in the forum there is a problem with tagDiv Composer in 10.4. Leaky Paywall’s developer has researched and identified a problem in Composer, not in the plugin. So I look forward to 10.4.1 with a fix.
As I have said many times, Newspaper, to really be number one, needs to work on its own integrated paywall plugin. Amazingly, getting paywalls, the way forward in online publishing, to work with Newspaper is a big problem, not just in regard to Stripe.
No content restriction plugin I have tried will work with any Newspaper cloud post template, meaning anyone who wants to restrict content cannot use the full design capability of Newspaper. Use a content restrictor with a Newspaper cloud post and the membership prompt only appears at the end of the article, after all content has already been revealed.
Why doesn’t somebody at Newspaper address this obvious issue?
Hello,
We made some changes in the tagDiv Composer plugin, so please deactivate the tagDiv Composer plugin, delete and re-install it again from Newspaper plugins => https://www.screencast.com/t/WLy01lbc
Let us know the results!
Thank you!
Thanks, Anamaria – that’s fixed.
I still think NP should work on a seamless integrated paywall plugin.
How many versions of 10.4 is there now?
Well, only one I think – it’s tagDiv Composer that is/was the problem.
Thank you Mark, for bringing this up.
Spent the whole sunday on this topic and already opened a support ticket at woocommerce.
@Anamaria, why the heck you guys dont publish an official update? Is it really your policy, that a customer has to search the forum to be up to date? Thank you for wasting my sunday.
Regards.
Agreed topmagazin – it’s a major issue. Newspaper takes little notice of the need for publications to make money. Emphasises (not so comprehensive) design over day-to-day functionality, survival, even.
Hello,
We did not make an official update, because the reported problem was related to the tagDiv Composer plugin in the theme, this being fixed and uploaded on our server, from where it can be installed the theme plugins (Newspaper-> Plugins => https://www.screencast.com/t/xX2HgvQLySE ).
When an official update is made the package off ThemeForest is replaced with the latest version of the theme plugins with all the fixes and implementations of the plugins (if it had been an official theme update, then only one issue would have been resolved).
We are sorry for the inconvenience!
Thank you for your understanding!
Thanks – I think topmagazin’s point might be that an announcement needs making once a major fix like that is done. Others might not be following this topic in the forum and be unaware of a problem. I suppose that would mean emailing all customers…
Hello,
To all those who reported that they had problems with strips, we sent them information that we had fixed the problem.
We will consider finding a way that is as efficient as possible for the information to reach all users.
Thank you!
You should consider doing such bug fixes with patches. Like Avada does.
You could provide smaller changes/bugfixes (also to plugins) “on the run”, without having to release a full update at codecanyon.
Sending an email to users seems to me just as little a good solution than not solving it at all until the next update.
Think about how many of your users didnt even notice yet that stripe functionality is broken. Solving such critical issues has to be pushed to all users.
Just my 2 cents.
