08:27:01 <Harpagophyt> can you help me debugging my upgrade?
08:28:29 <Harpagophyt> all settings from plugin.tx_vhs.settings.asset are twice in the frontend also the typo3temp/vhs-assets-jquery-bootstrapjs-eqheight-customjs.js?1411971931
10:11:48 <Harpagophyt> the real problem is, if the page comes from the cache or not. i disabled cache with config.no_cache
11:31:00 <geronimoo> hello! i've got a problem using the latest flux from repo - it only renders the page- and content templates with the original file names (MyPageTemplate.html and MyContentElement.html) - does anyone know something about that?
11:31:54 <geronimoo> with every different file name i get this error: „…………………../Resources/Private/Templates/Content/Fce-columns.html" is not a valid template resource URI.
11:32:54 <geronimoo> the element is displayed in the create element wizard but the configuration options wont appear, i only get a field called "The Title"
11:34:01 <geronimoo> this even happens if i copy the content from the example file into my fce-columns.html :-/
11:51:57 <geronimoooooo> allrighty my fault: flux 7.1 is not compatible to the latest versions of fluidpages and fluidcontent, I had to downgrade to fluidcontent 4.0 and fluidpages 3.0 - seems to work fine now!
13:12:15 <gbod_> Hi, will anyone of you attend the T3CON in Berlin next week?
13:15:20 <gbod_> I won't be at the Con - no ticket, but as I'm living in Berlin there might be a chance for a small drinkup/meetup.
13:40:17 <gbod_> mrboe: I know, but I don't have time for travelling at that weekend, Xaver asked about it last week too.
13:45:16 <gbod_> mrboe: Last week I did the munich fluidtypo3 presentation here at the Berlin T3 User group. It was about 3 hours long and they were really tired in the end. ;) And I even managed only the template part. Next time I'll show the controller/modell/own extension parts to them. They were really thrilled about the system.
13:45:24 <xaver> gbod_: i was at the T3UXW and won't attend the Con. I will be in essen
13:46:46 <gbod_> xaver: t3uxw was a nice event, wasn't it?
14:54:16 <alexxB> Hi, is it possible to access the "name" of a select field instead of the id only in a fluid content element? -> <flux:field.select items="{0 : 'Ohne Label', 1 : 'News & Stories',... e.g. here i would like to get the "News & Stories" to output
15:56:42 <gbod> cedricziel: Ah, yeah. And now that you're through it, you love the flux direction even more. ;)
15:57:04 <cedricziel> Last but not least: I'm really surprised how well you can handle all the things with core-only if you're developer
15:57:42 <cedricziel> it's a bit more hassle when you're not able to write small viewhelpers yourself
15:59:18 <cedricziel> geronimoooooo: this one is almost bullet proof i hope. ;)
16:00:18 <cedricziel> gbod: hm, maintaining flux is not easy at times. I'm hoping for improvements in the one or other area (in flux) after going down this road
16:01:20 <gbod> cedricziel: Is there a way to get more of the idea and the way you went?
16:06:33 <geronimoooooo> at the moment flux changes a lot, thats why its by far not bullet proof for updates atm - but its gonna be great :)
16:07:19 <cedricziel> we stabilized that and reduced those changes to the minimum geronimoooooo.
16:07:43 <cedricziel> as far as we are concerned: major versions are allowed to break stuff. you're allowed to stay behind.
16:09:34 <geronimoooooo> okay my experience on the last projects was that i had to change a lot, but you are right - the major versions changed
16:09:54 <geronimoooooo> dont get me wrong, i love flux - we are just kind of early adopters
16:10:23 <cedricziel> version upgrades are always a tradeoff of bugfixes and changes to existing stuff
16:10:45 <gbod> cedricziel: Maybe we find a way to document and present those changes and features far mor better than in commit messages. The library is a nice first start. randomresult an mrboe told something about video tuts in munich. And I got the same answers during my last two presentations of the system.
16:10:47 <cedricziel> it's like the definition of a upgrade
16:11:24 <geronimoooooo> i already thought about setting up a blog and collecting examples of my work with flux
16:11:43 <NamelessCoder> jumping in from the side here - our main problem is that TER won't allow multiple branches because in theory, we could easily have supported the same branching strategy the core uses. Sadly we're limited by that distribution method but we don't blame it - it's always been like that and an improvement is a huge task.
16:11:45 <geronimoooooo> its still a bit trick to get stuff running but its totally worth it
16:12:29 <NamelessCoder> so that leads to the use of semantic versioning in which minor versions are allowed to introduce smaller changes and major ones are allowed to sort of redo everything - but we still try to keep it to a minimum
16:13:04 <geronimoooooo> good idea - so i can release my stuff there?
16:13:09 <cedricziel> NamelessCoder: i deeply hope composer will solve that
16:13:15 <NamelessCoder> Flux 6->7 was that big a change because 4.x support was dropped and namespaces introduced - that's a HUGE change and naturally we're not the only ones affected. See for example EXT:powermail which was rewritten from scratch...
16:15:44 <rosieres> In the end everything is quite well documented and the news are worth reading. Beside that, the viewhelper reference could have 1 or 2 real life examples for usage each as it is done @ jquery. That would make stuff sometimes more clear. But in the end, the stuff is cool . . .
16:16:46 <NamelessCoder> rosieres you are absolutely right about the ViewHelper exampels - and we would be very happy to receive some of those (they're written into the class header and we also support writing standalone files that will be rendered, if you want more info just say so)
16:16:48 <geronimoooooo> i think more people should share their examples, that helps most
16:17:07 <gbod> cedricziel: Thanks, now I have something to check my own stuff against. :)
16:17:21 <NamelessCoder> See this folder: https://github.com/FluidTYPO3/vhs/tree/development/Documentation
16:17:38 <cedricziel> hehe, it's only a rough overview
16:17:41 <NamelessCoder> https://github.com/FluidTYPO3/vhs/tree/development/Documentation/Classes/ViewHelpers/Iterator/ForViewHelper is how you can write as much detail about any ViewHelper as you please
16:18:05 <rosieres> is there a gist for that? so i´ll put some if I find the time or if it is done on the fly by usage
16:18:21 <NamelessCoder> the documentation files are then detected by filename convention and rendered as part of the VH docs
16:18:44 <gbod> cedricziel: In munich we did two adhoc sessions with randomresult, xaver and mrboe. It was quite fun so we had to add a second session on sunday.
16:19:17 <rosieres> NamelessCoder: I´ll keep it in mind
16:19:27 <cedricziel> great; the videos on vimeo are 3 slots i had to present
16:19:44 <NamelessCoder> actually I should write a news item for fluidtypo3.org describing this approach
16:19:53 <NamelessCoder> because we can always use better docs!
16:20:01 <NamelessCoder> (same logic applies in flux btw)
16:20:38 <NamelessCoder> see just how delicious it looks: http://fluidtypo3.org/viewhelpers/vhs/development/Iterator/ForViewHelper.html
16:21:03 <gbod> NamelessCoder: Great Idea, maybe we can build more connections/links to the fluidbootstraptheme where lots of the stuff is used.
16:21:52 <NamelessCoder> these docs should be standalone and should match the version, that's how we can make sure they are rendered correctly
16:22:10 <NamelessCoder> but by all means, copy shit from those templates to create docs ;)
16:23:22 <rosieres> NamelessCoder: Well done. One thing is missing. Real life inline usage.
16:27:54 <cedricziel> another thing missing: a correct lexer for inline syntax in IntelliJ/PHPStorm. XML Syntax is fine, but reformating with inline syntax sucks co**s in hell
16:38:08 <mrboe> short question: when i put a FCE into a FCE i got http://snag.gy/4whgu.jpg
16:58:44 <bjo3rn> see you on the other side, randomresult
16:58:45 <cedricziel> bjo3rn: you are right-but as everywhere, taste it with some caution. it's easy and cheap to add a new CType with icon and template. there's no user experience lost
16:59:16 <gbod_> mrboe: I'd really like to be there, but atm there is no way at that weekend for me. :(
17:00:17 <bjo3rn> I think there is. I'd rather add one more fce than explain my client to use those fields.
17:16:37 <gbod_> cedricziel: Hm, and you favor this approach over the fce one. It's all those Stuff spread of five files minimum for a simple ce.
17:16:42 <cedricziel> yep, you miss the chance to configure multiple domains seperate from each other
17:16:54 <bjo3rn> I remember some Dane stating that was bad practice but I can be wrong
17:17:23 <cedricziel> gbod_: i didnt say i favoured anything over anything. every single way has it's uses.
17:17:42 <rosieres> bjo3rn -> ext_localconf.php -> \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPageTSConfig('<INCLUDE_TYPOSCRIPT: source="DIR:EXT:extExtExt/Configuration/TS_CONFIG_PAGE" extensions="ts">'); put any ts file in that path
17:17:46 <cedricziel> but what i say is: consider if you really need a fce built with an "external" mechanism
17:21:20 <NamelessCoder> when you create custom CTypes using extbase controllers and fluid templates then basically you are creating the same layer that flux+fluidcontent provides
17:23:05 <NamelessCoder> my point is: sure, it's possible to make that stuff yourself and not have any dependencies. But the way you do it almost always ends up in something along the lines of the integrations provided by flux in some degree
17:33:24 <NamelessCoder> "what if" you only had to identify a site package and could then place convention-based files in this package and use them as core content templates, core content forms (if separate from template), per-element typoscript (if required), page templates grouped by sub-directory, LLL files for each context, etc.?
17:33:42 <NamelessCoder> sort of zero-conf integration
17:34:52 <cedricziel> convention over configuration. Symfony does that for years (calling out to all the bjo3rn s)
17:34:55 <NamelessCoder> when everything becomes a matter of creating a file and being done, is there any argument to go other ways?
17:36:50 <NamelessCoder> muhaha. I own the extension key "site"
17:36:51 <cedricziel> sure Claus, and i like the idea. and it should be the ulrimate goal. but it needs to be bullet proof-at least as much as the cms itself is able to handle things
17:40:43 <rosieres> Harpagophyt it´s np must, but you do goo if you go with it did you enable debugging? -> http://docs.typo3.org/typo3cms/extensions/vhs/#debug-settings
17:40:51 <NamelessCoder> at which point the older abstractions maybe can be dropped because a consistent API exists on top, describing what should happen below - making it easier to finally switch
17:44:35 <Harpagophyt> rosieres what should debugging help? the problem is with caching
17:45:57 <rosieres> Harpagophyt: might giva clue what´s causing the doubling
17:47:09 <Harpagophyt> rosieres: you can look at http://www.pfarre-atzgersdorf.at for me it is no help ;-)