Forums / Developer / Language not activating in emotions plugin for ezoe
Erik Weinmaster
Monday 19 April 2010 11:28:56 am
I have ezoe enabled along with the emotions plugin for ezoe. I have setup in the ezoe.ini config Plugins[]=emotions and Buttons[]=emotions to add the feature. The funny thing is the actual functionality works just fine. I can click the button, click an emotion, and it returns the right image. However, the wording doesn't seem to be coming through. Thus in emotions.htm there are several references to {#emotions_dlg.bla_bla_bla}, and thats what I see, not the english (which is the language I'm using) title, or icon emotion description.
thanks,
erik
André R.
Tuesday 20 April 2010 5:07:50 am
ezoe is only tested with the extensions and buttons mentioned in ezoe.ini, to be able to enable that extension you'll have to merge emotions_dlg language strings to ezoeServerFunctions::i18n, which is the function that bridges translations in eZ Publish with the once you have in TinyMCE.
EDIT: But that won't help as this extensions add smily images to the content, and since these are not eZ Publish images, they are ignored by the xml parser and thus removed when you click publish / store.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Tuesday 20 April 2010 7:20:56 am
I don't understand why the emotions are removed when you click publish? The Emotions plugin is included in the 4.3 download (and 4.2 for that matter). I understand its up to individual people to customize the look and function of ezoe, but why is it stripped out in the end? Is this a bug in eZ Publish?
Monday 26 April 2010 9:43:24 am
No, ezxml does not understand images, only relations, and as long as the image miss a id="eZObject_<object_id>" attribute to a valid eZ object, it will be ignored.
One alternative would be to somehow map them to custom tags that have a "image_url" custom attribute on them, and the custom tag is defined as IsInline[<custom_tag_name>]=image in content.ini