06:56:46 <serogen> hello fluid poewered t3 community
07:00:16 <serogen> i really love your system and i used it in many project. but we have an big problem: we are using 30-40 times and fluidcontent element with and grid system for content areas inside for the box structure, and now the page need 2or3 minutes sometimes to load page in the backend. when i remove the flux grid, the backend page comes in 2 seconds!
07:01:17 <serogen> any idea why? is this a known limitation of fux? or maybe we did something wrong?
10:11:23 <jmverges> 1225709597: The template files "/var/www/jmverges.dev/typo3conf/ext/fluidcontent_core/Resources/Private/Partials/Properties/Menu/", "/var/www/jmverges.dev/typo3conf/ext/fluidcontent_core/Resources/Private/Partials/Properties/Menu/.html" could not be loaded. (More information)
10:21:14 <denis-fluid> Does someone know of a possiblity to get rid of the whitespaces produced by the fluid content elements. I'd like to keep the the indention and new lines in the templates to make them more readable.
10:23:16 <Akii> why not prettyfy the rendered html at the end?
11:12:04 <denis-fluid> And one more: Is it possible to prevent some users from accessing specific fluid content elements? (hide them from specific users)
11:52:00 <bamo> hey guys , how can i render my navigation in my pagetemplate?
11:53:10 <bamo> I kickstarted my own extension with FluidTYPO3 Provider Extension.
11:54:40 <Momodedf> what do you call your navigation ?
11:55:18 <denis-fluid> Akii: What is the correct flux view helper to render an image selection field. (one image)
11:55:39 <denis-fluid> Is it https://fluidtypo3.org/viewhelpers/flux/master/Field/FileViewHelper.html or https://fluidtypo3.org/viewhelpers/flux/master/Field/Inline/FalViewHelper.html
12:00:27 <denis-fluid> Ok fine. Yeah I did try it. Inline/Fal works great. Just thought that there would be a dedicated kind of element for one image selections.
12:00:28 <Momodedf> actualy there is a code snipets
12:01:03 <denis-fluid> And this one got me even more excited: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=17&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=f3733b3bf34ae4e9daf5cd9bb29e9205
12:01:19 <denis-fluid> Allowing only specific FCEs in columns :-)
12:02:25 <Momodedf> yes, its cool when you got a "creative" end user
12:02:39 <denis-fluid> Momodedf: That's the point. :-)
12:03:37 <denis-fluid> Momodedf: Do you know if it is possible to hide certain content elements from specific users or groups?
12:53:02 <oschulz> but the update script issue is a graet problem i think, also when logging is not enabled... my logging wasnt enabled, so i got no message in my log, great
12:53:21 <jmverges> okey, I could agree with that note, however shouldn't be available to select it from the admin, should be?
12:53:36 <Momodedf> oh I didnt noticed it was still available in the liste, cedricziel is there any way to remove it from elements list since its unusable ?
12:53:42 <NIMIUS|johannes> btw, you guys should consider writing a CHANGELOG, that would make updating (in general) a little easier
12:56:07 <NIMIUS|johannes> Here you go: The Changelog episode 127: http://5by5.tv/changelog/127
12:56:14 <cedricziel> jmverges: afaik we cleared all ctypes and re-added them.
12:56:26 <cedricziel> oh i dont like the changelog podcast
12:56:33 <cedricziel> but thank you, i will listen to it
12:57:07 <jmverges> cedricziel, then I should have something wrong in my configuration?=
12:57:27 <NIMIUS|johannes> I can see why - the hosts are a little weird sometimes
12:57:36 <cedricziel> let me cross check it before Claus can proof me wrong ;)
12:59:15 <cedricziel> it's definately removed from the list of possible types: https://github.com/FluidTYPO3/fluidcontent_core/blob/development/ext_tables.php#L51
13:04:14 <jmverges> I did it for an admin in a private platform with codeception framework and I works prety nice
13:04:48 <cedricziel> i would consider it a pain in the butt. as well as is testing the bigami between framework logic (read: extbase plugins), and core plugs
13:05:10 <cedricziel> nevertheless: if you can proof a valuable aproach, i'd be happy to look into it.
13:06:39 <jmverges> cedricziel, at the end the ux is important. If as user I shouldn't see textpic... selenium testing could prevent it
13:07:01 <jmverges> cedricziel, take a look to http://codeception.com/
13:08:45 <oschulz> hey, i looked into fluidcontent_core/class.ext_update.php this script does not work when you already have an AdditionalConfiguration.php
13:09:39 <oschulz> a better message instead of return message "nothing to do" is to warn user to campare the template file with the current file
13:22:18 <denis-fluid> cedricziel: Is it possible to hide certain fluid content elements from users or groups?
14:36:50 <denis-fluid> gbod: Just to make sure if understand it correct. "tt_content.fluidcontent_content.10 >" just drops the frontend rendering. But the rendering in the backend is still there.
14:37:08 <denis-fluid> To drop it there I would have to do "TCEFORM.tt_content.header.disabled =1" I assume
14:37:22 <denis-fluid> (just making sure that I understand it correctly :D)
14:37:51 <gbod> denis-fluid Yes, for the backend you need the TCEFORM stuff
14:40:51 <denis-fluid> cedricziel: Well I don't see any advantage in the standard content elements
14:41:16 <Momodedf> denis-fluid I find headers in backend usefull to name contents and remember what it is a first look
14:41:41 <cedricziel> denis-fluid: 1.) naming elements
14:41:42 <denis-fluid> Momodedf: Yeah that is what I thought about right now when I added the "tt_content.fluidcontent_content.10 >" to the template
14:41:44 <batjony> ok gurus and messengers, do you all use fluidcontent_core instead of css_styled_content, i am just wondering if I could have issues if I switch to fluidcontent_core for new projects ?
14:42:00 <cedricziel> 2.) using the header field in rendering inside the main section
14:42:22 <cedricziel> that move goes bad if done in a rush
14:42:30 <denis-fluid> cedricziel: Ok 1) is valid. 2) I don't know :D
14:42:38 <cedricziel> you have to know the limitations
14:43:02 <NamelessCoder> batjony be aware of your dependencies. Other extensions may require CSC. Incompatibility with CSC is the only real drawback of FCC (not counting the lack of textpic CType for already stated reasons)
14:43:50 <cedricziel> look, there's this field in the db called header, another one for the header type.. even a subheader one. why would you drop the usage of those in favour of a flexform field?
14:43:51 <NamelessCoder> some features offered by CSC such as TS conditional header wrapping are no longer supported; stuff like that you may need to build yourself in the elements that should do this.
14:44:03 <Momodedf> btw cedricziel I removes unsuported CType in TCEFORM (TCEFORM.tt_content.CTyper.emoveItems)
14:46:38 <NamelessCoder> CSC is an explosion of form fields ;)
14:46:52 <NamelessCoder> too bad we can't evict the TCA it generates :/
14:47:09 <Momodedf> End of day, sport time. See you guys tomorrow have nice day
14:47:15 <NamelessCoder> it's like, "you can remove me but I'll never be completely gone! HAHA!" --CSC
14:47:43 <batjony> NamelessCoder: do you have some ideas when the stable version of FCC will come ?
14:55:20 <batjony> and do we expect some new features in the stable version or basicly bug fixes ?
14:59:08 <cedricziel> i think fluidcontent_core works quite well batjony
15:00:02 <cedricziel> it has a basic feature set which needs to be freed from some bugs and we may need to do some ux things and improved handling for developers
15:12:49 <batjony> ok guys, today i have just started a new project from the scratch, so I have installed the latest dev fluid extensions and started to create some page templates
15:13:04 <batjony> i have just created a simple page template http://pastebin.com/1bU0ExRX
15:30:34 <batjony> i dont see options to select a layout provider
15:30:49 <batjony> i have "Page Layout - this page" and "Page Layout - subpages"
15:38:37 <batjony> cedricziel: so where is this "supposed to choose fluidpages as layout provider" ? is it some new feature in fluidpages, because there was not such thing in the past ?
15:47:28 <cedricziel> or use something like feed.ly which is a really nice rss reader
15:50:44 <Guest|61521> Hi Guys, I have just updated flux, cleared the cache in the install tool, deleted all files in typo3temp but I am getting this error when ever i cliick on the page tool Can't inherit abstract function FluidTYPO3\Flux\Form\FormInterface::setParent() (previously declared abstract in FluidTYPO3\Flux\Form\WizardInterface) anyideas?? thanks
15:54:48 <cedricziel> Guest|61521: more information please
15:56:06 <denis-fluid> cedricziel: What is the recommended way for image selection (only one image) in the flux context? At the moment I am using something like "<flux:field.inline.fal name="content.image" multiple="false" />" but for one image the widget feels pretty strange. There is no error when a user tries to upload more than one image. The additional image gets ignored without error messahe.
15:58:18 <Guest|61521> cedricziel - im running typo3 6.2.6, fluidpages 3.1.1, fluidcontent 4.1.0, flux 7.1.1 and i am testing the site with fluidbootstraptheme 1.2.0. Wehn i select any page in the page tree i get the errot 'Fatal error: Can't inherit abstract function FluidTYPO3\Flux\Form\FormInterface::setParent() (previously declared abstract in FluidTYPO3\Flux\Form\Wi
15:58:18 <Guest|61521> zardInterface) in /var/www/testing/typo3conf/ext/flux/Calsses/Form/WizardInterface.php on line 31'
15:58:58 <Guest|61521> sorry that should be in /var/www/testing/typo3conf/ext/flux/Classes/Form/WizardInterface.php
16:05:36 <Guest|61521> cedricziel - cleared the cache in the install tool, system cache, general cache, frontend cache and deleted all files in typo3temp
16:27:38 <cedricziel> did you check the install tool, if categories are enabled for tt_content?
16:28:42 <Guest|61521> cedricziel - any other ideas??
16:29:36 <batjony> cedricziel: yes they are enabled
16:33:31 <cedricziel> well batjony; i guess then it's time to enable the palette on the fluidcontent ctype
16:36:47 <batjony> cedricziel: ufff sorry i just saw that i have used categories.disabled = 1 in the page ts config, something which I have copied from my previous project :)
16:38:56 <batjony> so as I see its should not be a problem to use the sys categories in a custom fluid element ?
16:39:40 <batjony> and FAL is also possible in FCE ?
16:46:39 <cedricziel> yes, via the approach you have already chosen. but danilobuerger knows best about dealing with FAL. maybe he knows how the native images field in tt_content can be leveraged
16:47:40 <danilobuerger> sure you can use fal with fce
17:55:45 <jmverges> hey folks, I'm reading de documentation and I don't understand well the providers
18:00:56 <cedricziel> maybe it helps when you know that fluidcontent and fluidpages are just(tm) using providers to utilize flux for what they are doing
18:04:59 <jmverges> so flux is the providers used by flux are the ones in charge of tt_content and pages?