latest update broke my site

I just tested this on my own site and did not get any errors. Perhaps a hiccup in the server it seems? Can you please try again and let me know?

Hey Emily,

Sorry about that, but glad to hear that you had a backup. Do you have access to your server’s error logs by chance? You could look for the timestamp of the error and reply back with the exact error message found in your error logs.

Same here.

Log entry shows PHP Fatal error: Class 'WC_Stripe_Apple_Pay' not found in .../wp-content/themes/bgmc-tickets/functions.php on line 148

That line is removing the Apple Pay button from its default location:
remove_action( 'woocommerce_checkout_before_customer_details', array( WC_Stripe_Apple_Pay::instance(), 'display_apple_pay_button' ), 1 );

and was taken from the plugin’s official site.

• This reply was modified 7 years, 2 months ago by Peter Hardy-vanDoorn.

Hi there,

The WC_Stripe_Apple_Pay class is no longer named that; additionally, the button is no longer displayed on the Checkout page.

You are safe to remove that from your functions.php file.

@shellbeezy since this is quite a major, breaking change, I can’t help but think it should have been mentioned in the changelog! Very shoddy – not at all impressed and, to be quite blunt, I expect better from @automattic, especially since the advice to use that class was (and still is) linked to on the official plugin support page on woocommerce.com

Hey Peter,

Sorry about this, but I couldn’t find that snippet or mention of that class in our documentation, can you provide a link to where this is still mentioned?

https://docs.woocommerce.com/document/stripe/#section-16

Still no mention of that in the changelog though!

my logfiles don’t have much that makes sense to me. i tried again to update it and still got the error 500. this is what my logs say for today:

[Thu Jan 11 03:02:21 2018] [error] [client 80.212.233.167] Premature end of script headers: wp-login.php
[Thu Jan 11 03:41:00 2018] [error] [client 173.236.184.137] Premature end of script headers: index.php, referer: https://inspiritcrystals.com/hematite-195445/
[Thu Jan 11 05:03:33 2018] [error] [client 173.236.184.137] Premature end of script headers: index.php, referer: https://inspiritcrystals.com/crystals
[Thu Jan 11 05:12:12 2018] [error] [client 173.236.184.137] Premature end of script headers: index.php, referer: https://inspiritcrystals.com/product-category/books/
[Thu Jan 11 05:25:45 2018] [error] [client 173.236.184.137] Premature end of script headers: index.php, referer: https://inspiritcrystals.com/product-category/boxes/
[Thu Jan 11 07:20:46 2018] [error] [client 173.236.184.137] Premature end of script headers: index.php, referer: https://inspiritcrystals.com/product-category/odds-ends/pouches/
[Thu Jan 11 08:00:06 2018] [error] [client 66.220.156.60] Premature end of script headers: index.php, referer: https://m.facebook.com
[Thu Jan 11 08:09:53 2018] [error] [client 193.202.110.20] ModSecurity: Access allowed (phase 1). Matched phrase “Windows Live Writer” at REQUEST_HEADERS:User-Agent. [file “/dh/apache2/template/etc/mod_sec2/999_dreamhost_request_limits.conf”] [line “2”] [id “999000”] [hostname “inspiritcrystals.com”] [uri “/xmlrpc.php”] [unique_id “WleMUa3suIkAAHNGgUAAAABg”]
[Thu Jan 11 10:21:00 2018] [error] [client 34.228.17.47] Premature end of script headers: index.php
[Thu Jan 11 13:13:34 2018] [error] [client 173.236.184.137] Premature end of script headers: index.php, referer: https://inspiritcrystals.com/product-tag/june/
[Thu Jan 11 16:00:46 2018] [error] [client 97.95.32.228] Premature end of script headers: index.php, referer: https://inspiritcrystals.com/buddstone/

“Premature end of script headers: index.php” generally means you ran out of PHP memory.

I checked your server and you appear to be on PHP 5.6. Can you go into your DreamHost panel and change that to PHP 7? You should see a reduction in memory usage, which may resolve this.

@petervandoorn version 4.0.1 reintroduced the previous class name to prevent fatal errors.

@emilysparkle are you running version 4.0.1? I’m not sure any of the errors in the log file you pasted are severe enough to cause a 500 error, but updating PHP would be a good start.

• This reply was modified 7 years, 2 months ago by Thomas Shellberg.

updating my php solved my issue! thank you!