IRC logs

20150805

• 04:01:29 <pedda> hi there
• 04:01:52 <pedda> any clue why EXT:flux might add empty lines to the resulting flexform in db?
• 04:05:34 <jmverges> hi there pedda
• 04:05:35 <jmverges> no idea
• 04:05:40 <pedda> hey juan
• 04:05:41 <jmverges> it is causing some problem?
• 04:05:51 <pedda> yepp
• 04:06:05 <pedda> i had this once, and solved it somehow
• 04:06:41 <jmverges> if you think it is an issue, just open a ticket
• 04:07:55 <pedda> for instance: https://gist.github.com/wikipeter/a87b85f5bdb12977709a
• 04:08:02 <pedda> naah .. not sure
• 04:09:09 <pedda> it's rather like i've been cleaning up some code after someone else messed it up.. and i realize i stumble on the same issues periodically
• 04:10:00 <pedda> i should document any solutions to problems i solved in the past somewhere ..
• 04:11:25 <pedda> the symptoms of such a broken flexform are backend messages appearing at the top or extdirect debug messaages while hiding a page via context menu in the page tree
• 04:12:10 <pedda> Fatal error: Cannot use string offset as an array in /var/www/public_www/example.com/typo3conf/ext/fluidpages/Classes/Provider/PageProvider.php on line 244
• 04:12:25 <pedda> which is obvious if flexform contains empty lines
• 04:12:33 <jmverges> well, no idea
• 04:13:04 <pedda> i would expect flux to write all values to the flexform.. regardles if any checkbox/input field was touched by the user
• 04:13:30 <pedda> but it seems as if only those few are written, which have been modified by the user, rather than all
• 04:32:44 <pedda> maybe an inheritance issue
• 04:34:17 <pedda> if my root page has a flux setting set to true, and this setting also appears in a different page template on a page beyond the root page, the value of the setting (set to true) is inherited when i begin to edit the page properties of that child page
• 04:36:47 <pedda> if i set that property to false only this property gets saved to flexform
• 04:36:55 <pedda> others are replaced by empty lines
• 04:37:33 <pedda> nut sore if i get inheritenca right..
• 04:37:40 <pedda> -a +e
• 05:09:24 <pedda> jmverges i filed a bug ticket https://github.com/FluidTYPO3/flux/issues/878
• 05:09:31 <pedda> :)
• 09:25:18 <BennyS> Hi guys! I have a question regarding vhs. Is it possible to render HTML like that using the v:asset Viewhelper? <script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
• 09:26:13 <BennyS> When i try <v:asset.script external="1" path="//url"> i get an error, because i didnt use http:
• 10:43:27 <Guest|89401> Hello! I am using a TYPO3 System in Version 7.3.1. It is not possible to install the fluid site kickstarter package because the version of typo3 is higher than the extension is. nevertheless i could install the extensions, but get the error message in frontend. does anybody know if updates of the extension "fluidcontent", "fluidpages", "builder" an
• 10:43:27 <Guest|89401> d "fluidcontent_core" are planned?
• 10:50:57 <rosieres> namelessCoder in?
• 10:51:20 <rosieres> NamelessCoder in?
• 11:14:18 <rosieres> NamelessCoder now in ?
• 11:15:13 <rosieres> Have a guy here with a problem with his DS as hierarchy. Can I pass him to you, because it seems a bit complicated.
• 13:15:38 <pedda> is it possible to use v:content.render to render a formhandler plugin and assign data to the element via loadRegister="{recipient: '{company.email}'}" attribute and use that register within formhandler ??
• 13:16:10 <pedda> or is this rather usable for csc elements