Embedder version 1.2 Published

With Thanksgiving and piles of turkey safely tucked away, time for a new version of Embedder.

This update was prompted by the fact that someone noticed that Unicode characters (i.e. for languages like Chinese, Japanese, Hebrew and Arabic) were not working when you tried to put them in an embed.

Version 1.2 fixes that problem, and now you can use any characters you like (in the UTF-8 character set) in an embed. You can also use them in the an embed’s description too, though not in the name of an embed or group.

Also in this version, you can wrap your embeds with individual CSS styles (as if you were using the HTML style attribute). This increases the usefulness of wrapping embeds, and makes it easier too, since you do not have to create new style classes in your CSS style sheet.

To add wrap an existing embed with CSS styles, simply edit the embed’s settings. select the Wrap Embed option, and enter one or more styles into the CSS Style(s) input field.

Note, you can replace the CSS style values with embed attributes, and then you will be able to specify those values each time you use the embed in your blog.

This entry was posted in Embedder Plugin. Bookmark the permalink.

5 Responses to Embedder version 1.2 Published

  1. phil says:

    Great work! Description with Chinese words now can be inserted properly, you deserve a 5 star rate.

  2. moztools says:

    Much appreciated!

  3. David Schwartz says:

    This plugin seems to have some case-sensitivity problems.
    As long as I make both the custom field name and the tag in my content lower-case, it works. If I make them both upper-case or mixed-case, the short-code is displayed in the output instead of being replaced.

  4. moztools says:

    Hmm — probably a bug :).

    I’ll look into it — the intent is that (as in HTML) there should be no case-sensitivity for embed names. The plugin deliberately does not allow you to create two embeds with the same name but different cases (at least when they are global embed, I can’t really prevent it with custom fields), but I guess there are still a couple of loopholes here and there. It should not matter what case you use.

    Thanks for the feedback, David.

    Mike

  5. moztools says:

    On further reflection, it seems that WordPress shortcodes are case sensitive, and there is little I can do about that as long as Embedder uses shortcodes to implement embeds, since it is WordPress and not the plugin that decides whether or not to recognize a shortcode in the text and process it.

    It’s a one line change to restore full case-sensitivity, so I add that to the next version, but the next version will also have a completely new parser (optional at this point, but the Embedder plugin will eventually move over to it completely) and I have just checked and confirmed that the tags will no longer be case-sensitive when using the new parser.

    I believe this is ultimately the correct behavior since all the major tag languages take this approach, and it will allow users, like yourself, the choice of using upper, lower, or even mixed case tags.

    P.S. It could be another week or so before the new version is out, so if you want to make the change yourself, all you need to do is remove the “strtolower()” call on line 47 or emb-embed.php in version 1.2 of the plugin. (It’s the only strtolower() call in the function emb_add_local_embeds, if you are using WordPress to edit it!)

    In other words, line 47 should be changed from:
    $key = strtolower(trim($key));
    to this:
    $key = trim($key);

    Then your mixed case local embeds will work as expected. (Note that global embeds will require lower-case tags only until version 1.3 is out.)