IRC logs

201507

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

IRC log range: 201507*

20150701

  • 05:37:20 <fger> hi guys ... simple question: how do i receive a GET-Parameter value inside a fluidcontent element ?
  • 05:37:39 <fger> i pass it with a f:link.page additionalParams construct from another page
  • 05:38:18 <fger> dont find it in any context - does it have to be prefixed with some tx_fluidcontent_.... or do I need a controller inside my provider extension to pass it ?
  • 05:45:25 <bjo3rn> fger that smells like a content controller although I'm not sure if the current request is available then.
  • 05:51:29 <fger> I did a ContentController in my provider extension and extended the fluidcontent-ContentController. added a myelementAction($myVariableToPass) and am now determining the right additionalParams-syntax in my link.page viewhelper
  • 05:51:33 <bjo3rn> on the other hand you can access the superglobals like $_GET in a content controller *shiver*.
  • 05:52:54 <fger> oh nice security flaw then ;) ...
  • 05:53:07 <bjo3rn> yeeehaw!
  • 05:56:12 <bjo3rn> GeneralUtility::_GET('foo') maybe?
  • 06:07:39 <fger> hmm... i added a controller to my provider extension but it isnt recognized
  • 06:09:18 <fger> looked into the fluidbootstraptheme extension https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Classes/Controller/ContentController.php
  • 06:09:29 <fger> and inside its ext_tables.php and did it the same way
  • 06:09:49 <bjo3rn> probably an issue with namespaces?
  • 06:11:20 <fger> i register it with XY.XYtemplates in ext_tables.php
  • 06:11:35 <fger> and in my controller: namespace XY\XYTemplates\Controller...
  • 06:11:44 <bjo3rn> looks fine
  • 06:11:49 <fger> its in the correct folder inside Classes/Controller
  • 06:11:56 <fger> ContentController.php
  • 06:13:05 <bjo3rn> \FluidTYPO3\Flux\Core::registerProviderExtensionKey('XY.XYTemplates', 'Content'); ?
  • 06:14:40 <bjo3rn> btw. the action can't have any arguments
  • 06:23:23 <NamelessCoder> fger you need to nest the parameters in a tx_yourext_content[arg] way
  • 06:23:38 <NamelessCoder> raw query parameters are not intended to be available in any Extbase controller
  • 06:23:48 <NamelessCoder> (if you need that, GeneralUtility::_GET)
  • 06:24:27 <NamelessCoder> to check which scope is expected you can for example generate a link from your controller via UriBuilder or some f:link.action or something in the template that belongs to it
  • 06:51:16 <fger> hmm my problem is more that the controller action isnt weven called
  • 06:54:13 <fger> I'm now transmitting GET-Param called ?tx_XYtemplates_content[discussionID]=6
  • 06:58:55 <NamelessCoder> the controller class name has to match the extension key you register in ext_localconf.php, maybe you left out the "Vendor." part? Maybe the controller class is not named or placed correctly - or maybe the action method is protected or incorrectly named.
  • 06:59:22 <NamelessCoder> e.g. no "Action" suffix on the method. It has to be 100% extbase style.
  • 06:59:49 <fger> i did it like in fluidbootstraptheme
  • 06:59:51 <fger> all fine
  • 06:59:54 <NamelessCoder> gotta go - but pretty sure you will find the cause in one of those things ;)
  • 06:59:56 <fger> ContentController.php
  • 07:00:01 <fger> ok thx
  • 07:00:03 <NamelessCoder> can be a simple typo in filename or class
  • 07:00:11 <fger> probably
  • 07:03:22 <fger> and no, i dont even have an ext_localconf.php
  • 07:03:30 <fger> just like fluidbootstraptheme only exT_tables.php
  • 07:03:43 <fger> \FluidTYPO3\Flux\Core::registerProviderExtensionKey('FluidBT.Fluidbootstraptheme', 'Content');
  • 07:03:53 <fger> i register my extension the same way
  • 07:04:06 <fger> and have XY\XYTemplates\Controller as namespace
  • 07:10:38 <fger> ok, debugged it with xdebug ... my ContentController is called, but not my action
  • 07:10:42 <fger> will dig into that
  • 07:12:32 <bjo3rn> fger what is the name of your element's template file?
  • 07:21:35 <fger> the action name is forumDetailAction()
  • 07:21:44 <fger> template file name is .../ForumDetail.html
  • 07:33:15 <fger> seems right, doesnt it ? at which point is any custom controller/FCE ActionName generated ?
  • 08:10:01 <bjo3rn> fger that's correct indeed. hm...
  • 08:33:31 <NamelessCoder> fger whatever the reason may be... https://github.com/FluidTYPO3/flux/blob/development/Classes/Controller/AbstractFluxController.php#L271 might be getting the wrong context so if you're debugging I would start there
  • 08:45:30 <Tjark> hi, i just tested my provider ext. with Custom FCE´s in TYPO3 7.x (7.0, 7.1 and 7.3).
  • 08:45:30 <Tjark> I can select my FCE´s, but the flux fields are not visible.
  • 08:45:30 <Tjark> Any Ideas ?
  • 08:49:04 <fger> @namelesscoder: wow this is strange .. the renderAction of the AbstractFluxController isnt called at all, i cleared cache and did an xdebug breakpoint there ... doesnt work
  • 08:49:14 <bjo3rn> Tjark we released a bugfix today (4.2.4) please try that.
  • 08:51:04 <Tjark> @bjo3rn wow nice
  • 08:54:36 <Tjark> awesome, it works!
  • 09:03:44 <fger> ah, the resolveFluxControllerClassNameByExtensionKeyAndAction returns NULL
  • 09:18:51 <fger> seems it tries to resolve class "Tx_XYtemplates_Controller_PageController " , but i am using namespaces
  • 09:19:00 <fger> and the pagecontroller class is there
  • 09:23:20 <NamelessCoder> what exactly is your vendor name and extension key? the example dummy names you give aren't valid and if your name uses the same naming that might cause this
  • 09:24:03 <NamelessCoder> in your example, extension key must be "x_ytemplates" in the last example and "x_y_templates" in the ones before that
  • 09:25:01 <NamelessCoder> and you say ContentController is called - but you're giving an example from attempting to resolve the page controller. Are you doing two controllers?
  • 09:26:12 <NamelessCoder> (the resolving method executes any number of times, once for the page and X number of times depending on how many Flux-enabled content elements get rendered)
  • 09:32:47 <fger> ok, i register the content/page structure in my provider-extension like this:
  • 09:32:48 <fger> \FluidTYPO3\Flux\Core::registerProviderExtensionKey('F03.F03templates', 'Content');
  • 09:33:08 <fger> my extension folder is named f03templates
  • 09:45:03 <fger> the provider extension was built with builder
  • 09:47:47 <fger> i activated hardFail in the resolver and it failed first for the pageController,... I created it the same way like my ContentController
  • 09:47:51 <fger> still not found
  • 09:48:13 <fger> namespace F03\F03templates\Controller; in both controllers
  • 09:48:43 <fger> that isnt correctly mapped from Tx_F03templates_Controller_....
  • 09:49:43 <fger> TYPO3 6.2.latest on PHP 5.6
  • 09:51:16 <NamelessCoder> something definitely is off with that extension key
  • 09:51:24 <NamelessCoder> it's an O, not a zero, right?
  • 09:53:21 <NamelessCoder> https://github.com/FluidTYPO3/flux/blob/development/Classes/Helper/Resolver.php#L147
  • 09:53:35 <fger> zero
  • 09:53:36 <NamelessCoder> does your extension key have a vendor name here?
  • 09:53:53 <fger> yes - I added a Migrations/Code/ClassAliasMap.php file now
  • 09:53:57 <fger> then it works
  • 09:55:00 <NamelessCoder> https://github.com/FluidTYPO3/flux/blob/development/Classes/Controller/AbstractFluxController.php#L212
  • 09:55:18 <NamelessCoder> I bet on your end, $controllerExtensionKey lacks the vendor name. And that might be a bug.
  • 09:55:51 <NamelessCoder> do you use a custom Provider class?
  • 09:56:46 <fger> yes it lags the vendor name
  • 09:57:01 <fger> its f03templates when the method u linked last is called
  • 09:57:04 <NamelessCoder> https://github.com/FluidTYPO3/fluidcontent/blob/development/Classes/Provider/ContentProvider.php#L140 - is how fluidcontent will read the expected extension key which means the value recorded in DB should also contain the vendor name - which I bet yours doesn't
  • 09:57:09 <fger> but i register F03.F03templates
  • 09:57:26 <fger> hmm
  • 09:57:38 <fger> yeah i changed it later one
  • 09:57:40 <fger> -e
  • 09:58:08 <fger> the builder version i used put in a 'f03templates' in the ext_tables.php register statement
  • 09:58:16 <NamelessCoder> well, those two are, strangely enough, compatible in the eyes of fluidcontent but NOT in the eyes of Flux when resolving a controller class
  • 09:58:27 <fger> guess so
  • 09:58:40 <NamelessCoder> if you add a new content instance now, does it record the vendor name in DB? (asking so we narrow the problem down)
  • 09:59:00 <fger> and u are right, the DB entries dont have a vendor name if the provider extension is not registered with a vendor name FROM THE BEGINNING
  • 09:59:12 <fger> ok
  • 09:59:16 <fger> i will test mom
  • 10:00:30 <NamelessCoder> this would be the crucial point - if the new content record has the vendor name, there's no "bug" but it definitely is cause for confusion when you don't have a class alias map
  • 10:03:11 <NamelessCoder> the reason it works with and without vendor name until you try to resolve PHP classes is of course that Flux doesn't care when resolving paths for templates or expected filesystem paths
  • 10:04:11 <NamelessCoder> ah, the wonders of using vendor names in TYPO3 ^^
  • 10:04:15 <fger> ;)
  • 10:04:45 <fger> yes, using a vendor-name in the registration statement in the provider breaks my newContentWizard completely
  • 10:05:03 <fger> the pageTs, that is rendered into cf_fluidcontent in the DB doesnt seem compatible anymore
  • 10:08:42 <fger> see https://gist.github.com/fgerards/5a33027bd5c2b1ee14c8
  • 10:09:03 <fger> just posted the first lines
  • 10:21:19 <fger> but yes, the tx_fed_fcefile is set to F03.F03templates:<filename>
  • 10:23:30 <fger> so i guess as we already have around 250 FCEs with old db-naming i leave the register-process with "f03templates" and map the class in migrations/classes ...
  • 10:23:35 <fger> migrations/code...
  • 10:41:55 <fger> ok, i got it working with the migrations
  • 10:42:17 <fger> another "flaw": tx_f03templates_Content is the right prefix
  • 10:42:30 <fger> tx_f03templates_content wont work here
  • 10:42:35 <fger> notice the case-sensitivity
  • 10:42:42 <fger> never had that in TYPO3
  • 10:44:02 <fger> because if I build the link with sth like <f:link.action action="forumDetail" pageUid="123" arguments="{discussionId : uid}">...
  • 10:44:15 <fger> TYPO3 generates a tx_f03templates_content prefix
  • 10:44:17 <fger> which fails

