Forum Replies Created

Viewing 15 replies - 1 through 15 (of 76 total)
  • Thread Starter kwebdesign

    (@kwebdesign)

    Thanks, I’ll discuss with our client to see if this is something they’re interested in.

    Thread Starter kwebdesign

    (@kwebdesign)

    Sorry for the delayed update. I’ve recently downgraded Cookiebot, which caused my account to go into trial mode. Once the trial expired, I had to re-opt in for their free plan. I hadn’t realised this was necessary, causing Cookiebot to malfunction and prevent other code from running as expected. The solution was to re-opt in to the Cookiebot free plan.

    Thread Starter kwebdesign

    (@kwebdesign)

    Many thanks for taking the time to reply. Apologies for the hasty message. It turned out to be a conflict with Cookiebot, which I’ll look into.

    Thread Starter kwebdesign

    (@kwebdesign)

    I’ve just discovered that the email is being generated via the Shop Magic plugin, so I apologise for wasting the time of anyone who has viewed this thread.

    Thanks again to those who offered their assistance.

    Thread Starter kwebdesign

    (@kwebdesign)

    Just a little update…

    I’ve just set up a completely blank install of WordPress.
    I’ve installed WooCommerce with “Direct Bank Transfer” enabled and a dummy test product. I’ve also set up email functionality with WP Offload SES.

    Having placed a test order, I received the “Your {Website Name} order has been received!”, but once the order was cancelled, I didn’t receive the “Your Order {123456} is Cancelled” email. This suggests that it’s possibly another plugin generating this email. If so, I would have thought someone at WooCommerce would have picked up on this and mentioned it.

    In the meantime, I’ll look at cloning the original site and repeating the test, whilst removing one plugin at a time, to see if the email suddenly stops arriving.

    Thread Starter kwebdesign

    (@kwebdesign)

    As an alternative solution, I’d now like to try editing the body copy of this email, to include the preferred Reply To address.

    However, this particular email doesn’t appear under WooCommerce / Settings / Emails or within the WooCommerce email template files.

    I guess the most common template used for a customer, when an order is cancelled, would be the “Refunded order” email. With the “Direct bank transfer” payment option, this isn’t relevant, hence the use of this fallback email.

    I’ve tried the following…

    add_action( 'woocommerce_email_before_order_table', 'add_email_content', 10, 4 );
    
    function add_email_content( $order, $sent_to_admin, $plain_text, $email ) {
       if ( 'cancelled' === $order->get_status() && 'customer' === $email->role && 'yes' === $email->enabled ) {
          echo '<p>This is some additional content for the cancelled order email.</p>';
       }
    }
    

    This didn’t work.

    Is anyone able to tell me how I can edit the content that is included in this email?

    Thread Starter kwebdesign

    (@kwebdesign)

    Still no luck, but thanks again for trying.

    Thread Starter kwebdesign

    (@kwebdesign)

    Apologies for the delay responding and many thanks for your input.

    Unfortunately, I’ve just tested this snippet and the email received, still didn’t include a Reply To address.

    The 1st email with a subject of “Your {Company Name} order has been received!” did.
    The 2nd email with a subject of “Your Order {123456} is Cancelled” did not.

    Thread Starter kwebdesign

    (@kwebdesign)

    No problem. Thanks for the update.
    Whilst progressing with AWS, they’ve requested I verify an identity before I can be removed from Sandbox, so Step 4 might be better placed as Step 3.

    Thread Starter kwebdesign

    (@kwebdesign)

    The Offload SES Lite plugin provides a setup wizard.
    Step 3 of 6, includes the following information.

    Sandbox Mode

    By default, all new Amazon SES accounts are placed into sandbox mode, which means that you can only send emails to email addresses that are verified with Amazon. To move out of sandbox mode and send emails to any address, you’ll need to put in a request with Amazon to move to production.

    1. Login to your Amazon console and open an SES Sending Limits Increase case.
    2. In the form, make sure you provide the following information:
      • Region: Set this to Europe (London), the same region that you selected in the previous step.
      • Limit: Select “Desired Daily Sending Quota” and try to estimate the number of emails your site will send per day as the limit value (rounding up is fine).
      • Mail Type: Select “Transactional” from the drop down list.
      • My email-sending-complies with the AWS Services Terms and AUP: Yes
      • I only send to recipients who have specifically requested my mail: Yes
      • I have a process to handle bounces and complaints: Yes
      • Use Case Description: Describe the types of emails that your site will be sending.

    Once you submit the form, Amazon will review your request and send you an email letting you know if it has been approved and your account has been moved out of sandbox mode. Amazon usually reviews your request within one business day.

    You can continue setting up this plugin in the meantime by continuing to the next step.

    When I follow the “open an SES Sending Limits Increase case” link, it takes me here… https://support.console.aws.amazon.com/support/home?region=us-east-1#/case/create?issueType=service-limit-increase&limitType=service-code-ses

    Once I’ve selected EU (London), this is what I see.
    https://snipboard.io/5TesDm.jpg

    If you select a region, does the same thing happen for you?

    If so, I was suggesting that perhaps the instructions within the plugin might need adjusting slightly, to reflect this.

    Thread Starter kwebdesign

    (@kwebdesign)

    Issue resolved now. Thanks!

    Thread Starter kwebdesign

    (@kwebdesign)

    When I add the domain it says…

    Email identity {domain name removed} already exist.

    It’s definitely not in the list of senders though.

    Thanks for your input, it was very useful. I’ve contained a slightly wider block of code within the new condition…

    /**
     * Check at checkout if any
     * 
     * @access  public
     * @since   1.0.0
     * @param   Array   $fields
     * @param   Object  $errors
     */
    public function ycve_variation_validate_dt( $fields, $errors ){
    
        foreach ( WC()->cart->cart_contents as $key => $item ) {
            
            $product_id = $item['product_id'];
            $product    = wc_get_product( $product_id );
            
            // Check if the product is a variable product
            if ( $product->is_type( 'variable' ) ) {
                $variations = $product->get_children();
                
                if( ! empty( $variations ) ){
                    foreach( $variations as $variation ){
                        $this->ycve_check_exp_date_to( $variation );
                    }
                }
            
                $newProduct     = wc_get_product( $product_id );
                $newVariations  = $newProduct->get_children();
            
                if ( ! in_array( $item['variation_id'], $newVariations ) ) {
                    
                    $name       = $item['data']->get_name();
                    $itemsCount = count( WC()->cart->get_cart() );
                    $cart_url   = wc_get_cart_url();
                    $errorMsg   = '<b>' . $name . '</b> it is really not available! already removed from cart!! <a href="' . $cart_url . '"><b>Check cart</b></a>';
                
                    if( $itemsCount > 1 ){
                        $errorMsg = 'Product: <b>' . $name . '</b> in your cart, it is really not available and already removed from cart!! <a href="' . $cart_url . '"><b>Check cart</b></a>';
                    }
                
                    $errors->add( 'validation', $errorMsg );
                }
            }
        }//cart end
    }
    
    Thread Starter kwebdesign

    (@kwebdesign)

    Sorry, I should have been clearer in my original message.

    The websites that I’m having the issues with, aren’t showing up in the “Verified Senders” tab. When I said “The plugin shows 25 verified senders, but my Amazon account shows 66 verified senders.”, I’m trying to establish why only 25 show up in the “Verified Senders” tab. I’m assuming, if I can get them all to show up, the error will go away.

    The plugin and AWS is set to Europe London. I’ve checks one domain that does show in the “Verified Senders” tab and also a domain that doesn’t.

    Thread Starter kwebdesign

    (@kwebdesign)

    I cleared the message and refreshed the page, but the message did not return. I sent a test and returned to the General tab, and the message was there again.

Viewing 15 replies - 1 through 15 (of 76 total)