01:49:44 <soee> danilobuerger: so basically all data should ba fetched and passed to widget and widget should be responsible for fetching data for example from database ?
09:49:45 <danilobuerger> dont know .. was commited just this weekend
09:59:42 <randomresult> what does this mean in my error log PHP Fatal error: Class 'FluidTYPO3\Flux\Core' not found in /Users/***/Sites/GIT-PROJECTS/fluidpages-Fork/
10:03:03 <danilobuerger> randomresult i think bjo3rn had this one 2 days ago? dont know what it was though
10:03:28 <randomresult> i updated pages to the latest version
10:23:41 <randomresult> @bjo3rn in line 6 of fluidpages/ext_localconf.php there is this \FluidTYPO3\Flux\Core::unregisterConfigurationProvider('Tx_Fed_Provider_Configuration_PageConfigurationProvider');
10:24:10 <randomresult> but this directory is missing
10:58:26 <bjo3rn> why would you want to use flux master?
10:58:31 <randomresult> so im cool with that. it helps me alot doing great webs. so im thankful.
10:59:23 <bjo3rn> what are the advantages of using flux master instead of flux ter for you?
10:59:48 <randomresult> because updating fedext-extensions caused me a lot of trouble in the past. so building new webs or learning stuff for me is better to use the new versions than learning something and then change to the new version
11:00:07 <danilobuerger> [10:59:13] <@bjo3rn> [10:33:31] ehm. does uncache remove them? <---- no
11:00:47 <danilobuerger> randomresult re updating *_bootstrap, sure just submit a PR ;-)
11:01:52 <randomresult> i think my PR doesnt fit your thoughts of how this should be done.
11:02:15 <randomresult> i allway do something wrong - so this is a waste of time for both sides.
11:02:42 <bjo3rn> but you want to learn stuff and noone complains about anything so go ahead!
11:02:43 <danilobuerger> [10:59:14] <randomresult> [10:54:02] the point is: sometimes in fedext extensions you are at a point where they are not usable with your existing code. <---- thats why you should be on TER, if you need bleeding edge features and switch to git, you are responsible :-)
11:03:30 <danilobuerger> [11:02:15] <randomresult> i allway do something wrong - so this is a waste of time for both sides. <----- you should ahve seen my first few commits, i nearly killed cedric in the process
11:03:36 <bjo3rn> really randomresult, I encourage you to do PRs
11:03:56 <danilobuerger> i encourage you too, of course its more work in the beginning for all of us, but after that you know the stuff
11:05:02 <randomresult> well danilobuerger you told me to add headline in the migrationscript - i did. since then a lot of pr's are merged. not mine. so simply editing a headline is failed on my side.
11:05:57 <randomresult> anyway boys. lets get some work done. i will now look at fluidcontent_core because this is what i dreamt of at night
11:06:28 <randomresult> get rid of css-styled-content standard elements... how great is this
11:06:47 <bjo3rn> it's highly experimental, just sayin' ;)
11:06:48 <danilobuerger> randomresult ... if you want something merged fast... you need to tell people about it....
11:07:12 <danilobuerger> i always ping everybody around if i want something merged
11:07:13 <bjo3rn> yes, you can learn a lot from danilobuerger in that regard ;)
11:07:35 <danilobuerger> if you dont ping people you will have to wait a few days
11:08:23 <danilobuerger> randomresult you just need to say something like this: "hey bjo3rn mind merging that no brainer ? documentation#11 "
11:08:24 <FT3BOT> Issue 11: [DOC] Added a clear headline and changed the order of the solutions to m... https://github.com/fluidtypo3/documentation/issues/11
11:27:35 <randomresult> so danilobuerger when changing the *bootstrapthing... would you do one commit for each file and then one pull request with all commit at once?
11:27:51 <randomresult> or each file on commit and one pr?
11:28:09 <danilobuerger> naah, just do one commit for the whole package if you are just migrating view helpers
13:47:36 <randomresult> but could u explain to me what needs to be done - hasnt to be now.
13:47:45 <cedricziel> Good work, nevertheless, Harry ;)
13:48:22 <cedricziel> sure. we migrated all travis build scripts to use the official typo3 utitlities and only work on top of that to ensure consistency
13:49:07 <randomresult> so i should change the travis file too and ammend commit that one too?
13:58:16 <cedricziel> please compare the flux and fluidcontent one if you want to get to know the differences
13:58:43 <cedricziel> the fluidcontent one is basically the flux one + imports of fluidcontent specific configurations
13:59:03 <randomresult> make the travis-migration and then i start over and do the migration of namespacestuff in fluidcontent_bootstrap and pages
14:00:06 <bjo3rn> cedricziel do we need a dev-namespace branch?
14:00:22 <randomresult> no hurry, i dont use this anyway. i just thought it might be good to keep this up to date cause i used it to learn in the beginning
14:00:27 <cedricziel> there's been one for taking heikos stuff into account
14:00:52 <cedricziel> not sure if the NamelessDude finished the rampage over namespaces there
14:00:54 <bjo3rn> but not for the bootstrap packages
14:01:46 <bjo3rn> so you wouldn't mind your PRs being open for some time, randomresult ?
15:46:29 <kows> ist it posible to filter flexform data sets? lets say I have a slider and the slides contain one field, which contains a string. i want display the slides grouped by this field
15:50:44 <mrboe> @kows you can make a IF https://fedext.net/viewhelpers/vhs/master/IfViewHelper.html
15:51:16 <mrboe> or a switch case https://fedext.net/viewhelpers/vhs/master/SwitchViewHelper.html
15:51:37 <randomresult> mrboe i think he wants something diffrent
15:52:30 <randomresult> when i get him right, he wants to collect all slides with the same string.
16:19:44 <kows> want avoid any php/extension related code
16:20:30 <kows> and is it possible to get the slide objects from other page?
16:20:53 * randomresult must leave now... see u later all.
16:20:54 <bjo3rn> ok, then I'd say the simplest is to iterate over all slides, check each for the string and add the selected to a new array for later rendering.
16:21:17 <kows> (on front page all slides are shown and mantained and on sub pages the sliedes should be shown related to a field)
16:21:37 * randomresult have fun @danilobuerger , @bjo3rn and @cedricziel with your dirty games (nitties?) tonight
16:22:43 <danilobuerger> kows i would say just use v:iterator.filter
16:23:40 <danilobuerger> T0rsten you need to actually get the identifieres via v:resource.records.fal
16:23:46 <kows> okey thanks. Sorry for my bad english and knowledge. Last time I used fedext was early 2012 and now so much is changed and there isn a cool documentation
16:23:58 <danilobuerger> T0rsten {images} only contains the count, not the identifiers
16:24:21 <kows> so it would also be possible to simulate tt_news just with fluidpages/vhs ?
17:30:23 <FT3BOT> Issue 12: Is EXT:flux 5.0 incompatible with TYPO3 4.7? https://github.com/fluidtypo3/flux/issues/12
17:30:24 <FT3BOT> Issue 12: Is EXT:flux 5.0 incompatible with TYPO3 4.7? https://github.com/fluidtypo3/flux/issues/12
17:32:03 * randomresult tells @danilobuerger, @cedricziel, @NamelessCoder and @bjo3rn that he finished the locallang-guide and PR it into documentation-Repo.
17:32:26 <randomresult> @danilobuerger and @bjo3rn this way ? :)
17:32:47 <FT3BOT> Issue 12: Is EXT:flux 5.0 incompatible with TYPO3 4.7? https://github.com/fluidtypo3/flux/issues/12
17:32:48 <FT3BOT> Issue 12: Is EXT:flux 5.0 incompatible with TYPO3 4.7? https://github.com/fluidtypo3/flux/issues/12
17:33:01 <danilobuerger> see randomresult it works
17:39:15 <NamelessCoder> this naming is used for consistency, not inviting anyone to think any files or settings should be named "localLang" since that -never- is used in the core
17:39:26 <NamelessCoder> that's how much we care about details ;)
17:39:57 <randomresult> but its locallang with smal l isnt it?
17:44:07 <NamelessCoder> ah you, core you... just imagine how many damn hours have been wasted on typos and explaining, simply because Kasper thought saving four bytes was a better choice...
17:44:29 <NamelessCoder> it applies to so many places in the core, still. Better than it was, sure, but still not good
17:44:52 <FT3BOT> Issue 13: .FED_CONTENT not deleted when clearing cache https://github.com/fluidtypo3/flux/issues/13
17:44:53 <FT3BOT> Issue 13: .FED_CONTENT not deleted when clearing cache https://github.com/fluidtypo3/flux/issues/13
17:45:47 <1JTABHDZY> [documentation] NamelessCoder pushed 2 new commits to master: https://github.com/FluidTYPO3/documentation/compare/868f9443b57c...4342d1879713
17:45:47 <1JTABHDZY> documentation/master c866556 Harry Glatz: [DOC] Changed filename to WorkingWithLocallang.md
17:45:48 <FT3BOT> Issue 13: .FED_CONTENT not deleted when clearing cache https://github.com/fluidtypo3/flux/issues/13
17:46:20 <NamelessCoder> damn, spambot. You spammy!
17:53:22 <danilobuerger> cedricziel FT3BOT is acting up
17:54:32 <cedricziel> danilobuerger that was from the netsplit i guess
17:54:47 <cedricziel> but i will set him to ignore the github announcements here
17:55:17 <danilobuerger> cedricziel the problem is that issue linker has default for flux... i think we should disable that and issues must be qualified with name to be linked
22:46:21 <NamelessCoder> seriously, no - that's not something a VH should do with very few exceptions
22:46:45 <NamelessCoder> page properties for one (since this does not harvest the get parameter directly but is comfortably wrapped in a lot of other code)
22:47:11 <NamelessCoder> recommendation: use controller, read URL argument there. Remember to sanitise.
22:47:25 <soee> so the current breadcrumb menu has this limitation
22:47:50 <soee> that we can't put there records titles/names etc ?
22:48:07 <soee> and this should be done inside TS liek the old days ?
22:48:23 <danilobuerger> ------> recommendation: use controller <------
22:52:31 <soee> a bit more detaisl please? This controller should be responsible only for fetching such data ?
22:56:41 <NamelessCoder> what is the context? fluidcontent?
22:58:38 <NamelessCoder> if so: check fluidcontent_bootstrap controller class, make action for your template and read the URL parameter there. But you should consider now, that perhaps using a model and maybe even an extbase plugin is preferred