[TYPO3-ttnews] rgnewsce and tt_news 3.0

[Paul Hansen]

Krystian Szymukowicz wrote:

> Well - if the tabs are unnecessary for you you can always deactivate 
> them in EM config and then rgnewsce should work well with Pre-3.0. (but 
> frankly I haven't tested yet rgnewsce with 3.0 heavily).

Yes, that helps.

> As for integrating IRRE into tt_news - is not so simple. There are some 
> of tt_news properties that will be broken when using IRRE content 
> element concept:
> 1) forceFirstImageIsPreview
> 2) multipage single view
> 3) RSS feed
> 4) DAM records and multilanguage support must be taken into account
> 
> Right now in rgnewsce only DAM/traditional image/content reading was 
> done to make it possible to use it in LIST/LATEST views.
> So a lots of other things still needs to be done if IRRE in tt_news is 
> going to be officially supported.

Thanks Krystian. I had seen several of these referenced in Forge.

We only put the plaintext "short" into the feed rather than the entire 
content of the post. That solution isn't for everyone, we just want 
people to actually go the blog or news post (which would now be a lot 
richer with any CE in there).

I'm also comfortable with using the IRRE content for SINGLE view only, 
and the normal tt_news fields (notably Images and Subheader) for 
everything else. This is less user-friendly because there is less magic 
but it does simplify the solution needed.

IRRE also has advantages for using Insert Records (inserting the IRRE 
children) in other areas of the site, such as a newsletter. Keeping 
track of these child records is a little challenging, but 
TCAdefaults.tt_content.pid (in Page TSConfig) helps a lot.

I'll try to be productive and post what I can in terms of bug 
reports/patches for smooth compatibility with tt_news 3.0.

Krystian, Would you rather see these issues now, or only after tt_news 
3.0 has been released in the TER?

Paul