IRC logs

20141210

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

IRC log range: 20141210*

20141210

  • 09:35:59 <qBic> hey guys ... i have a very odd problem with fluid content elements
  • 09:36:25 <qBic> i already posted a report on github, but didn't get any answer yet
  • 09:36:50 <qBic> if i insert a new fluid content element on the first position everything is fine
  • 09:37:36 <qBic> but if i insert the element somewhere else, i guess sometimes the flux configuration is not found
  • 09:37:52 <qBic> this would be the report on github: https://github.com/FluidTYPO3/fluidcontent/issues/201
  • 10:39:21 <cbleicker> heyho
  • 10:42:02 <cbleicker> response in extbase does not contain any response header infos, right? i need to set the header directly in the controller action?
  • 10:46:55 <Akii> cbleicker: $this->response->addAdditionalHeaderData
  • 10:47:49 <cbleicker> and this will be processed from general page building?
  • 10:48:09 <Akii> yep even works for cached pages
  • 10:52:05 <cbleicker> aha :)
  • 10:52:06 <cbleicker> \TYPO3\CMS\Extbase\Mvc\Web\Response::setStatus
  • 10:52:35 <cbleicker> thanks, akii
  • 10:52:47 <Akii> np
  • 10:58:45 <tdeuling> hi @ all. is there a viewhelper in vhs for rendering a partial from a thirdparty extension?
  • 10:59:32 <qBic> hey guys ... i have a very odd problem with fluid content elements
  • 10:59:32 <qBic> i already posted a report on github, but didn't get any answer yet
  • 10:59:33 <qBic> if i insert a new fluid content element on the first position everything is fine
  • 10:59:33 <qBic> but if i insert the element somewhere else, i guess sometimes the flux configuration is not found
  • 10:59:33 <qBic> this would be the report on github: https://github.com/FluidTYPO3/fluidcontent/issues/201
  • 11:03:16 <NamelessCoder> tdeuling see https://fluidtypo3.org/viewhelpers/vhs/master/Render/TemplateViewHelper.html
  • 11:06:33 <tdeuling> NamelessCoder thanks, that one i've found already :) I thought about a viewhelper like: https://gist.github.com/Teddai/5830257 I think it's prettier to call such a viewhelper by using extensionName and partial..
  • 11:08:11 <tdeuling> wouldn't be it interesting for vhs? I could integrate them and create a pull request..
  • 11:09:14 <NamelessCoder> they do pretty much the same thing
  • 11:10:52 <NamelessCoder> what we could use, is support for rendering a specific section inside v:render.template, and I have no objections against letting v:render.template accept either the template path OR an extensionName+(template|partial=path-starting-from-templates-root)+(section).
  • 11:18:08 <tdeuling> that sounds good. the selection of a special section within a template/partial is absolutely necessary.
  • 11:18:45 <NamelessCoder> definitely; I think it's only missing from both those viewhelpers because they are from the 4.x days
  • 11:21:53 <tdeuling> I could offer some help on that, but I think I couldn't do that in such a good code quality like yours ;)
  • 11:24:09 <NamelessCoder> the first step would be to just get it working inside the class - if you do that and create a PR, we'll go over it together
  • 11:26:46 <qBic> hey @NamelessCoder, do you have any idea what could cause my above mentioned Problem with fluid content elements???
  • 11:26:47 <Guest|35521> I am trying to set up a new page with fluidcontent_core (+page,content,vhs) and tried to create a vanilla mailform, but i can't see any fields to edit in backend. did i miss anything or is the mailform not implemented in fluidcontent_core yet?
  • 11:28:28 <j6s> I am trying to set the group of an FCE via typoscript but it's not working properly. Is the thing I am trying even possible?
  • 11:28:58 <NamelessCoder> qBic unless you're using a custom Provider class and it is set up to be a bit too eager to trigger on content records, no... no idea.
  • 11:31:41 <qBic> well, no ... but maybe this helps: the problem occured updating TYPO3 from 6.1 to 6.2 and updating flux, vhs, fluidpages & fluidcontent to the current github versions
  • 11:33:12 <cbleicker> erm, controller action: $this->controllerContext = NULL ???
  • 11:33:17 <cbleicker> why NULL?
  • 11:36:02 <cbleicker> $this->getControllerContext()->getRequest()->getArguments()->getArgument('foo') should be possible or not?
  • 11:37:21 <cbleicker> this one works: $this->arguments->offsetGet('contact')->getPropertyMappingConfiguration()
  • 11:39:14 <NamelessCoder> $this->arguments is the definition, $this->request holds the request arguments
  • 11:39:39 <NamelessCoder> $this->controllerContext is, iirc, deprecated in favor of getControllerContext() - or vice versa
  • 11:47:41 <Guest|35521> i see you have bigger problems, but could i get a quick answer if the standard mailform is usable now with fluidcontent_core?
  • 11:56:09 <batjony> guys, how can I disable the view from a ContentController action ?
  • 11:56:36 <batjony> return false doestn work
  • 11:56:51 <tdeuling> @NamelessCoder sorry, got a phone call. I'll start it and send you a PR
  • 11:57:33 <NamelessCoder> Guest|35521 if I am remembering it right: the search, login and contact forms all silently depend on css_styled_content which is why fluidcontent_core does not (currently) support them.
  • 11:58:00 <NamelessCoder> tdeuling no rush, I am not really here
  • 11:59:54 <batjony> guys why something like http://pastebin.com/FewDxAL4 still renders the view
  • 12:00:39 <NamelessCoder> batjony return something not-empty
  • 12:01:03 <NamelessCoder> empty return means extbase calls the view->render
  • 12:02:17 <batjony> ya works now, i didnt know it, is there some other way to disable the view instead of return "something"
  • 12:02:34 <batjony> something like $this->getVIew()->setDisabled(true)...
  • 12:03:08 <Guest|35521> ok, thank you
  • 12:05:04 <NamelessCoder> batjony the short answer is no. The long answer is yes, but you have to manipulate the controller class - not the view. The controller renders the view, not the other way around
  • 12:05:38 <NamelessCoder> and you may find yourself overriding a handful of methods, all in the name of trying to avoid returning something not-empty
  • 12:10:16 <Xatenev> Heya
  • 12:10:34 <Xatenev> One question, its not really related to fluid but probbaly somebody of you knows the solution^^
  • 12:10:52 <Xatenev> I am using the normal backend content element "Text & Images". Problem: the images are rendered into the source code with width 0 and height 0
  • 12:10:58 <Xatenev> Maybe somebody got an idea? =)
  • 12:11:12 <Xatenev> It works for all other typo3 projects here...
  • 12:12:16 <Guest|35521> Xatenev do the image tests in install tool work?
  • 12:12:25 <Xatenev> It works for single images
  • 12:12:30 <Xatenev> the normal single image content element
  • 12:12:34 <Xatenev> just not with text & images...
  • 12:14:20 <Guest|35521> Xatenev maybe try a older css_styled_content static template?
  • 12:14:37 <Xatenev> *trying*
  • 12:14:37 <Xatenev> ^^
  • 12:15:06 <Xatenev> not working
  • 12:15:07 <Xatenev> =(^^
  • 12:18:21 <NamelessCoder> DENMARK! FUCK YEAH! http://i.imgur.com/zOKErBJ.jpg
  • 12:18:53 <Guest|35521> so at least its not a problem of typoskript. weird it works for single images
  • 12:20:09 <Guest|35521> would have guessed it would be some kind of ts register stuff.
  • 12:25:31 <Akii> haha
  • 14:52:34 <j6s> May I ask again, if I am right, that I can not read my group name from typoscript?
  • 16:37:15 <mloew> Hi everyone, can someone give me some hints as to why my Fluid Content Elements aren't displayed in the Typo3 Backend?
  • 16:37:40 <mloew> I use <flux:form wizardTab="Content Elements" >
  • 16:38:25 <mloew> Are there any common mistakes I could check for?
  • 16:42:49 <Akii> thats obsolete, read the changes and/or current documentation
  • 16:43:08 <mloew> If I manually chose "Fluid Content" as Content Type I see no types
  • 16:43:26 <mloew> I know it's deprecated... I can't update to the current TER Version as of right now =/
  • 16:43:39 <mloew> I'm on Flux 7.0.0
  • 18:53:28 <cbleicker> counter_number
  • 18:53:33 <cbleicker> counterNumber
  • 20:20:02 <cbleicker> anybody knows this? Exception while property mapping at property path &quot;customers.0&quot;:The target type was no string, but of type &quot;NULL&quot;
  • 20:44:02 <NamelessCoder> cbleicker sounds like a cached reflection of the controller argument not being refreshed
  • 20:44:19 <NamelessCoder> or a custom mapping rule that's not correct
  • 20:48:02 <cbleicker> extending AbstractEntity and it will be converted. without entity its not converted
  • 20:48:09 <cbleicker> watzefug?
  • 20:49:50 <NamelessCoder> only entities can be converted by the default PersistedObjectConverted
  • 20:51:29 <cbleicker> why?
  • 20:51:47 <cbleicker> this is totaly useless if youre working with dto :(
  • 20:54:36 <NamelessCoder> EXT:news solves this by manually mapping the DTO
  • 20:54:39 <NamelessCoder> https://git.typo3.org/TYPO3CMS/Extensions/news.git/blob/HEAD:/Classes/Controller/NewsController.php
  • 20:55:15 <NamelessCoder> I would create a typeconverter or register a genericobjectconverter for that argument
  • 21:45:16 <cbleicker> NamelessCoder: you can convert to simple objects ^^
  • 21:45:49 <cbleicker> ->setTypeConverterOption('\TYPO3\CMS\Extbase\Property\TypeConverter\PersistentObjectConverter', \TYPO3\CMS\Extbase\Property\TypeConverter\PersistentObjectConverter::CONFIGURATION_TARGET_TYPE, 'TYPO3\CMS\Extbase\Persistence\ObjectStorage<Foo\Bar\Domain\Dto\Customer>')
  • 21:46:46 <cbleicker> totaly wired