IRC logs

20150706

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

IRC log range: 20150706*

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