IRC logs

IRC logs

20140725

Logs from channel #fedext on freenode - our official support channel.

IRC log range: 20140725*

20140725

  • 06:40:59 <randomresult> @danilobuerger cool!
  • 08:41:14 <Guest|17175> Good morning. Can you guys help me out? I try to use RealURL with Fluid. But when I send form, URLs are very ugly. Anyone have an idea how to configure it?
  • 10:25:49 <Andy_H> Hi! In <v:page.menu> or <v:page:breadCrumb> there is an option to include doktype "Spacer" (includeSpacers="TRUE"). Is it possible to prevent these spacers being linked? Because links to spacers result as 404…
  • 11:05:23 <bjo3rn> Andy_H mind opnening an issue on github? I'll have a look later.
  • 11:05:43 <bjo3rn> I never came across spacers so I can't tell if it is a bug tbh
  • 11:05:57 <bjo3rn> it's kinda likely though
  • 11:17:47 <fger> hi guys, we got a problem with field.inline.fal in section/objects (TYPO3 6.2.4 / latest dev branches of flux/fluidcontent):
  • 11:18:49 <fger> 1. when u insert a new object in a section with a FAL relation and you try to insert a picture, an error occurs - you first have to save the whole FCE when u insert a new FAL section
  • 11:19:28 <fger> namelessCoder: question: is there a way to request an update if a new object in a section is added ?
  • 11:19:49 <fger> i didnt find a requestUpdate attr in flux:form.field.object or .section
  • 11:20:41 <fger> the users will run into the error message stating i.e. "Wrong configuration in table 6ab8abebfd"
  • 11:20:57 <fger> this is due to the fact, that the element wasnt saved yet....
  • 11:22:24 <fger> oh btw. using vhs latest dev-branch also
  • 11:25:44 <BenjaminR> fger: does flexforms have such functionality? i guess not.
  • 11:26:39 <fger> what functionality ? save the element before inserting an inline record ?
  • 11:26:42 <fger> i.e. ? yes it does
  • 11:26:44 <bjo3rn> FAL + sections/objects = no workee :/
  • 11:26:59 <bjo3rn> yet
  • 11:27:07 <fger> it doesnt at all ? is there an issue ticket i can watch/contribute ?
  • 11:27:15 <fger> i saw the DCE guys struggling with it also
  • 11:27:25 <bjo3rn> afaik it is not possible at all
  • 11:27:33 <bjo3rn> but
  • 11:27:55 <fger> well it should be possible if you extend i.e. the sys_reference table etc.
  • 11:27:55 <bjo3rn> Claus is working on the migration from flexforms to ste
  • 11:28:00 <fger> ste ?
  • 11:28:02 <BenjaminR> oh i didnt read the above part
  • 11:28:06 <bjo3rn> single table inheritance
  • 11:28:09 <fger> ah ok
  • 11:28:12 <BenjaminR> bjo3rn is right
  • 11:28:56 <bjo3rn> nah, it's not ste. it's dedicated tables for content elements.
  • 11:29:17 <fger> yeah ... somehow the FAL relation table has to know / needs some more info about the object the FAL record is related to
  • 11:29:20 <bjo3rn> anyway, flexforms will be removed somewhere in the future
  • 11:29:22 <BenjaminR> fal relations in sections definited dont work
  • 11:29:24 <BenjaminR> ...yet
  • 11:29:31 <fger> guess the layer "section/objects" is not represented in the core logic
  • 11:29:37 <bjo3rn> exactly
  • 11:29:43 <bjo3rn> that's a flexform thing
  • 11:30:04 <BenjaminR> flexform is core?
  • 11:30:09 <fger> then the FAL guys should have taken care of that :)
  • 11:30:17 <bjo3rn> is it?
  • 11:30:24 <bjo3rn> oups, noob alert 11
  • 11:30:26 <bjo3rn> ^^
  • 11:30:40 <BenjaminR> what else it is? just tell me :)
  • 11:30:48 <fger> what do you mean "flexform is core" ? its a way to store info in a database field and its used by the core yes
  • 11:30:56 <BenjaminR> its part of the core
  • 11:31:06 <BenjaminR> it isnt some addtional / optional package you can install
  • 11:31:09 <fger> no
  • 11:31:22 <bjo3rn> true, strike what I posted above
  • 11:31:46 <fger> its woven into the core, and so i guess its more up to the FAL/Core guys to make that FAL feature work with ALL core mechanisms (localization, workspaces, flexform features...)
  • 11:31:56 <fger> so i might post/search the core issue tracker :)
  • 11:32:08 <bjo3rn> good luck with that ;)
  • 11:32:14 <BenjaminR> i lost track of this conversation. i only said that flexforms are part of the typo3 core
  • 11:32:15 <BenjaminR> :)
  • 11:32:24 <BenjaminR> am i wrong? and why? :)
  • 11:32:31 <bjo3rn> BenjaminR you are right, that's the conclusion ^^
  • 11:32:37 <bjo3rn> and I was wrong
  • 11:32:53 <BenjaminR> doesnt matter :)
  • 11:32:56 <bjo3rn> true
  • 11:33:24 <BenjaminR> fger´s "no" irritated me
  • 11:33:26 <BenjaminR> ;)
  • 11:33:44 <bjo3rn> hehe, confusion all the way ^^
  • 11:33:59 <bjo3rn> async conversation is always fun ^^
  • 11:34:15 <BenjaminR> flux parses fluid and throws some flexform in the backend, not?
  • 11:34:18 <fger> no, it isnt a non-core extension :)
  • 11:34:26 <bjo3rn> muhaha
  • 11:34:27 <BenjaminR> so funtionaltity that isnt represented in flexform wont be in flux yet
  • 11:34:57 <BenjaminR> fx fal in sections :)
  • 11:35:02 <bjo3rn> correct, BenjaminR (afaik)
  • 11:35:19 <bjo3rn> and not untrue
  • 11:36:15 <fger> for the german guys: http://www.typo3.net/forum/thematik/zeige/thema/114274/
  • 11:36:35 <BenjaminR> btw dce isnt normalized too as i know
  • 11:36:45 <fger> yes they plan to do it in DCE 2
  • 11:37:05 <fger> but i guess the dev-community for TYPO3Fluid is more active/speedy :)
  • 11:56:42 <fger> btw. DCE has some nice typoscript snippet to remove the anchor-links around their DCE FCEs
  • 11:56:51 <fger> would be a nice on/off feature for flux
  • 11:56:54 <fger> sry fluidcontent
  • 11:57:42 <fger> https://gist.github.com/fgerards/45350abface3de07141c
  • 11:58:19 <BenjaminR> you mean fluidcontent_core or fluidcontent?
  • 11:58:25 <fger> imho both
  • 11:58:25 <BenjaminR> anyway this should work, not?
  • 11:58:28 <fger> yes
  • 11:58:42 <fger> it disables the anchor wrap only for fluidcontent elements
  • 11:58:52 <fger> the corresponding CType claus' extension registers
  • 11:58:59 <BenjaminR> so there is nothing we need :)
  • 11:59:00 <fger> DCE has it switchable on/off ... find it nice
  • 11:59:00 <BenjaminR> value := addToList(fluidcontent_content)
  • 11:59:05 <BenjaminR> fluidcontent_core
  • 11:59:07 <BenjaminR> it registers
  • 11:59:11 <BenjaminR> not?
  • 11:59:29 <fger> dunno, fluidcontent registers CType fluidcontent_content
  • 11:59:47 <BenjaminR> where is this on/off? extconf?
  • 11:59:53 <fger> typoscript ;)
  • 12:00:13 <BenjaminR> hm i think this is smth for fluidshare
  • 12:00:29 <BenjaminR> most people dont need it so why filling up the ts setup with such things :)
  • 12:00:37 <BenjaminR> if you need it you can add it yourself
  • 12:00:42 <BenjaminR> in your provider extension
  • 12:00:46 <BenjaminR> for me thats the better place for it
  • 12:02:16 <BenjaminR> i am out. bye guys
  • 12:03:28 <fger> cu
  • 12:26:19 <gencha_> is there a viewhelper to generate a link (like f:link.page), but which doesn't render an anchor tag around it?
  • 12:26:36 <gencha_> i want to generate a link for a form action
  • 12:27:00 <gencha_> and when using f:form, it appends a controller to the query
  • 12:28:15 <gencha_> right now i'm using {v:site.url()}index.php?id=xyz but it feels dirty
  • 12:32:55 <erredeco> <f:uri.page> ?
  • 12:33:00 <soee> use ^
  • 12:34:04 <gencha_> erredeco: very awesome. thanks! :)
  • 12:34:36 <erredeco> not at all. I see also there are some vhs viewhelper also
  • 12:35:31 <erredeco> like <v:link.typolink> or <v:uri.typolink> or even <v:uri.request>
  • 13:22:18 <gencha_> is there a viewhelper to retrieve information about the currently logged in fe user? like their name. i can't find anything :P
  • 13:34:14 <fger> yes there should be ... or just do it with cObject fluid viewhelper
  • 13:36:16 <gencha_> fger: didn't find anything. i'm extending Vhs:AbstractSecurityViewHelper right now
  • 13:36:29 <gencha_> wtf, why can't i use backslashes in this kiwi irc client
  • 13:48:00 <fger> gencha_ think you have to pass the feuser object to the view
  • 13:49:27 <fger> and fetch the logged-in user via $ GLOBALS[‘TSFE’]->fe_user->user
  • 13:55:29 <gencha_> fger: this is how i'm doing it now: http://pastie.org/9419973 short and sweet, thanks to the work in the AbstractSecurityViewHelper
  • 14:15:06 <batjony> Guys I want to create a custom content element and like soee suggested I will go with fluidcontent
  • 14:15:11 <batjony> Do I need also https://github.com/FluidTYPO3/fluidcontent_core ?
  • 14:17:06 <beo6> batjony: no
  • 14:18:09 <beo6> its just a replacement for css_styled_content
  • 14:24:28 <batjony> i have started to follow the example here https://github.com/FluidTYPO3/fluidcontent
  • 14:24:45 <batjony> is the example up to date ?
  • 14:24:50 <batjony> because I see Tx_Flux_Core::registerProviderExtensionKey('myextensionkey', 'Content');
  • 14:24:57 <batjony> so no namespaces here
  • 14:25:00 <beo6> how can i make Resource_Record_FalViewHelper return items inside a workspace?
  • 14:27:45 <batjony> I guess that this should be FluidTYPO3\Flux\Core::registerProviderExtensionKey instead of Tx_Flux_Core::registerProviderExtensionKey('myextensionkey', 'Content') ?
  • 14:28:33 <beo6> batjony: both should work
  • 14:38:51 <batjony> The ContentController.php should be placed in typo3conf/ext/<ext>/Classes/Controller/ ?
  • 16:29:54 <gencha_> ...spacerballs
  • 16:46:24 <bjo3rn> yep, vhs#638 was named chunknorris ^^
  • 16:48:25 <gencha_> :D
  • 17:40:32 <randomresult> hi there
  • 17:40:45 <randomresult> anyone around?
  • 20:24:19 <NamelessCoder> nobody names branches like our bjo3rn does
  • 20:25:53 <xaver> NamelessCoder: :P