IRC logs

20150303

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

IRC log range: 20150303*

20150303

  • 02:29:58 <pRiMU5> good morning everybody
  • 02:31:37 <pRiMU5> can any1 help me with a multilanguage issue? i have created a fce with an inline.fal element. everything works fine so far in default language. but when i translate a page and copy the default elements to the new created language, fedext is not saving the sys_language_uid to the fal in the sys_file_reference table. so i am not able to get the meta information of the translated relation.
  • 02:31:41 <pRiMU5> any ideas?
  • 05:15:00 <JohPie> I use <flux:field.inline.fal name="settings.picture" maxItems="1" /> in Configuration section for a page
  • 05:17:11 <JohPie> If the subpages have the same pagelayout I get an error after create a fal relation
  • 05:17:56 <JohPie> after saveing the page the relation is set for the page and for the subpages too
  • 05:18:13 <JohPie> Can someone verify this?
  • 05:19:16 <JohPie> I use TYPO3 6.2.10, flux 7.1.2, fluidpages 3.1.2 and fluidcontent 4.1.1
  • 06:16:55 <s-andersen> I have a single page in a pagetree, where the backend layout will simply not render, FE is fine. List module works fine. Even if I disable all content elements, there's no success. What can be the cause of this behavior?
  • 06:33:48 <tv_sebastian> Hi guys. Is there an approx date for the 7.2 release because of the support of 7.x ?
  • 06:59:37 <Idleworks> hej
  • 07:00:38 <deffcon_> hey guys. i migrated FCEs from FED to fluidcontent DCEs. backend preview shows me that it got the new definitions. but if i try to edit or look in frontend i get "INVALID VALUE("fed_fce") and "Content Element type "fed_fce" has no rendering definition!".
  • 07:00:55 <deffcon_> the tt_content entries have still "CType" "fed_fce"
  • 07:01:10 <deffcon_> and tx_fed_fcefile
  • 07:01:19 <deffcon_> what have i missed to do?
  • 07:01:40 <NamelessCoder> run the EM upgrade script for fluidcontent, that should correct your CType entries
  • 07:03:18 <deffcon_> sadly it gave following output "0 rows have been updated"
  • 07:05:01 <NamelessCoder> should work - https://github.com/FluidTYPO3/fluidcontent/blob/development/class.ext_update.php#L21
  • 07:05:26 <NamelessCoder> last changed some six months ago (to also clear caches)
  • 07:09:36 <Idleworks> i have several provider extension within a typo3 installation. each extension serves one page tree. is it possible to set content and page elements from flux to one page tree? at the moment I have one tab (group) for each extension. but that means an editor can select element of another page tree
  • 07:10:00 <deffcon_> was the same script. tough it showed 0 rows affected the fed_fce CTypes are replaced by fluidcontent_content
  • 07:14:05 <NamelessCoder> Idleworks see https://github.com/FluidTYPO3/flux/issues/747 - work in progress
  • 07:19:59 <NamelessCoder> deffcon_ yep, was the order of SQL queries. This commit just now fixes that. It still worked, just reported wrong.
  • 07:20:36 <deffcon_> it's great that it works ;)
  • 07:20:57 <NamelessCoder> thanks for finding the bug ;)
  • 07:22:45 <Idleworks> NamelessCoder thanks for the hint
  • 07:23:14 <NamelessCoder> Idleworks e.t.a probably some time during the weekend - need to get this week over first.
  • 07:24:08 <NamelessCoder> and after the change you'll be able to override anything, not just enabled/disabled state, through TS.
  • 07:24:47 <flyingfish> I have added extentions: fluidpages,fluidcontent,vhs,flux
  • 07:24:47 <flyingfish> after that i have created an extension with extension builder
  • 07:24:47 <flyingfish> after that i have added: \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile($_EXTKEY, 'Configuration/TypoScript', 'myextension_ext'); in ext_tables.php
  • 07:24:47 <flyingfish> in ext_localconf.php i've added:
  • 07:24:47 <flyingfish> \FluidTYPO3\Flux\Core::registerProviderExtensionKey('parkside_ext', 'Content');
  • 07:24:47 <flyingfish> \FluidTYPO3\Flux\Core::registerProviderExtensionKey('parkside_ext', 'Page');
  • 07:24:47 <flyingfish> After that i have set templateRoot, layoutRoot, partialRoot in setup.txt which is set up in template setup.
  • 07:24:48 <flyingfish> After that I have added Foo.html in template and the other foo.html in layouts )like suggested on this sites tutorial)
  • 07:24:48 <flyingfish> In page->edit->Page Layouts i got one option which i have selected.
  • 07:24:49 <flyingfish> now i get an error: Could not analyse class:flux\ViewHelpers\FormViewHelper maybe not loaded or no autoloader?
  • 07:24:49 <flyingfish> What did I miss/do wrong/forgot?
  • 07:25:53 <NamelessCoder> flyingfish you probably forgot to add the "flux" namespace in one or more of your templates
  • 07:26:30 <NamelessCoder> or you set it to a legacy value of Tx_Flux_ViewHelpers which should be FluidTYPO3\Flux\ViewHelpers now
  • 07:27:55 <NamelessCoder> if you use xmlns:flux, the correct namespace is http://typo3.org/ns/FluidTYPO3/Flux/ViewHelpers
  • 07:31:24 <flyingfish> hmm..i have changed now from: xmlns:flux="http://typo3.org/ns/flux/ViewHelpers" to xmlns:flux="http://typo3.org/ns/FluidTYPO3" and its still the same
  • 07:32:40 <flyingfish> these are all the xmlns's:
  • 07:32:41 <flyingfish> xmlns="http://www.w3.org/1999/xhtml" lang="en"
  • 07:32:41 <flyingfish> xmlns:f="http://typo3.org/ns/TYPO3/Fluid/ViewHelpers"
  • 07:32:41 <flyingfish> xmlns:flux="http://typo3.org/ns/FluidTYPO3"
  • 07:32:41 <flyingfish> xmlns:v="http://typo3.org/ns/vhs/ViewHelpers">
  • 07:33:16 <flyingfish> (after changing flux ns
  • 07:33:17 <flyingfish> )
  • 07:40:59 <NamelessCoder> http://typo3.org/ns/FluidTYPO3/Flux/ViewHelpers not http://typo3.org/ns/FluidTYPO3
  • 07:41:20 <NamelessCoder> maybe your client cropped that line but I definitely wrote the full URL earlier ;)
  • 07:41:41 <NamelessCoder> the same thing goes for VHS by the way
  • 07:42:49 <flyingfish> oh, tnx -... ill try now :)
  • 07:43:52 <flyingfish> YEAH ... tnx NamelessCoder!!! i owe you a beer! :)
  • 07:44:25 <NamelessCoder> ^^
  • 07:48:19 <AlexN> hello out there. I hope you do good :)
  • 07:49:12 <AlexN> in irc #typo3 i have heard this is the chatroom for fluid issues.
  • 07:50:29 <AlexN> Is that correct?
  • 07:52:28 <NamelessCoder> AlexN if it's about vhs, flux, fluidcontent, fluidpages, fluidcontent_core... then you've come to the right place
  • 07:55:31 <AlexN> Glad to hear that :) Well, I assign domain models in my controller to fluid but I cannot access the functions. I currently have a workaround using magical getter. Is it a mistake by myself or simply not possible to access model functions in fluid?
  • 07:57:21 <NamelessCoder> that's maybe a bit of a broad question. First of all: Fluid uses the ObjectAccess object to access values and this method supports all recognised getters on model instances
  • 07:57:47 <NamelessCoder> so the problem in this case sounds more like you're going outside the pattern of recognised getters - you shouldn't do that.
  • 07:58:24 <NamelessCoder> that being said: there are ways to achieve the result you want also with custom getters but without magic methods which you definitely should consider avoiding.
  • 07:58:46 <NamelessCoder> 1) let your domain objects implement ArrayAccess. ObjectAccess will recognise this and attempt access as array.
  • 07:59:12 <NamelessCoder> 2) Use v:call on your model instance to call unrecognised methods - but consider 1) first and foremost.
  • 08:02:00 <AlexN> Yeah, I agree with you. Magical getters aren't the best way to do. I will research the points you mentioned and come back if I have further questions regarding fluid :) For now you did me good tips. Thanks ! :)
  • 08:04:34 <NamelessCoder> yw
  • 08:55:36 <Guest|78812> Hey! can someone help me exploting a string with fluid?
  • 08:56:21 <Guest|78812> Here is what i tried: <v:iterator.explode content="test,test2,test3" glue="," as="var" /> ... debug return NULL :/
  • 08:59:27 <Akii> try using the inline annotation if available
  • 09:00:04 <Akii> otherwise make sure to use the scope properly: <v:iterator.explode ...>{var -> f:debug()}</v:iterator.explode>
  • 09:00:41 <Akii> *inline + v:var.set (or whatever the new VH is called)
  • 09:03:31 <AlexN> NamelessCoder? Do you have link where "domain objects implement ArrayAccess" is explained.
  • 09:06:02 <Guest|78812> inline isnt available i've tried this syntax: <v:iterator.explode content="test,test3,test5" glue="," as="var">{var -> f:debug()}</v:iterator.explode> but its still returning NULL
  • 09:10:13 <AlexN> Okay, I've found out... one has to write the function name without "get" as prefix.
  • 10:07:57 <Idleworks> @NamelessCoder I have a weird problem with flux and typo3 >= 6.2.9
  • 10:08:33 <Idleworks> somehow caching is completely turned off
  • 10:09:30 <Idleworks> when I deinstall provider ext and fluidpages, caching is ok
  • 10:09:51 <Idleworks> uninstall*
  • 10:10:42 <Idleworks> I try to find a solution for 3 hours
  • 10:11:10 <Idleworks> now i downgraded typo3 to 6.2.8 and caching is back on
  • 10:55:45 <Idleworks> figured out that this is a core bug when prefixLocalAnchors is set to all
  • 10:56:03 <Idleworks> so nothing to do with flux, sorry
  • 11:00:56 <Idleworks> https://forge.typo3.org/issues/65492
  • 11:18:38 <NamelessCoder> go right ahead guys - give that one a try on 7.1 ;)
  • 12:13:43 <Guest|48683> Hey guys, I use fluidcontent 4.1.1 with vhs 2.2.0 and got a strange problem. If I use the v:uri.typolink viewhelper the new content element rendering for this FCE breaks
  • 12:15:49 <Guest|48683> There is a broken image for the icon visible and no text from the language files are visible
  • 12:16:06 <Guest|48683> If I remove the viewhelper everything works fine...
  • 12:16:51 <NamelessCoder> Guest|48683 maybe you forgot to include the "v" namespace in the template
  • 12:17:14 <Guest|48683> I include this {namespace v=Tx_Vhs_ViewHelpers}
  • 12:17:30 <Guest|48683> Shouldn't that be sufficient?
  • 12:17:57 <NamelessCoder> you'll need {namespace v=FluidTYPO3\Vhs\ViewHelpers} for VHS 2.2+
  • 12:18:52 <Guest|48683> That's it!
  • 12:18:56 <Guest|48683> You're awesome :)
  • 12:18:59 <Guest|48683> Thanks mate
  • 12:19:18 <NamelessCoder> you're welcome :)
  • 14:51:11 <s-andersen> Hi, I load jQuery with vhs assets handling, loaded in the footer. Now I need to add some inline javascript from an extension below the file generated by vhs. But how do I accomplish this?
  • 14:55:15 <NamelessCoder> s-andersen give your jQuery inclusion a name property and add that in "dependencies" in the asset block you put your inline JS into
  • 14:55:48 <NamelessCoder> that will make the rendering order irrelevant so you can make sure it comes in the right order always
  • 15:06:59 <s-andersen> NamelessCoder: That works great! Now I have three different places I need to add code to the same file. Can I just chain three createFromContent() right after each other and call finalize just before the end of the extension?
  • 15:10:11 <NamelessCoder> not really - if you mean chaining as in fluid syntax (that doesn't make much sense with assets). But yes, you can have three assets depend on each other in a sequence
  • 15:13:35 <s-andersen> NamelessCoder: I do this: $this->asset->createFromContent($this->productDeleted($uid))->setType('js')->setDependencies('jquery')->setStandalone(FALSE)->finalize();
  • 15:14:04 <s-andersen> I need to do it three times. Should I make three separate instances instead of setting $this->asset
  • 15:15:07 <NamelessCoder> oh, you use php - neat
  • 15:15:14 <NamelessCoder> you need to have three of those statements then
  • 15:15:30 <NamelessCoder> chaining returns the same instance over and over; you need three seperate instances here.
  • 15:20:56 <s-andersen> NamelessCoder: This is just great. I'm converting an old pibase extension which I didn't make. I feared it would be a pain to stick to conventions of having JS in the footer, but VHS really makes it a breeze
  • 15:21:43 <NamelessCoder> you can also add them as TS if you like - same property names etc.
  • 15:22:02 <NamelessCoder> direct php is the most efficient of course
  • 15:22:59 <s-andersen> NamelessCoder: We already do most of the scripts via TS, but this inline JS required some dynamically inserted productnames and properties from PHP.
  • 15:23:44 <NamelessCoder> hehe yep, this is the whole point of having all three APIs supported :)
  • 15:24:36 <s-andersen> And this is where you deserve a lot of credit. I needed to solve a specific problem, and decided to browse the code to see what you had done, and because it was so well documented I figured that what I already did in TS was possible to do in PHP, even from a non-extbase extension.
  • 15:25:59 <NamelessCoder> aw thanks :)
  • 15:26:16 <NamelessCoder> the hard part is usually finding out which tool you need, because there are so many small use cases
  • 15:28:15 <s-andersen> Exactly, and I guess that is an issue for everyone, not only for people using FluidTYPO3, but even someone starting with TYPO3 will ask "What do I do to create a template", and there will be several possibilities, most of them outdated.
  • 17:09:34 <xaver> bammmm inproved lot of v7 stuff