20150702

  • 04:39:56 <Guest|25569> Hi everyone, I'm having a problem with flux:form.fields. None of the fields in a content element will show up in the backend. For fields in a page template it works totally fine
  • 04:47:14 <fger> rehi
  • 04:47:57 <fger> still wonder why prefix of GET-Parameters for passing variables to a Flux/Fluidcontent Controller Action for an FCE is case-sensitive
  • 04:48:22 <fger> would be better to performe a lowercase-operation, because that is common sense in TYPO3 world
  • 04:48:38 <fger> so tx_f03templates_content[...] doesnt work
  • 04:48:47 <fger> but tx_f03templates_Content[...] does work
  • 04:49:16 <Tjark> Guest|25569 TYPO3 7.x
  • 04:49:19 <Tjark> ?
  • 04:49:22 <fger> in all other cases i know tx_news_Pi1[..] would work and tx_news_pi1[..] would work too
  • 04:49:58 <Guest|25569> No, its 6.2.13
  • 07:06:43 <fger> no one ;) ?
  • 10:33:35 <fger> dumdidum ... still ?
  • 11:38:37 <Guest|14123> hi
  • 11:38:53 <Guest|14123> Just set-up a clean typo3 6.2 system with flux
  • 11:39:24 <Guest|14123> And I cant figure out why no configuration fields are shown in the backend
  • 11:39:35 <Guest|14123> used the example content/teaser.html

20150703

  • 02:54:45 <fger> good morning
  • 06:07:27 <domsann> Any1 an idea why I cannot execute storage->moveFile in my commandcontroller w/o php error?
  • 06:07:55 <domsann> I set permission permissions.file.storage.1 { ....moveFile = 1.....} for the cli user
  • 10:29:00 <Guest|79884> Hello guys, i have a problem with the v:page.languageMenu viewhelper. I have set hideNotTranslated="1". This works, for all languages except the default. When the default is hidden, it still appears in the language menu
  • 10:29:21 <Guest|79884> Would be great if some 1 got a solution
  • 11:59:56 <Guest|18156> some here ?

20150704

20150705

20150706

  • 01:50:41 <jmverges> hi there
  • 04:57:02 <Guest55629> Hello, i developed a lot of Content Elements with fluidcontent. Those includes also nested elements, like e.g. a slider with nested grids. Now i suddently run into the problem that content inside those nested containers are duplicated or even 3 times visible in frontent. In backend all looks OK. I found some bugreports in this direction, but they s
  • 04:57:02 <Guest55629> eem to be fixed already. Does anybody had this problem also once and has some hints to bugfix or workaround that?
  • 05:16:45 <mrboe> hi all
  • 05:17:11 <mrboe> can i have a section/object in an section/object ?
  • 05:26:07 <Guest55629> btw: I have not updated flux, so http://fluidtypo3.org/blog/news/new-colpos-value.html can not be the case i think.
  • 05:26:23 <Guest55629> And: I use current versions from TER
  • 06:51:05 <Guest55629> Hm.... I solved that problem partly. I have in a container two conditions: "{var} == false" and "{var} == true", with which I render content based on a setting here or there. But both conditions were executed. {var} comes from a checkbox, which is not always displaed (displayCond). But still wondering how a {var} can be both true AND false... If c
  • 06:51:05 <Guest55629> heckbox is not displayed, the real value is NULL. I thought in this case only ({var} == false) would be true, but not also ({var} == true)...
  • 06:51:23 <Guest55629> But that seems to be not a flux issue, but fluid...
  • 06:51:26 <Guest55629> Sr
  • 06:51:28 <Guest55629> Sry
  • 06:59:18 <NamelessCoder> Guest55629 the comparison above would not work. You should compare with 0 or 1 to determine true/false. Or just put the variable in there, e.g. condition="{var}"
  • 06:59:58 <NamelessCoder> it would not work because Fluid would see that as a string rather than an expression and a string (unless empty or containing a zero) will evaluate to TRUE when cast to boolean
  • 07:00:26 <NamelessCoder> (boolean) "1 == true"
  • 07:00:30 <NamelessCoder> (boolean) "0 == true"
  • 07:00:34 <NamelessCoder> both are TRUE
  • 07:04:40 <Guest55629> (facepalm) thanks a lot!
  • 07:05:12 <NamelessCoder> btw it is going to work
  • 07:05:23 <NamelessCoder> - standalone fluid supports such syntax
  • 07:05:48 <NamelessCoder> (assuming your {var} contains a string "true")
  • 07:06:07 <Guest55629> So problem is that my flux checkbox returns a string, right?
  • 07:12:05 <NamelessCoder> no, your problem could be that displayCond not showing the field doesn't result in the value being zeroed in DB
  • 07:19:13 <Guest55629> Ok, I'll make some tests with that. with 1/0 condition it works
  • 09:21:07 <svenDeKa> Hi guys, I was looking for a way to access values from a parent FCE of inside a child FCE but did not find anything. do you have a tip?
  • 09:21:29 <svenDeKa> .oor ressource to read it up?
  • 09:28:45 <svenDeKa> i get my parent element with {v:variable.set(name:'parent',value:'{v:content.info(contentUid:\'{record.tx_flux_parent}\')}')}, but how can I access values from flux-fields inside it?
  • 09:38:05 <fger> quick question: can i pass sorted objects to f:widget.paginate and the sorting is kept ?
  • 10:08:48 <svenDeKa> @fger. afaik, the sorting should be kept. but I think it builds an array from the objects you pass to it.
  • 10:10:14 <svenDeKa> for example: IN: ObjectStorage of MyObjects - Out: Array of MyObjects
  • 12:01:40 <fger> thx 4 info

20150707

  • 01:52:12 <jmverges> morning all
  • 04:25:14 <pedda> hi there
  • 06:45:09 <Guest|28536> Hi, just trying out fluidcontent_core - Nice work! One thing i miss is the mailform support. The mailform element is quite empty, and i can't find any Template for it in the extension. Is this not yet supported or do i miss something? (I can still use form if i comment "tt_content.mailform < plugin.tx_fluidcontentcore.bootstrap" in extension's setu
  • 06:45:09 <Guest|28536> p.txt)
  • 10:54:31 <drlimbo> good afternoon
  • 10:54:40 <drlimbo> is there a way to use fal images in a FCE with sections?
  • 10:55:06 <drlimbo> sure it is - i mean, is there a way to use multiple fal images in a section?
  • 11:47:08 <papillon6> drlimbo: Few days ago I tried to build an "slider-FCE" with multiple slides, having an FAL-image each. Didn't find a solution finally.
  • 11:48:11 <papillon6> If i added several slides (section) and created the image in the frist section, it was suddently saved in the second slide, too.
  • 11:49:00 <papillon6> I'm using and old-school file-field for now ;-) If you find a solution, please let me know.

20150708

  • 03:27:56 <jmverges> morning
  • 06:24:22 <fger> hi guys, will flux/fluidpages etc. be compatible with TYPO3 7.2/7.3 ? are there any breaking changes to be solved or why is FLUX 7.2.1 limited to TYPO3 7.1.x ?
  • 07:59:21 <fger> @namelessCoder: FLUX 7.2 compability ? any breaking changes from 7.1 to 7.2 ?
  • 10:21:36 <drlimbo> good afternoon
  • 10:21:48 <drlimbo> is there a way to render all Header as H2 instead of H1 with fluid?
  • 10:21:59 <drlimbo> "content.defaultHeaderType = 2" doesnt seem to work
  • 20:40:40 <Guest|5175> Hi, I've a question! I wanna combine a flux form Select and a fluid switch method, but cannot validate the array! https://gist.github.com/Ourelius/dc0baccc51dce531bf23 (line: 9, 20, 33, 44, 57)
  • 20:41:52 <Guest|5175> Error: No value found for key "TYPO3\CMS\Fluid\ViewHelpers\SwitchViewHelper->switchExpression", thus the key cannot be removed

