IRC logs

20140819

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

IRC log range: 20140819*

20140819

  • 09:51:05 <soee> xaver: ping
  • 09:51:16 <xaver> ?
  • 09:51:34 <soee> you are using fluidbootstraptheme ?
  • 09:52:37 <xaver> no i always create my own provider extension. But if i need a similar element i take a look.
  • 10:29:22 <momchil> guys is this fluid content core a full replacement of css_styled_content, does someone use it ? is it working well and stable ?
  • 10:59:35 <Boernd> Hi
  • 11:00:50 <Boernd> yesterday I tried to use v:if but the description in the documentation is not very helping. So I would suggest to add the examples from ttps://github.com/FluidTYPO3/vhs/pull/401 to the documentation page.
  • 11:01:46 <Boernd> I found these while searching the chat protocoll, but IMHO these should be on the documentation page where everyone which tries to use the viewhelper is looking for information.
  • 11:18:59 <ndee_> is there a way to have a localized asset?
  • 13:17:36 <dasFelix> I have a question about <flux:grid> VH. Why is there a name="foo" attribute and what about the label="foo" attribute? When I assign a name by name"Foo", the grid is gone in BE. And label="foo" doesn't show up anything in BE. (Dev Branch)
  • 13:40:17 <NamelessCoder> dasFelix assuming you're not talking about flux:grid itself since it has no label. If you mean flux:grid.column - name is lowercase, label should be automatically built to an XLF path that the core will then translate for you. If you mean flux:form.content inside flux:form.grid please be aware that the behavior of these have changed (in essence: do not use flux:form.content inside flux:grid.column, ever). If you meant something else, please
  • 13:40:17 <NamelessCoder> clarify.
  • 13:43:40 <dasFelix> thx NamelessCoder ... flux:grid.column / row works as expected. But I really mean flux:grid VH. And according to the reference there is a name/label attribute. Thats why I am confused.... please have a look: http://fluidtypo3.org/viewhelpers/flux/development/GridViewHelper.html
  • 13:44:54 <dasFelix> I just found this because I'm transforming my flux:flexform stuff to the new way
  • 14:19:43 <NamelessCoder> dasFelix "name" on flux:grid is a machine-name, using lowerCamelCase, and the value is only used when generating the BE-layout table definition as array (name gets used as array key)
  • 14:20:17 <NamelessCoder> "label" is available to set on *any* form component, but it is not used by all components
  • 14:35:04 <Kaimane> When creating a new content element using fluidcontent / flux there is no new tab in the "new content element wizard". What do I wrong and how to fix it? When installing "fluidbootstraptheme" (all dependent ext are installed) there is no new tab called "bootstrap" too.
  • 14:37:46 <bjo3rn> Kaimane first aid: flush all caches through the install too.
  • 14:37:48 <bjo3rn> *tool
  • 14:38:42 <Kaimane> bjo3rn: I did. "Clear all cache" and "Clear PHP opcode cache" in install tool. But after that the same behavior.
  • 14:39:12 <bjo3rn> which versions of the exts? ter or dev?
  • 14:39:34 <bjo3rn> included the static ts?
  • 14:39:34 <Kaimane> typo3 6.2.4 and all exts from github (dev branch).
  • 14:40:43 <bjo3rn> sorry, there is no more static ts. my bad.
  • 14:40:51 <Kaimane> static ts from fluidbootstraptheme and my ext is included.
  • 14:41:27 <bjo3rn> .oO
  • 14:42:21 <bjo3rn> please enable flux' debug mode (level 2). maybe there's an error in one of your templates.
  • 14:42:26 <Kaimane> Just in that moment I got the reason why new tabs were not shown.
  • 14:42:38 <bjo3rn> which is?
  • 14:43:58 <Kaimane> I installed the ext "uncache" from github (dev branch). When deinstalled it, cleared all caches and opened wizard again, all tabs are still there. "bootstrap", "grid" and my "fce".
  • 14:45:46 <bjo3rn> ok. can you reinstall uncache now?
  • 14:46:08 <Kaimane> Of course I can. Wait a moment please.
  • 14:46:37 <NamelessCoder> I may remember this incorrectly, but EXT:uncache would also prevent new caches from being created and would prevent this cache from working. You'd have to enable to cache circumvention in Flux itself for it to work
  • 14:47:09 <NamelessCoder> - not sure if the cache can/should be protected or ignored by EXT:uncache somehow
  • 14:47:23 <Kaimane> After clicking in install button I got a Fatal error: Call to a member function getBackend() on a non-object in /var/www/clients/client1/web390/private/typo3_src-6.2.4/typo3/sysext/core/Classes/Cache/Cache.php on line 95
  • 14:47:40 <bjo3rn> is the cache you are referring to the one that was .FED_MANIFEST previously, NamelessCoder ?
  • 14:47:48 <NamelessCoder> yes
  • 14:48:00 <NamelessCoder> moved to general category
  • 14:48:39 <Kaimane> After reload ext manager uncache is marked as installed.
  • 14:49:05 <Kaimane> And now the tabs in the wizard are still there.
  • 14:49:41 <bjo3rn> then don't hit 'flush caches' now ^^
  • 14:49:47 <NamelessCoder> Kaimane are you on 6.2? If so: switch TYPO3_CONTEXT environment variable (search docs for that term) to make caches less eager. It may very well mean you don't need EXT:uncache (which, admittedly, may be a bit excessive on 6.2 since introducing contexts)
  • 15:13:30 <Kaimane> NamelessCoder yes, I am on 6.2.4. I switched TYPO3_CONTEXT to "development" in install tool. Now i will deinstall EXT:uncache again.
  • 15:14:26 <NamelessCoder> since 6.2, Flux is also semi-aware of this context so you should have much less need to clear caches
  • 15:16:35 <Kaimane> That was my intension when I installed uncache ... less need of clicking clear caches ;-)
  • 15:21:31 <batjony> hello feders
  • 15:26:25 <batjony> i have a custom CE build with fluidcontent
  • 15:26:55 <batjony> and I want this element to fetch the pages inside a particular sys folder
  • 15:26:58 <batjony> is it possible ?
  • 15:33:54 <TorstenFink> Hi there, i use fluidcontent for building a 50/50 column element, now i also make a text element in a column of this 50/50 element and want to get the variables defined in the form.column, how is this possible?
  • 15:39:03 <NamelessCoder> batjony set pageUid on v:page.menu to UID of your sysfolder
  • 15:39:41 <NamelessCoder> TorstenFink slightly complicated use case, and this will only support the immediate parent element, but:
  • 15:40:38 <NamelessCoder> <flux:form.data table="tt_content" field="pi_flexform" uid="{record.tx_flux_parent}" as="parentData"> ... {parentData.settings.foobar} ... </flux:form.data>
  • 15:40:52 <NamelessCoder> check docs, that there was written from memory
  • 15:41:56 <TorstenFink> ok thanks, ill take a look
  • 15:43:57 <TorstenFink> perfect this is the viewhelper i searched for, thank you
  • 15:44:20 <NamelessCoder> you're welcome :)
  • 15:51:34 <batjony> NamelessCoder: you mean <v:page.menu pageUid="{pageUid sys folder}"></v:page.menu> located in the <f:section name="Main"> in the CE html
  • 15:51:35 <FT3BOT> ¯\_(ツ)_/¯
  • 15:52:31 <NamelessCoder> yes; argument pageUid on v:page.menu set to sysfolder UID
  • 15:52:49 <batjony> this does not render anything, just tried, all caches cleared
  • 15:55:05 <NamelessCoder> assuming you are using the viewhelper tag correctly, the explanation probably lies in your tree structure and how the sysfolder is located relative to the root typoscript template
  • 15:55:42 <NamelessCoder> when you use the sysfolder this way, it *must* be placed in a way that it respects the exact same rules and limitations a normal page has: typoscript inheritance, domain records, page template selected, layout, etc.
  • 15:57:03 <batjony> NamelessCoder: my sys folder contains pages with custom page type (doktype), most likely this is the reason
  • 15:57:16 <batjony> if I try with a sys folder with standard pages - it works
  • 15:57:30 <NamelessCoder> very likely reason. Check viewhelper documentation, it supports custom page types
  • 16:00:44 <batjony> ok, one more question, actually my goal is to render the content of all these custom page types which are inside the sys folder, this is some kind of slider, which content is located in this custom doctype pages, so one slide is actually one page from the sys folder
  • 16:01:29 <batjony> so I want to render all the pages in one place, without any menu
  • 16:02:02 <batjony> then I will add some javascript and create a nice slider
  • 16:03:45 <batjony> any idea ?
  • 16:04:57 <NamelessCoder> use v:page.menu with pageUid + v:content.render with pageUid
  • 16:05:35 <NamelessCoder> rendering will use TS on current page only, while rendering, but as long as you're aware of that, no problem.
  • 16:06:25 <batjony> my initial idea was to use the standard CONTENT typo3 object, and then use in the view <f:cObject typoscriptObjectPath="...." />
  • 16:06:26 <FT3BOT> ¯\_(ツ)_/¯
  • 16:21:22 <batjony> NamelessCoder: so you mean to use v:page.menu for getting all pageUids inside my sys folder and then to make some cycle which will render one by one the content for a particular pageUid using v:content.render ?
  • 16:22:10 <NamelessCoder> yep
  • 16:26:23 <batjony> i also see some slide arguments in the v:cotent.render documentation, but I cant understand them, for example "slide", "slideCollect" - can I use them for my goal, or they have different idea
  • 16:28:39 <NamelessCoder> that's a different purpose - the opposite, actuallyh
  • 16:31:37 <Guest|67309> hey guys i just wanna say, that there are some display problems at ipad and iphone on safari. I tried the new dev version of flux etc... cheers.
  • 16:31:56 <Guest|67309> *the error is that the ressources are failed to load
  • 16:32:12 <Guest|67309> so there is a connection problem displayed
  • 16:35:07 <batjony> NamelessCoder: I am looking on v:page.menu, but I do not see how it could return IDs, as I see the helper outputs html, does not return any result
  • 16:35:27 <batjony> or you mean to use the argument "as", which will store the result in a variable
  • 16:35:33 <batjony> and then use this variable ?
  • 16:47:20 <batjony> maybe @benjaminr coulse also help me ?
  • 16:49:52 <batjony> or @xaver or @soee :)
  • 16:50:31 <soee> batjony: yes use variable, and loop through returned array
  • 16:51:58 <batjony> soee: but I just tried <v:page.menu pageUid="12" as="menuItems"></v:page.menu> <f:debug>{menuItems}</f:debug> but {menuItems} does not contain anything
  • 16:51:59 <FT3BOT> ¯\_(ツ)_/¯
  • 16:53:35 <batjony> oo i see now, actually when "as" is used, v:page.menu works like a foreach loop
  • 16:53:55 <xaver> batjony: inside </v:page.menu>
  • 16:54:12 <batjony> ya, then it works :)
  • 16:54:14 <batjony> 10x
  • 17:40:07 <soee> gusy for og tags you are using TS or some extension ?
  • 18:05:10 <GRIMMCREATIVE> vhs - the absolute hammer. I love it... thanks. This ... Menu works - crazy shit.
  • 18:28:43 <GRIMMCREATIVE> someone a tipp for me how i can get an active class to f:link.page or v:page.link ? THANKS
  • 18:28:44 <FT3BOT> ¯\_(ツ)_/¯
  • 18:30:24 <GRIMMCREATIVE> omg. thinking before writing. have it
  • 20:50:34 <Guest|89961> Hi - I have noticed that sites I built on fluidtypo3 is slower than sites built with templaVoila. Should it not be the other way around?
  • 20:54:09 <GRIMMCREATIVE> can i not confirm. especially since 6.2 absolutely no longer.
  • 21:16:59 <xaver> Guest54515: normally no - it depends a lot on your template. If you use dynamic stuff and old versions it is possible
  • 21:17:33 <GRIMMCREATIVE> not the right guest i think :D - and he is already gone
  • 22:43:57 <Guest54515> :-)