09:27:22 <trendzetter> hi, I am setting up an environment for fluidtypo3. I downloaded 6.2.9 and the latest extensions in ter (also tried the fuildtypo3 distribution)
09:29:35 <trendzetter> The section Main is not displayed on page, only the title.
09:31:00 <cedricziel> are you talking about page templates?
09:31:04 <trendzetter> I have been wrestling with this for days. Can someone give me some hints on getting started with the new ways?
09:31:27 <trendzetter> I tried adding a example fluid content element
09:31:57 <trendzetter> 't is included in the distribution and with the provider extension if created by the builder
09:32:21 <cedricziel> once gain then: have you set up any kind of page template?
09:33:05 <trendzetter> yes, I have "Standard fluid page"
09:33:39 <cedricziel> do standard content elements work?
09:33:53 <trendzetter> and the template is empty with a provider extension in the includes
09:34:44 <trendzetter> standard content is displayed normally
09:35:20 <trendzetter> but the fluid content only has the title
09:37:43 <cedricziel> well, as i have no introspection into your code; can you please cross check with this example extension? https://github.com/FluidTYPO3/fluidtypo3org
09:37:57 <trendzetter> it could be useful to know a working combination of versions of the cms and the extensions required to get fluid working. I suspect that I have an incompatebility.
09:38:30 <trendzetter> I will download the version from github and give it a try
09:38:45 <cedricziel> ter combinations with a recent 6.2 shouldnt have problems
09:49:36 <trendzetter> I can add the content and the different types of pages in the backend. The pagelayout seems to be correct but the content elements are not displayed
09:58:35 <trendzetter> so basicly I have a plain 6.2.9 install without errors. the fluid extensions from ter and the fluidtypo3org provider extension delivering page template and content element template. for some reason the main section of the fluid content elements is missing
10:07:00 <NamelessCoder> trendzetter the fluidcontent elements included in the fluidtypo3org extension are written specifically for fluidtypo3.org and depend on typoscript as well as local folders - empty output is to be expected. You should try creating your own element or use some of the collections out there.
10:10:08 <trendzetter> I also used the example FCE saying <f:section name="Main">
10:10:08 <trendzetter> <h3>I am a content element!</h3>
10:11:20 <NamelessCoder> did you load the static typoscript belonging to the provider extension?
10:11:50 <trendzetter> I included the provider extension in includes of my root template
10:12:36 <NamelessCoder> and are you using css_styled_content or fluidcontent_core? If it's the former, you have to load that typoscript as well. If it's the latter, make sure you ran the update script via EM and that it wrote the typo3conf/AdditionalConfiguration.php file
10:12:59 <trendzetter> no css_styled_content, it is uninstalled.
10:13:40 <NamelessCoder> and if you are *completely* new at this and the site is still blank, you may want to try installing the "site" distribution from TER. It creates pages and setup for you so you eliminate potential errors in that area.
10:14:12 <NamelessCoder> there is a checklist with some 10+ items that all have to be done correctly for it to work - EXT:site automates that part.
10:14:20 <trendzetter> I started first from the site distribution
10:15:19 <trendzetter> I already have a fluid site running on 6.1 so it's not completely new but I got it from a typo3 with all extensions included (the bootstrap demo from a year ago or something)
10:15:39 <trendzetter> I cannot find the typo3conf/AdditionalConfiguration.php
10:15:50 <NamelessCoder> I assume you use fluidcontent_core since you don't use css_styled_content
10:16:41 <NamelessCoder> then either use EM to run the update script for fluidcontent_core or manually copy the file into place from Resources/Private/Configuration/AdditionalConfiguration.php
10:17:52 <NamelessCoder> that's item #8 on the list hehe
10:18:19 <trendzetter> it seems that was skipped by the site distribution because it gave some error about vhs installing multiple versions
10:18:23 <NamelessCoder> it SUCKS that it has to be copied this way but, sadly, there is no way around it. It's *extremely* legacy but required to be so
10:19:14 <NamelessCoder> ah yes... there is a dependency conflict somewhere I think... VHS is available in a too-recent version not supported by some exts (well, it is, but the metadata says no)
10:20:06 <trendzetter> I think the underlying issue might be ter having difficulties with certain combinations in dependncies
10:20:38 <trendzetter> thanks again! I am getting started now. you guys are the best