20150709

  • 03:16:04 <fger> good morning
  • 04:48:16 <coder46> kann ich stören
  • 04:48:18 <coder46> ???
  • 07:24:09 <Momodedf> Hello
  • 07:25:11 <Momodedf> I'm having issues passing from flux 7.1. to flux 7.2 :(
  • 07:25:29 <Momodedf> I hope somebody could help me
  • 07:36:25 <Momodedf> No FCE field are displayed at all in backend :(
  • 07:41:05 <Momodedf> Has anyone an example of a working provider with the last version ont fluitypo3 exts ?
  • 15:32:15 <t3like> How can I use thrating in combination with fluidtypo3? Here is my example, please read the last lines: http://pastebin.com/GRnbgbQu
  • 16:03:08 <t3like> For all the following people: just use tt_content as tablename and catch all other information with v:content.info

20150710

  • 06:53:45 <schnarald> hello. i got a problem using fluidpages on my fresh typo3 cms 7.1.0 version
  • 06:54:33 <schnarald> after installing and enabling fluidpages i get an error message in the browser
  • 06:54:42 <schnarald> Oops, an error occurred! Code: 20150710104332fa0baa8f
  • 06:55:03 <schnarald> nothing more in the body tag
  • 06:55:30 <schnarald> typo3.log does not provide much more information:
  • 06:55:39 <schnarald> Fri, 10 Jul 2015 10:43:33 +0000 [ALERT] request="ad6b51b41695c" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! Code: 20150710104332fa0baa8f - {"exception":{}}
  • 06:58:39 <svewap> Sorry to bother you, but does anyone know by chance why the field image_zoom is deactivated in the fluidcontent_core extension? The lightbox feature is still a nice feature for tablets and desktops.
  • 08:43:01 <Guest|706> Hey guys, the menu of "fluidcontent_core" won't work :(. I updated it with the update script but I have the error that the template files could not be loaded. I saw that theres a missing php closing tag in the AdditionalConfiguration.php and I added it. Won't work anyway. Need help!
  • 09:14:04 <Guest|58754> Hi. I'm trying to use own templates for the header in fluidcontent_core. Therefore I copied the original fluid-templates to my own template_provider-Extension and added some TS to set the new path: plugin.tx_fluidcontentcore.view.templateRootPaths.1 = ...
  • 09:14:24 <Guest|58754> but unfortunatly my templates ignored. :-(
  • 09:14:45 <Guest|58754> Have I forgotten something?
  • 09:55:05 <svewap> Try to use the 20 instead of 1
  • 10:10:49 <Guest|58754> thanks. this worked :)
  • 19:32:37 <flops> hi guys
  • 19:34:51 <flops> just fyi: the site extension isn't working in v. 6.2.14
  • 19:44:43 <flops> so I tried to install the extension manually and created my providerextension. everything seems to work, but only the fluidcontent elements that I created don't get rendered in the frontend. the headline gets rendered but the stuff in the render section just does not show up in the frontend
  • 19:45:07 <flops> anyone an idea how I could get rid of that problem?
  • 19:47:15 <flops> fluidcontent_core elements and obv the pagetemplate are rendered
  • 20:12:00 <NamelessCoder> flops please make sure it created typo3conf/AdditionalConfiguration.php - if it exists, you need to add some lines to it manually (see Resources dir in fluidcontent_core)
  • 20:12:08 <NamelessCoder> and with that, I go to bed :)
  • 20:12:26 <flops> ok thx gn8
  • 20:15:20 <flops> that fixed the problem. thx alot
  • 20:18:25 <flops> if you need any "help" regarding the site kickstarter problem e.g log-files I could send you these, although I think it is a typo3 problem. a lock-file doesn't get deleted. that problem existed a few times before...

20150711

20150712

20150713

  • 03:32:49 <Guest|38823> Hi. I'm using fluidcontent_core with a fluid template provider and a custom extras extension. My extbase plugin is rendered well, but without the given "header" field. How may I access this or tell fluidcontent_core to render the standard header to the plugin... ?
  • 03:33:12 <Guest|38823> *extbase extenstion. Damn auto-correct. ;-)
  • 03:42:42 <Guest|38823> ah. got it - v:content.info helped. :-)
  • 05:51:07 <Guest|5720> Anybody here? :-) I'm looking for a solution to get rid of the <div class="tx-my-extension">-wrap around my plugin. any hints?
  • 05:57:41 <Guest|76735> Hi. Sorry - accidentally closed the browser and destroyed my chat ;-) As I'm not sure if my question has arrived the chat; once again. I want to get rid of the <div class="tx-my-extension">|</div>-Wrap around my plugin. How may I achieve this? Thanks in advance.

20150714

  • 13:23:52 <dreadwarrior> Hey guys! Just wanted to drop in to let u know that the FluidTYPO3 (flux, fluidcontent_core, fluidcontent, fluidpages, fluidcontent) suite is working properly on 7.3 with this patch in ur provider extension: https://github.com/dreadwarrior/vantomas/commit/7d89f41cdaf4667ff76cd4906d4c206bebbfbe46
  • 13:23:57 <dreadwarrior> ext:css_styled_content carries this setup and if u disable it, u can't use the default CEs from the core
  • 13:24:03 <dreadwarrior> or rather: use the default CEs from the CType select box for the fluidcontent_core installation ;)
  • 13:24:17 <dreadwarrior> Please let me know what you think about it.

20150715

  • 02:51:02 <TYPO3ua> Hello, everybody!
  • 02:54:36 <TYPO3ua> When will flux, fluidpages, fluidcontent for TYPO3 version 7.3?
  • 04:03:19 <Denyerec> Hey All - I might need to secure a subcontractor to switch a site running on TV into one running on the latest versions of FLuidpages and Typo3. If anyone is available for this work and can examine the existing site to come up with a quote please get in touch ASAP.
  • 05:20:46 <NamelessCoder> Denyerec if you tweet about it I can retweet ;)
  • 05:21:27 <Denyerec> I'll see if anyone from the home crowd is interested here first, then I'll take you up on that offer :)
  • 05:21:39 <Denyerec> How's the 7.x work going ?
  • 05:23:45 <NamelessCoder> things are happening (and we have help) but I can't give an actual status at this time
  • 05:29:18 <Denyerec> Oooh you sound like Microsoft ;)
  • 05:29:32 <Denyerec> As I understand it it's almost a complete fork for the BE
  • 05:29:46 <Denyerec> Which has to be a royal pain in the arse.
  • 05:30:49 <TYPO3ua> When will flux, fluidpages and fluidcontent for TYPO3 version 7.3?
  • 05:32:06 <NamelessCoder> hehe NamelessMicroSoft
  • 05:32:33 <NamelessCoder> I say it like that because bjo3rn is taking care of coordinating the contributions we expect and our next release depends on those ;)
  • 05:33:02 <NamelessCoder> TYPO3ua see responses to Denyerec, it's about the same thing :)
  • 05:33:24 <Denyerec> Ahh I see
  • 05:33:35 <Denyerec> So it's more a question of "I literally have no idea" than "I'm not allowed to say"
  • 05:34:23 <TYPO3ua> :) thanks .... I see
  • 05:40:31 <NamelessCoder> hehe yeah pretty much. Although it's not "no idea", it's just not much of an idea yet :)
  • 05:41:45 <jmverges> good morning
  • 05:41:47 <NamelessCoder> hoping for a status update myself sometime this week but in all fairness it's vacation time, etc. - as soon as we know, there will be an article (both to inform about coming fixes and to thank the contributing companies)
  • 06:05:16 <NamelessCoder> morning jmverges :)
  • 06:07:12 <jmverges> what is going on NamelessCoder?
  • 06:11:01 <NamelessCoder> writing unit tests / working on a very complex project for content preservation. Very exciting hehe
  • 09:49:11 <Xatenev> in fluid how can I create a foreach loop with key value?
  • 09:49:22 <Xatenev> for example <f:for each="{settings.fields}" as ="field" key="mykey"
  • 09:50:03 <Xatenev> Oh... thats the solution.. nice ^_^
  • 16:11:45 <flops> hi guys
  • 16:17:48 <flops> I'm new to the whole fluid thing and I really like it but it also drives me crazy.
  • 16:19:25 <flops> I was using fluidcontent_core and I tried to render the default header of a custom content element.
  • 16:21:29 <flops> getting the text is no problem. but I just cannot get the settings from the apperance-tab header.type etc. I think I'm missing something really general

20150716

  • 10:32:06 <ndee> since NamelessCoder maybe here: hey guys, I’m getting following error, when I try to execute the „site“ extension: 2015/07/16 16:26:16 [error] 29643#0: *40191 FastCGI sent in stderr: "PHP message: PHP Fatal error: Call to a member function set() on a non-object in typo3_src-6.2.14/typo3/sysext/core/Classes/Core/ClassAliasMap.php on line 141. I’m running the latest 6.2.14 version. Anyone experienced that problem before? I’m running nginx with php5-fpm.

20150717

  • 02:01:06 <jmverges> good morning
  • 03:42:53 <Guest|24101> Good morning everybody. I'm struggling with some flux/fluidcontent stuff right now and was hoping someone in here can help me. I wanna use the flux:form.container element but it always says "Section expected at container but not found ". Anyone an idea what I'm doing wrong?
  • 03:51:45 <denis_droid> Someone here that can help me with merged settings in flux?
  • 09:08:26 <Guest|22616> Hi there. Is there a way to use fluidtypo3 with typo3 7.2?

20150718

20150719

20150720

