IRC logs

20140919

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

IRC log range: 20140919*

20140919

  • 09:02:02 <Guest|93776> somebody here
  • 09:02:03 <Guest|93776> ?
  • 09:38:19 <bjo3rn> Guest|93776 yes
  • 09:38:39 <bjo3rn> wazzup?
  • 09:58:28 <marteadrian> Hello, i'm trying to implement a menu for pages with teaser text and page image. My approach is to use http://fluidtypo3.org/viewhelpers/vhs/master/Page/MenuViewHelper.html with the attribute "as". Now i can not find any example or doc how to use this array defined in "as" parameter of view helper, to use it inseide viewhelper tag. Is there any tut
  • 09:58:28 <marteadrian> orial/doc/example available?
  • 09:58:51 <marteadrian> (I use git (develop) version of vhs)
  • 10:08:30 <marteadrian> so i just played around little bit and i use a for each loop inside menu view helper, which works already good for page.title. Now only problem remains, that i need some hint for using an image there. I would like to use "Page Ressources" in backend, create a new relation to an image. Anyone has a hint how to use that in helper?
  • 10:10:50 <gbod> marteadrian: Give <v:page.resources.fal /> a try
  • 10:11:27 <marteadrian> (y) thanks!
  • 10:56:42 <marteadrian> @gbod: I tried not with <v:resource.image identifier="{v:page.resources.fal(field: 'settings.pageimage', uid: {subpage.uid})}" />. Where settings.pageimage is an own flux field, defined like so: <flux:field.inline.fal name="settings.pageimage" label="Page Image" multiple="false" /> in page template. but i just get now output...
  • 11:05:58 <gbod> marteadrian: The following does the job for me:
  • 11:06:20 <gbod> <v:page.resources.fal table="pages" field="media" uid="{page.uid}" as="images">
  • 11:06:20 <gbod> <v:condition.type.isArray value="{images}">
  • 11:06:20 <gbod> <f:then>
  • 11:06:20 <gbod> <f:for each="{images}" as="image" iteration="iteration">
  • 11:06:20 <gbod> <v:media.image src="{image.url}" alt="{image.alternative}" width="120c" height="120c"/>
  • 11:06:21 <gbod> </f:for>
  • 11:06:21 <gbod> </f:then>
  • 11:06:30 <gbod> </v:condition.type.isArray>
  • 11:06:31 <gbod> </v:page.resources.fal>
  • 11:07:57 <gbod> media is the field in the page resources, {page.uid} is the uid of the page from which i like to get all the images.
  • 11:09:12 <gbod> It is the same way the ImageGallery in https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme works but for pages
  • 11:13:59 <marteadrian> @gbod: works like a charme! thanks. and thanks also for the link!
  • 11:15:37 <gbod> marteadrian: you're welcome
  • 11:17:52 <gbod> lol, that escalated quickly.
  • 11:19:23 <glucka> hi
  • 11:19:33 <glucka> I cant set plugin.tx_fluidcontentcore.settings.defaults.variant
  • 11:19:43 <glucka> version works!
  • 11:19:54 <glucka> any idee?
  • 11:22:53 <glucka> if i set version become an error.. but if i set variant see always Standard
  • 11:30:28 <gbod> glucka: hmm, if I set plugin.tx_fluidcontentcore.settings.defaults.variant = Vendor.ExtensionName and
  • 11:30:28 <gbod> plugin.tx_fluidcontentcore.settings.defaults.version = Text.New I get the correct selected entry "Text.New" in the version box,
  • 11:32:50 <gbod> glucka: But yes, the variants field stays at the "Standard" value
  • 11:35:33 <glucka> gbod: thanks for your confirmation
  • 11:35:50 <glucka> yes version works
  • 11:36:13 <gbod> glucka: but where do you get an error?
  • 11:36:16 <glucka> but only variant does not
  • 11:36:36 <glucka> the error was my fault
  • 11:39:55 <glucka> wrong version name given
  • 11:44:42 <glucka> ahh.. its works... by variant show always "Standard" but render the given variant
  • 11:45:19 <glucka> :)
  • 11:45:43 <gbod> glucka: Yeah, it's just presentational
  • 11:45:48 <gbod> glucka: :D
  • 11:47:16 <glucka> thanks ;)
  • 11:52:54 <marteadrian> hi, i want to make a multi-column FCE. The user should have the possibility to select different layout like e.g. "50/50" or "33/33/33". Is it possible with flux to define a backend layout which dynamically shows available columns after selecting the specific layout somehow? I could not find conditions which could be used in Configration section....
  • 11:52:54 <marteadrian> Thanks for any hint.
  • 11:56:24 <gbod> marteadrian: Take a look into https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme the Content/Row.html Template There you can see a way how you be able to do dynamic columns. Just play with it to get your wishes come true.
  • 11:58:05 <marteadrian> hmpf, again this link... i'll investigate there now first before asking here ;) thanks!
  • 11:58:50 <erredeco> Hi I have a serious problem after updating to Flux 7.1.0
  • 11:59:06 <erredeco> Every time I insert a plugin on the page I get the error
  • 11:59:52 <erredeco> Oops, an error occurred!
  • 11:59:52 <erredeco> No content template found
  • 12:00:04 <erredeco> also with "login form", "media element"
  • 12:00:09 <erredeco> :S :S
  • 12:00:14 <erredeco> please, help!!!
  • 12:01:23 <gbod> marteadrian: Yes, they did a really great job showing all the incredible things one is able to do with flux
  • 12:02:45 <erredeco> :S
  • 12:04:57 <gbod> erredeco: TER version?
  • 12:05:07 <erredeco> TER version
  • 12:05:16 <erredeco> installed downloading the t3x file
  • 12:05:59 <erredeco> I can try to download the git version...
  • 12:12:47 <erredeco> as far as I can see the "master" version from git has a different file from the TER version:
  • 12:13:07 <erredeco> ext_emconf.php
  • 12:13:18 <erredeco> all other files are identical
  • 12:18:04 <erredeco> :S :S
  • 12:22:20 <erredeco> I have fluidpages and fluidcontent 3.1.0 and 4.1.0 from git
  • 12:22:27 <erredeco> could it be the problem?
  • 12:31:22 <erredeco> that was the problem
  • 12:51:22 <SuburbanWorrier> @erredeco Can u tell me what versions work for you. I've just pulled all the dev versions from git and I get the error you mentioned whenever I use the BE page module
  • 13:14:32 <GRIMMCREATIVE> Hello all, i updated every FluidTYPO3 Extension with new development branch. Works but now my Backend Layouts are gone :( Some Idea why?
  • 13:16:01 <gbod> GRIMMCREATIVE: https://github.com/FluidTYPO3/fluidpages/commit/28da1127239a00b7fafb87a6317d4930ac3d5e63
  • 13:17:08 <GRIMMCREATIVE> :) THX alot @ gbod
  • 13:54:00 <glucka> latest fluidpage: if a clear the typo3temp folder, frontend is rendered once.. after refresh: The page is not configured! [type=0
  • 13:56:39 <glucka> if i logged in in backend.. frontend rendered normal...
  • 13:57:16 <glucka> logout: "The page is not configured! [type=0]..."
  • 14:00:43 <NamelessCoder> glucka I can't reproduce that problem at all. Did you check+save the new extension configuration for fluidpages?
  • 14:02:06 <glucka> yes, Backend Layout selected
  • 14:03:53 <NamelessCoder> not that; this one: https://github.com/FluidTYPO3/fluidpages/commit/ff0b36aded5f7ace355978378b49fe0c335fa0d4
  • 14:04:55 <glucka> i try it
  • 14:06:27 <gbod> NamelessCoder: Busy day ;)
  • 14:06:58 <NamelessCoder> it had to be done!
  • 14:10:02 <glucka> hmm.... Automatic initialisation is enabled
  • 14:11:04 <NamelessCoder> save config to be sure
  • 14:11:55 <glucka> same problem...
  • 14:13:58 <glucka> i use an older provider extension.. generatet with builder in july
  • 14:15:43 <NamelessCoder> sounds like the typoscript either is invalid, is caught out by some condition or is simply not loaded
  • 14:16:12 <Guest|67834> hello everybody: is it possible to change the order of fluid content element in typo 3 backend?
  • 14:16:14 <Guest|67834> http://www.directupload.net/file/d/3750/923yzowg_jpg.htm
  • 14:16:43 <glucka> and if im logged in in backend it works.. i cant explain why
  • 14:19:31 <NamelessCoder> Guest|67834 yes: use options="{Fluidcontent: {sorting: 123}}"
  • 14:19:35 <NamelessCoder> on flux:form
  • 14:21:29 <Guest|67834> this way: <flux:form sorting="1"> ???
  • 14:21:48 <glucka> i try a prev version of typo3 6.2
  • 14:22:15 <NamelessCoder> Guest|67834 no, write it the way I wrote it ;) <flux:form ... options="{Fluidcontent: {sorting: 123}}">
  • 14:25:11 <Guest|67834> testing
  • 14:29:32 <Guest|67834> <flux:form wizardTab="Test" id="spalte" label="Test" options="{Fluidcontent: {sorting: 1}}>
  • 14:29:35 <Guest|67834> doesnt works
  • 14:30:25 <NamelessCoder> default value is zero
  • 14:30:44 <NamelessCoder> must use recent fluidcontent version for this to work
  • 14:30:55 <NamelessCoder> system caches must be cleared to rebuild the definitions
  • 14:35:31 <erredeco> @SuburbanWorrier sorry for my late answer
  • 14:35:40 <erredeco> actually I'm using all versions from TER
  • 14:36:19 <SuburbanWorrier> @erredeco - thanks, and np being "late"
  • 14:36:20 <erredeco> sorry
  • 14:37:14 <SuburbanWorrier> for the record there was an update to a file in the git fluidpages extension. Clearly I was victim to a found and squashed bug.
  • 14:37:37 <erredeco> Flux 7.1.0, VHS 2.0.1, fluidpages 3.0.0, fluidcontent 4.0.0
  • 14:38:12 <erredeco> I see that there are updates
  • 14:38:24 <erredeco> vhs 2.0.2, fp 3.1.0 and fc 4.1.0
  • 14:39:16 <erredeco> btw: I found that the extension "vidi" has the same namespace "v" for the viewhelpers as vhs
  • 14:42:50 <NamelessCoder> namespaces can be chosen freely - we only suggest "v" as default
  • 15:00:15 <mikemCH> Hi i use the newest master flux7.1 vhs 2.01 fluidpages 3.1 fluidcontent 4.1... after creating a new provider extension using builder i get this error...Template could not be loaded. I tried "/Users/mx/Websites/mysite/cms/typo3conf/ext/fluidpages/Resources/Private/Templates/Page/Default.html" am i doing something wrong?
  • 16:29:41 <glucka> NamelessCoder: it is possible that Flux\Core::addStaticTypoScript not work in ext_tables?
  • 16:30:11 <glucka> if i put this code in ext_localconf... frontend works again
  • 16:47:34 <glucka> in ext_tables.php run the script only once