11:19:55 <pedda> http://fluidtypo3.org/documentation/templating-manual/advanced-provider-extensions/custom-flux-controllers/creating-flux-controllers.html <- is this how my PageController should look now?
11:20:18 <pedda> (and ContentController as well..)
11:21:04 <pedda> the text mentions fluidcontent i'm a bit confused as I extended \FluidTYPO3\Fluidcontent\Controller\AbstractContentController by now
13:51:08 <Denyerek> What's the best way to include an asset in conditional comments ?
13:51:23 <Denyerek> just put the conditional comment in the partial ?
13:54:26 <NamelessCoder> Denyerek, see http://fluidtypo3.org/community/irc-logs.html?tx_fluidtypo3org_content%5Bdate%5D=20140325&tx_fluidtypo3org_content%5Bcontroller%5D=Content&cHash=981056084b5a4cbb42cbb9f4ab6fb8c3#16:11:41 (topic is: TS added assets)
15:02:09 <Denyerek> If I want a user-customisable area on a site's page template, but don't want the user have to set that area up on every single page, what's the best approach ?
15:02:20 <Denyerek> Im thinking maybe a banner image, or a set of images like certification logos that appear on every page
15:02:41 <Denyerek> Should I have a content element on a hidden page I pull in with TS ?
15:02:58 <NamelessCoder> you can make a column with content sliding
15:02:58 <Denyerek> Or should I use a flex type set of page properties that somehow "slide"
15:03:09 <NamelessCoder> v:content.render has slide argument
15:03:30 <Denyerek> These images literally never, ever need to be different page-to-page
15:03:41 <NamelessCoder> or you can make a TS setting to contain a content element UID and then create the element in a sysfolder and render it by UID using v:content.render contentUids=""
15:03:45 <Denyerek> BUT the owner might need to swap one out for another (globally) when they get next year's certiifcation
15:03:56 <NamelessCoder> I would use a TS setting plus constant
15:03:59 <Denyerek> I think the latter approach should work
15:35:35 <pedda> i want to reference images from fal via flux:field.inline which table do i need to specify ?
15:35:50 <NamelessCoder> 1) you can call v:content.render anywhere as long as you include the v: namespace
15:36:06 <NamelessCoder> 2) you can render partials from your Layout
15:36:24 <Denyerek> I think I just realised what I was doing wrong re: partials.
15:36:35 <NamelessCoder> 3) if you need no layout, remove it from the template file and simply place an <f:render section="" /> to render a section from within the same template
15:36:44 <Denyerek> Now I just need to figure out how to call a TS constant in the partial, and then remember how to define the constant properly in TS ;)
15:36:48 <NamelessCoder> not having a layout is perfectly legal
15:37:02 <Denyerek> I'm still struggling to work out what belongs in a layout and what belongs in a template.
15:37:17 <Denyerek> Partials I've got cracked, I think, that's for bits that can be referenced from anywhere.
15:37:55 <NamelessCoder> the core issue is: if you have a Layout it is expected to render a *section* from your template. If you have no Layout, the template *itself* gets rendered. Which means: with layout, any f:render you use in your *template* outside of an f:section, is ignored. Without a Layout the *template* gets rendered and your f:render is encountered, which then renders the section.
15:38:40 <NamelessCoder> alternatively you can *not* use a Main section in your template and remove the Layout, but preserve the Configuration (and Preview) sections.
15:39:14 <Denyerek> So Layouts render Template sections.
15:39:48 <NamelessCoder> Template is the starting point since Template is what a controller action will render
15:40:04 <Denyerek> So you can have multiple layouts for one template ?
15:40:12 <NamelessCoder> the Layout (if any) is detected and if found, the Layout is rendered but told which Template it must use when rendering sections
15:40:20 <NamelessCoder> yes, you can have dynamic layouts
15:40:48 <NamelessCoder> you cannot specify two simultaneous Layouts (because the Template is where rendering starts) but you can change the name of the Layout it is associated with, on-the-fly
15:43:16 <NamelessCoder> Layouts allow a lot of output to be shared by multiple controller actions in a way that does not require manually using f:render in all places
15:43:48 <NamelessCoder> while it is true that it makes less sense in an FCE/page context, it makes a lot of sense for standard controllers - which fluidcontent and fluidpages still are, underneath
16:00:26 <Denyerek> And I should probably put this in TS Setup not Constants ?
16:00:35 <Denyerek> TBH, I've never been very clear on the difference there for this kind of thing :/
16:01:00 <NamelessCoder> the constant is there to allow easier editing of the value using the constant editor, but the value must still be inserted as TS setup that references this value
16:01:17 <NamelessCoder> internally TYPO3 does a str_replace on the complete TS to replace all constants references inside {$constant.name}
16:08:27 <randomresult> hehe that was a nice description : trying to teach a retard t tie his laces. that is what i feel like all the time when talking to @NamelessCoder @cedricziel @danilobuerger @bjo3rn or reading the docs
16:08:40 <NamelessCoder> there is much less flinging of poop going on here
16:08:48 * randomresult is trying to tie his laces
20:08:58 <WouterWolters> Hi all, just trying to get a working site with FLUIDTYPO3, but Iḿ stuck with: Arguments useShortcutData, useShortcutTarget and useShortcutUid are mutually exclusive. Please use only one at a time.
21:49:20 <ndee> a little bit O/T but do you guys have a server, where 3-4 devs are accessing the server? how do you handle permissions on such a server?