20150721

  • 05:07:10 <Guest|64502> HI, I just make my way trough the documentation and asked myself if it is possible to set content-elements only for special page-layouts?
  • 05:07:38 <Guest|64502> eg. user selects page "home" and there only 2 of 5 content-elements are allowed to be used
  • 05:14:20 <jmverges> hi there
  • 05:16:50 <Guest|64502> hi jmverges
  • 05:17:25 <jmverges> hi there
  • 05:19:10 <Guest|64502> any infos to my question?
  • 05:19:18 <jmverges> what question?
  • 05:21:38 <Guest|64502> oh sorry I thougth you can see my question
  • 05:21:46 <Guest|64502> I just make my way trough the documentation and asked myself if it is possible to set content-elements only for special page-layouts?
  • 05:22:02 <Guest|64502> I just make my way trough the documentation and asked myself if it is possible to set content-elements only for special page-layouts?
  • 05:22:07 <jmverges> yes, you can do it
  • 05:22:38 <jmverges> you need to allow it in special layouts and deny it in the other ones
  • 05:23:09 <jmverges> https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=23&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=2b3ec6eaf6bca818bad4e4d8c85b6b41
  • 05:23:17 <Guest|64502> nice - do I find how to in the documentation?
  • 05:23:35 <Guest|64502> thx a lot!
  • 05:24:51 <jmverges> https://github.com/FluidTYPO3/documentation/commit/ce960b034f4458ffd8e8307e6b0db8cfc68c0504
  • 05:26:22 <Guest|64502> awesome! cant wait to start my next projekt and try fluidcontent instead of backend-layouts and dce
  • 05:26:34 <jmverges> great
  • 05:27:03 <Guest|64502> have a nice day! cu

20150722

  • 04:51:06 <svenDeKa> god morning
  • 04:52:21 <svenDeKa> I am looking for a way to access a flux-parents variables inside a child-elements template.
  • 04:52:48 <svenDeKa> I tried content.info but this returns the pi_flexformfield, but no variables...
  • 04:53:07 <svenDeKa> I wouhld really appreciate a hint, if there is a way.
  • 04:55:17 <svenDeKa> sry, content.info wasnt precise: I mean {v:content.info(contentUid:'{record.tx_flux_parent}')}
  • 05:16:07 <svenDeKa> ok. tried v:render.record. but this doesnt output anything at all... :( -not even if I do <v:render.record record="{uid:35}"/>
  • 05:17:02 <svenDeKa> the idea was to try <v:render.record record="{uid:'{record.tx_flux_parent}'}"/>
  • 05:21:23 <svenDeKa> as mentioned here: https://fluidtypo3.org/community/irc-logs.html?tx_fluidtypo3org_content[date]=20141119&cHash=1addc7ada531144b667e5745b9be95be I tried v:content.render, but <v:content.render contentUids="{0:35}"/> downst geimme anything back,too.
  • 08:33:10 <pedda> hi there
  • 08:33:39 <pedda> does editing of pages != standard page work for you if you use fluidpages in that project ?
  • 08:34:01 <pedda> for instance: external url, if i change the external url and hit save, i get an fluidpages error
  • 08:34:22 <pedda> Fatal error: Cannot use string offset as an array in /var/www/public_www/emil-frey-classics.ch/typo3conf/ext/fluidpages/Classes/Provider/PageProvider.php on line 246
  • 08:34:30 <pedda> ups :P
  • 08:34:51 <pedda> too dumb for pasting error messages privately
  • 08:34:54 <jmverges> I don't get it
  • 09:01:20 <pedda> nvm
  • 09:01:23 <pedda> :)
  • 09:01:41 <pedda> seems as if a certain extension of mine is broken
  • 09:02:02 <pedda> if i disable it, things seem to work
  • 09:32:12 <jmverges> uhm
  • 09:36:17 <Stefanie> 'textpic' and file selection in BE do no longer work after installing vhs/flux/fuidcontent/fluid page - any ideas?
  • 09:36:53 <jmverges> did you install fluidcontent_core?
  • 09:37:08 <Stefanie> yes
  • 09:37:13 <jmverges> there you go
  • 09:37:37 <Stefanie> you mean de-install fluidcontent_core?
  • 09:37:42 <jmverges> https://github.com/FluidTYPO3/fluidcontent_core#special-note-about-the-textpic-text-with-images-content-type
  • 09:43:50 <Stefanie> okay, that explains part of my problem
  • 09:46:18 <Stefanie> however, I can't get fluid content element to allow file selection - I just get an empty window
  • 09:46:27 <Stefanie> <flux:field.inline.fal name="settings.images" multiple="TRUE" />
  • 09:49:35 <pedda> Stefanie put this code in typo3conf/AdditionalConfiguration and set line 3 to TRUE
  • 09:49:36 <pedda> https://gist.github.com/wikipeter/7eb8e00506570044d91b
  • 09:49:48 <pedda> you will see more than a blank page in most cases then
  • 09:50:05 <pedda> jmverges seems as if my issue persists somehow
  • 09:50:25 <pedda> the thing is: i use typoscript to define flux settings for a custom extbase extension's fe plugin
  • 09:51:21 <pedda> the whole typo3 project is a git repository, which guarantees me the same versions of extensions in that project
  • 09:51:36 <pedda> on my local machine, everything works as expected
  • 09:51:42 <pedda> on a remote machine it doesn't
  • 09:52:03 <pedda> the remote machine has a lower php version which is 5.3.10 i think
  • 09:52:13 <pedda> now my issue:
  • 09:52:36 <pedda> if my custom extension is enabled, i can create an fe plugin and see the fields in my plugin settings
  • 09:52:43 <pedda> i hit save and it seems to work
  • 09:52:48 <pedda> but
  • 09:53:35 <pedda> if i define basic.doctypes of EXT:fluidpages in extension manager in order to be able edit non standard typo3 pages in backend while fluidpages is running, my custom extension "breaks"
  • 09:54:14 <pedda> or at least i get plenty of error messages telling me that flux viewhelpers couldn't be loaded by the autoloader
  • 09:56:20 <pedda> i know this is strange...
  • 10:00:01 <Stefanie> pedda now i get:
  • 10:00:01 <Stefanie> Fatal error: Class 'TBE_FolderTree' not found in /html/typo3/typo3_src-6.2.12/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4432
  • 10:03:24 <pedda> you need to scroll down that message until some lines occur, which you recognize, as you're dealing with some feature of typo3 which starts breaking at a certain point
  • 10:05:18 <pedda> you get the point?
  • 10:05:26 <Stefanie> sorry, no
  • 10:05:41 <pedda> Class 'TBE_FolderTree' not found <- the file is missing
  • 10:05:48 <pedda> this is what te error message is saying
  • 10:05:56 <pedda> i can't tell you if it's there
  • 10:06:18 <pedda> you need to check this (most probably the file exists, as you don'T delete random files of the typo3 core)
  • 10:06:22 <pedda> so you need to scroll down
  • 10:06:29 <pedda> and check the messages in detail
  • 10:06:46 <pedda> until some line occurs which you recognize, because you'Re dealing with feature XY of typo3
  • 10:06:53 <pedda> at the moment
  • 10:07:13 <pedda> and that line is mentioning feature XY
  • 10:08:00 <pedda> the lines with the dark background are the ones to check step by step
  • 10:08:18 <pedda> as you can see which values were passed to the code
  • 10:08:28 <pedda> like: 27 FluidTYPO3\Flux\Form\AbstractFormComponent::createField("FluidTYPO3\Flux\Form\Field\SelectViewHelper", "settings.carousel.renderMode", NULL)
  • 10:12:43 <pedda> this way you can narrow down what causes the error
  • 10:19:17 <Stefanie> i'm lost - this is too deep down for a newbee like me... :-(
  • 10:19:38 <pedda> probably
  • 10:19:49 <pedda> what is your current task?
  • 10:20:03 <pedda> add flux field for FAL images in an FCE ?
  • 10:23:22 <pedda> Stefanie?
  • 10:24:12 <Stefanie> yes. and i cannot select a file as the window is empty (or produces the error message when debuggin g)
  • 10:24:43 <Stefanie> when i attach a file instead it is loaded to fileadmin/userupload but does not show in FE
  • 10:25:51 <Stefanie> only workaround i have is to enter the file path and name as string in a flux:field.input :-(
  • 10:29:58 <pedda> no
  • 10:30:19 <pedda> it won't appear magically in frontend unless you use a viewhelper to render a FAL image
  • 10:30:44 <pedda> this is what you're using: https://fluidtypo3.org/viewhelpers/flux/master/Field/Inline/FalViewHelper.html
  • 10:31:06 <pedda> you see this: Example how to get the first file reference from a fluidcontent element, for the flux field named "settings.files": {v:content.resources.fal(field: 'settings.files') -> v:iterator.first() -> v:variable.set(name: 'settings.files')}
  • 10:32:00 <Stefanie> i tried the template
  • 10:32:04 <Stefanie> https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display[gist]=5&tx_fluidshare_display[action]=display&tx_fluidshare_display[controller]=Gist&cHash=e403004449572e5ede2dd38d6d268f99
  • 10:32:24 <pedda> does this work from scratch for you?
  • 10:32:45 <pedda> if not: 2014-08-25 is a bit older than your flux version probably...
  • 10:33:02 <pedda> or other way round ... your flux version is older than the snippet
  • 10:33:15 <pedda> i need to leave now
  • 10:33:31 <Stefanie> thanks, pedda!
  • 10:36:08 <Stefanie> (got the latest flux version 7.2.1)
  • 12:41:47 <pedda> NamelessCoder around?
  • 12:41:56 <pedda> +still

20150723

20150724

20150725

20150726

20150727

  • 10:28:41 <mneuhaus> ahoy!
  • 10:29:02 <jmverges> hi mneuhaus
  • 10:29:33 <mneuhaus> am i right to assume, flux/fluidcontent isn't working yet with 7.3.1? ^^
  • 10:30:21 <jmverges> well you can give it a try
  • 10:30:30 <mneuhaus> i did ^^
  • 10:30:35 <jmverges> I'm on master doing stuff and they are working
  • 10:30:43 <mneuhaus> $hookObject must implement interface TYPO3\CMS\Core\Database\TableConfigurationPostProcessingHookInterface
  • 10:30:45 <jmverges> did you download github sources or extensions?
  • 10:31:06 <mneuhaus> initially from ter, but updated to git
  • 10:31:17 <jmverges> is implemented that interface
  • 10:31:43 <mneuhaus> i'll try again, dev oder master branch?
  • 10:31:45 <jmverges> I got that issue also, I don't know what is wrong because the interface is implemented
  • 10:31:54 <jmverges> development branch
  • 10:33:30 <mneuhaus> ok, then, *pulling up sleeves* lets find out what fails here :)
  • 10:39:24 <drlimbo> hi there, does someone already find a good solution for dynamic image rendering (size based on viewport)
  • 10:40:17 <mneuhaus> drlimbo: you mean through an ajax call?
  • 10:41:25 <mneuhaus> afaik you can't get information about the viewport through pure php means. only javascript can read detailed info like that. you could maybe "guess" based on the screen resolution i think there was a way to read that info using php
  • 10:42:07 <mneuhaus> scratch that, even screen resolution isn't accessable without js
  • 10:46:05 <mneuhaus> for me it seems not flux itself is the issue but the Compatibility6 ext
  • 10:46:34 <mneuhaus> yep that was the cause
  • 10:48:31 <drlimbo> mh yes mneuhaus didn't thought about the technique already =P
  • 10:48:51 <drlimbo> but it must be some js to determine the viewport
  • 10:51:15 <drlimbo> maybe some JS looping trough images and add a ?viewport=1024 parameter? and f:image or something uses this width?
  • 10:51:20 <NamelessCoder> hehe stand back. Marc has pulled up his sleeves, bugs will be squashed! ^^
  • 10:51:34 <drlimbo> i thought about using multiple <img> Tags and show the correct size with CSS
  • 10:52:12 <drlimbo> maybe NamelessCoder has a good idea?
  • 10:53:22 <NamelessCoder> sorry, don't really do FE work
  • 10:54:26 <drlimbo> no problem
  • 10:54:26 <mneuhaus> hehe ^^
  • 10:54:56 <mneuhaus> sorry, claus, the already fell down again, was just the compatibility6 ext screwing with me :)
  • 10:55:30 <NamelessCoder> oh, well, in that case: phew. But damn.
  • 10:55:32 <mneuhaus> drlimbo: what you're looking for is essentially something like this: https://github.com/scottjehl/picturefill
  • 10:56:53 <drlimbo> yess mneuhaus - and if there is a viewhelper for this, it would be awesome =P
  • 10:57:10 <jmverges> so mneuhaus the interface was about compatibily6 ?
  • 10:57:18 <mneuhaus> yep, fals alarm, sorry
  • 10:57:20 <drlimbo> but it can be done with multiple img.url
  • 10:57:50 <mneuhaus> didn't expect for a shipped sysext to screw up like that, and flux was the only other candidate about that interface :)
  • 10:58:14 <mneuhaus> drlimbo: a viewhelper almost seems like overkill, a simple partial would be quick and easy, no?
  • 10:58:29 <jmverges> drlimbo you could create a extension
  • 10:58:41 <jmverges> if you do, please share it
  • 10:59:13 <jmverges> I like the viewhelper idea
  • 10:59:17 <drlimbo> yes i also thought about jmverges
  • 10:59:45 <drlimbo> don't know if a have enough know-how for that, just created / edited some basic viewhelpers until now
  • 11:00:12 <jmverges> well take a look to the contribution guide first of all: https://fluidtypo3.org/documentation/contributing/contribution-guide.html
  • 11:01:28 <mneuhaus> <foo:img.picturefill src="foo.png" sizes="{xs: '200x300', sm: '400x500', md: '500x600', lg: '1000x1200'" />
  • 11:01:30 <mneuhaus> ? ^^
  • 11:01:43 <jmverges> mneuhaus picturefill is a crossbrowser thing for modern browsers stuff?
  • 11:01:46 <NamelessCoder> not a bad idea marc
  • 11:02:29 <mneuhaus> should be an easy quick, just an extension of the regular image viewhelper that calls its parent with the splitted sizes
  • 11:02:34 <NamelessCoder> yep
  • 11:03:05 <NamelessCoder> sizes="{xs: {0: 120, 1: 180}, sm: {0: 300, 1: 480}}" could also be allowed
  • 11:03:14 <mneuhaus> yep
  • 11:03:21 <NamelessCoder> would make it easier to pass each dimension as variable perhaps even calculated ones based on ratio
  • 11:03:32 <mneuhaus> although writing that seems quite messy
  • 11:03:37 <NamelessCoder> sizes="{xs: 100, sm: 300}"
  • 11:03:48 <mneuhaus> though might make sense because it might come from variables
  • 11:03:56 <NamelessCoder> just setting the width and assuming ratio conservation
  • 11:04:06 <mneuhaus> yep
  • 11:04:11 <NamelessCoder> oh it should support all of those :) and just detect what is what
  • 11:04:24 <mneuhaus> maybe i'll toy around later ;)
  • 11:04:27 <NamelessCoder> ;)
  • 11:04:40 <mneuhaus> god i love viewhelpers
  • 11:04:42 <drlimbo> that would be awesome mneuhaus
  • 11:05:03 <drlimbo> and sure im willing to test your viewhelper and give you feedback
  • 11:05:17 <mneuhaus> they are such an awesome way to have flexible yet simple and clean templates
  • 11:05:55 <mneuhaus> i managed to "bolt on" a custom filter + date selector onto a custom list layout for news without much hassle
  • 11:06:32 <mneuhaus> question would be how exactly the resulting html should look like
  • 11:07:58 <NamelessCoder> make it a tagbasedviewhelper
  • 11:08:17 <NamelessCoder> and maybe allow setting the name of the attribute in the tag that will store all size URIs
  • 11:08:28 <NamelessCoder> that should be pretty damn compatible with JS libs too
  • 11:09:54 <mneuhaus> in general i guess it should follow the proposed standard:
  • 11:09:55 <mneuhaus> <picture>
  • 11:09:55 <mneuhaus> <source srcset="examples/images/extralarge.jpg" media="(min-width: 1000px)">
  • 11:09:55 <mneuhaus> <source srcset="examples/images/art-large.jpg" media="(min-width: 800px)">
  • 11:09:55 <mneuhaus> <img srcset="examples/images/art-medium.jpg" alt="…">
  • 11:09:56 <mneuhaus> </picture>
  • 11:10:49 <mneuhaus> but i'll have to read up a little bit about the current picturefill state of things :)
  • 11:11:14 <jmverges> mneuhaus: that is w3c standard ?
  • 11:11:26 <mneuhaus> proposed one, yes
  • 11:11:47 <NamelessCoder> proposed usually means likely to become standard
  • 11:11:55 <mneuhaus> yep
  • 11:12:28 <mneuhaus> yet, from proposed to "standard" takes usually somehere around 0.5-10 years :D
  • 11:12:47 <NamelessCoder> hehe yeah like html5 ^^
  • 11:12:53 <mneuhaus> exactly :)
  • 11:13:47 <mneuhaus> well, doesn't look to bad currently:
  • 11:13:47 <mneuhaus> http://caniuse.com/#search=picture%20element
  • 11:14:01 <mneuhaus> basically ie + safari missing
  • 11:14:07 <mneuhaus> screw opera mini
  • 11:14:30 <NamelessCoder> yeah IE/safari biggest issues there
  • 11:14:52 <mneuhaus> that's what polyfills are for :)
  • 11:15:40 <mneuhaus> http://caniuse.com/#search=srcs is an alternative method
  • 11:15:55 <mneuhaus> looking even better than picture element
  • 11:16:21 <jmverges> yeah, you could use it
  • 11:17:50 <mneuhaus> well, gottarun for now :)
  • 11:18:06 <mneuhaus> i'll take a stab at it in a few hours
  • 13:00:05 <xaver> mneuhaus: different standards exist - i think we should support it if one standard are implemented everywhere.
  • 13:01:01 <xaver> if ie and safari starting same thing, firefox and chrome would maybe follow to have a standard
  • 13:03:46 <mneuhaus> i'd shoot for bot proposed ones picture element + srcset
  • 13:03:57 <mneuhaus> with a switch to choose which one

