ollycross
Forum Replies Created
-
Thank you for your help Krystian
I have opened a Jira ticket – PPC-1699
https://www.craftwithsarah.com/#memberships
- Click ‘Join now’
- Create an account
- Go to checkout
Under ‘payment methods’ you will see Stripe, but no Paypal button.
Thank you for your help.
I have updated the settings as you suggest, but it does not appear to have made a difference.
The PP option does still appear for non-subscription products.
The Paypal account belongs to the client and I do not have direct access to it, so if the status report says that Reference Payments are enabled then then that is probably correct. I have asked them to confirm.
I have tried this on production (V2.9.6), and in development (V3.0.5), the button is not showing up on either.
Hi Krystian,
For simplicity’s sake I will ignore the dev environment; all details here pertain to the live site at http://www.craftwithsarah.com
Are you using the new checkout UI or the old one?
I am not sure.Is the PayPal button missing only for subscription products, or for all products at checkout?
Only for subscriptionsAre you testing with a sandbox or a live PayPal account?
LiveStatus report:
https://privatebin.syde.com/?5f93b416ab5d6d3d#AiQ5dGLB5afWPB62obsCkLu13BpdpMPruZiN5gW9RpPyForum: Plugins
In reply to: [Caldera Forms - More Than Contact Forms] Deprecated php 7.4Thirding this. I have also submitted a support ticket.
The error:
Deprecated: Unparenthesized 'a ? b : c ? d : e' is deprecated. Use either '(a ? b : c) ? d : e' or 'a ? b : (c ? d : e)' in /var/www/html/assets/plugins/caldera-forms/classes/core.php on line 3732The offending code:
$entry_id = !empty($wp_query->query_vars[ 'cf_entry' ]) ? $wp_query->query_vars[ 'cf_entry' ] : isset($_GET, $_GET[ 'entry' ]) && absint($_GET[ 'entry' ]) ? $_GET[ 'entry' ] : null;The fixed code:
$entry_id = !empty($wp_query->query_vars[ 'cf_entry' ]) ? $wp_query->query_vars[ 'cf_entry' ] : (isset($_GET, $_GET[ 'entry' ]) && absint($_GET[ 'entry' ]) ? $_GET[ 'entry' ] : null);- This reply was modified 6 years ago by ollycross.
Hey Paul, can confirm this is fixed using Shield 9.
Nice work!
Cheers Paul
Hey every little helps, right? That would be great!
Thank you again for your help!
Reading around the issue, the offending code has been patched in V1.42.3; the 1.x releases are compatible back to php 5.5.
Maybe it would be possible to update to the latest 1.x release, until such a time as Shield 10 is released?
https://github.com/twigphp/Twig/commit/d0550b7a68d44551e3cae0aae5a6cf9180aec37e
I understand, 5.4 support is becoming more and more of an issue across a lot of projects.
We suppress all errors on production, but I’d prefer not to do this in development as it might mask issues in our own code, or those of direct dependencies that we can update. This deprecation is particularly problematic as it seems to be triggered every single time a template is called. On a site which makes heavy use of templates this makes the amount of noise unworkable.
Anyway, thank you for coming back to me. I’ll see if I can set up some kind of selective error suppression until such a time that it can be fixed upstream.
I was seeing this issue as well, since update to v14.0.
It seems I had
DB_COLLATION(incorrectly) set toutf8in mywp-config.php. 14.0 includes a DB migration which explicitly sets collation on the Yoast tables, so the incorrect collation entry was causing this to throw an error.The error message is a little unclear as to what has actually gone wrong, as it implies a table creation error.
I removed the constant and allowed WP to use it’s default collation, which seems to have worked fine. I guess I could also have explicitly set it to
utf8_general_ci/utf8mb4_unicode_ci.If you are having this problem, and you know that your DB user has permission to create / edit tables (if you managed to install WP in the first place this is probably the case), check your
wp-config.phpfile to see if you have aDB_COLLATIONconstant set.– If set, try removing it.
– If not set, try adding one, either:
—define('DB_COLLATION', 'utf8_general_ci');
—define('DB_COLLATION', 'utf8mb4_unicode_ci');
Depending on your version of MySQL / WordPress.Ah yeah I see your point, fair enough. Oh well, thank you for coming back to me. Keep up the good work!
v20200407.0.0 🙂
Forum: Plugins
In reply to: [WP Mautic] Settings page added for every pluginThank you!
That’s great, thank you for the speedy help!
Olly