Notification email

HomeSupportImage StoreNotification email

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #52729
    franklin82
    Participant

    I’ve setup to receive the notification emails but when they come through it only has the following in the message:

    “Photography” Content-type: text/html; charset=utf8

    The actual email from the settings page has the following details:

    ——

    A new order was place at your image store

    Order number:%order_number%

    Order total</strong> %total%

    Number of items: %items_count%

    Customer: %customer_first%

    Customer email: %customer_email%

    ——

    #52758
    Van Halen
    Participant

    Just to confirm this is a bug.

    We have the same problem and have not found any solution yet, it seems the email header gets broken (faulty line breaks?) after “Content-type: text/html; charset=utf8” at line 412 in /_inc/cart.php

    The rest of the code seems the be interpreted as the body of the email or ignored completely, same thing happens with the download and conformation email send to the customers.

    #52778
    jon6565
    Participant

    and it’s a massive bug!  someone can order images and I get the email as per the above and I have no idea what they have ordered.  Its like falling at the last hurdle!  I there a work-around?

     

    #52803
    Xpark Media
    Keymaster

    @franklin82, @Van Halen and @jon6565,

    this will be fix on the next release for the mean time change line 414 from

    		$message = apply_filters( 'ims_email_headers', $headers, $ImStore->opts['tags'], $this->substitutions );

    to

    		$headers = apply_filters( 'ims_email_headers', $headers, $ImStore->opts['tags'], $this->substitutions );
    #52830
    franklin82
    Participant

    Thanks

    #52847
    aurelie
    Participant

    Hi,

    I’m happy to read that this problem is known and will be fixed soon…

    Hax, in which file shall I change the line 414 as you propose ?

     

    #52891
    Xpark Media
    Keymaster

    @aurelie,

    the issue has been fixed in version 3.2.7

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.