10:36:20 <Guest|35656> Good morning guys. I built a dropdown menu with 3 levels. I used the v.page.menu.directory viewhelper. Is there a possibility to turn off the dropdown? thx
11:32:14 * bjo3rn doesn't understand what you are saying
11:32:35 <Guest|73757> Hello, everyone. I'm new to typo3 and i want to use fce in my typo3 6.2.2, so i found Fluid Powered TYPO3 but how can i use this ?
11:33:09 <Guest|73757> I wanted an alternative to TemplaVoila
11:34:59 <bjo3rn> Guest|73757: you might want to have a look at https://worksonmymachine.org/blog/fluidtypo3-quickstart
11:35:21 <bjo3rn> but be aware that this guide is a little outdated
11:35:29 <cedricziel> my last point was only about custom extensions
11:35:43 <bjo3rn> the naming of flux' viewhelpers has changed since versino 7.0
11:49:28 <jlumpe> cedricziel: is is possible to use the wizard to relate extbase models?
11:49:45 <georg_t> I stumbled upon https://github.com/FluidTYPO3/flux/issues/283 where NamelessCoder said "suggest wizard works with select and group".
11:50:17 <georg_t> group is deprecated, so I used select
11:51:06 <georg_t> > to relate extbase models - I'll check this
11:53:38 <cedricziel> hm, good q. i usually use input fields for that
11:54:17 <cedricziel> if you need multiple selects, you seem to require a controller action which gives you an instance of QueryResult
12:00:40 <georg_t> <flux:wizard.suggest table="tx_myext_domain_model_something" /> inside flux:field.input does not work
12:01:14 <cedricziel> relation with pages, does that work?
12:02:26 <georg_t> sorry. no. thats the answer to "is is possible to use the wizard to relate extbase models?"
12:03:02 <georg_t> I checked if the models are configured correctly. TCA and Extbase/Fluid do work
12:04:38 <georg_t> and yes. relation with pages in an fluidcontent element do work.
12:08:26 <Guest|73757> bjo3rn: I did the first part and getting this when i open the extension manager "typo3_src-6.2.2/typo3conf/ext/quickstart//composer.json"."
12:08:53 <Guest|73757> No composer manifest file found at
12:09:48 <cedricziel> the new package manager, which was introduced way after that article was written, requires you to place a composer manifest in the root of your extension
12:12:44 <cedricziel> i'll bring one fancy nineties one if my fiance didnt kill it
12:13:08 <bjo3rn> I have a "Ute, Schnute, Kasimir" towel. no kidding.
12:13:38 <bjo3rn> but srsly, you asked "is that true?" above.
12:17:04 <cedricziel> for select field which requires items argument ( you seem to require a controller action which gives you an instance of QueryResult)
12:17:25 <cedricziel> if he wants to have a suggest wizard for pages
12:25:58 <georg_t> perhaps I#m on the wrong way: as I really like fluidcontent I put together some tables which could be filled via the BE and wanted to get rid of all the plugin stuff.
12:26:31 <georg_t> Instead I created a fluidcontent element which should point to one db entry and output the result
12:28:04 <georg_t> as said above: using flux:field.relation it works
12:28:52 <bjo3rn> Guest|73757 are you using TER versions of the extensions?
12:28:53 <georg_t> but flux:field.relation lists all db entries orderd by uid (order bsy is ignored because of "select uid from...")
13:15:48 <hans> i looked at the viewhelper: page.content.render, its just posible to fetch content of one page and optional slide up to the root
13:16:18 <hans> but i see no solution by the present viewhelpers to fetch content from subpages
13:16:46 <bjo3rn> you can fetch page uids first using the menu viewhelper
13:17:49 <hans> ok, but when i want to grap content of the i will use the page.content.render vh, but then i alwasy get for example 2 (limit) of the singel pages
13:18:14 <hans> but i want to sort and order the content of all defined pages as a whole!
13:18:52 <hans> i would need somthing like this : <v:page.content.render pageUids="118,119 .."
13:26:55 <bjo3rn> there are a lot of hidden gems in html5 it seems
13:27:05 <BenjaminR> Info an Kunde: HTML5 Autocomplete ist eng verstrickt mit dem Input "name"-Attribut. Extbase hat seinen eigenen fest definierten Naming Convetions für Controller Action Parameter und damit für Feldnamen. Es scheint das passt nicht gut zusammen. Mehr aber keine exakten Aussagen hier: http://wiki.whatwg.org/wiki/Autocomplete_Types
16:05:26 <Romm> We are begining the build of a generic extension, named pagelist, which allows to easily list a set of pages. The goal is the same as tt_news or news does, but we use pages instead. I'd like to have a PageRepository in my controller which automatically build an object of a specific page's fields, including mm like medias.
16:05:43 <Romm> Then give it to my Fluid view and do whatever I want, of course. :p
16:06:26 <Romm> If you have some tips, I'll take it. =)
16:06:53 <bjo3rn> what about \TYPO3\CMS\Frontend\Page\PageRepository() for starters?
16:07:23 <cedricziel> i may sound reluctant, but for me it doesnt make sense :)
16:07:40 <cedricziel> and the repo is close to useless unless you have a proper domain object
16:40:00 <Guest|99706> Hello, doing my first steps with fluidtypo3. I managed to make a FCE and as an admin I can choose this element for page content, but as an editor I don't see this FCE. How can the editor use this FCE?
16:57:18 <Romm> Pages model & repository working by here :p
16:57:38 <Romm> One thing left : properly link the media property to the associated files
16:58:18 <Romm> Should I get a rope right now, or wait for that ? O:)
17:40:48 <Romm> cedricziel: got my repository working with correct links to the FileReference =D !
17:44:33 <Guest|99706> @cedricziel: I did check (the only one with fce btw) "tx_fed_fcefile" under "allowed exclude fields" under "page content". Or did you mean something else?
18:36:27 <BenjaminR> mrboe you need a ticket for t3cs?