adam1414
Forum Replies Created
-
Forum: Reviews
In reply to: [YITH WooCommerce Subscription] Vague sales language… PayPal MUST be usedAgreed … but, this is more of a warning to those looking to use the free plugin. It’s not as simple as just porting over, everything needs to be recreated. It’s important that people know this information when wanting to try out the free version first before going to the paid version.
The review, the notes and the concerns are all specific to this free version on this website. My review and feedback for the paid version would be different.
Forum: Reviews
In reply to: [YITH WooCommerce Subscription] Vague sales language… PayPal MUST be usedYes, the commercial version documentation is much more clear; and yes, it is the free/trial plugin version that is being reviewed here on this site.
Update – I’ve had to purchase the premium version because we have built custom code for our site around its functionality.
The conversion from the free plugin leaves a lot to be desired. We have many upset customers because of this error and we have to manually recreate each membership and have each customer go back through a payment process. Plus, we have custom code that runs based on meta-data in the purchase, so this has had to be refactored. This has cost us much time and money – far more than the original purchase of the plugin would have been had we have known that this payment issue was there (we weren’t in need of any of the other advanced features yet, so we thought we’d wait to purchase the full one until it was needed).
Forum: Reviews
In reply to: [YITH WooCommerce Subscription] Vague sales language… PayPal MUST be usedReally not interested in patronizing and incorrect replies just to save face. You can do your own research, every sales page of your website as well as the details tab/landing page on this one say that sentence…
“Users can find subscriptions… Users can upgrade or downgrade… Users can pause… Users can pay with PayPal” These are listed in the same area using the same language, denoting each of them as optional, which you could argue they are, except payments are not optional if you want a functional plugin and so PayPal MUST be used if you want the plugin to work.
I was good enough to give you guys a starting point to make changes. Look through your 1 star reviews, several are about a worthless free version of the plugin – maybe there’s a pattern, maybe a bit of documentation/warnings in the setup would help prevent people from wasting their time rather than rely on documentation pages hidden in a website as your argument.
- This reply was modified 1 year, 7 months ago by adam1414.
Forum: Plugins
In reply to: [YITH WooCommerce Subscription] Renewal Payments Don’t Work – StripeFor anyone else in need: https://docs.yithemes.com/yith-woocommerce-subscription/premium-settings/supported-gateways/
The free version is PayPal only.
Forum: Plugins
In reply to: [YITH WooCommerce Subscription] Renewal Payments Don’t Work – StripeI’ve gone through more of the help thread and documentation.
Shop owners would almost never want a subscription to renew automatically without taking payment, so the expectation is that this plugin would do just that – or it serves no purpose.
I’m not sure how I thought the plugin was working. I thought it may link/recreate the WC order and use the CC on the customer’s file. I’m really not sure, that’s why I opted for a plugin rather than to build it out. So, when I saw the language that PayPal “can” be used to pay I thought great – but not applicable to me. It really needs to be changed to say that PayPal MUST be used or there will be no payments taken with no warnings.
A disappointing waste of time/resources all created from vague/unclear sales language.
Forum: Plugins
In reply to: [W3 Total Cache] Undefined Variable: m2 in experience_lazyload_mutator.phpThank you, Marko, for the quick response. This was a fairly new install – I should have looked for an update first to see if that fixed it.
On a side note – it looks like the code sample from above still has a typo – I may be wrong and I’m sure this is just a sample for my sake and not from the actual code, but it looks like it should be m[2] and it is written as [m2] above. Just in case anyone else is referencing it.
Thanks again!
- This reply was modified 4 years, 3 months ago by adam1414.