Jump to content

mixit

Members
  • Content count

    32
  • Joined

  • Last visited

Profile Information

  • Real Name
    Patrick
  1. mixit

    [Contribution] U HTML Emails

    J, Try to read your osC mail in different e-mail readers (if possible) and also within a few webmail readers (like web2mail.com, AOL and gmail) to see if it is caused by your reader. Does the other mails (eg new account and order) do the same? If it is not the reader and other mails do work, I suppose the code did not get into your pages as intended. The plain text is translated by U HTML from the HTML-text to plain text and this is (in my opinion) not a preffered behavior because it is assembled into one line of text. See my additional postings in this forum and on the addon-page if you would like to know more and you can use it if you would like to make your own plain text layout. Patrick
  2. mixit

    [Contribution] U HTML Emails

    J, Good sources are: http://www.mailchimp.com/resources/templates/ -> 'download all the templates in one .ZIP file ' These articles helped me a lot: http://www.campaignmonitor.com/design-guidelines/ http://reachcustomersonline.com/2004/11/11/09.27.00/
  3. mixit

    [Contribution] U HTML Emails

    Hi Rob, My store is not yet live, but I do also think I is very helpful if it is also possible to use it in admin/send email. After I put it together I will post my solution here, I hope within a few weeks...
  4. mixit

    [Contribution] U HTML Emails

    Hi J, I do not precise understand your question, but the screenprint looks like the text-plain (for non-html email) and text-html (for html email) is displayed. Or do you meant the checkout_process e-mail is displayed in a other e-mail (like create_account)? If you use html and it is too complex (read: not basic html) e-mail programs can interpret it in a way you did not intended. To set up a layout it is very important to start with a minimum design, text, fields and tables. If this works you can add whatever you like, but one step at a time and: test, TEST, test .... and test again...
  5. mixit

    [Contribution] U HTML Emails

    How did you install, in fresh osC or with a merge program (like WinMerge)? I have not enough information, but did you put in all the "}" ?
  6. mixit

    [Contribution] U HTML Emails

    Moez, Although the green and strips worked for me (technically), I also setup a new template for two reasons: - now I was able to match the mail to my site (and it has no green or stripes B) ) - email readers interpret html very differently and I want to make it robust I make use for the basis for my html from: http://www.mailchimp.com/resources/templat...c_template.html Download page These articles helped me a lot: http://www.campaignmonitor.com/design-guidelines/ http://reachcustomersonline.com/2004/11/11/09.27.00/ ..and... test, test, TEST!!! (the free test at campaignmonitor.com I did not used yet)
  7. mixit

    [Contribution] U HTML Emails

    You are completely on the right spot. The 'setting' for CHARSET is done in the language-file. For me: includes/languages/english.php You will find: // charset for web pages and emails define('CHARSET', 'UTF-8'); If no CHARSET is found I think it is set to iso-8859. So, actually U HTML does not change standard ocS. Conclusion: U HTML users must set CHARSET to UTF-8?
  8. mixit

    [Contribution] U HTML Emails

    Are the " on the right place? -> <head><meta http-equiv="Content-Type" content=text/html; charset="iso-8859-1"></head> In my [output] it is: Content-Type: text/html; charset="UTF-8" How does U HTML changed this?
  9. mixit

    [Contribution] U HTML Emails

    Is the 'to' address (or other fields?) different in your two test cases (Vanilla and U HTML)? What is more different? Two systems? If it is one system, what do you change to get from vanilla to U HTML and back? (do you entirely (re-)install U HTML?) You can test if with U HTML and insert manually all vars in: $message->send('name', 'name@domain.com', 'name2', 'from@domain.com', 'subject'); If this does not work try the dump just before $message->send and see if vanilla and U HTML differ. And the [output] => --=_a23c.... is most important (this is the message body with text/plain and text/html. I guess the problem for is not in the 'html', but the vars in ->send. There are a lot of checks done before the address (and other feilds) is accepted. You can find them here: includes/classes/email.php and function send (almost at the end). Good luck...
  10. mixit

    [Contribution] U HTML Emails

    Moez, I guess you set EMAIL_USE_HTML == 'true'. It seems that email.php and mime.php have some trouble to make/translate the body of your mail. Maybe you did not set the admin -> configuration -> E-Mail Linefeeds to LF (Windows server to: CRLF)? (this translates the html_text to only "\n" or "\r\n" (therefore the original $email_text must only have code's/tags that strip_tags can strip) ) Something else you can try is: Find: $message->add_html($email_text, $text); Add after: var_dump($message); break; This will display (dump) the whole message the next time you trigger a mail. (do not try this in production... ;) ) Now you can see what is wrong (I hope). If you see html-coding in the dump ask your browser to diplay the source-code of the page. If this code seems good the email.php function add_html (and find_html_images) works o.k. You can now move the var_dump code just after $message->build_message(); The email.php function build_message is some more complex and triggers the mime.php, but this way you can focus and find the problem. I hope this approach works. P.
  11. mixit

    HTML EMAIL for Password Forgotten?

    You can try U HTML... http://addons.oscommerce.com/info/5825
  12. mixit

    [Contribution] U HTML Emails

    [update text/plain has no linefeeds] .. alternative 2. Solution is relative simple without any heavy modifications (as far I can see). Modification IN ADDITION to U HTML v2.1 (2008/08/02): --- step 1 modify admin/includes/functions/general.php AND catalog/includes/functions/general.php --- Find: function tep_mail($to_name, $to_email_address, $email_subject, $email_text, $from_email_name, $from_email_address) { if (SEND_EMAILS != 'true') return false; // Instantiate a new mail object $message = new email(array('X-Mailer: osCommerce')); // Build the text version $text = strip_tags($email_text); if (EMAIL_USE_HTML == 'true') { $message->add_html($email_text, $text); Add after: //--- Beginning of addition: Ultimate HTML Emails ---// global $UHTML_html_text; if (tep_not_null($UHTML_html_text) ){ $message->html_text = $UHTML_html_text; } //--- End of addition: Ultimate HTML Emails ---// --- step 2 add text/plain --- For the e-mail you want to modify the text/plain go to: catalog/includes/modules/UHtmlEmails/LAYOUT_NAME/FILENAME.php At the end of the file, before '?>' insert: $UHTML_html_text = "This is the text/plain code\nwith linefeeds.\n\nYou can also use the variables used in the $html_email."; That's all... This code is also added to the ADDONS-page. Kind regards, Patrick
  13. mixit

    [Contribution] U HTML Emails

    [update text/plain has no linefeeds] The problem seems to be the handling of the $email_text in general.php, function tep_mail. tep_mail expects $email_text to be text/plain (with \n as linefeed). If EMAIL_USE_HTML = true it uses $email_text as text/plain and converts $email_text to text/html with function tep_convert_linefeeds(array("\r\n", "\n", "\r"), '<br>', $email_text ) (-> simply replace 'text linefeed' by 'html linefeed'). (this is done in email.php function add_html) U HTML works the other way around and offers tep_mail html as $email_text. The text/html is handled fine with add_html because there are no \r and/or \n in the offered $email_text (which is html). At this moment there are a few alternatives that could work to put linefeeds in text/plain: 1. to make a U HTML tep_mail, cons: 'not standard osC' 2. change tep_mail in general.php (admin and catalog) to correct the email->html_text with an additional if EMAIL_USE_HTML=true && isset(ULTIMATE_HTML_EMAIL_LAYOUT) The problem with 2. is how to translate the html to text with linefeeds, or how a new variable from the modules/UHtmlEmails (with text/plain) can be used in general.php. Again, if you have some suggestions... ...maybe a other update soon...
  14. mixit

    [Contribution] U HTML Emails

    I installed this contribution and it was very easy and with great results! Thanks Olof and Liliagiba! There is one thing that is missing in this contribution, the 'Content-Type: text/plain' is worst than standard osC. If someone use a 'non-HTML' e-mail viewer with U HTML they see: storeDear customer,Thank you for shopping with us today.Please find below the details of your order. Order Number: 82 Detailed Invoice: https://www.store.com/account_history_info.php?order_id=82 Date Ordered: Wednesday 24 December, 2008 Contents of the order ProductModelPrice (Inc. VAT)Qty.Total (Inc. VAT) Product -Music Download: mp32.65 EUR12.65 EURTotal: 2.65 EURPayment Method: Credit CardBilling AddressName, Address, Country Standard osC puts linebreaks on the right places (in both text/plain and text/html). What can I do to display the Content-Type: text/html like it does, but change the Content-Type: text/plain with linebreaks to make it readable? I do not mind if I also must make a text/plain layout (in this way you are more certan on the behavour of the text layout than with conversion from the html). I hope to hear some suggestions... Kind regards, Patrick
  15. From the perspective of your user this is a VERY important function! For the site owner it is important because the users focus remains within your page and page experience! (prevents to use the browser button) It is also VERY (VERY, VERY) simple to implement. I do hope this contribution ends up in standard osC. Thanks to the contributors. http://addons.oscommerce.com/info/1586 (P.S. I personally prefer the javascript version)
×