Email Customizer [Deleted]

Status
Not open for further replies.
No, you don't need to uninstall it.

In add-ons list find trial version, click "Controls", select option to update add-on. Upload new php files, replacing old ones, import new XML file.
 
Arty updated Email Customizer with a new update entry:

Disable poster profile, custom code replacements

Changes:
  • Option to remove poster profile in topic reply notification.
  • Custom code replacements. This function can be used to:
    • Change layout of custom bbcode, such as replacing <h1> with <h1 style="color: red;">
    • Create shortcodes, such as replacing
      with <hr />
      [*]Change text in email without editing language pack



To update from previous version you need to upload new files, go to add-ons section in admin panel, find add-on, click "Controls"...



Read the rest of this update entry...
 
Using Abyss theme and Weekly Digest addon by Andy, emails look quite bad,

1.png


Whereas standard emails look great,

19223d.png


Any idea?
 
So just a quick question when it comes to Outlook 2013 client, and how the mail looks. (Using 1.0.1 version, premium)

This is from my preview in ACP:
upload_2016-3-13_12-47-55.webp

This is how Outlook 2013 handles it: (Andy's Inactive members)

upload_2016-3-13_12-48-23.webp

And this is how the browser IE handles it: (show in browser option from Outlook)
upload_2016-3-13_12-49-21.webp

And this is how Outlook handles mails coming from "contact us":
upload_2016-3-13_12-50-37.webp

@Arty any ideas on why its not really showing the same way?
 
Outlook is a nightmare. Instead of using HTML code, it converts email into MS Word format and displays it as MS Word document.

Unfortunately nothing can be done about that.

OK - so I should probably be focusing on having GMAIL, Outlook.com and other known web mails OK then.
Thanks for quick reply, and an awesome addon :)
 
Arty updated Email Customizer with a new update entry:

Support for Weekly Digest add-on

Changes:
  • Support for weekly digest add-on. Weekly digest add-on didn't apply any style to emails, resulting in email using default font colors in some mail readers. Email customizer add-on now automatically detects presence of weekly digest add-on and applies styling to emails generated by that add-on.
To update from previous version you need to upload new files, go to add-ons section in admin panel, find add-on, click "Controls" button, select option to update add-on and...

Read the rest of this update entry...
 
Just a note this throws an error trying to import styles based on pixelexit theme framework.
Code:
Exception: Infinite loop when resolving property callToAction - library/EmailCustomizer/Libraries/EmailParser/PropertyResolver.php:239

#0 /library/EmailCustomizer/Libraries/EmailParser/PropertyResolver.php(322): EmailParser\PropertyResolver->_resolveProperty('callToAction', Array)
#1 /library/EmailCustomizer/Libraries/EmailParser/PropertyResolver.php(284): EmailParser\PropertyResolver->_parseVariable('@callToAction.h...', Array)
#2 /library/EmailCustomizer/Libraries/EmailParser/PropertyResolver.php(248): EmailParser\PropertyResolver->_parsePropertyValue('display: inline...', Array)
#3 /library/EmailCustomizer/Libraries/EmailParser/PropertyResolver.php(172): EmailParser\PropertyResolver->_resolveProperty('callToAction')
#4 /library/EmailCustomizer/Libraries/EmailParser/StyleParser.php(682): EmailParser\PropertyResolver->resolveProperty('callToAction')
#5 /library/EmailCustomizer/Libraries/EmailParser/StyleParser.php(394): EmailParser\StyleParser->_getSplitProperty('callToAction')
#6 /library/EmailCustomizer/Libraries/EmailParser/StyleParser.php(25): EmailParser\StyleParser->_parseTopicReply()
#7 /library/EmailCustomizer/Libraries/EmailParser/StyleParser.php(54): EmailParser\StyleParser->__construct(Object(EmailParser\PropertyResolver))
#8 /library/EmailCustomizer/Libraries/EmailParser/StyleParser.php(66): EmailParser\StyleParser::create(Object(EmailParser\PropertyResolver))
#9 /library/EmailCustomizer/Controller/Import.php(77): EmailParser\StyleParser::parse(Object(EmailParser\PropertyResolver))
#10 /library/XenForo/FrontController.php(351): EmailCustomizer_Controller_Import->actionImportStyle()
#11 /library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#12 /admin.php(13): XenForo_FrontController->run()
#13 {main}

Request State
array(3) {
  ["url"] => string(66) "http://forum.example.com/admin.php?email-customizer/import-style"
  ["_GET"] => array(1) {
    ["email-customizer/import-style"] => string(0) ""
  }
  ["_POST"] => array(3) {
    ["style_id"] => string(2) "41"
    ["_xfConfirm"] => string(1) "1"
    ["_xfToken"] => string(8) "********"
  }
}
 
Most likely your forum style has a bug - style property tries to call itself from within style property. XenForo is rather lenient to such errors, it simply outputs raw XenForo variable when it encounters such situations. However this add-on must generate valid css code because many email clients are not as tolerant to errors as browsers and might mess up layout. Therefore add-on throws exception, so user would know there is a problem in forum style.

Check callToAction property (click style properties, in top right corner enter @callToAction and XenForo will redirect you to correct section). In some of its properties it might call to ether @callToAction or some other property. If it uses @callToAction, then its basic infinite loop. If it doesn't use @callToAction, it probably refers to some other property, which refers back to @callToAction, resulting in more complex loop.
 
Status
Not open for further replies.
Back
Top Bottom