Creative Marketing

I concede the point that the die is killing the output.

I still believe there has been a change somewhere that has affected the ability to debug without sending emails unless JSON is new to the checkout since 2.3.8. However at this point I am simply arguing a point that is more convenient for myself so I will close this ticket.

I use die because I want to output the variables without sending the email because the more I can fiddle around with variables without getting an email each debug the better.

The issue I am having isn’t even around the die. It’s the fact that the moment I put any print statement in my code now that the first character of that print statement is listed as a syntax error. As I have shown above I have removed my code from the play and I still get the syntax error in the core email template when I print anything.

If, as in my example I have already put to you, I put print '<pre>'; I will get Syntax error: unexpected token <. If I put print 'Hi'; I will get Syntax error: unexpected token H.

Previously I have been able to output variables (as in the screenshots in the imgur album in my previous post) and they would print out fine but now they don’t and I only get syntax errors.

As in my previous post I updated the site to the latest WooCommerce and WordPress without changing the code snippet above. This is now the output in checkout: http://i.imgur.com/L4BrUXO.jpg

Hi thanks for the reply.

In my empty site I have removed my code from the equation and am literally using a copy of the admin-new-order.php file with a print statement to the same effect:

<?php
/**
 * Admin new order email
 *
 * This template can be overridden by copying it to yourtheme/woocommerce/emails/admin-new-order.php.
 *
 * HOWEVER, on occasion WooCommerce will need to update template files and you (the theme developer).
 * will need to copy the new files to your theme to maintain compatibility. We try to do this.
 * as little as possible, but it does happen. When this occurs the version of the template file will.
 * be bumped and the readme will list any important changes.
 *
 * @see 	    http://docs.woothemes.com/document/template-structure/
 * @author WooThemes
 * @package WooCommerce/Templates/Emails/HTML
 * @version 2.5.0
 */

 if ( ! defined( 'ABSPATH' ) ) {
 	exit;
 }

 print '<pre>';
 print 'Hi';
 print '</pre>';
 die( 'test' );

 /**
  * @hooked WC_Emails::email_header() Output the email header
  */
 do_action( 'woocommerce_email_header', $email_heading, $email ); ?>

 <p><?php printf( __( 'You have received an order from %s. The order is as follows:', 'woocommerce' ), $order->get_formatted_billing_full_name() ); ?></p>

 <?php

 /**
  * @hooked WC_Emails::order_details() Shows the order details table.
  * @since 2.5.0
  */
 do_action( 'woocommerce_email_order_details', $order, $sent_to_admin, $plain_text, $email );

 /**
  * @hooked WC_Emails::order_meta() Shows order meta data.
  */
 do_action( 'woocommerce_email_order_meta', $order, $sent_to_admin, $plain_text, $email );

 /**
  * @hooked WC_Emails::customer_details() Shows customer details
  * @hooked WC_Emails::email_address() Shows email address
  */
 do_action( 'woocommerce_email_customer_details', $order, $sent_to_admin, $plain_text, $email );

 /**
  * @hooked WC_Emails::email_footer() Output the email footer
  */
 do_action( 'woocommerce_email_footer', $email );

I have left this in the empty site which I linked above which produces the same PHP error I have been seeing on my production site.
I have set wp_debug to true and have no errors coming up through this.

This is a change that happened when I updated. The last time I edited the code I was able to do prints and a die on the template with ease. When I came back to make updates after the update to 2.5 I was no longer able to use a print as this syntax error kept occurring. I had to debug by adding my print to the content of the email notification.

Yes that directory exists. I had backups into there successfully until the 23rd Aug. Since that time I have not had any emails (the backups are set to email) with a backup for this site. We have multiple sites set up with aiowps successfully working and backing up but this site is the only one not backing up.

No I had not.

I took a look and I get this error after trying a manual backup:

FAILURE : Error inserting record into *prefix*_aiowps_login_activity

However this looks like an error for my login to the site.