09:44:40 <mrboe> also this : flexform.field.wizard.abstractWizard
09:44:52 <randomresult> or flexform.field.wizard.abstractWizard - cause me and mrboe are trying to get the xsd-files working with autocomplete again in phpstorm
10:32:56 <hans> i got a question about making a page-template with a form (like: contact) and adding some config in the page-config, like "send to e-mail"
10:33:12 <hans> is it posible to make such a template
10:33:39 <hans> maybe to use the normal typo3 from record on it?
10:34:10 <bjo3rn> hi hans. either that or one of the available extensions like formhandler.
10:35:21 <hans> do you got an example template? so i can orientate myself?
10:36:20 <cedricziel> hi hans, the core has ext:form
10:39:13 <hans> oh, started to early :-/, i need to know a basic workflow how to make such a template!
10:40:27 <hans> i can manage it by making a normal page tpl and than add it by hand; but i asked myself if it can be done automtic, and just an e-mail adress is added where to send the msgs to
11:08:01 <bjo3rn> hans I think you should ask in #typo3 as this is not really fedext specific.
12:49:38 <randomresult> i just check out the new fluidcontent_core extension
13:15:59 <crus_e> hey guys! is it generally possible to put a <f:form> within a <v:render.request>? my submit action is ignored and i'd guess that it is just ignored because it gets called via <v:render.request action="index" ...>. any hints and/or traps?
13:25:15 <cedricziel> crus_e: Hi, f:form does nothing except rendering a form tag, there's no special vodoo involved :)
13:40:35 <crus_e> maybe i misunderstood the workings of fluidcontent but i used it to embed usual T3-plugins and have a nice collection of FCEs. it all works like a charm but with fluid forms. my guess is that <v.render request action="index" ...> never gets overwritten by the forms action (makes sense, why should it..)
13:42:21 <crus_e> is this a solved problem or should i just stick with a plugin?
13:50:45 <crus_e> reflecting the problem, i think <v:render.request /> should watch out for the GET param [action]=submit and overwrite the hardcoded action="index" accordingly if given
13:52:08 <crus_e> this behaviour would make it compatible with existing code as well as it would solve the form problem
14:00:54 <randomresult> if my when using the new fluidcontent_core extension (textelement) and i display that in the frontend - no p-tags are rendered in the textelement (its format.html right now - but format.raw does not change anything) any ideas how to get this infomrations from the RTE field?
14:23:45 <NamelessCoder> don't merge those yet, has bad protocol for link(s)
16:23:49 <randomresult> and then will look at the menu again... u scared me...
16:24:19 <NamelessCoder> don't be scared, all code is still there - just in a new place
16:24:41 <cedricziel> MindSpark: All good and fluffy?
16:25:37 <MindSpark> cedricziel: sort of, I am starting with the page attributes first. I had looked at VHS a couple of weeks ago. I believe they shouldn't be that hard….
18:05:36 <1JTABH0XM> [flux] bjo3rnf closed pull request #412: [FEATURE] Data storage on Form components and ViewHelpers (development...componentdatastore) https://github.com/FluidTYPO3/flux/pull/412
18:05:36 <21WABY6SZ> [flux] bjo3rnf closed pull request #410: [DOC] Truncated contribution mini-guide pointing to new location (development...development) https://github.com/FluidTYPO3/flux/pull/410
20:38:06 <randomresult> anyone using neos in here?