Hm, not really sure if I understand you here, sorry. Would it be possible that you elaborate more on this with some screen shot perhaps?

Hello Mark,

you might have a look at frontpage of my site second blogpost. It consists of just an image an after that a "continue reading" block. Till now it would have show the image on frontpage because the block "continue reading" was beating the automatic truncation. Now you can see the image only in blogpost fullview. But there is no "continue reading button" However, i dont want the button, i just want to show the image on frontpage.

Similiar thing with formatted text in first blogpost, if i had formatted text instead of image, it was showing formatted on frontpage, but now it shows unformatted text and only in full view it show same text formatted.

I hope this was understandable, please ask in other case. Thank you and best regards, Macjoomla

Everyone has different use of the image in the blog post and in your case, your setup would be best to show the first image as the post cover, http://take.ms/sBcAl

This way, regardless of what truncation style or method, the image would be used as a cover.

Yes, but then it woul be an empty post and could not be saved and this is not applicable for formatted text before manual continue reading.

In 5.1.7 onwards, you could configure EasyBlog to use the first image it finds in the post as the post cover. You don't necessarily need to use a post cover

Eitherway, I still think it doesn't make sense to have a post without any text at all :|

Hello Mark,

thank you for your suggestion, but what about the truncation and "continue reading" logic, that has been working in Easy Social? Its about the text too that comes before a manual "continue reading block", that used to be shown on frontage as formatted text and not as unformatted as automatic traction does. Overall i am not asking for a new feature, just for an old and used to feature

I will have to review this again as I can see in EasyBlog 5.0, we do not strip the html codes so long that it doesn't exceed the character limit.

Thank you Mark for reviewing this.

And one question to clarify, if i place a manual "continue reading" it should disable the automatic truncation with automatic "continue reading, doesn't it?

Thank you and best regards, Macjoomla

Hi Macjoomla,
Based on the codes, you actually need to have some form of content after the 'readmore' block in order for the truncation to disable. After all, the purpose of the 'readmore' block is to separate the introtext from the rest of the content.

Hello Raymond,

thank you for you answer, this is an interesting information and after my tests, i can confirm this behaviour with EasyBlog 5.1.7. In fact it is enough to have for example an empty text block after the "readmore" block. But then it shows the readmore button and there is nothing to read more.

Overall this seems to be the "big" change, because in older versions you did not need to have text after the readmore block. And then the readmore button was not shown either.

This is an importand difference, as we used to have small blogposts, that we do not want to have a "continue reading" button, because in fact there is nothing to read on. Blogposts added this way used to show well (formatted text or/and image without a readmore button on frontpage), but now there is only the headline left, because there is not text after the readmore button.

I hope you can understand my point and please consider to rethink this change, as i assume, this might not have a special reason to introduce this little change, have you?

Thank you and best regards, Macjoomla

Hi Macjoomla,
Based on the codes, you actually need to have some form of content after the 'readmore' block in order for the truncation to disable. After all, the purpose of the 'readmore' block is to separate the introtext from the rest of the content.

Hey Macjoomla,
Yes having an empty block works too, except the 'continue reading' show unless you turn it off completely, and the devs did mentioned that the readmore block's purpose is not to disable truncation on certain posts.
Unfortunately, it is not easy to change this back to the old behavior, at least not currently because many changes have already been made between 5.0 and 5.1.
Having said that, we may consider implementing this in the future, no solid guarantee though.

Hello Raymond,

thank you for your answer again. No matter what is its purpose, this is another issue about something that was working and is not working after the update. Even if its purpose was not to disable truncation, it did so and was used as it did. So i am looking forward, if you could consider to reimplement this feature for backwards compatibility

Thank you and best regards, Macjoomla

Hello Arlex,

thank you for you answer and this file, this is great and made my day, now everything looks as we are used to

So, for me as somebody, who does not know about programming, this seems to be an easy working way, why not including this in next version of EasyBlog 5.1.8

However, i am looking forward, if you are going to re include this in one of the next versions.

Thank you again for understanding and best regards, Macjoomla

PS: Is it possible to make this as an override even it is in administrator folder?

Thanks, will look into this and discuss with the team again.

Thanks, will look into this and discuss with the team again.

Hello Mark, thank you for discussing this, it is a really usefull behaviour.

Just a short feedback about the fixed post.php. This works perfect, if text has not as much characters as in truccation preferences. If text has more characters, it shows the the complete text and afterwards the "continue reading" button. But obviously there is nothing to read on. So it would be good to have this in mind to ignore the count of characters until truncation in these cases, a manual block of "continue reading" was inserted.

Thank you very much and best regards, Macjoomla

Hey there,

This truncate behaviour haven't change in the latest version of Easyblog 5.1.8 yet, but we already log this into our issue tracker in 5.2, we will see if we can manage to fix the rest of the issue when implement back this behaviour.

For now if you update to 5.1.8 later on, you have to add following code into this file :
JoomlaFolder/administrator/components/com_easyblog/includes/post/post.php
LINE 4243

After this line of code :

$hasReadmore = $this->intro && $this->content ? true : false;

Add this following code, you can refer on my attached screenshot below.

		if ($this->isEbd()) {

			$pattern = '#data-type=\"readmore\"*#i';

			preg_match($pattern, $this->intro, $matches);



			if ($matches) {

				$hasReadmore = true;

			}

		}

Hello Arlex,

thank you again for you help and your understanding. I am looking forward to to the version, you implement back this behaviour

Just a small note about your recent fix, this works best to not truncate text, if there is a manual "continue reading" placed. I am just wondering, why it is showing again the button "continie reading", even if there is no content after the block "continue reading". After the last fix it was viceversa – Is there a short way to fix this?

Thank you and best regards, Macjoomla

Do you mean now the issue is still showing "continue reading" button even there no more content on the blog with my fix?

Is it can point me which blog post having this issue on your blog listing page so I will check into your site directly.

Because i was unable to replicate this issue in locally.

Hello Arlex,

thank you for your answer, I appreciate your help very much

Yes, you can please take a look at the first two posts on my domain:
"Just Intro no content after "Continue reading" and "Test with only image and continue reading block"

Thank you and best regards, Macjoomla

It seems like that is bug even without my fix, I will log this issue into our issue tracker.

By the way, i already applied some temporary fix into your site, can you check again is it work fine now?

JoomlaFolder/administrator/components/com_easyblog/includes/post/post.php

// LINE 6235

		// Get the total of character

		$totalChar = $this->intro . $this->content;

		$totalLength = JString::strlen(strip_tags($totalChar));

		if ($totalLength == $length && $length > $max) {

			return false;

		}

Hello Arlex,

wow, this is what i call really fast – And seems to work perfect

Thank you very much for fixing and logging this issue. Best regards, Macjoomla

It seems like that is bug even without my fix, I will log this issue into our issue tracker.
By the way, i already applied some temporary fix into your site, can you check again is it work fine now?

Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.