IRC logs

20160310

• 03:39:13 <danielkoch> Hello. I want to update a T3 4.7 installation (built with fed 5.0.3) to T3 6.2. I moved to all the new extensions (fluidcontent, fluidpages, flux, vhs) and made changes in templates/namespace etc. Now I have one problem which I cannot solve. Inside my content element templates I a have a interation over different types. Inside the for loop I set two variables in this way: <fed:data.var name="objectType" value="{fed:data.func(func:
• 03:39:14 <danielkoch> 'key', arguments: {0: itemSectionObject})}" />
• 03:39:15 <danielkoch> The question: How can I do this with flux?
• 03:40:21 <danielkoch> or vhs
• 06:17:29 <danielkoch> Should I provide the complet code of this content tempkate?
• 07:04:58 <NamelessCoder> for danielkoch in case he checks back: see v:variable.set to set variables - and to know the current key, use "key" argument on f:for instead of calling the "key" function
• 07:25:14 <hans_> hi there !
• 07:26:27 <hans_> i got a problem with language fallbacks ..., im using 6.2... fluidcontent,fluidcontent_core, fluidpages, flux, vhs
• 07:26:51 <hans_> are these ext overwirting fallback configs ?
• 07:27:02 <hans_> can find a solution (for weeks) :-/
• 07:28:44 <cweiske> could you actually describe your problem?
• 07:29:24 <hans_> i got a page with 5 languages de,en,pl,pt ; de is deflaut
• 07:29:47 <hans_> now i want the lang fallback not to be default, i want "en"
• 07:31:08 <hans_> i can do this without, the extents above just using the core stuff; e.g. using the element "headline"
• 07:32:00 <hans_> when i add the extentions i can managed to get the fallback; also tx_news justs displays the defalut lan as fallback
• 07:32:46 <cweiske> how did you configure the fallback language?
• 07:33:02 <hans_> config.sys_language_mode = content_fallback; 1,0
• 07:34:13 <cweiske> sorry, I can't help you here. maybe others can
• 07:35:03 <hans_> also, tried this ext: "Full language fallback for TYPO3" with no success
• 07:35:14 <hans_> cweiske: ok thx !
• 09:49:56 <Fluidiscool> Hi room, can I use <f:image> without it printing width and height at all? Or is this a core problem?
• 09:51:23 <Fluidiscool> I want to remove width="xx" and height="xx" because that's legacy HTML and not needed.
• 09:54:30 <cweiske> no, this is not "legacy html"
• 09:55:14 <cweiske> and it is needed because browsers can reserve space for the image without having loaded a single bit of the file
• 09:57:46 <Fluidiscool> do you know how I can get rid of it? I don't want the browser to reserve space and all that.
• 09:59:40 <cweiske> why?
• 09:59:48 <cweiske> no, I don't know how to do that
• 09:59:57 <cweiske> I also don't know why anyone should not want that
• 10:00:12 <NamelessCoder> use f:uri.image and build the tag yourself
• 10:01:12 <Fluidiscool> thanks, Claus, I'll try that. Thank you too, Christian, I know you mean well.
• 10:03:06 <NamelessCoder> but width/height are in fact not legacy at all - and you get invalid HTML without them
• 10:04:21 <Fluidiscool> I don't think so. alt is mandatory, width and height isn't.
• 10:06:25 <cweiske> https://www.w3.org/TR/html401/struct/objects.html#h-13.2
• 10:07:48 <Fluidiscool> cweiske, it says source and alt is required, right?
• 10:08:03 <cweiske> yes, that's what "REQUIRED" means
• 10:08:22 <Fluidiscool> I know what "required" means.
• 10:08:33 <cweiske> then all is fine
• 10:09:01 <Fluidiscool> it was fine before. width and height isn't required, even according to your source.
• 10:09:21 <cweiske> I never said that height is required
• 10:09:57 <Fluidiscool> Got ya
• 10:12:15 <Fluidiscool> btw I'm building responsive websites. that's why I want to remove width and height. I handle the looks via CSS.
• 10:12:59 <cweiske> still no reason not to include width and height
• 10:14:50 <Fluidiscool> I see no reason to do so.
• 10:16:49 <NamelessCoder> reason would be correct rendering before css is loaded
• 10:18:43 <Fluidiscool> most modern responsive frameworks don't care about that.
• 10:18:55 <Fluidiscool> (I'm using bootstrap)
• 10:19:36 <Fluidiscool> the image is going to be 1000px wide on a large screen and 240px on a mobile device.
• 10:25:12 <Fluidiscool> so which is the "correct" value?
• 10:34:53 <NamelessCoder> depends on whether or not you do mobile-first and/or have a media-independent rendering
• 10:49:03 <Fluidiscool> yes, so it seems it's not as clear cut as some folks think it is. I know it breaks my responsive rendering in the framework I'm using.
• 10:49:33 <Fluidiscool> f:uri.image does what it should. :)
• 10:53:36 <Fluidiscool> I hope cweiske didn't leave because of me... I know he means well.
• 10:54:31 <NamelessCoder> pretty sure he didn't leave because of you :)
• 11:02:04 <Fluidiscool> :) I hope so. I'm leaving now, because my problem has been solved. Thanks!