20150728

  • 03:18:07 <Guest|95418> Good morning everybody. I'm struggling with some flux/fluidcontent stuff right now and was hoping someone in here can help me. I wanna use the flux:form.container element but it always says "Section expected at container but not found ". Anyone an idea what I'm doing wrong?
  • 03:47:25 <xaver> Guest|95418: i never used container, but this message is from T3 core. Maybe provide a gist with code. looks like somehting isn't found
  • 03:48:44 <xaver> around line 68 in typo3/sysext/backend/Classes/Form/Container/FlexFormElementContainer.php
  • 03:49:19 <xaver> also provide version informations of flux fluidcontent and T3
  • 04:37:57 <mneuhaus> so, after a bit of digging around yesterday i now know more about srcset and picture element regarding responsive images
  • 04:38:40 <mneuhaus> those 2 serve to similiar, but different purposes. srcset ist meant to offer different image sizes of the *same* focus and aspect ratio
  • 04:39:20 <mneuhaus> picture element on the other hand is more granular and can offer different focus and aspect ratios to better fit into the specific breakpoints
  • 04:39:40 <mneuhaus> so, i guess both could/should be implemented. i got a basic srcset version running:
  • 04:39:52 <mneuhaus> <v:media.image src="fileadmin/Dummies/Hund-im-Schnee.png" srcset="100,300,600,1200" />
  • 04:41:55 <mneuhaus> and i think it'll create a picture element similar to this:
  • 04:42:31 <mneuhaus> <v:media.picture src="fileadmin/Dummies/Hund-im-Schnee.png" alt="foo">
  • 04:42:31 <mneuhaus> <v:media.source media="(min-width: 1000px)" width="100c" heigh="300c" />
  • 04:42:31 <mneuhaus> <v:media.source media="(min-width: 800px)" width="100c" heigh="100c" />
  • 04:42:31 <mneuhaus> <v:media.source width="50c" heigh="50c" />
  • 04:42:31 <mneuhaus> </v:media.picture>
  • 04:42:59 <Guest|95418> Hi @xaver. Thanks for your reply.
  • 04:43:24 <Guest|95418> Gist: https://gist.github.com/flatchar/4a5daaa9ca67e8b57eca. I use typo3 7.3.1, flux 7.2.1 and fluidcontent 4.2.4. Any ideas? :)
  • 04:44:19 <Guest|95418> well. clever. drop the dot at the end ;) https://gist.github.com/flatchar/4a5daaa9ca67e8b57eca
  • 04:49:48 <Guest|95418> Even the example for Bootstrap Grids on fluidtypo3.org (https://gist.githubusercontent.com/misterboe/34018646f84e4c8a81b6/raw/ColMasterFlex.html) uses Containers but doesn't work for me.
  • 05:20:52 <xaver> Guest|95418: maybe it is broken in v7
  • 05:21:03 <xaver> file a issue :)
  • 05:21:10 <xaver> v7 has a lot of changes
  • 05:24:09 <jmverges> mneuhaus: I like it
  • 06:49:42 <Guest|95418> okay. Thanks @xaver.
  • 08:16:17 <drlimbo> mneuhaus: did u already startet with your responsive image viewhelper? =P
  • 08:17:13 <mneuhaus> yep, already wrote a bit about it this morning
  • 08:17:30 <mneuhaus> i'll post it to you through a dm to not spam this channel:)
  • 08:17:39 <drlimbo> sure, no problem
  • 08:20:30 <mneuhaus> i'll see if i have time to continue tonight
  • 08:21:26 <mneuhaus> srcset is working but code-wise quite ugly i think i'll make a trait for srcset and add it to the 2 existing image viewhelpers (resourse.image + media.image)
  • 08:56:14 <drlimbo> is there a viewhelper to put some "content" in the <head> sections -> like v:asset.script but without script =P
  • 08:56:37 <drlimbo> i need some conditional-comment + script like <!--[if lt IE 9]> .. <script...
  • 08:58:17 <drlimbo> same as typoscript page.headerData
  • 08:59:28 <mneuhaus> from where? a page template, content element, plugin, etc?
  • 09:00:24 <drlimbo> sorry, from fluid page template where i load all scripts and css with v:asset.
  • 09:02:44 <mneuhaus> https://fluidtypo3.org/viewhelpers/vhs/master/Page/HeaderViewHelper.html
  • 09:02:46 <mneuhaus> ?
  • 09:04:27 <drlimbo> haha, its that easy =P thanks mneuhaus
  • 09:04:46 <mneuhaus> you're welcome
  • 09:04:48 <drlimbo> didn't now about page.header - and somehow i didnt found it in the documentary
  • 16:02:14 <Outdoorsman> Does anyone know how can I show all content elements on a page from another page that are filtered by tags each CE was given?
  • 16:29:17 <NamelessCoder> hey Charles.
  • 16:29:41 <NamelessCoder> I think your only option here is to use a controller and the category API
  • 16:30:00 <NamelessCoder> it should allow you to select all records from tt_content which have a particular category or tag
  • 16:30:10 <NamelessCoder> but I'm not sure what the API is...

