IRC logs

20141110

Logs from channel #fedext on freenode - our official support channel.

IRC log range: 20141110*

20141110

  • 08:31:15 <mrboe> back from t3crr - good morning
  • 09:09:07 <bjo3rn> wow, that was a long trip home mrboe ^^
  • 09:12:43 <mrboe> sure - i was traveling with @randomresult
  • 09:12:53 <mrboe> the old swr4 junky
  • 09:12:59 <bjo3rn> ah, wheelchair. I see.
  • 09:45:08 <batjony> morning guys
  • 09:46:13 <batjony> i am wondering if its a good idea to embed a separate css file per fluid content element for better further reusability
  • 09:46:32 <batjony> my question is how can I set a separate css file for my content elements
  • 09:47:24 <batjony> and lets say if in one page i have many same content elements, how can I ensure that this css will be loaded only once time
  • 09:47:39 <batjony> some ideas ?
  • 09:51:32 <bjo3rn> batjony that's easy. use v:asset.style in your ce's template
  • 09:52:58 <bjo3rn> you can define dependencies as well and vhs will take care that all assets are only included once where required
  • 09:53:39 <batjony> nice 10x
  • 09:53:46 <batjony> i will try it
  • 09:54:12 <bjo3rn> you might be interested in reading this: https://worksonmymachine.org/blog/asset-handling-with-fluidtypo3
  • 11:37:07 <NIMIUS|johannes> wizardTab="blabla" should place my Element in the tab "blabla", shouldn't it?
  • 11:37:22 <Akii> not anymore
  • 11:37:29 <Akii> it's now "group" inside the options array
  • 11:37:42 <NIMIUS|johannes> aah, now i know why it isn't working
  • 11:37:43 <Akii> options="{group: 'blabla', ...
  • 11:37:55 <Akii> same for icon
  • 11:38:12 <NIMIUS|johannes> oh, thanks. I think I would have asked that in 10 minutes
  • 11:38:22 <Akii> :D np
  • 11:38:23 <mrboe> <flux:form id="accordion" options="{useTypoScript: 0, group: 'Bootstrap', Fluidcontent: {sorting: 300}, icon: '{f:uri.resource(path: \'Icons/bootstrap/glyphicons_113_justify.png\')}'}">
  • 11:38:39 <NIMIUS|johannes> maybe that should be noted in https://fluidtypo3.org/viewhelpers/flux/master/FormViewHelper.html
  • 12:09:49 <danilobuerger> NIMIUS|johannes good idea, maybe you can change it and submit a pull request :-)
  • 12:19:18 <Xatenev> Heya
  • 12:19:35 <Xatenev> Can I ask a question here, even if its not related to fluid? :p
  • 12:19:43 <Xatenev> its more related to standard t3 :p
  • 12:21:03 <danilobuerger> well you can, but you might not get an answer ;-)
  • 12:21:46 <Xatenev> Thats okay, worth a try though.
  • 12:21:57 <Xatenev> I am using tt_news extension, but the pagebrowser isnt showing in the list view :|
  • 12:22:10 <Xatenev> No idea how I can show it :( :p
  • 12:34:48 <NIMIUS|johannes> Am I correct to assume, that I can not include partials in my Configuration section?
  • 12:35:46 <danilobuerger> NIMIUS|johannes no you are not
  • 12:36:06 <danilobuerger> See fluidcontent_core for example
  • 12:36:28 <NIMIUS|johannes> ok - then it was just my installation being weird - happens a lot lately
  • 13:11:48 <xaver> NIMIUS|johannes: it wasn't possible in older version - Nimius is nicki or?
  • 13:23:11 <NIMIUS|johannes> xaver - NIMIUS is her company, I am Johannes
  • 14:43:22 <svenDeKa> hi everybody.
  • 14:43:48 <svenDeKa> I just have a quick question about the changes concerning rte + flux
  • 14:46:14 <svenDeKa> we upgraded flux from 7.0.0 to 7.1.2 and experienced problems with links from RTE in FCEs: e.g. file links we no longer parsed properly but stayed like <a href="url.tdl/?file:123">...
  • 14:46:25 <svenDeKa> did anybody else experience sth like that?
  • 14:46:26 <Akii> already fixed in dev
  • 14:46:34 <svenDeKa> whooohooo!
  • 14:46:42 <svenDeKa> thx
  • 14:46:45 <Akii> np
  • 15:51:08 <jmverges> hey mates, I'm trying to figure out something
  • 15:52:47 <jmverges> Imagine that I would like to work with a product as a normal page where I can add several CE's to describe it. On the other hand, I need to manage some data with Extbase like the stock of the products. Which approach should I use?
  • 15:59:35 <danilobuerger> Akii when did we fix that?
  • 15:59:49 <Akii> I was told this is fixed in the dev branch
  • 16:00:39 <danilobuerger> ah yes, i did change the rte defaults after 7.1.2
  • 16:00:51 <danilobuerger> already forgetting my own commits
  • 16:01:01 <Akii> :)
  • 16:01:44 <danilobuerger> svenDeKa did you try out flux development? does it fix your links in rte problem?
  • 17:15:17 <ste101> Hello, I would need help with the PrintfViewHelper inline.
  • 17:15:47 <ste101> The example {someText -> f:format.printf(arguments: {1: 'TYPO3'})} should print 'We love TYPO3'
  • 17:16:50 <ste101> Could someone please tell me how to write the part of 'someText' that I get the correct output? Thanks in advance
  • 17:19:33 <danilobuerger> ste101 someText should be a variable that contains the string "We love %s" for you to get the desired output
  • 17:22:07 <xaver> thats why i like gettext standard so much also single and multiple is supported :)
  • 17:24:30 <xaver> blog.lingohub.com/developers/2013/07/php-internationalization-with-gettext-tutorial/#An_example_of_PHP_file_that_uses_example_mo
  • 20:37:58 <jmverges> good night mates
  • 20:38:46 <jmverges> does anybody know any tutorial or extension example to work with extension builder and all ft3 approach?
  • 20:49:10 <xaver> jmverges: Oo
  • 20:49:55 <jmverges> xaver, I know. Maybe I'm merging things in my mind
  • 20:50:41 <jmverges> but, If I want to have models, etc, can I use flux for their render in Frontend or in admin?
  • 20:50:51 <jmverges> instead of use TCAs
  • 20:51:37 <xaver> no
  • 20:53:19 <jmverges> no?
  • 20:54:10 <jmverges> so If I need to work with Models, I cannot use anything from FluidTYPO3 ?
  • 20:54:41 <xaver> you can use vhs
  • 20:55:12 <jmverges> but not flux
  • 20:56:09 <jmverges> Maybe I remember wrong, was not posible wtih fedext extend the extensions created by extension builder?
  • 20:56:42 <xaver> you mean builder oder extension_builder
  • 20:56:57 <jmverges> extension_builder
  • 20:57:21 <jmverges> I think that I remember to "play" with fedext and extension builer
  • 20:57:27 <jmverges> extension_builder*
  • 20:57:45 <xaver> i think you would need to store the template to reate backend fields and store them inflexforms by default
  • 20:57:53 <xaver> NamelessCoder: did i miss something Oo
  • 20:58:18 <gbod> jmverges If you'd like to use the model annotation features from flux - extension_builder won't help you at all.
  • 20:58:39 <xaver> extbuilder provides models and all fields are present
  • 20:58:55 <NamelessCoder> yeah fluidtypo3 and extension_builder don't mix. Two very separate responsibilities.
  • 20:59:20 <gbod> xaver: but you have a explicit tca defintion files.
  • 20:59:26 <jmverges> NamelessCoder, however, was it possible with fedext first version?
  • 20:59:55 <xaver> jmverges: really old stuff
  • 21:00:38 <jmverges> I know, but was it possible? is just to know if I'm wrong or just outdated
  • 21:01:04 <xaver> using flux in extension_builder would be unlogical and could result be extending it in problems
  • 21:01:22 <NamelessCoder> in the interest of completeness and for logs, here's what you currently can and cannot do with flux and domain models.
  • 21:01:23 <xaver> vhs can do a lot
  • 21:02:00 <xaver> vhs is resomsable to create fields in fluidpages or conntentelements in backend and not in sysfolders with item lists
  • 21:02:09 <NamelessCoder> you can: 1) use flux to generate the form that TCA normally would, 2) define such a form in the following ways: annotations, PHP, Fluid, TypoScript.
  • 21:02:59 <NamelessCoder> you cannot: 1) generate the SQL, 2) make this fully automatic, 3) utilise TCA features which are not supported by flux, e.g. palettes, showitem-lists.
  • 21:03:17 <xaver> but you would need to write getter and setters - extension_builder creates both TCA and model
  • 21:03:18 <NamelessCoder> you cannot: 3) generate repositories or have these work by convention.
  • 21:04:23 <NamelessCoder> so: Flux does not generate your model or your SQL. You can choose to replace the TCA part with Flux and you have a few options for that, all of which are currently undocumented except for an early video.
  • 21:04:40 <NamelessCoder> https://vimeo.com/74294449 is that video
  • 21:05:23 <gbod> EXT:fluidshare gives some hints too.
  • 21:05:25 <NamelessCoder> EXT:flll will generate and auto-update .xlf files for your extension(s) so you can offload that task.
  • 21:06:13 <NamelessCoder> and unfortunately this is the point where hints and support runs out; teaching the use of all details of this would take more time than writing the docs would and I'm already too short on time to write those docs.
  • 21:09:40 <jmverges> thank you for the explanation
  • 21:12:48 <NamelessCoder> yw
  • 21:27:21 <ulrikkold> I cannot get flux:field.text enableRichText to work? Is there anything obvious I might have forgotten?
  • 21:27:39 <ulrikkold> that is 'enableRichText="1"' ...
  • 21:49:49 <jmverges> good night mates, tomorrow more
  • 21:49:51 <jmverges> bye
  • 22:06:34 <ulrikkold> good night, ppl