11:45:17 <nimius|thephpjo> i just hit the error in this ticket: https://github.com/FluidTYPO3/flux/issues/533 – however, dumb me deleted those tables (renamed and deleted). How do i recreate them?
11:51:15 <xaver> nimius|thephpjo: copy the ext_tables.sql and execute or update to dev version of flux
11:58:35 <cedricziel> f:translate solely deals with xml/xliff resources for translation
11:59:13 <cedricziel> you therefore need an entry in one of your translation files (which also nicely decouples that from the view and reduces magic strings)
11:59:31 <limboo> i think with arguments="" i can replace some strings from the translation files
12:02:16 <cedricziel> is suspect you need no arguments at all
12:02:28 <cedricziel> just leave them and prepare your xml/xliff files
12:41:53 <floxx> hi ho…i want to define metag tag robots in page configuration. my gist: https://gist.github.com/floxx/fcf0b4aaaccef8a99cdd
12:42:27 <floxx> by saving the page, there comes "Invalid value ("index")" in the select box, in frontend there is only meta tag robots=index
12:43:08 <floxx> it seems the commas are the problem
12:43:15 <floxx> what would be the right syntax here?
12:54:24 <Harpagophyt> Hello! is there a chance to generate the locallang file automtical with the translation keys?
12:57:41 <limboo> cedricziel sorry i was out for lunch
12:58:18 <limboo> with the language files everything works well, but i'd like to put the "translation" directly in the template, because there are only a few words
12:58:29 <limboo> so i think it easier to manage then in the translation-files
15:46:34 <MatthiasKrappitz> But nothing happens. Template is used, Content Element is displayed, but Controller Action gets never executed.
15:50:24 <MatthiasKrappitz> I'm also confused as the documentation at http://fluidtypo3.org/documentation/templating-manual/advanced-provider-extensions/custom-flux-controllers/creating-flux-controllers.html says it should be called AbstractFluxController, but in EXT:fluidcontent_bootstrap it is AbstractContentController.
15:50:56 <MatthiasKrappitz> And the documentation does not mention a AbstractContentController at all.
15:53:31 <MatthiasKrappitz> got it working now by not using namespaces: class Tx_Raikeelements_Controller_ContentController extends Tx_Fluidcontent_Controller_AbstractContentController {
16:21:00 <TYPO3ua> not working this ...{f:translate(key: 'item.label', extensionName: 'tt')} at <flux:field.input name="item" label="{f:translate(key: 'item.label', extensionName: 'tt')}"/>
17:27:59 <Guest|62313> Hi everybody, is there a viewhelper for repsonsive images? Cause i dont use CSC... is there a alternative usage?
17:30:05 <bjo3rn> hi Guest|62313 there's no special viewhelper (what would you assume it to do btw?) but it's easy to create a custom content element for that
17:30:23 <NamelessCoder> I can only say that if it worked before, it's because it relied on a bug in the Filter class (by not providing the actual expected format of a reference id)
17:32:17 <NamelessCoder> if the format of a reference id is supposed to be vaid as a single integer it shold be adapted to be so in the code explicitly. But in such a case any use of an unexpected integer (including zero) would thrown an exception rather than ignore the value when rendering it and zero it out when saving it.
17:36:11 <Guest|62313> but how i should create that? The size of image has to resize automatically like the new responsive function of typo 6.2
17:37:04 <bjo3rn> well, I don't know the functionality in 6.2. some time ago I created a content element using picturefill.js
17:38:02 <bjo3rn> what would you expect from a responsive image viewhelper to do?
17:40:14 <artisticMink> Hello, is there a way (or lets say workaround) for accessing flux field values by realurl to do some mapping? Similiar to realurls lookuptable.
18:53:27 <Guest|62313> bjoern, with the new typo 6.2 version comes the function "repsonsive image" which resizes the images for mobile, tablets etc. not with css
19:03:01 <GRIMMCREATIVE> What is TYPO3 doing since 6.2 - it creates multiple images with different sizes. so what you can do is just the same with fluid inside your fluidcontent element. i use the data attribute technique like in the introduction package of TYPO3 6.2
20:30:16 <Outdoorsman> Wow... spent 4 hours trying to upgrade an older TYPO3 site. Apparently there's still a ways to before we have broad extension support of 6.2.x.
20:31:48 <xaver> Outdoorsman: what exts - best way to update is to get rid of old stuff