IRC logs

20140729

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

IRC log range: 20140729*

20140729

  • 10:08:21 <dkn64738> hi, has anyone tried to use chained/dotted name properties in flux:field configuration? (flux 7.1.0 git version develop branch) more details: https://gist.github.com/danielkuehni/dba1c9b508c834783885
  • 10:10:49 <randomresult> moin
  • 10:37:04 <floxx> chained name attribute image.link works, if we're using image.attribute.alt or image.link, they are ignored
  • 10:37:10 <floxx> although written to database
  • 10:37:43 <floxx> erm…i meant image.attribute.alt and image.url are ignored
  • 10:58:35 <floxx> this happens only in object/section
  • 11:04:33 <ltrebing> good morning everyone
  • 11:10:27 <ltrebing> I have the exact same problem as jlumpe had at http://fluidtypo3.org/community/irc-logs.html?tx_fluidtypo3org_content%5Bdate%5D=20140613&tx_fluidtypo3org_content%5Bcontroller%5D=Content&cHash=c3410a77fe79964f8ed7fdd44440eec9#11:26:54 and am trying to figure out what the solution was
  • 11:14:32 <ltrebing> maybe cedricziel can point me in the right direction?
  • 11:16:06 <ltrebing> ah, https://github.com/FluidTYPO3/fluidcontent_core/issues/44 looks potentially helpful
  • 12:30:30 <floxx> once again: had anyone problems with chained name attributes inside sections?
  • 12:31:51 <mrboe> chained names?
  • 12:33:38 <floxx> yep. <flux:field.input name="image.link" -> worrks
  • 12:33:47 <floxx> <flux:field.file name="image.url" -> nope
  • 12:33:53 <floxx> <flux:field.input name="image.attribute.alt" -> nope
  • 12:34:21 <mrboe> claus told me not to do that in sections
  • 12:34:45 <floxx> good to know ;)
  • 12:34:53 <mrboe> because this will not be written in the array (or something like that)
  • 12:35:02 <floxx> it's written to db
  • 12:35:17 <floxx> but in backend and frontend the 2 fields are missing
  • 12:35:25 <mrboe> ImageAttrAlt
  • 12:35:59 <mrboe> we had that problem in fluidboostraptheme
  • 12:36:16 <mrboe> we wanted to use settings.Fieldname
  • 12:36:36 <mrboe> but in the secion/object this will not work
  • 12:37:40 <floxx> what's driving me crazy: it's illogical why image.link works
  • 12:37:43 <mrboe> like here: https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Content/Button.html
  • 12:38:22 <mrboe> because image.link is a attribute that exists
  • 12:38:57 <mrboe> i guess
  • 12:39:33 <floxx> however :-D thank you. will remeber that for the future
  • 13:31:15 <Kaimane> Hey. I cant use xmlns instead {namespace ...} declaration in my ext using typo3 6.2.4. If I use xmlns I got an Exception: Could not analyse class:vhs\ViewHelpers\Page\Content\RenderViewHelper maybe not loaded or no autoloader? How can I solve that?
  • 13:31:44 <Kaimane> By using {namespace v=Tx_Vhs_ViewHelpers} everything works really fine.
  • 13:31:51 <mrboe> hey @Kaimane
  • 13:32:07 <Kaimane> hey @mrboe
  • 13:33:08 <mrboe> there are two possibilities 1. you move all v: to a partial (not use that in layouts) 2. use {namespace v=Tx_Vhs_ViewHelpers} in layouts
  • 13:33:51 <mrboe> like this https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/commit/148ca6071b698ad9ccb7bf9af4cfc8d6cd06e2d0
  • 13:51:35 <NamelessCoder> Kaimane page.content.render is deprecated and removed, content.render works.
  • 14:47:28 <hirnschmalz> Hi there, I updated flux and no got the error 'ext/flux/Classes/Configuration/BackendConfigurationManager.php on line 176' searching in the IRC logs tell me, that I'm not the only one
  • 14:48:08 <hirnschmalz> I already truncated all cf_* tables cleared TYPO3 caches, cleared APC cache and also removed all files in typo3temp - no luck so far
  • 14:49:44 <hirnschmalz> I'm using ab2fd40
  • 15:05:44 <beo6> hirnschmalz: try to change to DB cache in the install tool. Helped me
  • 15:13:13 <JustAPoring> is there a viewhelper for a category menu (similar to a HMENU with special=categories)?
  • 15:13:17 <JustAPoring> in vhs that is
  • 15:13:25 <JustAPoring> at first glance I didn't see anything
  • 15:13:39 <Kaimane> @mrboe that was the problem. v: was used in a layout. when moving v: to another partial there is no execption anymore.
  • 15:21:18 <Kaimane> But when I now use xmlns in a partial e.g. xmlns:v="http://typo3.org/ns/vhs/ViewHelpers" (for v 1.9.1) I got another exception: "Could not analyse class:vhs\ViewHelpers\Asset\StyleViewHelper maybe not loaded or no autoloader?"
  • 15:22:14 <NamelessCoder> Kaiman use http://typo3.org/ns/FluidTYPO3/Vhs/ViewHelpers
  • 15:22:25 <NamelessCoder> 1.9.1 uses namespaces
  • 15:23:55 <Kaimane> Got the same exception: "Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Asset\StyleViewHelper maybe not loaded or no autoloader?"
  • 15:24:33 <Kaimane> But with {namespace v=Tx_Vhs_ViewHelpers} there is no exception.
  • 15:27:18 <NamelessCoder> the class clearly exists: https://github.com/FluidTYPO3/vhs/blob/development/Classes/ViewHelpers/Asset/StyleViewHelper.php so perhaps something's up with the caching or currently checked out version
  • 15:27:42 <xaver> i had similar problems with select and switch to namespaces and stuff
  • 15:27:56 <xaver> my solution was namespaces and development
  • 15:30:41 <Kaimane> Of course, the class exists. Using vhs from ter in version 1.9.1.
  • 15:31:16 <Kaimane> So, using {namespace v=Tx_Vhs_ViewHelpers} everything works fine without any errors.
  • 15:33:32 <mrboe> but @Kaimane thats because you have used that in layouts?
  • 15:34:39 <Kaimane> In my layout there is neither {namespace ...} nor xmlns
  • 15:35:03 <Kaimane> I only use f: in layout
  • 15:35:08 <mrboe> yes
  • 15:35:29 <mrboe> ok
  • 15:35:43 <mrboe> and you got errors
  • 15:35:57 <mrboe> never had that
  • 15:36:20 <Kaimane> yes. when using xmlns in a partial I got an exception: could not analyse class ...
  • 15:38:02 <mrboe> and you use it like here? https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Page/Render.html
  • 15:38:29 <mrboe> xmlns:v="http://typo3.org/ns/FluidTYPO3/Vhs/ViewHelpers"
  • 15:39:08 <mrboe> because in the docs its written like that >> xmlns:v="http://typo3.org/ns/vhs/ViewHelpers"
  • 15:39:14 <mrboe> and thats wrong
  • 15:41:34 <Kaimane> yes using it like in the page template. xmlns in my page template works but I do not use v: right there. only flux: and f:
  • 15:41:52 <Kaimane> changed the xmlns to xmlns:v="http://typo3.org/ns/FluidTYPO3/Vhs/ViewHelpers" ... but the same error.
  • 15:42:05 <Kaimane> Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Asset\StyleViewHelper maybe not loaded or no autoloader?
  • 15:43:17 <mrboe> have you looked into the vhs ext if its really there
  • 15:44:22 <Kaimane> yes. the class is still there. vhs/Classes/ViewHelpers/Asset/StyleViewHelper.php
  • 16:03:49 <hirnschmalz> beo6: changing to DB cache also worked for me - thank you very much
  • 16:04:04 <Kaimane> What's the best way to upgrade vhs from 1.9.1 (ter version) to 2.0.0 from git?
  • 16:08:37 <NamelessCoder> nice, github-bot - 25 minute delay ^^
  • 16:49:38 <benjamin_654> hi together
  • 16:49:42 <Kaimane> Want to give you an update. I upgraded chs to version 2.0.0 from git. Now xmlns works perfect without exceptions. No need to use {namespace ...} anymore.
  • 16:50:23 <benjamin_654> i am setting up a new 6.2 project and i am not sure if i should use fedext development oder master branch
  • 16:50:58 <benjamin_654> what do you suggest? what are currently the biggest differences?
  • 16:51:33 <mrboe> its the choice between old or new bug ;)
  • 16:55:39 <Kaimane> chs = vhs ;)
  • 17:09:19 <Guest|72339> hi all
  • 17:09:39 <Guest|72339> anyone can tell me if its possible to get tt_content element by uid with vhs?
  • 19:33:40 <xaver> benjamin_654: i use develop. Develop isn't stable and some annoying bug can show up. But a lot of stuff is fixed and improved.
  • 19:34:05 <xaver> development is like in other projects master. we use master for actual releases.
  • 19:36:24 <ltrebing> aka git-flow-ish :)
  • 21:16:15 <benjamin_654> xaver: thx - i´ll go with develop (:
  • 21:17:30 <xaver> benjamin_654: also the docu isn't always up2date
  • 21:19:06 <benjamin_654> the best docu is always the source (: - at least for the view helpers where i can quickly understand whats going on ..