10:00:05 <oliver_1234> Hi guys. I'm trying out fluidcontent_core with typo3 6.2.1 . When I create a new content element (e.g simple text) I get this error: #1: PHP Warning: array_combine() [<a href='function.array-combine'>function.array-combine</a>]: Both parameters should have at least 1 element in typo3conf/ext/fluidcontent_core/Classes/UserFunction/ProviderField.php
10:41:00 <Harpagophyt> then i have another problem - thx
10:41:24 <Harpagophyt> ah, the css will be written as typo3temp/...
10:42:34 <oliver_1234> use absolute path. /typo3conf/ext/<extkey>/Resources/Public/Images
10:44:47 <Harpagophyt> it works with standalone = 1 rewrite = 0 - solved - thx
11:16:06 <oliver_1234> I'm trying out fluidcontent_core with typo3 6.2.1 . When I create a new content element (e.g simple text) I get this error: #1: PHP Warning: array_combine() [<a href='function.array-combine'>function.array-combine</a>]: Both parameters should have at least 1 element in typo3conf/ext/fluidcontent_core/Classes/UserFunction/ProviderField.php line 63
13:26:16 <soee> hmm strange 'issue' maybe: if i have my provider extension and subdir like Public/foo/bar/baz/sass and compile here css file that is included using asset VH, and in this css file image id used that is in Public/Images (so it has path set like: ../.../../../foo.gif) than on fronted page need 5 seconds to load as it is waiting for this file (is moved to typo3temp ?)
13:26:44 <soee> but if i put my compiled css fiel into Public/Styles and reference image like ../Images/ than all works fine
13:39:47 <Denyerek> AFAIK, images referenced in CSS are processed and cached soee
13:40:01 <Denyerek> To simplify things, I left my SCSS and CSS in the same folder.
13:40:29 <Denyerek> As I don't really care about having the SCSS kept separately (Others may disagree but I couldn't find an easy way)
13:40:48 <Denyerek> Plus it means the paths in the SCSS and CSS are consistent
13:53:21 <soee> Denyerek: the think mught be depth of this path or something
13:55:42 <Harpagophyt> how can i activate this mysterious LLL
15:28:25 <cedricziel> the build artifact is being deployed with an approriate build task that is custom to the target env
15:30:00 <Denyerek> So if someone else were to check our your repo, but didn't have node, npm, grunt, bower and all those other things, they're essentially unable to work until they completely rebuild their environment ?
15:30:25 <Denyerek> I suppose they could work against the mock
16:51:55 <Guest|2703> i got a question regarding flux v7: i've created a flux field "text" and enabled the richtext editor as stated in the docs with defaultExtras. The thing is, when i create links with the RTE they do not get converted into realurl like format but are build with id=x
16:52:17 <Guest|2703> the links are internal ones to other pages