01:12:16 <Outdoorsman> I created a provider extension that seems to be correctly overlaying fluidbootstraptheme. However, for some reason when going to add a new content element, I don't see the additional bootstrap content elements that come with fluidbootstraptheme. What am I missing?
01:13:26 <Outdoorsman> I am using the view extension to help with overlays.
01:13:35 <NamelessCoder> did you set plugin.tx_fluidbootstraptheme.view.overlays.YOURKEY.templateRootPath (and not for example plugin.tx_fluidbootstraptheme.view.templateRootPath)
01:13:47 <NamelessCoder> EXT:view is not required for overlays of Flux-based features
01:14:02 <NamelessCoder> it's purely for cases when you need to overlay views of a third-party, non-Flux plugin
01:14:37 <NamelessCoder> exactly like news - the primary use case
01:14:53 <Outdoorsman> I used it on the last project for news.
01:15:26 <NamelessCoder> it doesn't hurt that it's installed, but you may not need it (and Extbase *is* faster without it)
01:15:44 <NamelessCoder> like a few miliseconds faster
01:16:31 <Outdoorsman> There's an extension called ftbcustomiser that I used to customize fluidbootstraptheme last time. This time I am trying to do the whole thing using my own provider extension so I'm wondering if there's some steps I'm missing since I'm still new to the process.
01:16:41 <NamelessCoder> btw Charles workspaces support is almost finished and we need help testing it
01:17:09 <NamelessCoder> I'm not sure how to operate that extension, sorry
01:17:43 <Outdoorsman> !!! You have gone above and beyond again! I'm still waiting on the check you're getting funded from. As soon as it gets here you'll have what I mentioned coming your way.
01:19:14 <NamelessCoder> essentially it's all contained in https://github.com/FluidTYPO3/fluidpages/pull/185 at this point
01:19:43 <Outdoorsman> If I just update to lastest dev I'll get it too right?
01:19:44 <NamelessCoder> but don't get excited too soon, it's a nasty area full of edge cases and I've only touched the basic stuff
01:20:15 <Outdoorsman> Firsthand experience now... you mentioned there was a lot of unknown.
01:20:28 <NamelessCoder> no, to get this one you need to "git pull https://github.com/NamelessCoder/fluidpages.git --single-branch workspaceservice" inside fluidpages
12:00:37 <featdd> then I dont know why it renders the div :-/
12:01:55 <NamelessCoder> featdd 1) template has no layout, 2) div is in Layout file or 3) you're rendering a partial that contains no sections. To fix: 1) add layout, 2) remove div with xmlns, 3) add a section then render that section when rendering the partial
12:07:52 <glucka> hi, slide collect is now always on by v:render? i cant find any information
12:08:28 <glucka> i look in the source and i think it is
12:08:40 <NamelessCoder> use slide - slideCollect and it were identical
12:10:44 <glucka> i think simple slide should not collecting
12:10:54 <featdd> NamelessCoder: it wont work in one action but in an other
12:11:32 <NamelessCoder> featdd there are only the options I noted above - assuming you did not intentionally place your div with xmlns inside an f:section
12:12:52 <featdd> I tried by give the partial an extra layout so it works in the show action but in an other action it just renders the empty div with the namespaces
12:13:14 <NamelessCoder> partials cannot have layouts
12:13:41 <NamelessCoder> you should be adding an f:section in your partial and from all places you use f:render to render that partial, additionally add a section="NameOfThatSection"
12:14:24 <NamelessCoder> without section: partial is rendered in a way that all content NOT inside an f:section gets rendered and everything inside f:section is removed
12:14:37 <NamelessCoder> with section: renders everything inside the section and nothing outside
12:17:54 <featdd> NamelessCoder: works! thank you :-)
12:37:03 <glucka> with the typoscript slide function can i overwrite the sliding mechanism and show only the current element without collected elements
12:37:42 <glucka> it is currently possible with v:render?
13:11:56 <masimo> Is there some tutorial on building simple site with fluid typo3 ? for example - one layout with 3 menu buttons and one custom element ?
13:38:37 <batjony> hi Feders :) i am following the documentation http://fluidtypo3.org/documentation/templating-manual/templating/provider-extension/generating-extensions.html
13:38:59 <batjony> i have created a provider extension with the builder, which has some default "Hello wordls" templates
13:39:35 <batjony> but when I browse the frontend - i do not see any "hello world"
13:45:49 <batjony> as i see, the builder has created two templates: Private/Templates/Page/MyPageTemplate.html and Private/Templates/Content/MyContentTemplate.html with some hello world
13:46:04 <batjony> are they loaded automatically, or I should do something ?
13:46:14 <mrboe> yes and now you need some layout and some partials
13:46:49 <mrboe> if you want to get into that stuff you could have a look at https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme
13:51:12 <mrboe> here the layout of that pagetemplate https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Layouts/FrontPage.html
13:55:21 <batjony> i want just to create a simple site with 3 buttons :) i do not see complete info..... for example I have in the admin - 3 pages - Home, About us, Contact How can I render them in the frontend like menu.. and how can I show the content from the backend ..
14:05:51 <batjony> NamelessCoder: I see some example https://github.com/FluidTYPO3/fluidtypo3 when do you plan to finish it ?
14:09:49 <mrboe> hey batjony, i dont understand why you dont have a look into fluidboostraptheme. this is build to help people to get into. you can finde pages examples, menus, and contentelements in there.
14:47:39 <batjony> mrboe: when I installed the main fluid extensions, the button for adding content elements in a page - disappeared http://postimg.org/image/x3z8o2kjr/
14:48:57 <batjony> it seems that the fluid extensions breaked the backend layout
15:43:22 <ltrebing> Installed EXT:fluidpages (latest development commit from Github), added Templates/Page/Standard.html and Layout/Page/Front.html to my provider extension, did the database compare thing, deleted typo3temp, cleared all caches, but still nothing new in the page properties. Which step have I omitted?
15:43:23 <Denyerec> batjony - via the toolbar or the install tool ?
15:55:01 <xaver> Denyerec: who? some people don't like it and thats ok - everyone is free to use what he wants (so long i'm not related to the project :P)
15:55:51 <batjony> Denyerec: you are not a fan of fedext ?
15:56:05 <Denyerec> Seems to me in searching, though, that WhataeverThisIsCalled (Fedext?) is still the easiest way to implement page layouts and FCEs tho.
16:03:26 <ltrebing> Installed EXT:fluidpages (latest development commit from Github), added Templates/Page/Standard.html and Layout/Page/Front.html to my provider extension, did the database compare thing, deleted typo3temp, cleared all caches, but still nothing new in the page properties. Which step have I omitted?
16:04:11 <mrboe> have you used "bilder" to create your ext
16:05:24 <mrboe> install that - and create your provider ext
16:05:37 <xaver> for me is bootstrap stuff more like a example and working elements, but i always crate my own extension with builder to avoid to style every bootstrap element
16:06:18 <ltrebing> Ah, no, colleague created it manually.
16:06:35 <ltrebing> Fluid content stuff and everything works though ...
16:07:47 <mrboe> @batjony have you used a fresh install of typo3
16:08:00 <batjony> no, but have cleared all possible caches
16:28:35 <Denyerec> Though I could tear the bootstrap pacakge apart to figure it out.
16:32:23 <Guest|15347> hi, is there any way to access the standard content fields like header, header_link,.. from fluid layout of a fluid content element. something like {parentRec.header} or so?
16:42:38 <ltrebing> Ah, the other thing that was missing was this: \FluidTYPO3\Flux\Core::registerProviderExtensionKey($extensionKey, 'Page');
17:10:30 <Outdoorsman> gluka That would explain why I was getting errors when I did a test with it a few days ago. Do you know why it was removed and if so, why it's still in the docs?
17:11:10 <Outdoorsman> I'm referring to slideCollect
17:12:33 <ltrebing> Next problem here: I have a basic page configuration with a one-row, one-column grid, but the Page module doesn’t show anything that looks like a grid
17:13:16 <glucka> with the latest vhs you cannot disable the collecting
17:13:33 <Outdoorsman> I figured it was just an error that needed to be reported. We should probably notify someone about the docs.
17:13:39 <glucka> by typo3 slide collecting default ist off
17:14:22 <glucka> https://github.com/FluidTYPO3/vhs/issues can you confirm?
17:19:05 <ltrebing> Ah, found the solution: I had to unset the page’s backend layout first
17:24:28 <Outdoorsman> gluka I just did a quick test. Slide does collect by default. slide="1" only collects from current page, slide="2" will prepend content up one level to the content on the current level but no further.
17:25:16 <glucka> Outdoorsman: have you the latest vhs?
17:48:39 <NamelessCoder> solution: remove the page layout selector fields by way of access lists for user groups not allowed to make that decision ;)
17:48:39 <ltrebing> glucka: basically when you’re transitioning from backend_layout to fluidpages you must unset backend_layout EVERYWHERE or you’ll get empty pages in the backend for no obvious reason
17:49:33 <Outdoorsman> glucka and ltrebing, Are you talking about the native Backend Layout available in the list tool? I currently am using the native Backend Layout to with fluidpages to arrange my content into logical rows/columns.
17:49:50 <ltrebing> Outdoorsman: yes, does that work for you?
17:56:30 <ltrebing> NamelessCoder: so in my case I should see the normal old-school backend layout view and the fact that I see nothing means that I broke it otherwise?
17:58:34 <NamelessCoder> If field pages.be_layout either set to 1) none, to 2) empty string or 3) a be_layout record that contains no grid definition, and if no pageTSconfig exists which defines a grid, and if you don't use the gridelements page grid provider, and if your page rootline contains a template selection which contains a grid, THEN you should see fluidpages' grid.
18:21:57 <ltrebing> To me it looks like this: EXT:fluidpages assumes that the core is creating the grid view and therefore doesn’t create its own, but the core actually doesn’t create it either because something about EXT:fluidpages confuses it.
18:22:09 <ltrebing> Still trying to figure out what exactly “something” is ...
18:22:16 <Outdoorsman> xaver I've just been using Backend Layout to arrange the backend grid. But just now I started playing with flux and see that you can arrange things that same way using flux... http://fluidtypo3.org/viewhelpers/flux/master/Grid/ColumnViewHelper.html
18:25:05 <Outdoorsman> Oh good I'm onto something then. Not a BIG deal, but it is nice to be able to do it quickly and visually like Backend Layout allows you to do though. Too bad we can't tap that somehow.
18:27:15 <ltrebing> xaver: Yes, unless backend_layout is set.
18:27:45 <xaver> (never tried backend_layout and fluidpages)
18:28:33 <ltrebing> xaver: Because, as NamelessCoder explained, EXT:fluidpages is so non-aggressive that it doesn’t render its own grid when it believes that the core already renders one.
18:30:46 <ltrebing> xaver: I don’t intend to use both together (although I still wonder how Outdoorsman managed to do that).
18:31:02 <ltrebing> Outdoorsman: which versions of Typo3 and EXT:fluidpages are you using?
18:32:26 <Outdoorsman> ltrebing, when I read what NamelessCoder wrote, it makes sense why it works... it's a order of precedence thing.
18:32:38 <Outdoorsman> ...not one versus the other.
18:33:24 <Outdoorsman> *Roughly* similar to creating an overlay.
18:33:39 <ltrebing> But which versions are you using?
18:34:12 <Outdoorsman> latest 6.2.x, and dev versions of all flux/vhs/fluidcontent/fluidpages
18:34:32 <ltrebing> I don’t say that it makes no sense, I just say that it apparently doesn’t work as intended in some constellations.
18:36:04 <xaver> it can depend on the order in your package XML. Maybe when fluidpages checks for another layout it not rendered/present yet.
18:36:52 <ltrebing> xaver: What would not be present yet?
18:37:17 <Outdoorsman> xaver, in the WithSidebar.html, how can I figure out what the sections Preview and Main refer to? I'm still getting a handle on how these work. https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Page/WithSidebar.html#L23
18:37:38 <ltrebing> xaver: My “old” backend grid came from the core, not from anything weird like EXT:gridelements.
18:38:03 <xaver> if fluidpages looks for another BEtemplate and it isn't initialized
18:38:15 <Outdoorsman> ltrebing: Same here, mine came from core too.
18:38:59 <xaver> main is FE preview is for content elements normally - your pewview in page overview
18:40:25 <Outdoorsman> xaver: Are these global sections specified somewhere else that are universal to all templates?
18:40:57 <Outdoorsman> I've been looking and can't find a reference to those sections in any other files yet.
18:41:22 <ltrebing> Outdoorsman: The section names are always Configuration (for the backend form), Preview (for the backend preview), and Main (for frontend rendering).
18:45:10 <Outdoorsman> Ahhh ok... that makes sense. I'm now looking for documentation on that.
18:47:57 <xaver> in documention is something about templates, but e.g. preview setion is missing