Pages Issues with Pages

[Cameron Son]

I'm having a baffling issue with Pages. I have been working on migrating my v3.x forum suite to v4.x, and my Pages content carried over horribly. I originally had articles as my home page which would display community news, and I would use the old "teaser" paragraph as what the main page created would show. Only if it were clicked would it show more. 

 

What's killing me here is my old "teaser" content sometimes had URL's embedded in text. For some reason, in IPB4 I cannot get Pages to show hyperlinks unless an article is actually clicked, thereby making for a very odd news page.

 

As an example, something that should appear like this: A new product was released today....

Now appears like this: A new product was released today... (note no hyperlink for the word "released").

 

Only when the article title is clicked to read more do the hyperlinks finally show. What am I missing here? Seems rather crucial!

 

[opentype]

Yes, that is the new default (and there are reasons for it). Assuming the full HTML is still in the field, when you edit a record, you would have to change the article listing template to call the field content directly without stripped formatting. That isn’t the default anymore, but doable. 

[Cameron Son]

13 minutes ago, opentype said:

Yes, that is the new default (and there are reasons for it). Assuming the full HTML is still in the field, when you edit a record, you would have to change the article listing template to call the field content directly without stripped formatting. That isn’t the default anymore, but doable. 

Thanks much for your reply! Is there an example of this somewhere? Seems moving from the old article system to the new Pages system is not so friendly, especially with the old "teaser" paragraph going the way of the dodo bird. I can't seem to even get my teaser paragraph to show on the main page I create. It just wants to show the body, so the only thing I can think of to really fix this for the moment is to merge the old teaser field into the body from the backend of SQL.

Anyways, now I'm getting too in-depth. I guess for now I'm just keen on figuring out the link issue.

[opentype]

As I said, you need to edit the article template you have picked. It will have something like this in it.

<section class='ipsType_normal ipsType_richText ipsType_break ipsSpacer_bottom' data-ipsTruncate data-ipsTruncate-size='7 lines' data-ipsTruncate-type='remove'>
					{$record->truncated()|raw}
				</section>

That’s what’s pulling the unstyled article text and limiting it to a 7 lines preview in this case. You would have to replace that with your teaser field. But I don’t what that is called in your installation.   

[Cameron Son]

Hey, thanks again @opentype!

Curious to know...is there a reason I should not be doing this? You mentioned it was intentionally pulled. I want to make sure I'm not leaving potential to muck something else up in the process.

[opentype]

I always suggest to start with a copy of the template you are editing and then you can always undo your changes. 

The problem with stripped fields is that the editor fields are now full HTML and you can’t just cut that off at a certain point. That might break the whole page. But if you have your own teaser fields (from the old installation) which can be shown in full length without cutting it off, then you won’t have that problem and you can replace the auto-generated truncated body text with your teaser field. 

[Cameron Son]

All is a bit more clear now, @opentype. Thank you for your help in this thread!

[Justin Bowman]

@opentype how would i go about changing the article text to include BBCode?

[Justin Bowman]

If you dont mind having the full article show up you can do the following

 

				<section class='ipsType_normal ipsType_richText ipsType_break ipsSpacer_bottom'>
					{$record->_content|raw}
				</section>

instead of
 

				<section class='ipsType_normal ipsType_richText ipsType_break ipsSpacer_bottom' data-ipsTruncate data-ipsTruncate-size='7 lines' data-ipsTruncate-type='remove'>
					{$record->truncated()|raw}
				</section>