09:51:40 <NamelessCoder> benefit: each section is cached separately which means you touch much less code when rendering, compared to the switch. Worst of all f:switch isn't compilable on 6.2
09:51:45 <drlimbo> i didnt know section="Content{ContentLayout}" will work
09:52:25 <NamelessCoder> also works for Layout but there, you won't be able to use any ViewHelpers to generate the dynamic parts of the Layout name - it is parsed quite differently.
09:55:16 <drlimbo> i created a flexible element, and added some Text in the Backend in the default Title-Field
09:55:42 <drlimbo> is there a way to hide the title and render this in my FCE as a h2 or to render it default as H2 instead of H1?
09:56:07 <drlimbo> i saw the type:hidden select, but the users will always forget to set this
10:51:31 <k4mi> Hey, I have question about v:content.resources.fal and the record argument. If I for example use record="{uid: '8'}", I get a perfect result. But if I want to get all the records with pid 10 ( I thought the argument should be record="{pid: '10'}"), I dont get any results.
10:52:02 <k4mi> (bear with me if I totally miss the point, just started yesterday with typofluid extensions)
10:56:57 <NamelessCoder> k4mi the "record" argument expects the database record that has the relations to FAL objects
11:04:20 <k4mi> Ah okay,thank you. Kinda makes sense :)
11:15:06 <Guest|39353> Hey guys. Ive been here some time ago with the following problem:
11:15:10 <Guest|39353> "Once i add the enabledControls param the error appears. If i leave it empty ("{}") or dont add it it works fine (i need the delete option as the hide option actually doesnt work)"
11:15:37 <Guest|39353> just fixed it by writing a new viewhelper extending the inline viewhelper
11:15:43 <Guest|39353> setting the enabledControls in php
11:26:23 <mrboe> @NamelessCoder here are teh files
13:38:40 <Outdoorsman> I want to commit more things on Github but need some help to understand the process.
13:40:26 <Outdoorsman> If I fork for instance fluidbootstraptheme on Github and time goes by, how do I merge my fork just locally so it is caught up to the most recent changes on the upstream?
16:37:41 <Outdoorsman> jonasjo check out some code examples here. Many of them are fancy ways of doing thing but it could give you some ideas if not what you're looking for. https://fluidtypo3.org/library/code-examples.html
16:40:30 <jonasjo> i saw those, but if you are really new to flux (and fluid) the fancy part kinda is the problem ;)
16:41:40 <jonasjo> in the mean time i found https://worksonmymachine.org/blog/a-guide-to-menu-rendering-with-fluidtypo3 which kinda looks like what i was searching for :)
16:42:34 <Outdoorsman> Actually I know about that. That's what I learned my first menu from too.
16:43:49 <Outdoorsman> He did a nice job. What I didn't realize when I read that right away is that you can have an automatically generated menu with just a few lines. <v:page.menu useShortcutData="TRUE" />
16:46:14 <Outdoorsman> Notice that <v:page.menu ... /> is a self closing tag. If you use it to wrap manual rendering you get the joy of doing a lot of things manually... very manually in some cases. <v:page.menu> ... </v:page.menu>
16:51:30 <jonasjo> i guess i just play around with it a little
16:51:55 <Outdoorsman> Once you go through the pain of writing a manually, you can use and reuse the code and it's not quite as bad as I first thought. Nevertheless, I'm still convinced that there a LOT that could be done to make things easier in auto mode.
16:52:51 <Outdoorsman> I'd love to see quite a few more parameters so we don't have to write custom stuff so often just to get a simple bootstrap or foundation menu working (a common case).
16:53:27 <jonasjo> i think i know what you mean now with "manual"
18:40:13 <jonasjo> i got a question regarding v:page.menu anyone around?
18:58:20 <jonasjo> shouldn't v.page.menu render a whole menu, like with all subpages and all? (without shortcuts, ok)
19:24:02 <NamelessCoder> if you can at all make do with automatic rendering, it is preferrable. It's faster and will render all the levels you designate
19:24:31 <jonasjo> that may be the problem i had the whole time. i thought i could render the whloe pagetree with v.page.menu
19:39:28 <NamelessCoder> if you used <v:page.menu ... /> as tag, you should expect to see N levels of menus if all menus in the tree are visible in menu
19:40:05 <NamelessCoder> there's a diff between <v:page.menu>...</v:page.menu> and <v:page.menu /> if you have whitespace inside the tag
19:40:40 <jonasjo> so just to be clear here. in manual mode i just have one level. but this level should include all pages on this level, right?
19:57:34 <NamelessCoder> last chapter of https://worksonmymachine.org/blog/a-guide-to-menu-rendering-with-fluidtypo3 is relevant here.
19:58:36 <NamelessCoder> to make things clear: when you use manual rendering, expandAll and levels has no meaning (you'll be controlling that by how many times you call v:page.menu/v:page.menu.sub inside
19:59:55 <NamelessCoder> you would now expect that if you remove expandAll, levels and entryLevel parameters from the menu, that it will render all your pages below page UID zero but only the first level of pages
19:59:58 <jonasjo> but, the snippet from above, shouldn't it render ale the three pages ?
20:00:13 <NamelessCoder> I suspect it only renders the current page because of entrylevel 1
20:01:53 <NamelessCoder> yes - and to make the viewhelper absolutely aware what you want, add the as="menu"
20:02:53 <NamelessCoder> this will avoid unexpected behavior if your menu output is completely empty (e.g. no items exist). Because you have no custom HTML inside v:page.menu, the content could be detected as empty. With the "as" argument that cannot happen; it always assigns the template variable and renders tag content, never falling back to auto rendering.
20:09:27 <NamelessCoder> little bit creepy, honestly. I haven't seen the viewhelper do stuff like that unless there was something horribly wrong with the loop used in the template - and yours is fine
20:09:46 <NamelessCoder> I wish I could reproduce the problem :/
20:09:57 <NamelessCoder> hate it with things don't make sense
20:11:15 <jonasjo> yeah, mtt, too. that is why i was so unyielding :-/
20:11:23 <jonasjo> doens't want to bother at all ;9
20:11:43 <jonasjo> i'll set up a new instance and let you know
20:12:33 <NamelessCoder> thx - and if that one also fails I think it's time to send me a dump of the instance with all files included, plus some added info about your php version.
20:12:47 <jonasjo> thank you very much. a least i know i'm not crasy :-)
20:12:49 <NamelessCoder> in the faint hope that lets me reproduce it
20:13:10 <NamelessCoder> I'm hoping this was some crazy fluke - like I said, I've never, ever seen this happen and I've seen pretty much everything in Fluid ^^
20:29:17 <NamelessCoder> if you're not constrained by project dependencies, and if you have time, please try the exact same thing you're doing, but with a 7.1.0 core. Mean while I'm trying on 6.2.9 (was on 7.1.0 and 6.2.10 before)
20:35:26 <NamelessCoder> something is definitely wrong here on 6.2
20:37:50 <jonasjo> i will. but shouldn't i test on 6.2.11 ?
20:37:59 <jonasjo> i have some time on my hand :-)
20:40:46 <NamelessCoder> ah yes that was released today right?
20:44:06 <jonasjo> it renders nothing with <v:page.menu />
20:44:20 <NamelessCoder> I'm beginning to feel your pain here
20:44:45 <NamelessCoder> my attempts have no output whatsoever. Internally, the v:page.menu uses PageSelect and this class consistently returns an empty value
20:44:58 <NamelessCoder> now, to track down the reason for this crappola
20:45:06 <jonasjo> i kind of feel relieved, sorry ;)
20:45:12 <NamelessCoder> I bet it's some undoc'ed SQL change...
20:45:20 <NamelessCoder> hehe I've been here before ;)
20:47:06 <jonasjo> i'm more the FE person though ;)
20:50:51 <NamelessCoder> this is the generated query here - it returns zero results but no errors: SELECT * FROM pages WHERE
20:50:51 <NamelessCoder> pid=2 AND pages.deleted=0 AND (fe_group = '-1' OR fe_group LIKE '-1,%' OR fe_group LIKE '%,-1' OR fe_group LIKE '%,-1,%' OR fe_group = '0' OR fe_group LIKE '0,%' OR fe_group LIKE '%,0' OR fe_group LIKE '%,0,%' OR fe_group = '' OR fe_group = '0') AND pages.deleted=0 AND pages.t3ver_state<=0 AND pages.pid<>-1 AND pages.hidden=0 AND pages.starttime<=1426726140 AND (pages.endtime=0 OR pages.endtime>1426726140) AND (pages.fe_group='' OR pages.fe_group
20:50:51 <NamelessCoder> IS NULL OR pages.fe_group='0' OR FIND_IN_SET('0',pages.fe_group) OR FIND_IN_SET('-1',pages.fe_group)) AND doktype IN (1,3,4,7) AND nav_hide=0
20:54:48 <NamelessCoder> and prepare to kick my ass mentally :/
20:55:24 <NamelessCoder> EXT:site does indeed write the pages like it must, but does it save them with doktype=0 and is this doktype not recognised? I do believe so, yes.
20:55:45 <NamelessCoder> saving the pages once sets doktype=1 and the pages pop up
20:56:00 <NamelessCoder> basically, it solves everything here...
21:01:40 <NamelessCoder> give it an hour, tops, then refresh EM's list of extensions. EXT:site should pop up in 1.3.3 which creates pages with doktype=1
21:01:53 <NamelessCoder> thanks for not giving up btw ;)
21:01:58 <jonasjo> oh cool,which band? i belevie you'r into metal, right? me, too ;)
21:07:04 <NamelessCoder> sleep tight, try the site thing tomorrow and all will be well :) I'll think about putting a page menu into the templates that are created, plus some other basic stuff
21:07:06 <jonasjo> had to give it a few spins, but now i'm really diggin it
21:07:34 <NamelessCoder> learning curve can be a bit steep but once you remember, should make most of your FE work a lot faster ;)