April 2016 | New fonts, improved special links section, curly bracket support

Update

 

Here are the main changes introduced in April of 2016:

The first change applies to all implementations of the BEE editor, including BEE Free and BEE Pro. The second and third one are for applications that have embedded the editor using BEE Plugin.

Let's take a closer look.

 

New fonts available

You can now choose from a wider selection of fonts in the BEE editor, including Lato, Open Sans, and Roboto.

 

How will these fonts render in email clients?

The new fonts are not supported by all the email clients, but we've built CSS font stacks into the BEE editor that automatically fallback to a web safe font in the case a subscriber's email client is not able to render that particular web font.

To keep the HTML code optimized and the BEE editor working smoothly, we have made a small change to the way the font family is applied to a text block via the text editor: the font attribute is now applied to the entire text block. If you need to style different paragraphs using different fonts, simply move them into separate text blocks.

More about using fonts in BEE editor.

More easily and quickly insert special links

Special links allow those that embed the editor into their application to make it easy for users to attach certain links (e.g. "unsubscribe", or "web version of the message", or a link to landing pages available in the application, etc.).

Please note that the new Special links UI applies to images or buttons only. The Special links UI is found under the Content Properties > Action > Special links (in blue), as you can see below: 

It now automatically organizes special links in categories...

... and allows users to easily search for a specific link.

 

Support for curly brackets

Do your merge tags use curly brackets? The BEE editor now supports the double curly brackets syntax. This had been requested by many users of the plugin as their applications used that particular syntax.

 

Until now, this syntax was not supported as it conflicted with the code used by the BEE editor itself. The conflicts have been resolved, and you can now use this popular syntax in your merge tags and merge content. We hope this helps!

See the full list of changes in the release notes article.

Please post a comment below (or contact us) if you have any questions on the above.

Have more questions? Submit a request

Comments

  • Avatar
    Pavel Markov

    Great!!!

  • Avatar
    Justin Zhu

    Awesome work! Esp on the curly brace update.

  • Avatar
    admin

    One question: I have embedded the BeePlugin, will it be automatically updated?
    Thank you

  • Avatar
    Guille Padilla

    Hi all, the application will be automatically updated for all.

  • Avatar
    Daniel

    I have some issues and I don't know If its related to the new update, but after the update I've noticed this error in staging/development environment.
    The Production environment is working fine.

    I've debugged the result of $result = curl_exec($ch); within getCredentials()
    Can someone help me with this?

    cUrl error (#60): SSL certificate problem: self signed certificate in certificate chain

    Verbose information:

    * Hostname was found in DNS cache
    
    * Hostname in DNS cache was stale, zapped
    * Trying 54.77.63.241...
    * Connected to auth.getbee.io (54.77.63.241) port 443 (#0)
    * SSL certificate problem: self signed certificate in certificate chain
    * Closing connection 0

  • Avatar
    Pavel Markov

    Daniel,
    curl_setopt($cHandler, CURLOPT_SSL_VERIFYHOST, false);
    curl_setopt($cHandler, CURLOPT_SSL_VERIFYPEER, true);

  • Avatar
    Daniel

    I have tried that dangerous "fix" but I am facing the same issue.
    Maybe if it worked I could have used that in my development environment, but no way I was going to disable ssl in production.

    Anyone knows why im facing this error? Is auth.getbee.io certificate OK ?

  • Avatar
    Daniel

    Pavel, It worked using:

    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);

    Nevertheless there must be an explanation why its working on my server and having problems in my development environment.

    Im gonna use that setting only in production.
    Thanks

  • Avatar
    Dan Bonville

    I may be missing something, but I am not seeing the updated UI for Special Links on our embedded version of the editor. Do we need to "do something" to see this change in the plugin?

    Thanks!

  • Avatar
    Sergio M.

    Hi Dan,

    These updates were automatically applied to the plugin, so no action is needed.

    Two suggestions:
    - It might be a caching issue. You could clear your browser's cache or test it in a different browser.
    - The new Special links UI is shown when linking to an image or button only. It's found when selecting an image or button and under Content properties > Action > Special links. We've updated the section above to clarify this. Please see: http://help.beefree.io/hc/en-us/articles/207419699#2

    Hope this helps!

  • Avatar
    Dan Bonville

    Thanks Sergio, that explains it!