Sometimes the internal rewrites in Jive produce broken HTML. For instance if somebody posts a message that only contains a emoticon, I download the following HTML through the webservices:
<body><p><span __jive_emoticon_name="laugh" __jive_macro_name="emoticon"></span></p></body>
Obviously this is not going to render correctly. Where can I find documentation for all the possible __jive_* attributes in the rewrite output tso that I can restore them to valid HTML suitable for rendering?
Anyone? I would like to get started on fixing the HTML but I need some documentation for that.
Hey Jochem,
You're right, those attributes aren't valid html, so I've filed a bug in our system under the ID CS-17612. Until then, it looks like you'll just have to work with the values that we use per version. I looked around, and I couldn't find any documentation on how our emoticon's html was done, so I just used the RTE to get the html for the emoticons under 4.0 and 3.0.10. They are listed below. If you want the emoticons for any other versions, just make a document in the RTE, put all of the emoticons in it, then switch to html mode. That will give you the emoticon html that we'll give you in the returns from your web services calls.
Thanks,
Kevin
4.0 emoticons:
<img src="/4.0.0/images/emoticons/happy.gif" jivemacro="emoticon" ___jive_emoticon_name="happy" />
<img src="/4.0.0/images/emoticons/laugh.gif" jivemacro="emoticon" ___jive_emoticon_name="laugh" />
<img src="/4.0.0/images/emoticons/silly.gif" jivemacro="emoticon" ___jive_emoticon_name="silly" />
<img src="/4.0.0/images/emoticons/wink.gif" jivemacro="emoticon" ___jive_emoticon_name="wink" />
<img src="/4.0.0/images/emoticons/plain.gif" jivemacro="emoticon" ___jive_emoticon_name="plain" />
<img src="/4.0.0/images/emoticons/angry.gif" jivemacro="emoticon" ___jive_emoticon_name="angry" />
<img src="/4.0.0/images/emoticons/blush.gif" jivemacro="emoticon" ___jive_emoticon_name="blush" />
<img src="/4.0.0/images/emoticons/confused.gif" jivemacro="emoticon" ___jive_emoticon_name="confused" />
<img src="/4.0.0/images/emoticons/cool.gif" jivemacro="emoticon" ___jive_emoticon_name="cool" />
<img src="/4.0.0/images/emoticons/cry.gif" jivemacro="emoticon" ___jive_emoticon_name="cry" />
<img src="/4.0.0/images/emoticons/devil.gif" jivemacro="emoticon" ___jive_emoticon_name="devil" />
<img src="/4.0.0/images/emoticons/grin.gif" jivemacro="emoticon" ___jive_emoticon_name="grin" />
<img src="/4.0.0/images/emoticons/love.gif" jivemacro="emoticon" ___jive_emoticon_name="love" />
<img src="/4.0.0/images/emoticons/mischief.gif" jivemacro="emoticon" ___jive_emoticon_name="mischief" />
<img src="/4.0.0/images/emoticons/sad.gif" jivemacro="emoticon" ___jive_emoticon_name="sad" />
<img src="/4.0.0/images/emoticons/shocked.gif" jivemacro="emoticon" ___jive_emoticon_name="shocked" />
3.0.10 emoticons:
<img src="/images/emoticons/happy.gif" jivemacro="emoticon" ___jive_emoticon_name="happy" />
<img src="/images/emoticons/laugh.gif" jivemacro="emoticon" ___jive_emoticon_name="laugh" />
<img src="/images/emoticons/silly.gif" jivemacro="emoticon" ___jive_emoticon_name="silly" />
<img src="/images/emoticons/wink.gif" jivemacro="emoticon" ___jive_emoticon_name="wink" />
<img src="/images/emoticons/plain.gif" jivemacro="emoticon" ___jive_emoticon_name="plain" />
<img src="/images/emoticons/angry.gif" jivemacro="emoticon" ___jive_emoticon_name="angry" />
<img src="/images/emoticons/blush.gif" jivemacro="emoticon" ___jive_emoticon_name="blush" />
<img src="/images/emoticons/confused.gif" jivemacro="emoticon" ___jive_emoticon_name="confused" />
<img src="/images/emoticons/cool.gif" jivemacro="emoticon" ___jive_emoticon_name="cool" />
<img src="/images/emoticons/cry.gif" jivemacro="emoticon" ___jive_emoticon_name="cry" />
<img src="/images/emoticons/devil.gif" jivemacro="emoticon" ___jive_emoticon_name="devil" />
<img src="/images/emoticons/grin.gif" jivemacro="emoticon" ___jive_emoticon_name="grin" />
<img src="/images/emoticons/love.gif" jivemacro="emoticon" ___jive_emoticon_name="love" />
<img src="/images/emoticons/mischief.gif" jivemacro="emoticon" ___jive_emoticon_name="mischief" />
<img src="/images/emoticons/sad.gif" jivemacro="emoticon" ___jive_emoticon_name="sad" />
<img src="/images/emoticons/shocked.gif" jivemacro="emoticon" ___jive_emoticon_name="shocked" />
Kevin Imber wrote on 11/18/2009 10:58 PM:
You're right, those attributes aren't valid html, so I've filed a bug in our system under the ID CS-17612. Until then, it looks like you'll just have to work with the values that we use per version. I looked around, and I couldn't find any documentation on how our emoticon's html was done, so I just used the RTE to get the html for the emoticons under 4.0 and 3.0.10.
How can I extract the version of the server from the webservices?
They are listed below. If you want the emoticons for any other versions, just make a document in the RTE, put all of the emoticons in it, then switch to html mode. That will give you the emoticon html that we'll give you in the returns from your web services calls.
And how about the way you encode quotes? Code blocks? Inline images? I
would much rather have an algorithm then a bunch of examples.
Jochem,
It doesn't seem to be possible to get the version info without admin privileges. I've filed a feature request for a new web services call to give that information out under the ID CS-17629. As for documentation about how our encoding works, I'm not finding anything yet. I'll keep looking, and let you know if I find something that can help you. Let me know if you have any other questions.
Thanks,
Kevin
Kevin Imber wrote on 11/19/2009 8:18 PM:
It doesn't seem to be possible to get the version info without admin privileges. I've filed a feature request for a new web services call to give that information out under the ID CS-17629.
Thanks.
As for documentation about how our encoding works, I'm not finding anything yet. I'll keep looking, and let you know if I find something that can help you. Let me know if you have any other questions.
I have another one, which is documentation on going to other way. This
is about reading through the webservivces, but I am also trying to go
the other way and post messages through the webservices. There I have
the problem that you are running some transformations that result in
unreadable messages. I have started a different thread about that at
Hey Jochem,
Unfortunately, I don't think we have documentation on encoding or similar topics. We've been incredibly busy lately in support, but hopefully we'll be able to respond to your other case soon.
Thanks,
Kevin
kevin.imber wrote:
You're right, those attributes aren't valid html, so I've filed a bug in our system under the ID CS-17612.
If the Triage was for a patient he would be dead now.
I see CS-17612 has passed triage. Unfortunately the current one-liner "HTML for emoticon not valid" is a vast understatement of the problem. Emoticons were just the example. The problem caused by not being able to get the URL of an inline image is much bigger then the problem of a broken emoticon. Not to mention tables and all sorts of code escaping and quotes. In additon, the list of affected versions is incomplete. The issue at the very least also affects 3.0.8 and unfortunately a recent upgrade from 2.5.7 to 2.5.16 means that my primary forums are affected now too.
Could you please expand the scope of the problem and affected versions and classify the priority accordingly?
Hi Jochem,
I've changed some of the details of the bug report for you, and I've given it a bump for your recent requests, but the bug priority is something that the engineering team decides based on their time and where they need to go with it, so I won't change that.
Thanks,
Kevin
I am still not seeing 2.5.16 not 3.0.8 in the list of affected versions. And can you update the actual title of the issue? Since we don't get access to Jira to read the comments it is important that the title is an acurate representation of the issue.
Hi Jochem,
I've added those versions to the bug. The name was fixed on the first update. Let me know if you have any other questions.
Thanks,
Kevin
Jive combines the most powerful features of collaboration software, community software,
social networking software & social media monitoring into the leading SBS solution.
© Copyright 2000–2010 Jive Software. All rights reserved.
915 SW Stark St., Suite 400, Portland, OR 97205
Sales: 877-495-3700 | General: 503-295-3700
Privacy Policy | Sitemap | Jobs | Contact Us