20150729

  • 04:48:16 <Guest|65519> Hi guys. Quick question; I have a table containing a couple thousand records. I need to be able to select one or many of these records to form an arbitrary group that is later rendered on the page. Basically, you select a few records and those are thrown into a table. That's all. So far, I tried to achieve this using a simple select-box, as well as
  • 04:48:16 <Guest|65519> flux:field.relation, both in combination with flux:wizard.suggest. Sadly, neither works as intended. I can fill the select-box by using a custom viewhelper, but that implies loading all records right away, which might slow things down and seems pretty unnecessary. I also couldn't get the suggest-wizard to list any entries at all. flux:field.relati
  • 04:48:16 <Guest|65519> on, on the other hand, does work with the wizard, but it also loads all the records right away. Further, I was not able to show any other value than that of the first column of the record. It's numeric and pretty non-descriptive, an obvious no-go. I'm pretty new to this stuff, so please forgive any obvious ignorance. I did look at fluidtypo3 refere
  • 04:48:16 <Guest|65519> nce, but my questions remain the same. Using Typo3 version 6.2.1, fluid 7.2.1.
  • 04:55:05 <Guest|65519> Sorry, 6.2.13, not 6.2.1
  • 05:05:57 <ToM04> hi, I am just starting with fluidcontent and try to build a simple Content-Element
  • 05:06:21 <ToM04> but now I get an error in the frontend. would be nice if someone could help me.
  • 05:09:12 <featdd> ToM04: what error?
  • 05:10:29 <ToM04> #1225709596: The template files "/srv/www/nginx/typo3conf/ext/wu_template/Resources/Private/Layouts/Content.html", "/srv/www/nginx/typo3conf/ext/wu_template/Resources/Private/Layouts/Content" could not be loaded
  • 05:11:48 <ToM04> I am not sure why a content.html gets used. my content-element is called testimonial.html
  • 05:17:37 <ToM04> ok. looks like I have to change my page template
  • 08:23:36 <JohPie> jmverges: I miss a button to reopen a issue... :(
  • 08:23:43 <JohPie> in gitHub
  • 08:23:56 <jmverges> what?
  • 08:24:08 <JohPie> https://github.com/FluidTYPO3/flux/issues/792
  • 08:25:22 <jmverges> what happen with that issue John?
  • 08:25:31 <jmverges> JohPie
  • 08:25:43 <JohPie> I have allready this problem
  • 08:26:08 <JohPie> an can reproduce this in different systems
  • 08:26:10 <jmverges> I tried it in master and 6.2 LTS
  • 08:26:40 <jmverges> I can't reproduce it
  • 08:26:46 <JohPie> do you have pages with different settings for disalbe content-Elements?
  • 08:27:13 <jmverges> nop, I just did it in the template of the site
  • 08:27:16 <jmverges> in my root
  • 08:27:49 <JohPie> I think you don't understand the issue (or I have explain it wrong)
  • 08:28:31 <JohPie> oh... I think I forgott something in explain
  • 08:29:05 <jmverges> please explain it better
  • 08:29:22 <jmverges> you can write in a closed issue
  • 08:29:54 <JohPie> it doesn't work, if you have the disable-setting only for some pages
  • 08:30:19 <mneuhaus> jmverges fyi here's the wip pr for responsive images: https://github.com/FluidTYPO3/vhs/pull/875
  • 08:30:22 <jmverges> please, update the issue properly if you don't mind and I will take a look
  • 08:30:33 <jmverges> mneuhaus: I saw it
  • 08:31:16 <jmverges> There is a phpcs problem
  • 08:31:23 <jmverges> https://travis-ci.org/FluidTYPO3/vhs/jobs/73094513
  • 08:31:36 <jmverges> but it looks good to me in general
  • 08:31:53 <JohPie> jmverges: I update my last comment
  • 08:32:06 <mneuhaus> the srcset implementation isn't as clean as i'd like yet. will fix that phpcs issue of course ;)
  • 08:32:44 <jmverges> mneuhaus I think your viewhelper will be very useful
  • 08:34:11 <mneuhaus> yep, theyre looking suprisingly simple + useful :)
  • 08:34:27 <jmverges> JohPie, could you explain each step to reproduce it? the comment is a bit lazy for me. Imagine I just have a clean installation
  • 08:35:30 <JohPie> ok
  • 08:45:02 <jmverges> thank you JohPie
  • 08:45:33 <jmverges> I will take a look when I have a bit of time, maybe not today but sure tomorrow
  • 08:45:48 <jmverges> did you update all FT3 extensions to the last ones?
  • 08:46:03 <jmverges> I was working the other day with Wizard and cache problems
  • 08:47:21 <JohPie> flux, fluidpage, fluidcontent have a fresh pull from master
  • 08:49:14 <JohPie> in development the disable setting doesn't work anymore, but I will test it more then one time befor open a issue
  • 10:42:40 <IntVa> hi
  • 10:43:39 <IntVa> anyone here to help? ;)
  • 10:51:56 <IntVa> Is it possible to create a CE that works like IRE? a set of eg. inputs as a "section" that can be added unlimited
  • 10:53:43 <mneuhaus> IntVa: yep it's called a section, you can check out this content element as an example:
  • 10:53:43 <mneuhaus> https://github.com/bootstraptheme-for-typo3/fluidcontent_bootstrap/blob/development/Resources/Private/Templates/Content/NavigationList.html
  • 10:54:23 <IntVa> thx, I check the link!
  • 10:54:58 <mneuhaus> you're welcome
  • 10:56:02 <mneuhaus> don't stumble over the {items} array you get, each item is an array of the "type" of item
  • 10:56:10 <mneuhaus> because you can have different types of items
  • 10:56:22 <mneuhaus> like in that example above, you have header, item or divider
  • 10:57:06 <mneuhaus> take a peek at the resulting {items} array and i think you'll get what i mean :)
  • 10:58:18 <IntVa> ok. and the object(s) are needed. or is it just the section that builds it like IRE
  • 10:59:01 <mneuhaus> yes, you need the object a objects describes the fields the items have
  • 10:59:31 <IntVa> alright. I give it a try
  • 13:37:06 <xaver> mneuhaus: is edge compatible to src-set
  • 15:14:40 <mneuhaus> you mean ie=edge?
  • 15:14:53 <mneuhaus> not sure, i only readup a bit yesterday myself
  • 15:19:28 <xaver> mneuhaus: maybe you need to pay for it in Windows10
  • 15:21:53 <jmverges> fuck windows
  • 15:22:01 <jmverges> fuck ie
  • 15:26:00 <mneuhaus> xaver: i guess the polyfill will take care of cases like that
  • 15:26:19 <xaver> https://twitter.com/h0uz3/status/626426845051912192/photo/1
  • 15:26:34 <mneuhaus> …
  • 15:26:36 <mneuhaus> omg
  • 15:26:58 <mneuhaus> windows 10 free to download an install
  • 15:27:00 <xaver> :)
  • 15:27:51 <mneuhaus> would you like to speed up the boot time of your apps? you can start this app immidiatly by using 1 shitcoin or wait 15min for it to load. 100shitcoins cost 19.99€
  • 15:28:15 <mneuhaus> windows 10 with in-osx-purchase
  • 15:28:27 <mneuhaus> -x
  • 15:29:54 <xaver> mneuhaus: reboot later button usage $5
  • 15:30:06 <mneuhaus> 3shitcoins
  • 15:30:12 <xaver> and for security - pay per login
  • 15:30:21 <xaver> no hacker will pay for yyou
  • 15:30:28 <mneuhaus> you need to hide costs behind coins, makes more money
  • 15:30:47 <mneuhaus> because you don't "pay with money"
  • 15:31:09 <jmverges> did you start in computers with windows?
  • 15:31:44 <mneuhaus> me? yep, used 95,98,2k,xp and vista
  • 15:31:56 <mneuhaus> after vista 2 years ubuntu, then mac
  • 15:33:02 <xaver> i can't see appserver sessionbeans anymore -_-
  • 15:34:48 <jmverges> I started with msdos and 3.11, now even my father uses ubuntu
  • 15:35:23 <mneuhaus> toyed with msdos and 3.11 on the pc of a friend, but my first own pc was a pentium 2 with win95
  • 15:44:09 <jmverges> the only "good" thing microsoft did was putting "cheap" computers in our homes. the bad thing about that is people used to work with it. how many lost and paid hours of developers in projects doing fucking crossbrowser for fucking IE?
  • 15:44:46 <xaver> jmverges: windows is good for a lot of things :)
  • 15:45:10 <jmverges> oh, xaver, come on...
  • 15:45:55 <xaver> downlaod linux, laughing at people with it, windows10 shurly pushes South Park freemium episode in Emmys
  • 15:46:14 <jmverges> hahahahaha
  • 15:54:06 <jmverges> mneuhaus: what about the phpcs thing?
  • 15:54:34 <mneuhaus> jmverges: sorry, didn't come to it yet :(
  • 15:54:39 <mneuhaus> tomorrow i hope :)
  • 15:54:44 <jmverges> great
  • 15:55:10 <mneuhaus> + a few other tweaks :)
  • 18:27:35 <xaver> mneuhaus: http://blogs.windows.com/msedgedev/2015/06/08/introducing-srcset-responsive-images-in-microsoft-edge/

