00:08:00 * Denyerek wonders if NamelessCoder's fingers have cooled down any...
00:08:42 <Denyerek> soee, I fgured out the inline syntax for the if statement, so that's pretty now
00:12:19 <Guest|45675> @Denyerek Are you using TYPO3 6.2?
00:13:23 <Guest|45675> I have a new install of 6.2 and it seems that all I get are errors and I haven't even done anything yet!!!
00:14:34 <Guest|45675> #1237823695: Argument "table" was not registered. (More information)
00:14:34 <Guest|45675> TYPO3\CMS\Fluid\Core\Parser\Exception thrown in file
00:14:34 <Guest|45675> #1237823695 Argument "table" was not registered.
00:15:28 <Guest|45675> Hmmm guess I should use copy/paste carefully here... sorry about the extra lines there.
00:17:33 <Guest|45675> That's a frontend error. In TYPO3 6.2, I have installed... flux, vhs, fluidpages, fluidcontent, fluidpages_bootstrap, fluidcontent_bootstrap.
00:27:14 <Denyerek> You not seen me for the last 12 hours? :D
00:27:30 <Denyerek> It's starting to fall into place, but there are many unknowns and I feel a twinge of terror when NamelessCoder and cedricziel are not online :)
00:41:18 <Outdoorsman> Hi @Denyerek I'm now nicknamed.
00:41:32 <Denyerek> __clone method called on non-object in /home/denyerec/src/typo3-6.2/typo3/sysext/fluid/Classes/View/AbstractTemplateView.php on line 209
00:42:51 <NamelessCoder> hi Outdoorsman - all the way from the USA. Welcome :)
00:44:45 <Outdoorsman> Thank you @NamelessCoder... I talked to you a few days ago. I'm the guy that said I had about 50 sites. I'm a little further than before but I must just be doing something wrong?
00:45:22 <NamelessCoder> I think your error comes from fluidcontent_bootstrap or fluidpages_bootstrap
00:45:38 <Outdoorsman> For starters... Builder extension isn't compatible with 6.2 yet so haven't made a provider extension like you mentioned.
00:46:23 <NamelessCoder> are you comfortable with git?
00:46:25 <Outdoorsman> I belive you are right, but I don't know why I would be getting errors when I haven't even done anything. I installed a blank template in the root element.
00:46:59 <Outdoorsman> I don't use git, but as long as I can just use it to grab code I'm willing to do that.
00:47:15 <NamelessCoder> this is what we'll need it for, nothing else ;)
00:47:17 <Outdoorsman> I'm just not currently able to use it for versioning.
00:47:51 <NamelessCoder> start by uninstalling and removing folders for extensions builder, fluidcontent_bootstrap and fluidpages_bootstrap
00:47:59 <NamelessCoder> then, from document root:
00:48:28 <NamelessCoder> git clone https://github.com/FluidTYPO3/builder.git typo3conf/ext/builder --single-branch --branch development
00:48:41 <NamelessCoder> git clone https://github.com/FluidTYPO3/builder.git typo3conf/ext/fluidcontent_bootstrap --single-branch --branch development
00:48:48 <NamelessCoder> git clone https://github.com/FluidTYPO3/builder.git typo3conf/ext/fluidpages_bootstrap --single-branch --branch development
00:49:04 <NamelessCoder> then, install the extensions through extension manager
00:49:21 <NamelessCoder> reload (browser refresh) the backend and you should see the "builder" module
00:50:05 <NamelessCoder> now, before you do more, make sure that 1) you include the static TS for fluidpages_bootstrap and fluidcontent_bootstrap and 2) clear the system cache
00:51:03 <NamelessCoder> you *may* need to manually delete all files in typo3temp, and if all else fails, you may need to manually clear all "cache_*" and "cf_*" tables in your database (often necessary when you upgrade)
00:52:00 <NamelessCoder> at this point you should be able to 1) select a page template when editing pages and 2) add bootstrap-type content elements
00:52:37 <Outdoorsman> I read over and over your comments the other day. I assumed that to include that static templates I would do that in the typical TS template on in the root page. But then I started looking at how you have things laid out in the specialty extension and am second guessing that. (By the way, I don't have specialty installed on this site... just my other test site)
00:53:05 <Outdoorsman> So what method are you recommending?
00:53:07 <NamelessCoder> the specialty extension teaches a few procedures that differ from standard practice
00:53:23 <NamelessCoder> I recommend first getting comfortable with the standard practice, which is to include the static TS into root TS template
00:53:35 <Outdoorsman> Whew... I was a little confused where to do that.
00:53:53 <NamelessCoder> btw, EXT:specialty is something the bootstrap_package delivers and is not officially fluidtypo3 as such - it's damn close, though.
00:53:59 <Outdoorsman> That does make me a bit more comfortable for the time being.
00:54:11 <NamelessCoder> yep, easier to manage if you have typo3 experience ;)
00:54:13 <Outdoorsman> Sounds like I could transition once I get the feel of things
00:54:38 <NamelessCoder> the specialty approach is ideal for versioning extensions - but get the other way under your skin first, then there's room to learn the tricks
00:55:09 <NamelessCoder> and you'll know exactly what you need to replicate, configuration-wise, using other include strategies ;)
00:55:12 <Outdoorsman> Thanks for differentiating that.
00:56:26 <Outdoorsman> So just to be clear about what fliudpages_bootstrap is... doesn't it include a page template ready to go right out of the box, meaning I could start adding content to pages once I select it as the template for the root and subpages?
00:56:43 <NamelessCoder> that is exactly what it does
00:57:11 <NamelessCoder> I have an alternative suggestion which it would make sense to use as a start since you're in the very beginning now
00:57:28 <NamelessCoder> do not install fluidpages_bootstrap and fluidcontent_bootstrap - instead, install this little piece:
00:57:53 <NamelessCoder> git clone https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme.git typo3conf/ext/fluidbootstraptheme --single-branch --branch development
00:58:01 <Outdoorsman> Good... that's what I wanted. Once I have a working version of that, then I can at least look into it a bit. Would this be the extension to modify to fit my own HTML template that needs to be bootstrap compatible then or do I really need to start from scratch for a custom HTML template?
00:58:31 <NamelessCoder> this extension contains both page and content templates, is designed as a base extension to build sites on bootstrap - and will be the successor to the two extensions mentioned
00:58:40 <Denyerek> Claus - any pointers on the breadCrumb viewhelper choking ?
00:59:49 <NamelessCoder> Outdoorsman here's where it gets a bit interesting - there are so many structure strategies I would like to recommend but I'm afraid to overload you
01:00:08 <NamelessCoder> but I can hint about what is actually possible with fluidcontent and fluidpages
01:00:34 <NamelessCoder> - you can use whichever standard shipped templates you want, and override those you want to customise, without modifying the original files in any way
01:01:09 <NamelessCoder> - you can package your overridden templates in the same extension as your custom templates: that way you provide both additional content elements and overrides for existing ones
01:01:24 <Outdoorsman> Well I like doing things right and am familiar with large direcotory structures since I also use Magento. Nevertheless, when things become too time consuming to create quickly it defeats the purpose sometimes if you know what I mean.
01:01:24 <NamelessCoder> - both of these things are equally possible with page templates
01:01:37 <NamelessCoder> I know exactly what you mean
01:01:53 <NamelessCoder> this is a perfect example of choosing the right (sufficiently basic) tool for the job
01:02:47 <NamelessCoder> the hints above point to the ideal way of both creating your own custom elements and overriding some of the base ones - it even teaches you a strategy that can be used for all extbase extensions like EXT:news
01:03:33 <Outdoorsman> The overriding method sounds like it works quite similar to how Magento works too, so I'm familiar with that strategy.
01:03:38 <NamelessCoder> the name of the override-templates-feature is "overlays" and you can read a bit more about that here: https://github.com/FluidTYPO3/view/blob/master/README.md#template-path-overlays
01:04:04 <NamelessCoder> perfect - yes, it would be much like existing, bigger, convention-based template structures
01:04:09 <Denyerek> The overrides thing sounds awesome.
01:04:24 <Denyerek> I think randomresult_afk was on about it the other day
01:04:29 <Denyerek> have a base set of reusable stuff
01:04:35 <Denyerek> and then overlay the ones you need to modify
01:04:44 <NamelessCoder> both fluidcontent and fluidpages support "overlays" natively, no need to install EXT:view. Other extensions like EXT:news can be "overlayed" when EXT:view is installed. The TS setup approach is the same for all.
01:05:00 <NamelessCoder> I could go on all night...
01:05:21 <NamelessCoder> if you decide to jump even further you can abandon css_styled_content and switch to fluidcontent_core (fcc)
01:05:46 <NamelessCoder> this extension allows you to use all the things I just described - as standard typo3 content
01:06:14 <NamelessCoder> it switches away from TS objects to render different content, to using fluid templates which are formatted like fluidcontent templates
01:06:23 <Outdoorsman> Yes, I got all sweaty when I thought about dropping css_styled_content because then I'm clearly All In 100% to this new system which I don't even know yet :)
01:06:44 <NamelessCoder> still beta - but I use it on fluidtypo3.org and it is being used in production in a few other places already.
01:06:57 <NamelessCoder> takes a bit of bravery to be an early adopter ;)
01:07:48 <NamelessCoder> the good thing about fluidcontent_core is it is 100% identical to fluidcontent elements - learn one and you'll already know how the other works
01:07:51 <Outdoorsman> From the sound of it. It's something that I could adopt at a later date as well and it wouldn't necessarily be a big deal as it's mostly getting rid of inline styles and more appropriately wrapped content, is that right?
01:08:05 <Denyerek> yeah current csc doesn't have much baggage anymore.
01:08:18 <NamelessCoder> definitely - you can go the fcc way later, but it would be a fair bit of work to migrate csc customisations to fcc templates
01:08:20 <Denyerek> I'm building my current site on it, next one will probably be fluidcontent only
01:09:04 <NamelessCoder> fluidcontent_core is our way to get all the control we want and use fluid - so we're completely going the other way from csc
01:09:13 <Outdoorsman> ...hmmm really? So are the differences even apparent down to the template level?
01:10:00 <NamelessCoder> you install the exts slightly differently, but after that you make the templates in exactly the same ways
01:10:04 <Outdoorsman> ohhhhhh. So what's the difference then on my end?
01:10:40 <NamelessCoder> the point of fcc: you can use the core's CTypes (text, image, uploads, bullets, etc) as if they were fluidcontent elements
01:12:12 <NamelessCoder> instead of the csc "stdWrap" you have a "Layout", instead of each tt_content.xyz definition TS array you have a Fluid template, instead of a flexform or TCA to make fields you have Flux fields - and you get support for adding nested content elements in any content type (just an example: Image element can use other content elements as captions)
01:12:22 <NamelessCoder> (I could go ooooon and on)
01:12:29 <Outdoorsman> So if I populate my site with standard content elements, I would have to redo them all when I install fluidcontent_core to utilize the identical content elements that are fluid driven.
01:13:05 <NamelessCoder> 1) content styled using CSC is not CSS-compatible with FCC. Scopes and selectors must be changed.
01:13:26 <NamelessCoder> 2) TS-defined modiffications of stdWrap, header rendering etc. is not compatible and must be recreated as Fluid
01:13:39 <Outdoorsman> Ok... you're just blowing my mind here. That's amazing!
01:13:42 <NamelessCoder> 3) Fields which we use, are limited compared to ones CSC uses
01:14:15 <NamelessCoder> my biggest problem is I haven't enough time to explain this in writing as proper docs... there is SO MUCH which should be explained
01:14:16 <Outdoorsman> I have no attachment to CSC styling.
01:15:35 <Denyerek> Claus before you run out of steam...
01:15:45 <NamelessCoder> but now I hope I've given you some info to go on to get the site running, CSC or FCC regardless - and that you've some courage to try these ;)
01:16:13 <NamelessCoder> if you haven't already done so, save the CLI commands I gave earlier
01:16:47 <NamelessCoder> if you ever encounter a bug, it is always worth while to try the git versions instead of the TER ones - they get the bugfixes slightly quicker
01:17:04 <Outdoorsman> I'm doing the CLI stuff now. I will be back Monday possibly. Where can I PayPal you some thanks?
01:37:47 <NamelessCoder> btw regarding 1a from earlier... <v:page.link pageUid="{page.pid}" /> - variant viewhelper, automatically retrieves the title as link text.
01:38:16 <NamelessCoder> add tag content to manually set link text like in the fluid-native page link viewhelper
01:38:59 <NamelessCoder> ooh and btw Denyerek congratulations! You've now used ~10% of the VHS viewhelpers ^^
01:39:57 <Denyerek> Do I get a Typo3 Achievement ?
01:45:06 <Denyerek> Fatal error: __clone method called on non-object in /home/denyerec/src/typo3-6.2/typo3/sysext/fluid/Classes/View/AbstractTemplateView.php on line 209
01:49:04 <NamelessCoder> so.... Template has section Main, uses f:layout - Layout has f:render section="Main" and inside section Main, is the inline call to f:render?
01:50:09 <Outdoorsman> @NamelessCoder I ran this successfully, git clone https://github.com/FluidTYPO3/fluidpages_bootstrap.git typo3conf/ext/fluidpages_bootstrap && cd typo3conf/ext/fluidpages_bootstrap && git checkout development && cd ../../..
01:50:11 <Outdoorsman> but when I try to install it I get the error, "Your TYPO3 version is higher than allowed. You can use TYPO3 versions 4.6 - 6.1.99"
01:50:21 <Denyerek> <f:render section="Main"/> <-- that gets called from my Layout
01:50:32 <NamelessCoder> aah yes Outdoorsman - those are still outdated
01:50:57 <NamelessCoder> repeat for fluidpages_bootstrap
01:51:27 <Outdoorsman> So was it just a bookkeeping thing that you haven't upated the version requirements?
01:51:37 <NamelessCoder> we are a bit behind getting these out (not least because a successor ext is being made)
01:52:04 <NamelessCoder> the "development" label definitely fits ;)
01:52:12 <Denyerek> ok great, the breadcrumb was down to typo3temp caching
01:52:16 <Denyerek> I will have to remember to keep on top of that.
01:52:18 <NamelessCoder> should be a few days then new TER versions will come out with proper deps
01:52:46 <Denyerek> <v:page.link pageUid="{page.pid}" /> <-- that is not a PARENT link, it's a link to the current page
01:52:48 <Outdoorsman> Ahh... that makes sense. I'm just hoping to actively be using these so hope there's going to be a stable version of things that all work together soon.
01:52:54 <NamelessCoder> Denyerek this is the exception.... when class name CASE is the error, cache won't detect when you fix the case problem
01:53:16 <NamelessCoder> stable versions coming any day soon - count on it :)
01:53:55 <Denyerek> Outdoorsman, that's a pretty solid guarantee, Claus has done a monster amount of work on this and doesn't appear to be slowing down.
01:56:04 <NamelessCoder> I would however try replacing fluidcontent_bootstrap and fluidpages_bootstrap with the fluidbootstraptheme extension - that would be more future proof, although the ext is going to be changing a bit the next few days before finally hitting TER
01:57:17 <NamelessCoder> oh well... may as well create two TER releases :)
01:58:07 <Outdoorsman> This is the happiest day of my life! I'm seeing things now showing up in the Page Layouts tab. I've been work on trying to get things working for several days and apparently it's because the extension didn't work and had to come from the dev branch. I just assumed it my newbieness.
02:02:21 <Denyerek> same, creates a link to the current page
02:02:35 <NamelessCoder> {page -> f:debug()} showing a proper page record?
02:02:39 <Outdoorsman> Ya that would be good for the others out there excited to use 6.2 who waited until the stable release like me. I will be in offline for the next day or two, but will be back at this soon. Have a great weekend everyone :)
02:02:54 <NamelessCoder> thanks - great weekend to you too :)
08:59:21 <Denyerek> You'll be relieved to hear thus morning I am not working on Typo, but retouching Poledancers again.
08:59:32 <Denyerek> You all get to take the weekend off ;)
16:03:38 <BenjaminR> In place of all satisfied users of FluidPoweredT3 - congratulations to the NamelessCoder - keep up the great work! https://www.youtube.com/watch?v=bJ7B9x027uc