CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Bug #5650

After installation none output

Added by Stefan Mayer over 3 years ago. Updated over 2 years ago.

Status:New Start date:2009-12-07
Priority:Must have Due date:
Assignee:Krystian Szymukowicz % Done:

0%

Category:-
Target version:-
Votes: 0

Description

I use TYPO3 4.2.9, tt_news 3.0.1 and rgnewsce 0.1.0. After installing the extension through ext manager I activated "extra tab in standard news". Next I added static template in main template. I created a new article and added a content element. After saving I cleared the TYPO3-cache. In FE I opened the new article and there is.. nothing!

Is it a bug or is it a feature? ;)
What did I wrong? Is it a bug? What information do you need to fix it?

tt_news_single.png (75.4 kB) Stefan Mayer, 2009-12-07 15:26

tt_news_ts.txt (1.5 kB) Stefan Mayer, 2009-12-07 15:26

History

Updated by Stefan Mayer over 3 years ago

I checked $markerArray before return and the content is rendered correctly. But there is still no output in FE..

Updated by Krystian Szymukowicz over 3 years ago

  • Assignee set to Krystian Szymukowicz

Well I can not reproduce this at my installation.

I've found that if you select SINGLE2 from views then it will not show the content (this is a bug for sure), but if you have selected SINGLE where your singles are then it should work.

Sorry but I have no idea what is wrong at your instillation.

Updated by Stefan Mayer over 3 years ago

I don't use SINGLE2, I use the standard SINGLE (that was the first thing I checked).. What I don't unterstand is, why the marker are not filled in FE, because the data are in the $markerArray!

I added a screenshot, where you can see that the marker is filled with data from tt_news and a content element. Between the navigation and "Kommentare" is the empty SINGLE view..

I also added my TS, maybe there is a mistake?

I hope you will find something wrong, because thats the greatest tt_news extension in the last years and I want to use it.

Updated by Krystian Szymukowicz over 3 years ago

Maybe you have other extensions which changes the tt_news markers.
My advice is to uninstall all non-standard extension except tt_news and rgnewsce and try if then it will work.

Updated by Stefan Mayer over 3 years ago

I tried it, but without success.. I tried it with another TYPO3 project and there it works fine! I don't know why, because it is the same tt_news configuration on both installations. I try to figure out what the problem is ;)

Updated by Stefan Mayer over 3 years ago

Now all works fine :)

I don't know if it was my fault or a bug.

Problem and solution:

My pagetree looks like this:

- Intro
---- Section 1
-------- ...
---- Section 2
-------- ...
---- Section 3
-------- ...
---- Section 4
-------- ...

On the Intro page I added a TS site template and wrote the configuration for this site. On the Section pages I added TS extension templates to extend the TS Site template, because I want an other style on this pages. I figured out that rgnewsce was working on Intro page, but not on a Section page. After removing the TS extension templates it was working on Section pages. Now I ticked the checkboxes to delete constants and setup in TS extension template. After this it was working!

Was is my fault or is it a bug?

Updated by Krystian Szymukowicz over 3 years ago

Well - the problem is that I can not reproduce your issue.

I have:

Home (TS record clear on setup and constants)
-- News (TS record ext - include static rgnewsce)
--- News single (TS record - some modification of plugin.tt_news)

and it works.

Try to reproduce your issue at other installation.

Updated by Stefan Mayer over 3 years ago

I will upload my TS from intro and section page later, so that you can use them! Maybe I should do a pagetree export.. We will see.

Updated by Hauke Hain almost 3 years ago

I had the same problem. While debugging the hook I stumble about this condition:

($row['type'] == 0 && $confArr['extraTabForTTContent'] == 1)

After enabling "extra tab in standard news [extraTabForTTContent]" in the extension manager it works as expected.
Is there a special reason why this is checked?

An update that fixes this or a warning in the explanation of "extra tab in standard news [extraTabForTTContent]" would be nice.

By the way: You may update the typo3 dependency version.

Also available in: Atom PDF