20150730

  • 00:24:54 <mneuhaus> xaver: lol :D "Note: In order to ship our implementation of srcset in time for Windows 10, Microsoft Edge currently does not support the width (w) descriptor – we’re working on adding this in a future update."
  • 00:25:07 <mneuhaus> the width descriptior is the most useful part ^^
  • 00:43:20 <intva> good morning ;)
  • 00:44:34 <intva> I have a strange problem. made a simple file field, saved an image. in the var the whole path and the imagename is saved but v:media.image just renders the URL. same with f:image
  • 01:58:13 <rosieres> intva code?
  • 02:13:51 <intva> hi rosieres. right now I changed it to fal inside the sections. but this doesn't work too
  • 02:14:19 <intva> is it possible to use flux:field.inline.fal inside a section-object
  • 02:15:25 <intva> this is my code: http://pastebin.com/i0e6tQST
  • 02:15:52 <MarcHH> Hi. When using the TYPO3 content element "Insert Record" to make a reference to another content element I get an error in the FE which breaks down to the wrong SQL-statement "SELECT * FROM tt_content WHERE uid IN () ORDER BY sorting ASC". TYPO3 6.2.14, current flux,vhs etc. PageProvider build with FluidPowered TYPO3, content rendering with fluidcon
  • 02:15:52 <MarcHH> tent_core. Any idea?
  • 02:16:38 <rosieres> intva -> field: 'object.previewImage' ??
  • 02:17:04 <rosieres> IC
  • 02:19:38 <intva> @rosieres what do you mean?
  • 02:20:36 <rosieres> intva: first. you are good advised to use settings array instead of object.
  • 02:23:17 <rosieres> intva: this 100% works -> http://codeshare.io/f5IhY
  • 02:24:56 <intva> hmm. ok settings made the trick
  • 02:24:57 <intva> thx
  • 02:25:09 <intva> can I ask one more question ;)
  • 02:25:22 <rosieres> intva: this is because settings is automatically propagated
  • 02:25:28 <intva> ah ok
  • 02:26:42 <intva> when I select the fal image I get an error "Wrong configuration in table 16cbf816a0"
  • 02:27:00 <intva> I have to save the "empty" content-element and then saving the fal image is possible. any idea?
  • 02:28:22 <rosieres> intva: is it a clean install or did you upgrade flux and so on?
  • 02:28:55 <intva> upgrade
  • 02:29:27 <rosieres> clear caches, run update scripts, then compare installtool
  • 02:30:00 <intva> ok. and one more thing ;), sorry, but this are my first tries with fluidcontent
  • 02:30:21 <intva> I want to translate the name/label of the fields inside the section/object
  • 02:30:41 <intva> I have <trans-unit id="flux.downloadsCE.fields.previewImage">
  • 02:30:41 <intva> <source>Preview-Image</source>
  • 02:30:41 <intva> </trans-unit>
  • 02:31:00 <intva> but in the backend no "text" shows up
  • 02:31:24 <intva> other translations outside of sections work
  • 02:31:48 <rosieres> you are good advised to put translations in external file
  • 02:32:09 <intva> yes they are in a locallang file
  • 02:34:38 <rosieres> intva: gist the code for the files
  • 02:34:50 <rosieres> https://gist.github.com/
  • 02:35:15 <intva> https://gist.github.com/anonymous/27a9ec97685778354a4c
  • 02:35:35 <rosieres> and the rest?
  • 02:36:00 <rosieres> you can put multiple files in a gist
  • 02:36:16 <intva> is exactly like the pastebin from before
  • 02:36:35 <rosieres> yes. But I want to see the code of the reference
  • 02:37:43 <intva> https://gist.github.com/anonymous/1b8e0b0461f0c9ed4213
  • 02:38:41 <rosieres> is this only true to FAL?
  • 02:39:17 <intva> no to all fields inside the section
  • 02:39:40 <rosieres> preview or main?
  • 02:39:56 <intva> preview
  • 02:40:15 <intva> ehm, I mean when saving the content-element
  • 02:40:53 <rosieres> <f:if condition="{preview}==1"> wtf is that?
  • 02:40:54 <FT3BOT> ¯\_(ツ)_/¯
  • 02:41:32 <intva> haha, yes it is just for me testing and quick and dirty
  • 02:42:35 <rosieres> and why don't you set settings.previewImage ? in form.object
  • 02:46:47 <MarcHH> Hi again. :-) When using the TYPO3 content element "Insert Record" to make a reference to another content element I get an error in the FE which breaks down to the wrong SQL-statement "SELECT * FROM tt_content WHERE uid IN () ORDER BY sorting ASC". TYPO3 6.2.14, current flux,vhs etc. PageProvider build with FluidPowered TYPO3, content rendering wit
  • 02:46:47 <MarcHH> h fluidcontent_core. Any idea?
  • 02:47:23 <rosieres> intva: you are also good advised to use sheets -> flux:form.section -> flux:form.sheet
  • 02:47:46 <MarcHH> I've seen related bug reports (#103, #160) but can't figure out which is already fixed and which may be a good/bad idea to patch locally...
  • 02:48:32 <rosieres> MarcHH in flux?
  • 02:50:35 <MarcHH> fluidcontent_core
  • 02:51:10 <rosieres> MarcHH no open issues. So I shall be fixed.
  • 02:51:29 <rosieres> https://github.com/FluidTYPO3/fluidcontent_core
  • 02:52:04 <rosieres> are you running TER or git version?
  • 02:52:12 <MarcHH> https://github.com/FluidTYPO3/fluidcontent_core/issues/164
  • 02:53:05 <MarcHH> it seems that one of the "fixes" have broken this. Is there any "best practice" to handle this problem?
  • 02:53:49 <rosieres> ARE YOU RUNNING TER VERSION?
  • 02:54:05 <MarcHH> yes
  • 02:54:27 <rosieres> then take the git developent branch which has the fix in
  • 02:55:12 <MarcHH> ok, thanks. I'll try this.
  • 02:55:25 <rosieres> you know hwo?
  • 03:00:30 <MarcHH> pulling from git and deploying on the server? :-)
  • 03:00:49 <rosieres> y
  • 03:01:16 <MarcHH> yes, thank you.
  • 03:08:46 <intva> ok, but will using sheets solve my translation problem?
  • 03:09:45 <MarcHH> Thanks rosieres, dev branch seems to solve the problem. (y)
  • 03:13:29 <rosieres> good
  • 03:16:32 <rosieres> intva: removing unessecary nesting and using sheets as best practice should make it easier. And maybe the translation then appears.
  • 03:17:54 <intva> but unessecary nesting? I just want a section with some fields inside. thats it
  • 03:19:41 <rosieres> intva: see the first listing -> https://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/language-usage.html
  • 03:20:13 <rosieres> <form><form.sheet></form.sheet></form>
  • 03:20:34 <intva> form-form.sheet.section.object.field
  • 03:21:24 <rosieres> forget object
  • 03:21:32 <rosieres> you are using settings array
  • 03:21:51 <intva> ok, I thougth object is needed inside sections
  • 03:21:56 <intva> I give it a try
  • 03:23:03 <rosieres> section is older stuff.
  • 03:23:47 <rosieres> section is toplevel now
  • 03:58:09 <sitegeist_alex> Good morning everybody! If have a question regarding https://github.com/FluidTYPO3/vhs/issues/808
  • 03:59:40 <sitegeist_alex> We are still in progress with the update of vhs and found out that the following was working before the update of vhs to the current development branch:
  • 03:59:51 <sitegeist_alex> <v:resource.image identifier="{v:content.resources.fal(field: 'image') -> v:iterator.extract(key: 'id') -> v:iterator.first()}" maxWidth="150" />
  • 04:00:13 <sitegeist_alex> this generated an <img>-Tag and now it only results in "Array"
  • 04:02:46 <sitegeist_alex> This behaviour has been introduced in commit 0630c1a
  • 04:03:34 <sitegeist_alex> Could you reopen the issue #808 so that I can fix that?
  • 05:47:59 <rosieres> jmverges long time not seen. I saw you envolved :-)
  • 05:48:13 <jmverges> hi rosieres, yeah mate
  • 05:48:21 <jmverges> I had a bad months
  • 05:49:35 <jmverges> stress plus anxiety, I left the job, I study sailing and know I'm back to code ;)
  • 05:53:55 <rosieres> hopefully you are fine again!
  • 06:00:10 <NamelessCoder> sitegeist_alex is <v:resource.image> itself outputting "Array" or does it put "Array" as identifier? In any case: issue re-opened!
  • 06:02:01 <7GHAAT81V> [builder] NamelessCoder closed pull request #71: [TASK] Updated extension name field description (development...updateLabel) https://github.com/FluidTYPO3/builder/pull/71
  • 06:02:01 <18VAADLRE> [builder] NamelessCoder pushed 2 new commits to development: https://github.com/FluidTYPO3/builder/compare/62a96cd8e2f6...6617cecc1b04
  • 06:02:01 <18VAADLRE> builder/development cfb5992 jmverges: [TASK] Updated extension name field description
  • 06:02:02 <18VAADLRE> builder/development 6617cec Claus Due: Merge pull request #71 from jmverges/updateLabel...
  • 06:53:38 <Guest|67067> hi, I have fluidcontent_core running and want to add a checkbox to the upload.html. is this possible?
  • 08:03:25 <moger-xx> I am running fluidpages and have a page template "category" with a corresponding categoryAction in my pageController. I also have a "detail" template with a detail action. Now , in categoryAction, I want to forward to detailAction. I get an exception: "Could not analyse class:Tx_ConMyprovider_Controller_PageController maybe not loaded or no autol
  • 08:03:26 <moger-xx> oader?"
  • 08:03:41 <moger-xx> i simply do $this->forward('detail');
  • 08:04:39 <moger-xx> what I want to archieve is a typo3 page that switches dynamically between two page templates.
  • 08:05:14 <moger-xx> of course I could also do this with one template, a variable and two partials but i prefer two distinct actions and templates.
  • 09:13:00 <Timross> Hi, I'm trying to override one of the partials in fluidcontent_core with my own partial in my extension. but it doesn't seem to work.
  • 09:14:16 <Timross> I've added the following to my setup text in my ext,
  • 09:14:18 <Timross> plugin.tx_fluidcontentcore.view {
  • 09:14:25 <Timross> partialRootPaths.1 = EXT:site_distribution/Resources/Private/Partials/
  • 09:14:36 <Timross> }
  • 09:15:27 <Timross> but what ever I do it always uses the partial from the core.
  • 09:16:31 <Timross> it looks correct in the typoscript object browser in the backend.
  • 09:16:39 <jmverges> you cleared cache?
  • 09:16:46 <Timross> yep :-)
  • 09:17:01 <jmverges> did you make your extension depends on fluidcontent_core in emconf?
  • 09:18:34 <Timross> well, it was set up with the 'site' kickstrater
  • 09:18:57 <Timross> and I haven't modified any dependencies.
  • 09:19:12 <jmverges> I don't know really
  • 09:19:39 <jmverges> right know I'm with other stuff, take a look in fluidtypo3.org documentation and logs
  • 09:20:07 <Timross> I was debugging TYPO3\CMS\Fluid\View\TemplateView->getPartialPathAndFilename()
  • 09:21:34 <Timross> And the paths that get checked are
  • 09:21:37 <Timross> 0 /var/www/vhosts/typo362fluid.dev/httpdocs/typo3conf/ext/fluidcontent_core/Resources/Private/Partials/
  • 09:21:53 <Timross> 1 /var/www/vhosts/typo362fluid.dev/httpdocs/typo3conf/ext/site_distribution/Resources/Private/Partials/
  • 09:22:04 <Timross> Which seems to be the wrong way around.
  • 09:22:21 <Timross> It always matches the core first.
  • 09:22:55 <Timross> In one of my news overrides it works perfectly and puts my override first.
  • 09:26:26 <Timross> plugin.tx_news.view.partialRootPaths.2 = {$plugin.tx_sitenews.view.partialRootPaths.default}
  • 09:27:03 <Timross> where the variable is EXT:site_news/Resources/Private/Partials/
  • 09:30:12 <jmverges> if you think it is an issue, feel free to open one in github
  • 09:30:51 <Timross> I just wondered if anyone had seen to problem or been successfull.
  • 09:31:21 <Timross> I will try and make a unit test that illustrates the error
  • 09:31:34 <xaver> unittests are always welcome :)
  • 09:38:16 <Guest|82794> Hi I get the error '"" is not a valid template resource URI.' if I use the current development flux version
  • 11:02:38 <Timross> For anyone that is interested, the FluxService has a method getDefaultViewConfigurationForExtensionKey() that sets the default template root paths at index 10
  • 11:02:44 <Timross> plugin.tx_fluidcontentcore.view.partialRootPaths.10
  • 11:03:30 <Timross> So trying to override the code templates by setting a value at the index 2 doesn't work
  • 11:03:43 <Timross> because the root paths are sorted by index.
  • 11:04:05 <xaver> content core normally supports different variants and versions of them
  • 11:04:31 <Timross> but the default view config always gets called.
  • 11:04:59 <Timross> so it's actually getting set in the setup.txt and in the php.
  • 11:05:26 <xaver> Timross: https://github.com/FluidTYPO3/fluidcontent_core/#concept-overlaying-and-overriding
  • 11:06:54 <Timross> facepalm.
  • 11:09:17 <Timross> I don't want a variant though, I want to ALWAYS render an image in a custom way. So I want to make use of the overlay functionality that comes wiht the templateRootPath method
  • 11:09:53 <Timross> the fact that the content_core typoscript sets the index at 0. implies that I can override it at .1
  • 11:10:04 <Timross> But that's not the case as it is also set at .10
  • 11:12:20 <Timross> but I do understand that variants are a flexible solution.
  • 11:13:39 <xaver> Timross: https://github.com/FluidTYPO3/fluidcontent_core/blob/development/Configuration/TypoScript/setup.txt#L10
  • 11:14:36 <xaver> you can set some defaults and stuff...
  • 11:17:37 <Timross> Ah ok. So In my extension, I can set plugin.tx_fluidcontentcore.settings.image.variant = ...
  • 11:18:20 <Timross> And that will mean that the image is always rendered with the variant from my ext.
  • 11:22:43 <Timross> I was also trying to override a partial and not a whole content object. I guess this only works for CoreContent elements?
  • 11:23:55 <xaver> yeah
  • 11:24:45 <Timross> ok, cool. Thanks for your help
  • 11:27:26 <Timross> ha, I just checked the latest version of https://github.com/FluidTYPO3/flux/blob/development/Classes/Service/FluxService.php#L290
  • 11:27:45 <Timross> the default index is now set to .0
  • 11:28:01 <Timross> I've just got an older version.
  • 11:28:46 <Timross> fixed in dev, but not master yet.
  • 11:30:58 <xaver> Timross: master is only the release from TER
  • 11:50:51 <Timross> @xaver: I installed with composer, but it's all cool. It's working now. Just took me a while to get it all straight in my head. Thanks for your help
  • 15:04:38 <Outdoorsman> Hi again NamelessCoder. Boris Schauer (mrboe) Just tipped me off to adding `\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addToAllTCAtypes('tt_content','--div--;Categories,categories','');` to `ext_tables.php` of my provider extension, which makes the Categories tab and it's contents appear on TYPO 7.2 content elements now. For some reason the categories just quit showing up on content elements with the advent of TYPO3 7.2 though it was
  • 15:04:38 <Outdoorsman> worked out of the box in 6.2 and 7.1. I submitted a Forge issue for it... https://forge.typo3.org/issues/68650

20150731

  • 07:47:43 <mneuhaus> drlimbo: https://github.com/FluidTYPO3/vhs/pull/875
  • 08:33:17 <Konstantin> Hey everybody!
  • 08:33:25 <Konstantin> First time here. Seems nice :)
  • 08:40:27 <Konstantin-sal> I've made a custom HTML template file for content element made inside my FLUID extension. How can i add images using standard backend tab Images ? It isn't even activated by default... Here is the file with my gallery
  • 08:40:41 <Konstantin-sal> https://www.filepicker.io/api/file/ZUs4OTOmRU2hs3ES0ezp
  • 08:54:56 <jmverges> I'm taking a look to it
  • 08:55:24 <jmverges> this all is related with the provider I thinkç
  • 08:59:14 <jmverges> Konstantin-sal: do you have a controller also?
  • 09:01:21 <jmverges> your template is not working
  • 09:07:00 <jmverges> hey again
  • 09:07:12 <jmverges> your template is not working for me
  • 09:07:32 <jmverges> I really don't understand what are you trying to do but it looks a bit complex for me
  • 11:05:32 <Konstantin-sal> It's working for me. I don't have a controller. This is a part of generated extension by Builder ext.