UPDATES EasyBlog 6.0.14 Released! Joomla 5.x and PHP 8.x compatible now!

Helpdesk

Your Time
Our Time
Response Time
24 — 48 hours
We strive to provide the fastest ever response possible. However, we are not super beings.

Allow at least 24 — 48 hours
  Support is online
Our support specialists is available now. We will attend to you as soon as we can.
  Support is online
None
When publishing a frontend Joomla article, the ES content plugin generates a stream item. The issue is that the stream item generated contains the entire article HTML itself (encoded of course). Attached to this post is an example of a single stream item from #_social_stream that has a size of 155 Kilobytes. If users generate thousands of articles it's going to take up a lot of space fast. I understand that users will write smaller articles most of the time, however it would be ideal to save hundreds/thousands of megabytes of DB space. One of two methods could solve this for future article stream items:

1. Rather than caching the entire article text, simply cache the display character limit (default is 300 characters). Stream items would continue to display exactly as they do without using a ton of space.

2. Render the text from the article itself. Kunena stream items seem to do this as seen here: https://dev.peakfun.com/stream/item/103

For the sake of investigating here's a link to the big stream item: https://dev.peakfun.com/stream/item/102
The replies under this section are restricted to logged in users or users with an active subscription with us