07:58:12 <tpinne> I just installed a fresh T3 7.2 and used the fluidtypo3 site starter for the first time. Everything worked out of the box, despite when I create a new content element there are no input fields, the text content type is not available and so. Are there known incompatibilities with 7.2? Especially with fluidcontent_core maybe?
08:10:05 <tpinne> If I uninstall fluidcontent_core and install css_styled_content I get the normal forms I know
08:10:32 <tpinne> If I uninstall both, it is the same es with fluidcontent_core
08:20:26 <NamelessCoder> tpinne if by "text" you meant "textpic" then yes, this one is removed in fluidcontent_core.
08:23:12 <NamelessCoder> the TCA is also quite different for CSC/FCC and I'm not sure if it already happened in 7.2, but the plan was to remove CSC TCA from the core itself and move it to CSC so if that happened, there may be even less of the TCA you're used to seeing.
08:24:36 <tpinne> no, I meant the normal "text", not "textpic"
08:25:03 <tpinne> ok, so it seems that the csc TCA has been removed from the core?
08:25:23 <tpinne> Something on which you rely in the current version of FCC?
08:26:17 <tpinne> This would explain why I only see input field with CSC installed
08:31:34 <tpinne> if I have both extensions installed I see the normal form elements + the FCC flexform example elements for header and container class names. And the FE renders the FCC html
08:32:19 <tpinne> But the github pages state that these extensions can't be used together, so I guess there will be problems later on?
13:44:35 <pedda> seems as if i need a custom provider
13:44:37 <NamelessCoder> TS, custom form components, custom ViewHelpers etc. can load these possible values for you
13:44:46 <NamelessCoder> - or a custom Provider, of course.
13:44:54 <pedda> but i also managed to retrieve and preprocess the data by the help of viewhelpers
13:45:17 <pedda> but i have another question claus
13:45:31 <pedda> this is a snippet of mine: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=21&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=7a7647c69217d82c66f625123b9a5581
13:45:57 <pedda> since 19th march it stopped working
13:46:23 <pedda> there was some automagically created Preview section refactoring going on
13:46:39 <pedda> which broke the typoscript based flux feature i think
13:46:54 <NamelessCoder> off the bat, those two shouldn't be related at all
13:47:06 <pedda> the problem is: Preview Section is missing
13:47:18 <pedda> if flux is specified via typoscript
13:48:41 <pedda> it all starts with the following error message: #1257246929: "" is not a valid template resource URI.
13:48:56 <NamelessCoder> right, the PreviewView assumes a template file
13:50:27 <pedda> after some digging it seems as the whole process gets stuck here: http://codeshare.io/GjXjx
13:51:23 <pedda> can i improve my ts setup to disable a preview section requirement?
14:01:56 <pedda> bjo3rn fixed this one: https://github.com/FluidTYPO3/flux/pull/832
14:02:19 <pedda> while dealing with https://github.com/FluidTYPO3/fluidpages/issues/256
14:02:54 <pedda> this actually is fixed, but this fix does not affect all doctypes
14:03:06 <pedda> i have still an issue if page is an external url
14:03:41 <pedda> as a workaround i was able to add required doctypes in the em settings of EXT:fluidpages
14:04:38 <NamelessCoder> correct me if I'm wrong, but a non-standard doktype also means that the fluidpages fields should not display, UNLESS you add those doktypes in the config
14:04:46 <pedda> this can be simulated if you change the doctype of a standard page (which already contains any flux/flexform) and set it's type to external url for instance