08:30:34 <soee> page templates from fluidbootstraptheme but the fluidpages extension is required anyway and will result with error in forntent if you dont configure any other template and set
08:33:36 * randomresult does not know how to solve that
08:34:28 <mrboe> perhabs NamelessCoder can give us the information if that yould be possible
09:11:33 <soee> mrboe: quick guess, siply install extension without dependencies, than inside ext_tables.php do a extra check with isLoaded() http://typo3.org/api/typo3cms/class_t_y_p_o3_1_1_c_m_s_1_1_extensionmanager_1_1_utility_1_1_install_utility.html#a99de93336264a537a73d76607cbadac1 and then include related stuff
09:11:59 <soee> also in such cacse some info in extension manager configuration or something would be required to inform user
09:12:17 <soee> that extension will not work until he installes one of dependencies
09:13:26 <mrboe> soee: if you were able to do it it yould be nice to get a PR, this is something i really dont know
09:13:32 <soee> i think "similiar" situation is when you disable templates for bages and content in extension configuration, you have installed fluidbootstraptheme, fluidpages, fluidcontent but you do not use any ot them in the end
09:14:37 <soee> mrboe: ok i kand do PR but please try to catch NamelessCoder and ask if he agree with this concept
10:49:39 <ilCerchiari> Hi Guys, is it possible to use fluidcontent_core features with custom content created with a fluidcontent based ext? I'm having troubles in creating the flexforms.
10:58:12 <xaver> fluidcontent_core uses the fields in tt_content and not the flexform
11:01:15 <ilCerchiari> Sorry maybe I did not explain myself right. What I'm trying to acheive is to have for all content "basic" and custom fce the same behaviour. For example for content header and container, losing them disabling cc_styled_content.
11:15:03 <ilCerchiari> xaver: For example in fce "Appearence" tab results: "Data Structure ERROR: No proper configuration"
11:21:19 <xaver> you have no configruation in your page
11:23:45 <mrboe> xaver perhabs you could give us a awnser about the dependencies problem
11:28:45 <ilCerchiari> Sorry xaver, what do you mean? normal contents work fine, but even if I include what is in fluidcontent_core layouts in my fce layout I end up in the same situation. What am I missing?
11:35:21 <ilCerchiari> I have that and my fce work fine with both css_styled_content and fluidcontent_core
11:35:59 <ilCerchiari> what disappears with the latter is the Appereance tab where in normal contents I can configure header type and class and container
11:36:51 <NamelessCoder> ilCerchiari bugs have been fixed in the typo3 core itself, in exactly these contexts. Unless you are using the git master of TYPO3 CMS you will experience issues in setups which use many custom forms in the same element.
11:37:00 <NamelessCoder> fluidcontent_core qualifies as such content
11:37:43 <ilCerchiari> oh that makes sense, therefore this bug affects 6.2.4 released version, am I correct?
11:38:02 <NamelessCoder> yes, this version is also affected
11:38:29 <ilCerchiari> :( thanks I go cry alone in my corner
11:38:47 <NamelessCoder> in essence the problem is that some parts of TYPO3 still did not pass a required value to hooks. You can check out the git master and use that without any problems though
11:38:47 <ilCerchiari> seriously thanks to all for the help
11:39:23 <ilCerchiari> ah ok I'll give a check, thanks again
11:40:42 <NamelessCoder> you too. By the way if you use fluidcontent_core and have not seen it, https://github.com/FluidTYPO3/fluidcontent_core/issues/35 might be relevant
11:41:36 <ilCerchiari> Nope I missed it, but I've just started my wandering with fluidcontent_. I go read it immediately.
12:42:58 <randomresult> that one was a blast in the past
12:43:20 <randomresult> wait.. no ... that was a past in the blast
12:45:57 <NamelessCoder> danilobuerger everything depends on the level of integration you need, would be easier to make a recommendation if the scope can be (somewhat) narrowed down
12:46:07 <randomresult> @NamelessCoder any thoughts about releasing new TER-Versions of the flux-family?
12:46:51 <NamelessCoder> https://github.com/FluidTYPO3/flux/issues/627 and https://github.com/FluidTYPO3/flux/issues/573 first
12:48:24 <randomresult> we should get danilobuerger working on the second one :)
12:50:29 <randomresult> i told danilobuerger i will pay him in beer. but i decided that that was a bad idea - he is bavarian - could be more expensive than his normal fee
12:50:37 <NamelessCoder> mrboe being discussed internally, not yet ready for publishing
12:51:08 <randomresult> @NamelessCoder how many time you estimate to solve this ones?
12:55:59 <Denyerec> Are we still installing from Git these days or are the TER versions recommended?
12:56:47 <Denyerec> danilobuerger - I feel your pain regarding shops.
12:57:15 <Denyerec> Having worked for an agency that produced various shop products off the back of a genuinely terrible framework and backend datastructure, anything is possible if you're willing to customise it hard enough.
12:57:31 <Denyerec> I think the major pitfall is when a project tries to encompass every possible configuration and then you end up with Magento.
12:58:11 <randomresult> Denyerec i would go for dev-git-versions
12:58:25 <NamelessCoder> I hate to say it, but for small custom shops, custom code is often less expensive to handle.
12:59:22 <randomresult> i will give shopware a try
12:59:51 <randomresult> anyone know when working with submodules, what causes a submodule to be in a detached Branch?
13:00:26 <Denyerec> NamelessCoder - you are quite correct
13:00:39 <Denyerec> Also, typically, shops will invariably have various quirks that will need working in
13:01:02 <Denyerec> Their stock codes aren't unique, or they have different length UIDs depending on supplier, or they need a stock alert on only certain products etc.
13:01:18 <NamelessCoder> get someone whose brain is in the right place regarding the architecture you make and it should work smooth enough
13:01:52 <soee_> ok to going back @ my topic, if we install fluidpages, it automatically wants to render pages configuration right ?
13:01:53 <Denyerec> The point being if you're a small outfit and you need to work those quirks into Magento, you're pretty boned.
13:28:12 <NamelessCoder> extbase_realurl has a similar integration which works faster and is more extbase-centric
13:29:18 <NamelessCoder> I guess if you need to render typoscript objects, use typoscript_rendering but if you need to call extbase controllers, use extbase_realurl
13:41:58 <xaver> why does Travis not run this test https://github.com/FluidTYPO3/FluidTYPO3-CodingStandards/blob/master/commit_message_inspector.php can't we access the message?
13:51:19 <soee> mrboe: ill do some tests with this suggest option and then we will see how it all works
13:54:02 <fizelchen> hi, i have problem with languages. Typo3 6.1.10, flux, fluid_content, fluid_pages latest dev version.
13:54:55 <fizelchen> when i switch form columns view to language view, all my ce inside of fces are missing from the language, not selected by the language selector
13:55:19 <fizelchen> the FCEs are visible in both languages (here EN and DE)
14:51:11 <batjony> NamelessCoder: lets ask the boss here :) how do you proceed with the extensions deployment - git sub modules, composer, using only TER or some custom shell scripts like @xaver
15:00:22 <xaver> submodule sounds nice, be i had problems with deployment and keys. composer sounds good. Developer like NamelessCoder or me normally use the developed stuff and not the TER
15:00:43 <xaver> if you use git you have less testing and maybe more issues
15:00:53 <soee> what wa steh command to create git branch and do automatic checkout ?
15:01:31 <NamelessCoder> batjony I'd say it depends on which strategy you use to version control the typo3 site itself. If you git the entire site root, submodules is a great way.
15:07:16 <batjony> NamelessCoder: is there a way using the composer
15:07:45 <batjony> do we have all the extensions in https://packagist.org/
15:08:24 <xaver> my opinion is don't run behind the crowed. Talk with your college and best solution in your case. If composer is already standard, use it. If your deployment always loads the source from all the git repos and you don't use github the chances of a downtime
15:10:15 <batjony> i do not see the builder extension in https://packagist.org/
15:10:37 <batjony> and most likely a lot other typo3 third party extensions will be missing
15:10:59 <batjony> so probably the composer is not a good solution for typo3 deployment
15:11:35 <soee> but copmoser ca use oter repositories right ?
15:12:03 <NamelessCoder> afaik it also supports raw repositories by URL
15:12:31 <NamelessCoder> won't support also loading deps of those exts, though - naturally so
15:15:23 <batjony> and finally http://typo3.org/extensions/repository/view/builder is it the fluid typo3 builder extension from https://github.com/FluidTYPO3/builder ?
15:16:06 <batjony> because i see the author is Claus Due
15:21:18 <NamelessCoder> yes, that's the TER version of the github repository
15:51:02 <batjony> NamelessCoder: btw typo3/cli_dispatch.phpsh extbase builder:providerextension --controllers 1 - does not create any controller
15:51:33 <batjony> as I see - there is only a folder "Controller"
16:14:26 <NamelessCoder> batjony controller class writing is still not implemented (the beta label is quite true)
16:25:09 <slh> hey there, is the falviewhelper supposed to work on TYPO3 6.1?
16:26:46 <NamelessCoder> slh basic support only; core has a lot of fixes in 6.2 for inline record relations in flexforms
17:22:15 <slh> @namelesscoder thanks for the info, but i get a fatal error related to mergeRecursiveWithOverrule on the FalViewHelper
17:23:21 <slh> the method is just not present in 6.1
17:38:05 <NamelessCoder> that settles it then - won't work on 6.1. I'm fine with that btw since no support probably is better than crappy partial, error-prone support because of core bugs
17:38:18 <NamelessCoder> a fatal php erro may be a bit excessive though
20:11:00 <glucka> hi, if i use v:render slide="-1" can i disable the collecting?
22:21:27 <Outdoorsman> glucka, I believe you can disable collecting by setting slideCollect="0" (if it's not disabled by default... the docs don't specify the default). http://fluidtypo3.org/viewhelpers/vhs/development/Content/RenderViewHelper.html
22:30:44 <Outdoorsman> Is this how you would do it to? I was wondering that yesterday.
22:31:23 <xaver> Outdoorsman: https://github.com/xf-/fluidtypo3-vagrant somebody who tests windows needs to comment out rsync or install it via something
22:32:22 <Outdoorsman> Just a way to separate resources from different extensions. It's long but seems appropriate since I'm doing the same thing for the Private folder.
22:32:36 <soee> Outdoorsman: ../Public/Styles/ext/ and Public/Script/ext/ etc
22:32:46 <soee> i would split each asset type into separate folders
22:34:34 <soee> also maybe better for me would be vendor_web_sitename
22:35:00 <soee> this way with 'web' in the middle i can easily identify package type
22:35:02 <Outdoorsman> Hmmm, I think your method would result in few folders which I like.
22:36:17 <Outdoorsman> soee I like how you think. Your full of answers. You should ask questions more often... ha ha.
22:43:27 <Outdoorsman> xaver, that looks really cool! I'm not really familiar with the tools you are using there and don't have enough time to do that now.
22:45:04 <Outdoorsman> Looks like you've taken the pain out of the whole thing though by just making a VM. I'm more familiar with VMware though since that's what I'm running.
22:45:40 <xaver> vagrant supports vmware, but needs a license
22:46:05 <Outdoorsman> VMware or Vagrant needs the license?