08:58:04 <randomresult> good morning. shouldnt it be possible to define a TS-Setting like this in a ConfigurationSection: <v:var.set name="settings.useTypoScript" value="{v:var.typoscript(path: 'plugin.tx_MYEXT.settings.useTypoScript')}"/> ?
10:12:35 <alex_sch_> When using flux view helpers like input the placeholder attr doesn't work. That's a know issue?
10:43:27 <Noch_ein_Kamel> Hi everyone. I have trouble using a custom controller for my fluidcontent elements. I narrowed it down to the ResolveUtility not able to resolve the class name of my Controller but I'm a bit lost there. Anyone available to help? Using 6.1.7 with latest TER versions or flux, fluidcontent.
10:50:21 <Noch_ein_Kamel> I guess it's just some vendor name issue as it works if I remove the vendor name from my class and force-load (require) it in my localconf. But that's ugly ^^
10:50:38 <randomresult> set a dark mark - the Deatheaters will appear :)
10:51:52 <randomresult> we should set up the bot to ping the team if they are mentioned
10:53:12 <randomresult> Noch_ein_Kamel as said. ask BenjaminR, bjoern, cedricziel, danilobuerger or NamelessCoder
10:59:36 <Noch_ein_Kamel> Ah, okay :-) Was a bit confused because the register... was only mentioned on the fluidpages github and not the fluidcontent :-)
11:01:59 <Noch_ein_Kamel> Okay i'll try with the fluidtypo3org extension template and "call back" if it's still not working. Thanks!
11:04:22 <BenjaminR> bjo3rn - true - register instructions are missing on fluidcontent readme - could you add this or should i take over later?
11:13:02 <Noch_ein_Kamel> The Controller is working now, but one more question: Before I hade two TS collections. One for Content and one for Pages. Now there is only one plugin.tx_kamel.view configuration for both? i.e. using the layout folder from the fluidcontent extension is also deprecated?
11:14:45 <randomresult> @bjo3rn u yesterday said something about deleting tables with the comparetool in install - what was it?
11:15:56 <bjo3rn> Noch_ein_Kamel yes, you set all paths with plugin.tx_myext.view.xxxRootPath
11:16:20 <bjo3rn> randomresult compare tool said datamap_bla table could be deleted
11:22:05 <Guest68219> hi! Ist ist possible to translate the fluidpages page configuration in page language version? Thus, can i make i flux input field translateable through page overlay?
11:23:14 <randomresult> Guest68219 yes you can - as far as i understand u right
11:23:28 <randomresult> you want to translate backendforms right?
11:28:36 <Guest68219> Is it aggainst the concept of fluidpages, or is it just not implemented yet? I used the flux field to make some page content manageable, which is unique on the page - image slider contents. Is the page configuration ment to be used just for real configuration?
11:30:30 <bjo3rn> afaik there's no official discussion if it is a configuration thing only.
11:31:11 <bjo3rn> I'm pretty sure you _can_ make it language aware using an overlay but I haven't done/required it myself yet.
11:32:12 <bjo3rn> I wouldn't say it's against the concept though
11:42:41 <randomresult> im still having the issue, that if i copy an element it will add the first element from the frontpage to the copied element
11:42:43 <Defos> The JS is requested from base Dir, but the project is in a subdirectory.
11:44:13 <Guest68219> @bjoern: I think a workaround for my case would be, to make some records selectable in the page configuration. The records thereself can be translated. But this is just a workaround whcih does not match other use cases and which doesn't allow the very rapid development which is possible with flux
12:08:16 <Defos> And in Frontend i'm getting Fatal error: Call to undefined method FluidTYPO3\Flux\Form\Container\Section::getStopInheritance() in xxx/typo3conf/ext/flux/Classes/Provider/AbstractProvider.php on line 802
12:08:38 <Defos> even tried downgrading to flux 6.0.4, no luck
12:14:34 <danilobuerger> Guest68219: did you need something
12:18:06 <Guest68219> I'm looking for a solution to make fluidpages flux form values translateable with page overlay. Do you have any experiences with this?
12:18:20 * randomresult needs a big load of christal meth for now - anyone?
12:19:21 <danilobuerger> i am trying to figure that out as well
12:19:35 <danilobuerger> no luck yet, will focus on it next week or so
12:20:40 <Guest68219> I just tried to make the flexform field translateable like any other field in TYPO3. But i had no luck either..
12:22:42 <Guest68219> Could you give me information via email if you find a solution?
12:26:34 * randomresult is off for a restart... me the retard is off for a restart
12:44:31 <randomresult> if i copy an element out of a FCE (for ex a textelment inside a column of an fce) to another place, it will move an elment from uid 1.
12:44:54 <randomresult> so the element disapears on the home-page and will be moved with the copy to the new position on a subpage
12:45:29 <randomresult> is it a known bug - if yes where do i find the issue? related to fluidconten? Pages? flux?
12:46:39 <BenjaminR> if there is a known issue you find it on github - browse them
12:48:52 <randomresult> i found one... says its fixed
12:49:36 <BenjaminR> if it fits your issue comment on it and document your setup
12:50:35 <NamelessCoder> randomresult the VERY best thing you can do when reporting copy/paste/move/translate issues...
12:50:59 <NamelessCoder> 1) include a dump of values of tx_flux_parent, tx_flux_column and colPos before and after move
12:52:31 <NamelessCoder> 2) describe exactly which action you take to move, for example: "I click the content icon of an element nested inside container foobar of a parent element which sits in colPos 1, I then click copy - page reloads, I click the paste-as-reference icon in top of column with colPos 0. I expect a copy to be created and inserted top of the column, but xyz happens instead"
12:54:00 <NamelessCoder> especially with these copy/paste issues it is hugely important to report the exact procedure, because it can trigger in so many different ways and under so many different starting and ending conditions (e.g., nested element, directly in column, moved via drag-drop into CE column, into page column, etc) and they all imply different command parameters :(
12:54:18 <NamelessCoder> which by the way is also why this f'ing bug even exists.
12:55:52 <NamelessCoder> sorry to complicate matters this way, but in this case we truly need this much detail
13:48:32 <cedricziel> the last sentence in the first link points that out
13:48:49 * NamelessCoder just skips to the conclusion
13:49:40 <limboo> ah, the module < plugin stuff i missed, maybe its working like that
13:49:52 <cedricziel> if you cant get around i suppose you show off, what you're actually trying to do, so we can put our magic bowls back on the shef :)
13:56:08 <NamelessCoder> 1) if you use typo3 6.0+ you should be using namespaces for these classes, e.g. \TYPO3\CMS\Extbase\Configuration\ConfigurationManagerInterface
13:56:27 <NamelessCoder> if you still need to use the old names, you'll likely need to write them as \Tx_Extbase.....
13:56:58 <NamelessCoder> 2) Since you have no pluginName to provide which makes sense, you need a version of Extbase which can function without this argument. That implies 6.1+
13:57:18 <NamelessCoder> and implied by this: you must not use the second and third argument on getConfiguration()
13:58:05 <NamelessCoder> 3) It is quite likely that you will need to use getConfiguration(.....::CONFIGURATION_TYPE_FULL_TYPOSCRIPT) and then read $thatValue['module.']['tx_whatever.']['settings.']
13:58:22 <NamelessCoder> note the dotted-path-in-array-key syntax
13:59:50 <NamelessCoder> finally, when you execute the CLI script make absolutely sure you execute it as a user who has write permissions in typo3temp - or you may not be able to write class reflections etc. which can generate those types of "not found" errors
14:00:31 <NamelessCoder> there is a lot more to tell about CLI mode but I'm afraid I don't have time to explain all of it ;)
14:01:01 <NamelessCoder> the guys over at #typo3 may be able to tell you more secrets of the CLI ^^
14:13:20 <BenjaminR> But we can switch to german when it becomes complicated :)
14:13:36 <cedricziel> english keeps it searchable for everyone :)
14:13:57 <ad_on_is> well, i upgraded a freshly started project to typo3 6.2... i also upgraded flux, fluidpages, fluidcontent and vhs to the newest git-tag version
14:14:15 <NamelessCoder> also: http://fluidtypo3.org/community/irc-logs.html doesn't like German ;)
14:14:52 <ad_on_is> i've used fluidpages_bootstrap for templating
14:15:24 <ad_on_is> in the localconf of fluidpages_bootstrap there's something like:
14:19:05 <ad_on_is> for better reading... here's the ext_localconf.php that worked until 6.1
14:30:35 <NamelessCoder> hmm, ad_on_is I think you're talking about the "speciality" extension or some other
14:30:47 <NamelessCoder> we don't use this approach
14:30:57 <NamelessCoder> also, fluidpages_bootstrap has no localconf...
14:32:19 <NamelessCoder> in any case: this would appear to be some issue between 6.1 / 6.2 and not related to an extension but to the core itself
14:33:12 <NamelessCoder> I can tell you this: the reason is not the missing t3lib folder. The code piece you pasted is simply a *definition* - the same definition (with the key being the old filename) is being read inside the TYPO3 core
14:34:01 <NamelessCoder> if you get errors from the class you point to in that hook definition, check that this class is compatible with 6.2 (and, just as example, does not attempt to manually require/require_once any files from t3lib)
14:35:01 <NamelessCoder> but you really should be asking for help with this one through #typo3 since it is purely a core/hook-class matter and not related to fluidtypo3 except maybe for it being used in the third-party bootstrap-package Fabien from ecodev.ch creates ;)
14:36:59 <NamelessCoder> few release notes on Flux 7.0 - http://fluidtypo3.org/blog/news/flux-70-released.html
14:37:36 <ad_on_is> ah ok... i thought fluidpages_bootstrap is related to fluidtypo3, since they are on the same github user
14:39:08 <NamelessCoder> they are, but the code you pasted is not from that ext
14:40:08 <NamelessCoder> current version of ext_tables.php which has the TS inclusion, for extension fluidpages_bootstrap in the official origin: https://github.com/FluidTYPO3/fluidpages_bootstrap/blob/development/ext_tables.php
14:40:20 <ad_on_is> no, as you said, it was from the bootstrap-typo3-package
14:40:25 <NamelessCoder> if your file differs from this, you're not using the official version ;)
14:40:57 <NamelessCoder> you may find the issue here if it is reported: https://github.com/Ecodev/bootstrap_package/issues
14:41:11 <NamelessCoder> if not, I certainly would report it so Fabien has a chance to adapt it :)
14:43:15 <ad_on_is> i think my problem is somewhere else
14:43:37 <ad_on_is> if i uncomment ext_tables.php the page is still rendered
14:43:39 <NamelessCoder> in that case I think it's the EXT:speciality which Fabien manages. If you need help finding him or reporting the issue don't hesitate to ask (Fabien is also on this team so he's cross-responsible ;))
17:12:17 <NamelessCoder> clews known issue, cased by the way flexforms reference files. No solution until fixed in typo3 core. Workaround: use flux:field.file instead of fal field
17:26:16 <Guest|70326> Hello, mein tpl crashed... I got no error or something. I use t3 6.2 and I think teh namespaces are wrong. At the moment I use "{namespace flux=Tx_Flux_ViewHelpers}"
17:27:15 <NamelessCoder> and have a look at http://fluidtypo3.org/blog.html
17:27:28 <NamelessCoder> http://fluidtypo3.org/blog/news/flux-70-released.html to be precise for history
17:29:04 <Guest|70326> and vsh namespace -> {namespace v=Tx_Vhs_ViewHelpers}?
17:29:41 <NamelessCoder> yes - until version 2.0 of VHS at which point we will switch that to namespace classes as well
17:32:57 <ad_on_is> has registerFluidFlexFormPlugin() changed in any way? because install->tool check extensions gives me an error "Call to a member function exec_SELECTcountRows()", but the implementation still works
17:34:14 <NamelessCoder> it changed to include a fieldname, but that's about it
17:34:38 <NamelessCoder> I think the problem there comes from another place trying to count fx sys_template records - you are sure your DB schema is up-to-date?
17:58:37 <Guest|70326> thanks, I will check it! :)
18:03:07 <mhowellsmead> hi claus, thanks for the link.
18:03:38 <mhowellsmead> the problem is that i have tried installing cms 6.2 and the newest versions of fluidcontent, vhs, vidi, flux and media.
18:03:40 <NamelessCoder> hey Mark - sorry it took a while, missed your tweet first time around
18:04:31 <mhowellsmead> have my own brand new ext using fluid which works perfectly until i want to use flux:flexform.field.inline.fal
18:04:52 <NamelessCoder> lots of people unfortunately have problems with that one
18:05:07 <NamelessCoder> in summary: use flux:field.file
18:05:12 <mhowellsmead> when i implement it into my fluid template, i have no fields whatsoever.
18:05:42 <NamelessCoder> the inline fal thing will work in very limited cases so as soon as you have a problem with it, go to the workaround flux:field.file - it's sad, but no way around it yet
18:06:53 <NamelessCoder> and <flux:field.inline.fal /> is the right field
18:07:15 <NamelessCoder> only the *old* viewhelpers have aliases in the old namespace ;)
18:07:39 <NamelessCoder> bit confusing at first but once you get used to always checking the namespace and using the new location of viewhelpers, all should be well
18:07:46 <mhowellsmead> can i paste a code chunk here?
18:07:53 <NamelessCoder> you still may experience issues with inline.fal but at least now you have a workaround ;)
18:13:19 <NamelessCoder> it's the only thing I can spot which could be fixed
18:14:10 <NamelessCoder> if you still have problems with the fal field, try out flux:field.file - alternatively, ask danilobuerger (he may know more about special requirements for this field or the classes it uses)
18:14:12 <mhowellsmead> for reference and a different (already completed) project; will this all work on 6.1.7 but with the newest extensions? or is 6.2. compulsory for all this?
18:14:31 <NamelessCoder> there is ONE bug left which 6.1.7 has not fixed yet
18:14:54 <NamelessCoder> it applies only when you use the OLD namespace in your fluidtemplate, so you should not be affected
18:16:17 <danilobuerger> mhowellsmead gist looks fine, field should show up in backend
18:17:11 <NamelessCoder> that's what I thought - almost all fields should require nothing but the "name" property, few fields require additional ones - namely the relation or multivalued fields
18:38:37 <NamelessCoder> hint: the exception 1224254792 "namespace could not be resolved" always comes from inline usage of a VH namespace that was not added
18:38:43 <NamelessCoder> it does not happen if the usage is tag based
18:42:59 <Denyerek> You guys go the "folder of shortcuts" route for page header /footer menus the customer needs to control ?
18:43:11 <Denyerek> I thought a UID list with excludes would be too fiddly fro them to manage
18:43:40 <NamelessCoder> Denyerek yes, store those links somewhere easy to understand
18:44:42 <NamelessCoder> way to go mhowellsmead ;)
18:44:47 <mhowellsmead> done! right. where's that beer?
19:00:32 * randomresult will catch some food now - off for the hunt!
19:09:15 <benjamin_654> hi, i have a problem with fluidpages: "No suitable request handler found" - has someone had this too?
19:17:53 <benjamin_654> ah, found something: i will follow NamelesCoder´s instructions from https://gist.github.com/NamelessCoder/8714035#comment-1198300
21:55:59 <NamelessCoder> yes, and possibly removing one
22:17:24 <soee> NamelessCoder: divison part faisl for me here: {result.validAnswers->v:math.product(b: 100)->v:math.division(b: result.answers->f:count())}
22:17:50 <soee> maybe result.answers->f:count() is the problem here ?