By Juz on Thursday, 15 October 2015
Posted in Technical Issues
Likes 0
Views 585
Votes 0
Hi,

We've set Stream -> Truncate Content At Specified Length = 140 characters. However this is causing problems in our Easysocial app. When clicking "More" on the app, nothing happens. The text doesn't expand such that user can read full stream item. So we removed the limit. However, the web app still shows "More" after some text. Same with mobile app. Is there any way to display entire stream item without "More"? Until Appcarvers team can fix this issue on the mobile app.

Thx.
Hi Juz,

You can disable the stream's content truncation by turning off the option 'Truncate Content' from your EasySocial backend under Settings -> Stream -> General -> Content

Hope this help and have a nice day!
Sam
·
Friday, 16 October 2015 12:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Juz,

Please provide us with the steps to reproduce this on your site and also please provide us with the access to the site as well
·
Friday, 16 October 2015 01:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark,

Refer attachment. In ES demo, we set ES backend -> Stream -> General -> Truncate Content At Specified Length = 140 characters. So the content is truncated and user must click "More" to read entire stream item content. All this works fine when accessing ES via the web.

However, there is a critical bug in the ES mobile app (Appcarvers) that doesn't display the content in full. Click "More" in the app and it doesn't do anything, doesn't render full content. So while Appcarvers team fixes the issue, we're wondering if we can remove the truncate limit so that entire stream item content is always displayed in full by default.

So we removed any value in the text box ES backend -> Stream -> General -> Truncate Content At Specified Length. When we re-login and scroll through past stream items, we notice that content is not being displayed in full and "More" option still exists. Is there a way to display every stream item in full?

Thx.
Juz
·
Friday, 16 October 2015 10:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Appcarvers has written their own API to generate the output of the events through their own com_api. If this works well on the web, I don't see how is this an issue with EasySocial. You should bring this up in their forums.
·
Friday, 16 October 2015 12:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for your reply Sam. Silly of me to not notice that option
Juz
·
Friday, 16 October 2015 13:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Juz, glad that your issues are resolved now.
·
Friday, 16 October 2015 14:01
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post