IRC logs

20150730

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

IRC log range: 20150730*

20150730

  • 00:24:54 <mneuhaus> xaver: lol :D "Note: In order to ship our implementation of srcset in time for Windows 10, Microsoft Edge currently does not support the width (w) descriptor – we’re working on adding this in a future update."
  • 00:25:07 <mneuhaus> the width descriptior is the most useful part ^^
  • 00:43:20 <intva> good morning ;)
  • 00:44:34 <intva> I have a strange problem. made a simple file field, saved an image. in the var the whole path and the imagename is saved but v:media.image just renders the URL. same with f:image
  • 01:58:13 <rosieres> intva code?
  • 02:13:51 <intva> hi rosieres. right now I changed it to fal inside the sections. but this doesn't work too
  • 02:14:19 <intva> is it possible to use flux:field.inline.fal inside a section-object
  • 02:15:25 <intva> this is my code: http://pastebin.com/i0e6tQST
  • 02:15:52 <MarcHH> Hi. When using the TYPO3 content element "Insert Record" to make a reference to another content element I get an error in the FE which breaks down to the wrong SQL-statement "SELECT * FROM tt_content WHERE uid IN () ORDER BY sorting ASC". TYPO3 6.2.14, current flux,vhs etc. PageProvider build with FluidPowered TYPO3, content rendering with fluidcon
  • 02:15:52 <MarcHH> tent_core. Any idea?
  • 02:16:38 <rosieres> intva -> field: 'object.previewImage' ??
  • 02:17:04 <rosieres> IC
  • 02:19:38 <intva> @rosieres what do you mean?
  • 02:20:36 <rosieres> intva: first. you are good advised to use settings array instead of object.
  • 02:23:17 <rosieres> intva: this 100% works -> http://codeshare.io/f5IhY
  • 02:24:56 <intva> hmm. ok settings made the trick
  • 02:24:57 <intva> thx
  • 02:25:09 <intva> can I ask one more question ;)
  • 02:25:22 <rosieres> intva: this is because settings is automatically propagated
  • 02:25:28 <intva> ah ok
  • 02:26:42 <intva> when I select the fal image I get an error "Wrong configuration in table 16cbf816a0"
  • 02:27:00 <intva> I have to save the "empty" content-element and then saving the fal image is possible. any idea?
  • 02:28:22 <rosieres> intva: is it a clean install or did you upgrade flux and so on?
  • 02:28:55 <intva> upgrade
  • 02:29:27 <rosieres> clear caches, run update scripts, then compare installtool
  • 02:30:00 <intva> ok. and one more thing ;), sorry, but this are my first tries with fluidcontent
  • 02:30:21 <intva> I want to translate the name/label of the fields inside the section/object
  • 02:30:41 <intva> I have <trans-unit id="flux.downloadsCE.fields.previewImage">
  • 02:30:41 <intva> <source>Preview-Image</source>
  • 02:30:41 <intva> </trans-unit>
  • 02:31:00 <intva> but in the backend no "text" shows up
  • 02:31:24 <intva> other translations outside of sections work
  • 02:31:48 <rosieres> you are good advised to put translations in external file
  • 02:32:09 <intva> yes they are in a locallang file
  • 02:34:38 <rosieres> intva: gist the code for the files
  • 02:34:50 <rosieres> https://gist.github.com/
  • 02:35:15 <intva> https://gist.github.com/anonymous/27a9ec97685778354a4c
  • 02:35:35 <rosieres> and the rest?
  • 02:36:00 <rosieres> you can put multiple files in a gist
  • 02:36:16 <intva> is exactly like the pastebin from before
  • 02:36:35 <rosieres> yes. But I want to see the code of the reference
  • 02:37:43 <intva> https://gist.github.com/anonymous/1b8e0b0461f0c9ed4213
  • 02:38:41 <rosieres> is this only true to FAL?
  • 02:39:17 <intva> no to all fields inside the section
  • 02:39:40 <rosieres> preview or main?
  • 02:39:56 <intva> preview
  • 02:40:15 <intva> ehm, I mean when saving the content-element
  • 02:40:53 <rosieres> <f:if condition="{preview}==1"> wtf is that?
  • 02:40:54 <FT3BOT> ¯\_(ツ)_/¯
  • 02:41:32 <intva> haha, yes it is just for me testing and quick and dirty
  • 02:42:35 <rosieres> and why don't you set settings.previewImage ? in form.object
  • 02:46:47 <MarcHH> Hi again. :-) When using the TYPO3 content element "Insert Record" to make a reference to another content element I get an error in the FE which breaks down to the wrong SQL-statement "SELECT * FROM tt_content WHERE uid IN () ORDER BY sorting ASC". TYPO3 6.2.14, current flux,vhs etc. PageProvider build with FluidPowered TYPO3, content rendering wit
  • 02:46:47 <MarcHH> h fluidcontent_core. Any idea?
  • 02:47:23 <rosieres> intva: you are also good advised to use sheets -> flux:form.section -> flux:form.sheet
  • 02:47:46 <MarcHH> I've seen related bug reports (#103, #160) but can't figure out which is already fixed and which may be a good/bad idea to patch locally...
  • 02:48:32 <rosieres> MarcHH in flux?
  • 02:50:35 <MarcHH> fluidcontent_core
  • 02:51:10 <rosieres> MarcHH no open issues. So I shall be fixed.
  • 02:51:29 <rosieres> https://github.com/FluidTYPO3/fluidcontent_core
  • 02:52:04 <rosieres> are you running TER or git version?
  • 02:52:12 <MarcHH> https://github.com/FluidTYPO3/fluidcontent_core/issues/164
  • 02:53:05 <MarcHH> it seems that one of the "fixes" have broken this. Is there any "best practice" to handle this problem?
  • 02:53:49 <rosieres> ARE YOU RUNNING TER VERSION?
  • 02:54:05 <MarcHH> yes
  • 02:54:27 <rosieres> then take the git developent branch which has the fix in
  • 02:55:12 <MarcHH> ok, thanks. I'll try this.
  • 02:55:25 <rosieres> you know hwo?
  • 03:00:30 <MarcHH> pulling from git and deploying on the server? :-)
  • 03:00:49 <rosieres> y
  • 03:01:16 <MarcHH> yes, thank you.
  • 03:08:46 <intva> ok, but will using sheets solve my translation problem?
  • 03:09:45 <MarcHH> Thanks rosieres, dev branch seems to solve the problem. (y)
  • 03:13:29 <rosieres> good
  • 03:16:32 <rosieres> intva: removing unessecary nesting and using sheets as best practice should make it easier. And maybe the translation then appears.
  • 03:17:54 <intva> but unessecary nesting? I just want a section with some fields inside. thats it
  • 03:19:41 <rosieres> intva: see the first listing -> https://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/language-usage.html
  • 03:20:13 <rosieres> <form><form.sheet></form.sheet></form>
  • 03:20:34 <intva> form-form.sheet.section.object.field
  • 03:21:24 <rosieres> forget object
  • 03:21:32 <rosieres> you are using settings array
  • 03:21:51 <intva> ok, I thougth object is needed inside sections
  • 03:21:56 <intva> I give it a try
  • 03:23:03 <rosieres> section is older stuff.
  • 03:23:47 <rosieres> section is toplevel now
  • 03:58:09 <sitegeist_alex> Good morning everybody! If have a question regarding https://github.com/FluidTYPO3/vhs/issues/808
  • 03:59:40 <sitegeist_alex> We are still in progress with the update of vhs and found out that the following was working before the update of vhs to the current development branch:
  • 03:59:51 <sitegeist_alex> <v:resource.image identifier="{v:content.resources.fal(field: 'image') -> v:iterator.extract(key: 'id') -> v:iterator.first()}" maxWidth="150" />
  • 04:00:13 <sitegeist_alex> this generated an <img>-Tag and now it only results in "Array"
  • 04:02:46 <sitegeist_alex> This behaviour has been introduced in commit 0630c1a
  • 04:03:34 <sitegeist_alex> Could you reopen the issue #808 so that I can fix that?
  • 05:47:59 <rosieres> jmverges long time not seen. I saw you envolved :-)
  • 05:48:13 <jmverges> hi rosieres, yeah mate
  • 05:48:21 <jmverges> I had a bad months
  • 05:49:35 <jmverges> stress plus anxiety, I left the job, I study sailing and know I'm back to code ;)
  • 05:53:55 <rosieres> hopefully you are fine again!
  • 06:00:10 <NamelessCoder> sitegeist_alex is <v:resource.image> itself outputting "Array" or does it put "Array" as identifier? In any case: issue re-opened!
  • 06:02:01 <7GHAAT81V> [builder] NamelessCoder closed pull request #71: [TASK] Updated extension name field description (development...updateLabel) https://github.com/FluidTYPO3/builder/pull/71
  • 06:02:01 <18VAADLRE> [builder] NamelessCoder pushed 2 new commits to development: https://github.com/FluidTYPO3/builder/compare/62a96cd8e2f6...6617cecc1b04
  • 06:02:01 <18VAADLRE> builder/development cfb5992 jmverges: [TASK] Updated extension name field description
  • 06:02:02 <18VAADLRE> builder/development 6617cec Claus Due: Merge pull request #71 from jmverges/updateLabel...
  • 06:53:38 <Guest|67067> hi, I have fluidcontent_core running and want to add a checkbox to the upload.html. is this possible?
  • 08:03:25 <moger-xx> I am running fluidpages and have a page template "category" with a corresponding categoryAction in my pageController. I also have a "detail" template with a detail action. Now , in categoryAction, I want to forward to detailAction. I get an exception: "Could not analyse class:Tx_ConMyprovider_Controller_PageController maybe not loaded or no autol
  • 08:03:26 <moger-xx> oader?"
  • 08:03:41 <moger-xx> i simply do $this->forward('detail');
  • 08:04:39 <moger-xx> what I want to archieve is a typo3 page that switches dynamically between two page templates.
  • 08:05:14 <moger-xx> of course I could also do this with one template, a variable and two partials but i prefer two distinct actions and templates.
  • 09:13:00 <Timross> Hi, I'm trying to override one of the partials in fluidcontent_core with my own partial in my extension. but it doesn't seem to work.
  • 09:14:16 <Timross> I've added the following to my setup text in my ext,
  • 09:14:18 <Timross> plugin.tx_fluidcontentcore.view {
  • 09:14:25 <Timross> partialRootPaths.1 = EXT:site_distribution/Resources/Private/Partials/
  • 09:14:36 <Timross> }
  • 09:15:27 <Timross> but what ever I do it always uses the partial from the core.
  • 09:16:31 <Timross> it looks correct in the typoscript object browser in the backend.
  • 09:16:39 <jmverges> you cleared cache?
  • 09:16:46 <Timross> yep :-)
  • 09:17:01 <jmverges> did you make your extension depends on fluidcontent_core in emconf?
  • 09:18:34 <Timross> well, it was set up with the 'site' kickstrater
  • 09:18:57 <Timross> and I haven't modified any dependencies.
  • 09:19:12 <jmverges> I don't know really
  • 09:19:39 <jmverges> right know I'm with other stuff, take a look in fluidtypo3.org documentation and logs
  • 09:20:07 <Timross> I was debugging TYPO3\CMS\Fluid\View\TemplateView->getPartialPathAndFilename()
  • 09:21:34 <Timross> And the paths that get checked are
  • 09:21:37 <Timross> 0 /var/www/vhosts/typo362fluid.dev/httpdocs/typo3conf/ext/fluidcontent_core/Resources/Private/Partials/
  • 09:21:53 <Timross> 1 /var/www/vhosts/typo362fluid.dev/httpdocs/typo3conf/ext/site_distribution/Resources/Private/Partials/
  • 09:22:04 <Timross> Which seems to be the wrong way around.
  • 09:22:21 <Timross> It always matches the core first.
  • 09:22:55 <Timross> In one of my news overrides it works perfectly and puts my override first.
  • 09:26:26 <Timross> plugin.tx_news.view.partialRootPaths.2 = {$plugin.tx_sitenews.view.partialRootPaths.default}
  • 09:27:03 <Timross> where the variable is EXT:site_news/Resources/Private/Partials/
  • 09:30:12 <jmverges> if you think it is an issue, feel free to open one in github
  • 09:30:51 <Timross> I just wondered if anyone had seen to problem or been successfull.
  • 09:31:21 <Timross> I will try and make a unit test that illustrates the error
  • 09:31:34 <xaver> unittests are always welcome :)
  • 09:38:16 <Guest|82794> Hi I get the error '"" is not a valid template resource URI.' if I use the current development flux version
  • 11:02:38 <Timross> For anyone that is interested, the FluxService has a method getDefaultViewConfigurationForExtensionKey() that sets the default template root paths at index 10
  • 11:02:44 <Timross> plugin.tx_fluidcontentcore.view.partialRootPaths.10
  • 11:03:30 <Timross> So trying to override the code templates by setting a value at the index 2 doesn't work
  • 11:03:43 <Timross> because the root paths are sorted by index.
  • 11:04:05 <xaver> content core normally supports different variants and versions of them
  • 11:04:31 <Timross> but the default view config always gets called.
  • 11:04:59 <Timross> so it's actually getting set in the setup.txt and in the php.
  • 11:05:26 <xaver> Timross: https://github.com/FluidTYPO3/fluidcontent_core/#concept-overlaying-and-overriding
  • 11:06:54 <Timross> facepalm.
  • 11:09:17 <Timross> I don't want a variant though, I want to ALWAYS render an image in a custom way. So I want to make use of the overlay functionality that comes wiht the templateRootPath method
  • 11:09:53 <Timross> the fact that the content_core typoscript sets the index at 0. implies that I can override it at .1
  • 11:10:04 <Timross> But that's not the case as it is also set at .10
  • 11:12:20 <Timross> but I do understand that variants are a flexible solution.
  • 11:13:39 <xaver> Timross: https://github.com/FluidTYPO3/fluidcontent_core/blob/development/Configuration/TypoScript/setup.txt#L10
  • 11:14:36 <xaver> you can set some defaults and stuff...
  • 11:17:37 <Timross> Ah ok. So In my extension, I can set plugin.tx_fluidcontentcore.settings.image.variant = ...
  • 11:18:20 <Timross> And that will mean that the image is always rendered with the variant from my ext.
  • 11:22:43 <Timross> I was also trying to override a partial and not a whole content object. I guess this only works for CoreContent elements?
  • 11:23:55 <xaver> yeah
  • 11:24:45 <Timross> ok, cool. Thanks for your help
  • 11:27:26 <Timross> ha, I just checked the latest version of https://github.com/FluidTYPO3/flux/blob/development/Classes/Service/FluxService.php#L290
  • 11:27:45 <Timross> the default index is now set to .0
  • 11:28:01 <Timross> I've just got an older version.
  • 11:28:46 <Timross> fixed in dev, but not master yet.
  • 11:30:58 <xaver> Timross: master is only the release from TER
  • 11:50:51 <Timross> @xaver: I installed with composer, but it's all cool. It's working now. Just took me a while to get it all straight in my head. Thanks for your help
  • 15:04:38 <Outdoorsman> Hi again NamelessCoder. Boris Schauer (mrboe) Just tipped me off to adding `\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addToAllTCAtypes('tt_content','--div--;Categories,categories','');` to `ext_tables.php` of my provider extension, which makes the Categories tab and it's contents appear on TYPO 7.2 content elements now. For some reason the categories just quit showing up on content elements with the advent of TYPO3 7.2 though it was
  • 15:04:38 <Outdoorsman> worked out of the box in 6.2 and 7.1. I submitted a Forge issue for it... https://forge.typo3.org/issues/68650