06:25:12 <arnekolja> i added an image to page tca and try to read it in a <v:page.menu /> viewhelper when iterating over my pages, like {mainLevel.tx_mytheme_sectionbuttonimage}. any idea how to get the image reference? when debugging the property, it results in '1'. how do i get the reference?
06:27:35 <arnekolja> there is no mainLevel.tx_mytheme_sectionbuttonimage.originalResource or something, just the integer 1.
06:45:06 <NamelessCoder> arnekolja since you're in FAL at that point, you need v:resource.record.fal
06:45:33 <NamelessCoder> feed it the page record in your menu loop and the name of the field it should extract relations from
06:50:15 <arnekolja> NamelessCoder thanks. trying it like <v:resource.record.fal table="pages" record="{mainLevel}" field="tx_krbutheme_sectionbuttonimage" as="_image"><f:debug>{_image}</f:debug></v:resource.record.fal> but it gets me an empty array. do i have to do something special to make sure FAL works in my TCA definition?
06:51:04 <arnekolja> this is the TCA part: http://pastebin.com/6QuwXnDc
06:54:32 <NamelessCoder> assuming you have no typos and the input variables are correct, that should work
06:56:10 <arnekolja> okay. thanks, I'll try to find a mistake, if there is one :-)
07:46:32 <arnekolja> I got it. Had to rename image in ´´'config' => \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig('image',´´ to tx_krbutheme_sectionbuttonimage. misinterpreted the parameter :)
08:41:07 <Torsten85> Hey... any way to geht fludicontent_core to work with mailform?
10:05:02 <Denyerec> Ah, wasn't after technical help CLaus, I was just interested in your viewpoint on the Neos/Typo split.
10:05:08 <Denyerec> So now might not be the best time :)
10:07:07 <rosieres> namelesscoder: that's what I wanted to avoid due the fact that the database is in usage already -> TCA -> https://gist.github.com/anonymous/33b75c63a006f36e1f9f
10:10:38 <NamelessCoder> hehe no, not the best time today - but it's very fast to say. I like the split; I suggested it many years ago too. I had hoped more people would stay with TYPO3 because we can always use brainpower, but under the circumstances I think that (so far) it has been done the right way, for both communities.
10:11:22 <Denyerec> I'm not aware, yet, of who went where in terms of brain power.
10:12:19 <NamelessCoder> rosieres without MM you have to use a "group" + internaltype=db but that's sketchy at best. The right way is MM, other ways are cutting corners.
10:12:35 <Denyerec> For me, the worst case scenario is too many people leave to develop Neos, Neos doesn't work out, and Typo3 stagnates and dies too.
10:12:54 <Denyerec> As I am still not 100% how, exactly, one uses Neos :D
10:14:35 <NamelessCoder> it's too early to tell but imho, after the split, the potential failure of neos would have much less impact on TYPO3 (and of course vice versa). It's better now than before, risk-wise in that regard.
10:30:48 <Denyerec> Quite, quite. You seem to be firmly in the T3 camp.
10:31:10 <Denyerec> And I wonder if that's just due to baggage, or a feeling that one product has a better outlook.
10:31:20 <Denyerec> Or simply that Neos still isn't ready
10:34:12 <NamelessCoder> well, people come to me when they have needs that neos just can't fill
10:35:55 <Denyerec> Which I guess says a lot about where T3 sits right now ;)
10:36:11 <Denyerec> Is that an ideological gap, though, or simply that they "haven't written it yet"
10:36:57 <NamelessCoder> that's where it gets equal parts technical and political
10:37:42 <NamelessCoder> neos/flow just hasn't been as interested in lifting TYPO3 heritage since abandoning the berlin manifesto
10:38:20 <NamelessCoder> - not being forced to introduce compatibility or a clean upgrade path is where things finally forked off (and that's about the time I wrote my open letter to suggest splitting flow/neos from TYPO3)
10:39:08 <NamelessCoder> then there was the level of ambition: rather than import anything, everything was created anew (and to boot, not many third-party libraries were deemed good enough, and were re-invented)
10:40:09 <NamelessCoder> the result is that flow and neos are VERY specific products which don't really (yet) either connect with or integrate with those products that caused TYPO3's popularity in the first place
10:41:18 <NamelessCoder> to be fair, this is being solved.
10:41:40 <NamelessCoder> and for many years while that was going on, in the direction it did, people didn
10:42:04 <NamelessCoder> 't move much in TYPO3 itself - still hoping/trusting/believing that neos would be a successor
10:42:51 <NamelessCoder> even the official communication from TYPO3 up until a few months ago expressed full confidence in the successorship, although more of a spiritual successor than one that is technically a successor.
10:46:24 <Denyerec> People pinned hope on Neos and Typo3 slowed. Then Neos didn't emerge as the upgrade path to Typo3 that people thoughtit would be.
10:47:00 <Denyerec> Now that things are more officially split, though, are there still people thinking of building an upgrade route from Typo3 to Neos
10:47:00 <NamelessCoder> anyway, that's just what I think. We can't undo these decisions so the best we can do with them now is learn how and why they were wrong and act accordingly in the future - admit a mistake, learn from it and move on.
11:03:01 <Rabe69> settings.category contains a number
11:05:43 <Rabe69> of an existing category and there are several file records where this category is assigned
11:08:14 <rosieres> Rabe69: did you consult the documentation and did you understand why your debug cannot output anything?
11:10:01 <NamelessCoder> wahooo, breakthrough in Fluid wrestling match. Now rendering templates :)
11:11:44 <NamelessCoder> Denyerec the devil is in the details. On the surface both products are able to do much the same thing, but the way it is done is very different
11:12:27 <NamelessCoder> if you're a developer you can probably make both products do exactly what you want. It might take a bit more time on flow/neos because that framework will definitely punish you if you cannot follow all the rules
11:12:54 <NamelessCoder> case in point: extbase request validation. Imagine that, except even more tightly coupled to the framework ;)
11:14:14 <Rabe69> rosieres: what docu do you mean?
11:15:46 <Rabe69> If i read this page: https://fluidtypo3.org/viewhelpers/vhs/master/Resource/FileViewHelper.html
11:16:13 <Rabe69> ViewHelper to output or assign FAL sys_file records
11:29:59 <Rabe69> I thing this is a bug in vhs/Classes/ViewHelpers/Resource/AbstractResourceViewHelper.php
11:30:26 <Rabe69> Line 64 should be $res = $GLOBALS['TYPO3_DB']->exec_SELECTquery('uid_foreign', 'sys_category_record_mm', 'tablenames = \'sys_file_metadata\' AND uid_local IN (' . $sqlCategories . ')');
11:30:42 <Rabe69> and not $res = $GLOBALS['TYPO3_DB']->exec_SELECTquery('uid_foreign', 'sys_category_record_mm', 'tablenames = \'sys_file\' AND uid_local IN (' . $sqlCategories . ')');