10:00:00 <batjony> gbod: why most of the fluid TER extensions include the ,git folder
10:01:56 <rosieres> Is it a feature or a bug that as soon a pagetemplate is chosen the new ce wizard only has very limited options???
10:04:26 <gbod> batjony: As fa as I can see it's an issue with our current way of ter releasing. But as it doesn't break anything It shouldn't be a problem.
10:05:24 <batjony> depends if you set the whole typo3conf/ext folder in the repo, then issues appear
10:05:50 <gbod> rosieres: Is there a allow/deny clause for content elements in one of you page templates?
10:06:10 <batjony> i still dont use the composer, most likely i will migrate to composer soon, currently i put my project typo3conf/ext folder in a git repo
10:06:31 <gbod> batjony: Why would one put TER extensions in a repo? But sure I see the issue.
10:07:51 <batjony> why ? because, i want easy and smart depployments ! everything I develop is in my local machine, then when I deploy it - everything goes on the live server
10:08:35 <batjony> if some other employee wants to pull it, then he has everything he need - all extensions - a real working environment
10:09:01 <batjony> same number of extensions, same version of extensions
10:11:16 <gbod> batjony - I like to keep changed only stuff in my repo, all the other things are just dependencies. But YMMV.
10:11:37 <gbod> changed by me or other project attendees.
10:12:08 <batjony> ya I know, thats why there are tool like composers, but not all the extensions are properly configured to use composers
10:12:44 <batjony> thats why until everything works fine with Composer, i will keep them all in a repo
10:13:19 <batjony> imagine you have a project with 20 different extensions
10:13:33 <batjony> and on this project works other developers
10:13:52 <batjony> and this project is deployed to a Test Server, Pre-live Server and Live Server
10:14:21 <batjony> its STUPID to configure all the extensions X times and this produce a lot bugs
10:15:13 <gbod> Well, as this is not a deployment channel - let's agree to disagree and stop it - as long as you call me stupid in all caps.
10:16:12 <batjony> the deployments is related to the extension structure
10:18:17 <gbod> batjony: Instead of discussing off topic I did this: https://github.com/NamelessCoder/gizzle-typo3-plugins/issues/1
10:20:49 <batjony> 10x, i have not offended anyone, just sharing info :)
10:21:27 <batjony> of course the best solution is the Composer, but last time i have tried, the composer files were not properly configured in the extensions
10:21:56 <batjony> and also not all typo3 extensions have their composer files
10:22:40 <bjo3rn> I know people who put the complete root folder into a git repo :S
10:23:15 <bjo3rn> but as gbod correctly stated: YMMV.
10:23:43 <bjo3rn> so, I am with you both that .git shouldn't be included in a TER release.
10:25:25 <soma> i agree with that. i was also a bit surprised that they were in the releases
10:54:54 <batjony> hmm some idea why i cant include the fluidcontent_core static template with
11:11:36 <NamelessCoder> no, like I said, bet you it won't render plugins
11:12:09 <NamelessCoder> the reason is the order in which tt_content.* is built and the TS required for rendering plugins is generated
11:12:25 <batjony> you mean that if its included with this way I cant include any plugin in a page ?
11:12:31 <NamelessCoder> css_styled_content is targeted by special name in order to load it first and this targeting only works if the template is included as static from extension
11:13:24 <NamelessCoder> we do this for fluidcontent_core via AdditionalConfiguration.php which is why when this file exists, fluidcontent_core can insert the TS that renders plugins correctly, in the right order, but it HAS to be included as static TS because it gets targeted by special name and this name is only matched if included as static TS
11:13:36 <NamelessCoder> check out the templateparser.
11:16:07 <batjony> k my last project was built with css_styled_content included with INCLUDE_TYPOSCRIPT, there were also some custom plugins included, but didnt meet any issues
11:17:14 <NamelessCoder> all depends on how your plugins are included - but definitely check out the templateparser if you wish to know exactly why it works how it does. It's a very special behavior, one that I've described here and elsewhere quite a few times by now
13:35:53 <rosieres> <flux:field.inline.fal name="myimage" showThumbs="1" enabledControls="{info:1,new:1,dragdrop:1,sort:1,hide:1}"/> opens the media vidi image selector but as soon as I choose an image I run into a wron configuration of tt_content popup message. Anybody ran ever into this?
13:59:47 <mrboe> hey guys some off topic - when i delete typo3temp/* - must i go to install tool and "create" the folders or will they be created if they needed?
14:29:04 <m4d-m4t> hey guys! Just updated flux (7.0.0), fluidcontent (4.0.0) and vhs (1.9.1) to flux (7.1.2), fluidcontent (4.1.1) and vhs (2.1.4). Seems that my own fluidcontent extensions, which is based on fluidcontent_bootstrap, does not work anymore.
14:29:15 <m4d-m4t> I'm getting a "#1257246929: "/home/www/p229323/html/typo3/typo3conf/ext/fluidcontent_drschreibers/Resources/Private/Templates/Content/Experts.html" is not a valid template resource URI. " - exception
14:31:56 <m4d-m4t> and went through the update notes, but could not find any hints. Has someone experienced the same issue and has a solution for this problem? Big thanks!