[Carole Langman]

This reply is private.

[Carole Langman]

This reply is private.

[Carole Langman]

This reply is private.

[Carole Langman]

Hi Geoff,

Thanks for your reply.

FYI: The automated emails started working again after a Divi Update. However, all automated emails involving a payment now have a visible PHP error showing on customer and admin emails alike:

Notice: post was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/Divi/page.php’), the_content, apply_filters(‘the_content’), WP_Hook->apply_filters, do_shortcode, preg_replace_callback, do_shortcode_tag, WC_Shortcodes::checkout, WC_Shortcodes::shortcode_wrapper, WC_Shortcode_Checkout::output, WC_Shortcode_Checkout::order_received, wc_get_template, include(‘/plugins/woocommerce/templates/checkout/thankyou.php’), do_action(‘woocommerce_thankyou_paypal’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Gateway_Paypal_PDT_Handler->check_response, WC_Gateway_Paypal_Response->payment_complete, WC_Order->payment_complete, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_processing’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_Cu in /home/carolel2/public_html/wp-includes/functions.php on line 4139

We’ve also updated our ticket with Woo.

A copy of our updated PHP Error Log is HERE.https://www.dropbox.com/s/2g3p2apahic0lc7/php_errorlog%20copy.txt?dl=0

Screenshot of automated Email: https://www.dropbox.com/s/4t99cgib6x9946h/Screen%20Shot%202017-07-02%20at%203.43.54%20PM.jpg?dl=0

We tried all of the suggestions in your email. We are already updated with all of our plugins and themes, including Event Tickets Plus Extension: Enhance Woo Order Templates. We also tried deactivating Woo Commerce Order Status Control plugin and ran a test order after that, but the PHP error remains.

Attached screenshots showing plugin versions for Event Tickets, plus settings for Tickets in Events.

We’d be grateful if you can check the error log to see if we can pinpoint a fix.

Many thanks,

Carole

[Carole Langman]

Hi Jennifer,

Many thanks for your reply. We tried two of the code snippets, which solved both issues of Display Attendees being automatically checked in WP-Admin and removing the check box on the Event page.

The thread you linked here was an old thread dating back to March of 2016. At the end of the thread, it was reported that a fix had been made in version 4.1.2.

“I just wanted to jump back in to let you know that Event Tickets and Event Tickets Plus 4.1.2 were just released and included a patch for this issue. The public attendee list is now disabled by default for new and past events. Please update to the latest version when you have a chance and please feel free to open a new thread if you continue to have any issues with this or anything else down the road.”

As the problem has now resurfaced in Version 4.5.1, will there be a new fix to disable these by default (again)?

Many thanks,

Carole

[Carole Langman]

Hi Geoff,

Thank you for your reply. Indeed you are correct. It seems to have cleared itself.

I did a master flush of our website cache yesterday and again this evening. It may also have been the Cloudflare Service we’ve been using, which we deactivated this evening. In any event, we’re very happy to see the custom code worked. 🙂

We love the Buy Now Button. Is there a custom code to change the color?

Many thanks,

Carole

[Carole Langman]

Just wanted to share a simple fix suggested by Woo Commerce:

The My Account page was a secure page – https://www.devondogs.co.uk/myaccount/ and the Events page URL was: http://www.devondogs.co.uk/events/, thus rendering the login cookies as invalid.

Once we changed all of the website pages to https, the logging out stopped. It was a very simple fix to change in the WordPress dashboard – wp-admin/options-general.php

Many thanks,

Carole

[Carole Langman]

Hi Andras,

Thanks for the reply. We heard back from SiteGround after they tried several options to fix. Here is a copy of their reply:

I reviewed the case and then checked the server logs. There were indeed blocked requests due to the specified errors, but they were caused by the fact that there are rewrite rules in the .htaccess file so that bad bots are blocked. Still, to avoid issues caused by that I went ahead and:

1. Copied the current .htaccess file to .htaccess-orig.
2. Removed the blocking rewrite rules from the new .htaccess file.

After another retry the issue was still present so I looked further for the cause.

During my investigation I found out that there is a custom php.ini file. After checking it I found out that it specified settings that are by default mandatory on our shared servers and cannot be changed. Due to that I renamed the file so it is excluded from loading – after all it might cause issues in this case, than rather helping resolving one.

Regrettably, the issue was still present and after several failed attempts to disable plugins that might cause this I ran out of ideas. Since there is no server-side issue and the problem is related to a specific are of the website leads me to believe that the problem is an application related one. Since we are not able to resolve this it will be best that you contact a professional developer with the necessary knowledge and skill set.

So we are back to square one again. We tried to staging the website but were unable to test it, as the Events Calendar page kept reverting to the live website, even though we changed the URL, which of course negated the exercise.

Can you advise if there is something else we have to do in order to have the Events Calendar work on a cloned website?

Thanks again for your help,

Carole

[Carole Langman]

Hi Andras,

Yes, we refresh the page every time, but remain logged out. This video show us doing that: Dropbox

• No we are not using a caching plugin.
• The User in the video had Admin privileges.

I can set you up as a Tech Support Admin user, but if these forums are public, I don’t really want to publicize that information. Can I send it to you privately?

Since the date of posting this ticket last week, Woo Commerce wrote back to us with this reply:

It might also be worthwhile reaching out to your hosting provider for more help on this. The reason I’m mentioning this is that a quick search pointed me at the following resource: https://wiki.apache.org/httpd/ClientDeniedByServerConfiguration

We are awaiting a reply from SiteGround UK and will keep you updated.

Many thanks,

Carole

[Carole Langman]

OK, thanks George.

Many thanks,

Carole

[Carole Langman]

Yes, it worked. 🙂 Thanks again.

[Carole Langman]

Thanks so much for your help, Cliff. I will try that.

[Carole Langman]

Thank you Cliff. Much appreciated.

Just double-checking – do I add this code to functions.php in wp includes, or somewhere else?

[Carole Langman]

Hi George – are you any further with this? thanks

[Carole Langman]

Hi George, any news on this one yet?

Thanks

[Author]

Posts