10:37:47 <rvvn> I removed it but it's not the issue
10:38:13 <pedda> NamelessCoder this is not working anymore: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=21&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=7a7647c69217d82c66f625123b9a5581
10:39:20 <pedda> funny fact: it's related to the refactoring of Preview section thingy
10:45:11 <rvvn> I tried this code example : https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=25&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=8ffc96c6eab4763485697641631c7a74
07:58:12 <tpinne> I just installed a fresh T3 7.2 and used the fluidtypo3 site starter for the first time. Everything worked out of the box, despite when I create a new content element there are no input fields, the text content type is not available and so. Are there known incompatibilities with 7.2? Especially with fluidcontent_core maybe?
08:10:05 <tpinne> If I uninstall fluidcontent_core and install css_styled_content I get the normal forms I know
08:10:32 <tpinne> If I uninstall both, it is the same es with fluidcontent_core
08:20:26 <NamelessCoder> tpinne if by "text" you meant "textpic" then yes, this one is removed in fluidcontent_core.
08:23:12 <NamelessCoder> the TCA is also quite different for CSC/FCC and I'm not sure if it already happened in 7.2, but the plan was to remove CSC TCA from the core itself and move it to CSC so if that happened, there may be even less of the TCA you're used to seeing.
08:24:36 <tpinne> no, I meant the normal "text", not "textpic"
08:25:03 <tpinne> ok, so it seems that the csc TCA has been removed from the core?
08:25:23 <tpinne> Something on which you rely in the current version of FCC?
08:26:17 <tpinne> This would explain why I only see input field with CSC installed
08:31:34 <tpinne> if I have both extensions installed I see the normal form elements + the FCC flexform example elements for header and container class names. And the FE renders the FCC html
08:32:19 <tpinne> But the github pages state that these extensions can't be used together, so I guess there will be problems later on?
13:44:35 <pedda> seems as if i need a custom provider
13:44:37 <NamelessCoder> TS, custom form components, custom ViewHelpers etc. can load these possible values for you
13:44:46 <NamelessCoder> - or a custom Provider, of course.
13:44:54 <pedda> but i also managed to retrieve and preprocess the data by the help of viewhelpers
13:45:17 <pedda> but i have another question claus
13:45:31 <pedda> this is a snippet of mine: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=21&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=7a7647c69217d82c66f625123b9a5581
13:45:57 <pedda> since 19th march it stopped working
13:46:23 <pedda> there was some automagically created Preview section refactoring going on
13:46:39 <pedda> which broke the typoscript based flux feature i think
13:46:54 <NamelessCoder> off the bat, those two shouldn't be related at all
13:47:06 <pedda> the problem is: Preview Section is missing
13:47:18 <pedda> if flux is specified via typoscript
13:48:41 <pedda> it all starts with the following error message: #1257246929: "" is not a valid template resource URI.
13:48:56 <NamelessCoder> right, the PreviewView assumes a template file
13:50:27 <pedda> after some digging it seems as the whole process gets stuck here: http://codeshare.io/GjXjx
13:51:23 <pedda> can i improve my ts setup to disable a preview section requirement?
14:01:56 <pedda> bjo3rn fixed this one: https://github.com/FluidTYPO3/flux/pull/832
14:02:19 <pedda> while dealing with https://github.com/FluidTYPO3/fluidpages/issues/256
14:02:54 <pedda> this actually is fixed, but this fix does not affect all doctypes
14:03:06 <pedda> i have still an issue if page is an external url
14:03:41 <pedda> as a workaround i was able to add required doctypes in the em settings of EXT:fluidpages
14:04:38 <NamelessCoder> correct me if I'm wrong, but a non-standard doktype also means that the fluidpages fields should not display, UNLESS you add those doktypes in the config
14:04:46 <pedda> this can be simulated if you change the doctype of a standard page (which already contains any flux/flexform) and set it's type to external url for instance
02:39:26 <ndee> I added an input field "settings.nav_icon" in a page template. In my layout, where I render my v:page.menu, I would like to access that value. Is that possible?
03:40:04 <Danny^^P> Hey! I'm using <f:render partial="header" arguments="{_all}" /> in my Layout. In the partial I like to use something like <v:asset.style... But the tag is not rendered. It is just printed into html. What will I have to do, that it is correct rendered?
06:52:31 <Guest|54558> Hi! I've build a new template with fluid. I like to use the default FCEs like Text, Text with picture etc. How can I template them? or will I have to build them complete by my own again?
07:40:01 <NamelessCoder> Guest|54558 if you used fluidcontent_core you can replace individual templates. If you didn't, you're probably using css_styled_content and your only option to "template" the built-in content types is to modify their TypoScript object structures.
07:45:28 <boOgiE> is there a "special" section name for direct_mail in plain version
07:46:19 <boOgiE> i get these message instead of the content: [Nicht angezeigte Inhaltselemente: fluidcontent_content ]
07:52:15 <boOgiE> does anybody know what i'm talking about?
07:57:05 <Guest|54558> NamelessCoder: Thank you! I looked at fluidcontent_core and tried first with variants. I have definied one and can select them. But in frontend I get only "Oops an error occured"
07:57:44 <NamelessCoder> disable the production exception handler to get an error message that isn't useless
07:58:53 <Guest|54558> ah, found it... there was a typo. Now it works. Thank you very much!
08:38:29 <boOgiE> can someone help me plz, i try to explain my issue: i'm using fluidTYPO3 with my own defined content elements. everything works fine except the plain version of directmail. In these template the fluid content elements are not parsed, i get "[Not displayed content items: fluidcontent_content ]"-Error message instead. does anyone know how to fix it? i hope my explanation was understandable
08:44:48 <NamelessCoder> boOgiE direct_mail isn't finding the rendering instruction for plugins - I assume this would also affect any other non-core CE.
08:46:28 <NamelessCoder> internally, the rendering instruction gets created from ext_localconf.php just like any other plugin. It gets added as TypoScript definitions (see core's configurePlugin etc. methods) and it appears those definitions aren't available.
08:47:09 <boOgiE> ok, thanks for the hint, i try to fix that :)
08:47:21 <NamelessCoder> - unfortunately there could be a thousand different reasons why this is happening, so you *will* need to hunt for explanations on the web about custom plugins with direct_mail - I'm sure someone else has experienced this
08:47:43 <boOgiE> never used plugins with directmail before -.-
08:48:43 <NamelessCoder> I'm guessing now, but direct_mail may be using a custom page type or a simulated frontend context which causes your TS to be cleared somehow.
11:16:36 <NamelessCoder> haven't used direct_mail for at least two years and it's kind of off topic. #typo3 might help.
11:16:49 <Xatenev> NamelessCoder: ye i asked there aswell :) ^^
11:16:53 <Xatenev> Just thought u maybe know about it
17:08:19 <Guest|7764> Hi! I've played around with fluidcontent_core and defined some own variants of the Text Content Element. I'd like to do something similar with the image element. But how can I get the images in my template?
17:56:34 <NamelessCoder> Guest|7764 the v:resource.* ViewHelpers - or a custom controller (the latter is often a better idea for performance, the former a better idea for extendability)
07:08:50 <hans_> hi there, how can ich realize a file download in my fce ?
07:57:52 <NamelessCoder> hans_ if you just want the BE user to select a file that then becomes a link, you can use the following methods: 1) input field + "link" wizard, 2) file input field, 3) FAL IRRE. You can then extract those files using the FAL factory (search google or check sources of various VHS ViewHelpers how to do that) and link to the file. If you need a protected download you'll need a controller and I suggest a proper plugin for that.
08:28:48 <hans_> NamelessCoder: thx, i will check the FAL IRRE stuff later, have to find fast solutions now! i used v:link.typolink for now!
08:31:32 <NamelessCoder> - it works, is fast, supports the wizards and most other storages.
08:35:16 <Guest|82476> The home page should be collecting the “sub content 1” and “sub content 2”, so it should behave like a one pager.
08:35:16 <Guest|82476> And the other pages should be behaving as ‘normal’ pages.
08:35:17 <Guest|82476> I downloaded the FluidTypo3 kickstarter package. And followed then this tutorial: https://worksonmymachine.org/blog/onepage-design-with-fluidtypo3 where it is described how to achieve a onepager with FluidTypo3.
06:25:12 <arnekolja> i added an image to page tca and try to read it in a <v:page.menu /> viewhelper when iterating over my pages, like {mainLevel.tx_mytheme_sectionbuttonimage}. any idea how to get the image reference? when debugging the property, it results in '1'. how do i get the reference?
06:27:35 <arnekolja> there is no mainLevel.tx_mytheme_sectionbuttonimage.originalResource or something, just the integer 1.
06:45:06 <NamelessCoder> arnekolja since you're in FAL at that point, you need v:resource.record.fal
06:45:33 <NamelessCoder> feed it the page record in your menu loop and the name of the field it should extract relations from
06:50:15 <arnekolja> NamelessCoder thanks. trying it like <v:resource.record.fal table="pages" record="{mainLevel}" field="tx_krbutheme_sectionbuttonimage" as="_image"><f:debug>{_image}</f:debug></v:resource.record.fal> but it gets me an empty array. do i have to do something special to make sure FAL works in my TCA definition?
06:51:04 <arnekolja> this is the TCA part: http://pastebin.com/6QuwXnDc
06:54:32 <NamelessCoder> assuming you have no typos and the input variables are correct, that should work
06:56:10 <arnekolja> okay. thanks, I'll try to find a mistake, if there is one :-)
07:46:32 <arnekolja> I got it. Had to rename image in ´´'config' => \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig('image',´´ to tx_krbutheme_sectionbuttonimage. misinterpreted the parameter :)
08:41:07 <Torsten85> Hey... any way to geht fludicontent_core to work with mailform?
10:05:02 <Denyerec> Ah, wasn't after technical help CLaus, I was just interested in your viewpoint on the Neos/Typo split.
10:05:08 <Denyerec> So now might not be the best time :)
10:07:07 <rosieres> namelesscoder: that's what I wanted to avoid due the fact that the database is in usage already -> TCA -> https://gist.github.com/anonymous/33b75c63a006f36e1f9f
10:10:38 <NamelessCoder> hehe no, not the best time today - but it's very fast to say. I like the split; I suggested it many years ago too. I had hoped more people would stay with TYPO3 because we can always use brainpower, but under the circumstances I think that (so far) it has been done the right way, for both communities.
10:11:22 <Denyerec> I'm not aware, yet, of who went where in terms of brain power.
10:12:19 <NamelessCoder> rosieres without MM you have to use a "group" + internaltype=db but that's sketchy at best. The right way is MM, other ways are cutting corners.
10:12:35 <Denyerec> For me, the worst case scenario is too many people leave to develop Neos, Neos doesn't work out, and Typo3 stagnates and dies too.
10:12:54 <Denyerec> As I am still not 100% how, exactly, one uses Neos :D
10:14:35 <NamelessCoder> it's too early to tell but imho, after the split, the potential failure of neos would have much less impact on TYPO3 (and of course vice versa). It's better now than before, risk-wise in that regard.
10:30:48 <Denyerec> Quite, quite. You seem to be firmly in the T3 camp.
10:31:10 <Denyerec> And I wonder if that's just due to baggage, or a feeling that one product has a better outlook.
10:31:20 <Denyerec> Or simply that Neos still isn't ready
10:34:12 <NamelessCoder> well, people come to me when they have needs that neos just can't fill
10:35:55 <Denyerec> Which I guess says a lot about where T3 sits right now ;)
10:36:11 <Denyerec> Is that an ideological gap, though, or simply that they "haven't written it yet"
10:36:57 <NamelessCoder> that's where it gets equal parts technical and political
10:37:42 <NamelessCoder> neos/flow just hasn't been as interested in lifting TYPO3 heritage since abandoning the berlin manifesto
10:38:20 <NamelessCoder> - not being forced to introduce compatibility or a clean upgrade path is where things finally forked off (and that's about the time I wrote my open letter to suggest splitting flow/neos from TYPO3)
10:39:08 <NamelessCoder> then there was the level of ambition: rather than import anything, everything was created anew (and to boot, not many third-party libraries were deemed good enough, and were re-invented)
10:40:09 <NamelessCoder> the result is that flow and neos are VERY specific products which don't really (yet) either connect with or integrate with those products that caused TYPO3's popularity in the first place
10:41:18 <NamelessCoder> to be fair, this is being solved.
10:41:40 <NamelessCoder> and for many years while that was going on, in the direction it did, people didn
10:42:04 <NamelessCoder> 't move much in TYPO3 itself - still hoping/trusting/believing that neos would be a successor
10:42:51 <NamelessCoder> even the official communication from TYPO3 up until a few months ago expressed full confidence in the successorship, although more of a spiritual successor than one that is technically a successor.
10:46:24 <Denyerec> People pinned hope on Neos and Typo3 slowed. Then Neos didn't emerge as the upgrade path to Typo3 that people thoughtit would be.
10:47:00 <Denyerec> Now that things are more officially split, though, are there still people thinking of building an upgrade route from Typo3 to Neos
10:47:00 <NamelessCoder> anyway, that's just what I think. We can't undo these decisions so the best we can do with them now is learn how and why they were wrong and act accordingly in the future - admit a mistake, learn from it and move on.
11:03:01 <Rabe69> settings.category contains a number
11:05:43 <Rabe69> of an existing category and there are several file records where this category is assigned
11:08:14 <rosieres> Rabe69: did you consult the documentation and did you understand why your debug cannot output anything?
11:10:01 <NamelessCoder> wahooo, breakthrough in Fluid wrestling match. Now rendering templates :)
11:11:44 <NamelessCoder> Denyerec the devil is in the details. On the surface both products are able to do much the same thing, but the way it is done is very different
11:12:27 <NamelessCoder> if you're a developer you can probably make both products do exactly what you want. It might take a bit more time on flow/neos because that framework will definitely punish you if you cannot follow all the rules
11:12:54 <NamelessCoder> case in point: extbase request validation. Imagine that, except even more tightly coupled to the framework ;)
11:14:14 <Rabe69> rosieres: what docu do you mean?
11:15:46 <Rabe69> If i read this page: https://fluidtypo3.org/viewhelpers/vhs/master/Resource/FileViewHelper.html
11:16:13 <Rabe69> ViewHelper to output or assign FAL sys_file records
11:29:59 <Rabe69> I thing this is a bug in vhs/Classes/ViewHelpers/Resource/AbstractResourceViewHelper.php
11:30:26 <Rabe69> Line 64 should be $res = $GLOBALS['TYPO3_DB']->exec_SELECTquery('uid_foreign', 'sys_category_record_mm', 'tablenames = \'sys_file_metadata\' AND uid_local IN (' . $sqlCategories . ')');
11:30:42 <Rabe69> and not $res = $GLOBALS['TYPO3_DB']->exec_SELECTquery('uid_foreign', 'sys_category_record_mm', 'tablenames = \'sys_file\' AND uid_local IN (' . $sqlCategories . ')');
08:02:57 <Guest|72191> so I created a test element, saw the colPos that was associated to it, then updated the other elements with this new colPos
08:03:12 <Guest|72191> which is strange, as I assumed it only uses the "name" property
08:24:30 <NamelessCoder> flux child content uses "name" and stores the value not in colPos but in tx_flux_column (parent UID stored in tx_flux_parent)
08:24:55 <NamelessCoder> there's an EM upgrade script to do the colPos conversion btw
08:49:50 <Guest|72191> I saw that it should use the "tx_flux_column" field, and it does show the selection in the backend. but in the frontend it always complains about colPos and in the backend the column does not show the elements, at least not until i update the colpos myself
08:50:08 <Guest|72191> where can I find the EM upgrade script?
09:21:35 <tpinne> Hi guys, what's the currently preferred way to make flux:field.inline.fal work inside flux:form.object?? I found some github issues for this with hints to check if the record is new. But what would be the correct displayCond or if condition to make that work?
09:26:30 <tpinne> And that each object can have its own fal record referenced :-/
09:35:11 <tpinne> Never mind... Did some further reading and I think it's not possible at all yet. So I will work around that issue
09:52:36 <Guest|72191> the old <fed:data.var maps to <v:variable.register.set ?
00:38:57 <framercy> I have a little problem with the fluidpages pageController. I want to get some objects from a repository upon page load for building an enhanced info navigation. Here is the So far working code - But the QueryResult stays empty:
01:04:50 <framercy> Ok - found the answer myself - it was a storage page mismatch . A $query->getQuerySettings()->setRespectStoragePage(FALSE); fixes the issue thx....
05:52:12 <Guest|25135> Hi, is it possible to get the concentatet assets of vhs:asset.script compressed with gzip for the transfer to the clients browser ?
06:04:05 <Guest|25135> is there anyone who can help ?
06:35:51 <NamelessCoder> Guest|25135 you can't modify the file itself, but you can add apache .htaccess rules that will serve files matching vhs merged file name pattern (or all .js/.css files) using gzip or whichever compression you prefer
07:23:30 <thewong> Hi, i installed the VHS Viewhelper Extension. Everything is fine, but one questions is still remaining. I use the integration with Typoscript and additionally the v:asset.script fluid viewhelper. in my site there are to js files generated, one with the files from the ts and one with the files from the viewhelpers, what am i doing wrong
07:24:18 <NamelessCoder> thewong make sure you use the same "name" property in both Fluid and TS, that makes the TS overrule what was added from Fluid
07:25:50 <thewong> i think we misunderstand, i include via TS the files js1.js & js2.js and via fluid js3.js and js4.js, this results in two vhs-...js files one, combined js1&js2 and the other js3&js4
07:31:33 <jobs> is there a way to make <f:section name="Preview"> <flux:widget.grid /> </f:section> working for the list view in the BE, now it show "no titel" for all fluid content elements
05:09:09 <Guest|29358> I get a really weird error from time to time
05:09:34 <Guest|29358> Call to undefined method FluidCache_ExtensionName_Content_action_index_00fde650b5acb96af39602c0d39b07cf4539f697::section_62bce9422ff2d14f69ab80a154510232fc8a9afd() in \typo3\sysext\fluid\Classes\View\AbstractTemplateView.php on line 222
05:09:51 <Guest|29358> of course in the cached class the method section_sha1 does not exist
05:09:59 <Guest|29358> but why is it not generated?
05:10:03 <Guest|29358> is there a config I am missing?
05:46:22 <Guest|84221> Hey! With the help of fluidcontent_core I build a own variant of the Text Content Element. But I don't manage to build my own variant of an Image Element. Is there anywhere an example or documentation available?
06:43:15 <marl07> Hi. Is it possible to create a custom content element and move flux form fields inside the "Appearance" Tab of TYPO3? It works for the CoreContent elements, but I have not found a way to do this for my custom content elements.
08:00:46 <rosieres> Imagine somebody files a question to you like you did. Could you help him?
09:02:13 <NamelessCoder> marl07 see "showitems" and TCA types. You need to define TCA for your custom type to move fields around like that. It's outside the scope of this channel though ;)
10:53:17 <Guest|84221> Hey! With the help of fluidcontent_core I build a own variant of the Text Content Element. But I don't manage to build my own variant of an Image Element. Is there anywhere an example or documentation available?
04:41:20 <Vlad1> Hi how are you guys doing? I have multidementional object/array and I want the uid of the first element of the first child. Does any one could please let me know how can I accomplish this
04:42:04 <Vlad1> I have tried with {researcher.museums->v:iterator.first()} but I do not know to read the uid of the returned object
05:00:31 <NamelessCoder> Vlad1 try v:iterator.extract w/ single argument, if necessary chain it with v:iterator.first() - whether or not you need to do that depends on exactly what is in the array and in which order.
05:08:54 <Vlad1> I tried it {researcher.museums->v:iterator.first()->v:iterator.extract(key:'uid',single:TRUE)}
07:35:44 <Jeff|tollwerk> Hey guys, can you tell me how to supply an select-field with a list of items retrieved from a certain db-table in Flux?
07:41:32 <Jeff|tollwerk> Ah okay, it seems that I have to use the releation-viewhelper, gotta try this
07:47:16 <svenDeKa> Hi everybody, I am experiencing a common bug to this: https://github.com/FluidTYPO3/flux/issues/841, but in 6.2.12. does anybody else have experienced that flux:form.section/...object doesnt work in fluidpages-context?
08:03:39 <svenDeKa> ..or am I maybe mistaken to use this feature in that particular context?
04:16:11 <Guest|23539> Hi there. I'm wondering why the fluidcontent, fluidcontent_core and flux-extension has version requirements up to 7.1.99 - as TYPO3 7.3 is released: will the extensions running (minor change in version requirements in ext_emconf) or is there still some work to do?
04:25:56 <Guest|74342> Hi everyone, I'm new to templating with fluid powered TYPO3 and I think I've found a bug within TYPO3-workspaces. So where may I address my concern?
04:27:10 <bjo3rn> Guest|84221 please open an issue on Github in the appropriate repository: https://github.com/FluidTYPO3
04:27:56 <bjo3rn> Oh, sorry, wrong guest. I meant Guest|84221 ;)
04:28:09 <Guest|74342> OK :) thank you for your quick respond!
04:28:38 <bjo3rn> Guest|23539 there's still some things to iron out for 7.2 and 7.3 hasn't been tested yet I guess.
04:31:59 <Guest|74342> i use typo3 6.2 with the newest released Fluid Powered TYPO3 extensions
04:47:31 <Guest|23539> thanks. Might it be a good idea (or not) to start a new project on 7.2/7.3 now?
05:12:22 <MarcT> Hi guys, I'm just experiencing w/ fluidpages, flux, fluidcontent etc. and really appreciate your great work... seems to make life easier ;) Maybe someone could answer one question: If I create several CEs w/ fluidcontent, is there any chance to individually set TCA overrides for those? Example: For CE1 I want to show the header-palette, for CE2 not
05:12:23 <MarcT> ... Thanks for your help in advance.
05:18:55 <MarcT> I found this answer from NamlessCoder in the IRC two days ago... "marl07 see "showitems" and TCA types. You need to define TCA for your custom type to move fields around like that. It's outside the scope of this channel though ;)" Just don't get how to address single CEs, because all of the seem to use [types][fluidcontent_content] ;)
11:03:56 <jeff|tollwerk> Hey guys. I really like the allowedContentTypes-feature of flux and also the possibility to further restrict the selection of _which"_ fluidcontent-types exactly to select. Unfortunately I figured that this feature is not available for CType list e.g. restricting which plugins exactly to place, am I right?
11:17:05 <jeff|tollwerk> Ah, I figured out a way to do this
13:53:46 <content_wizard> hi. anyone knows where to find doc on registering fluid content elements so they appear on new element wizard?
13:53:48 <content_wizard> type used to be "fluid content type", i remember some update in last 2 years changed that.
17:37:57 <Guest|96617> hey, should "flux:form.section" work for page configuration or shouldn't it be used there at all? there is already an issue on github #841, but it's not just in typo3 7.2 and it's not about the "form.object" but "form.section" form element.
17:40:07 <Guest|96617> It seems to save some times, but mostly if doesn't save the new items and just throws away all already saved records.
11:20:18 <Kaimane> Is it possible to use v:page.menu.directory VH but without tagName and tagNameChildren wraps? If I leave tagName and tagNameChildren empty the VH still renders empty tag brackets like <>.
15:47:15 <am-adrian> Hi, i'm using last version of fluibootstraptheme from TER. Is it possible to deactivate the css for bootstrap.min.css? (I'm using a css including bootstrap which is generated by less)
15:10:49 <nhaskins> I'm having trouble getting my locallang.xlf file to work. When I edit my page, on the page layouts tab my layout is labelled as LLL:EXT:hcosprovider/Resources/Private/Language/locallang.xlf:flux.standard
15:10:49 <nhaskins> My locallang.xlf file is here https://gist.github.com/neil-h/41e143cc416aa73cf7c6
15:10:49 <nhaskins> Why isn't my layout being labeled as "Standard page layout"?
15:48:19 <NamelessCoder_> nhaskins is the locallang.xlf file in the right location, including case sensitive folder names, and did you clear the system caches after adding the label?
15:59:07 <nhaskins> Yes, it is in the correct location.
15:59:48 <nhaskins> For caches I see "flush general caches", and "flush frontend caches". I've done both multiple times.
16:00:06 <nhaskins> Is there a separate "system cache" option somewhere?
17:37:10 <NamelessCoder_> you need "flush system caches". The option can be enabled in user settings, for admins only or as generally available option for any user. It can also be enabled by setting the "Development" TYPO3_CONTEXT (install tool, env)
17:37:47 <NamelessCoder_> alternatively, use clear caches option of the install tool itself. That one clears everything including system caches
18:09:11 <nhaskins> OK, I've changed to the dev enviroment, flushed my system caches, and it works now. Thanks for the help.
05:18:35 <Matt23a> Hi! I have installed gridelements, because I wanted to use a accordion-extension. I deleted it, because it didn't work with fluid. Now I my grid elements have lost height. The buttons are in the left bottom corner. Is there a way to fix it?
05:28:42 <NamelessCoder_> Matt23a this is 100% a gridelements question and this channel is for FluidTYPO3 questions. But to answer your question you need to delete generated CSS/JS files and/or clear system caches to get rid of the CSS and JS overrides gridelements has injected into your backend assets.
05:46:13 <Matt23a> NamelessCoder_: Thank you. I deleted gridelements and still have FluidTYPO3 installed, so I thought the question would fit here. Where do I find the generated CSS/JS files? I deleted the files in typo3temp/compressor, but nothing changed.
05:49:07 <NamelessCoder_> should be safe to just rm -rf typo3temp and clear your system caches
05:14:29 <syssi> @NamelessCoder_ Hi Claus! There seems to be a regression at variable.set (vhs 2.3.3/master).
05:15:13 <syssi> This way of building an array works fine: <v:variable.set name="test" value="{0: 'bar'}" />
05:15:39 <syssi> In the past this was possible also: <v:variable.set name="test" value="{foo: 'bar'}" />
05:16:45 <syssi> Today (vhs 2.3.3) the last statement validates to a string (value: "{foo: 'bar'}").
05:18:18 <syssi> So I'm unable to create associative arrays atm.
05:28:25 <NamelessCoder_> 95% sure that's because you have a syntax issue in the array
06:03:26 <syssi> I have tried: <v:variable.set name="test" value="{foo: 'bar'}" /> and <v:variable.set name="test" value="{'foo': 'bar'}" /> without success.
06:33:26 <NamelessCoder_> parameter type is "mixed" which means it is up to Fluid to detect what is being passed: https://github.com/FluidTYPO3/vhs/blob/development/Classes/ViewHelpers/Variable/SetViewHelper.php#L66
06:34:02 <NamelessCoder_> if this is broken, any ViewHelper that accepts "mixed" will be unable to receive an associative array - in other words, it'll be something changed in Fluid itself
06:35:07 <Guest|4135> Hi! I'm trying to create a own variant of image with fluidcontent_core. Is there anywhere an example available how to do that?
06:37:10 <NamelessCoder_> hi Guest|4135 :) the README.md of fluidcontent_core shows how to add new variants - and to get started, just copy the template from fluidcontent_core into your own extension and edit it from there.
06:37:48 <NamelessCoder_> if all template paths and registrations are correct, fluidcontent_core will detect your template and add an option in the "Variant" selector
06:54:19 <syssi> @NamelessCoder_: I understand. The problem must be located at fluid (!= vhs).
06:58:19 <NamelessCoder_> hmmm... no new features there so if anything, this would have to have come as a side effect of some bug fix in fluid
07:00:10 <syssi> I will try to reproduce the issue on a clean install at first.
07:09:13 <Guest|4135> NamelessCoder_: Sorry, I got a telephone call... I managed it, to create a variant of Text. That works fine. But I am in trouble with Image. I am not able to figure out, how to output the images in my template variant
07:09:53 <NamelessCoder_> check the template that ships with fluidcontent_core - and use the default fields for images in the content element
07:14:51 <Guest|4135> I looked at Templates/CoreContent/Image.html. Do I have to copy the whole file to my extension and modify the sections Preview and Main?
07:15:14 <NamelessCoder_> that's the easy way to go yes :)
07:24:15 <Guest|4135> after copying the file and the dependent (Properties/{Header,Container,Images) und Content/Image I get the error: Oops, an error occurred! Code: 20150625132056382d8077
07:33:02 <NamelessCoder_> can't tell the problem from that - you need to disable the ProductionExceptionHandler. TYPO3 is in production mode regarding errors and won't throw exceptions, instead it gives you the time plus some random chars as "error message"
07:33:33 <NamelessCoder_> but you don't need to copy partials etc. if you add fluidcontent_core's partialRootPaths and such to you own extension's view paths
07:41:00 <Guest|4135> I thought, that the ExceptionHandler ist diabled. [SYS][productionExceptionHandler] is empty.
07:43:12 <NamelessCoder_> setting the context setting to Development should set all parameters correctly
07:59:37 <Guest|4135> Thank you very much! Just setting Development in the Backend did'nt show up the whole error message. But setting it in webserver config helped. Now I could find the error... Typo in Layout Path. Now it works fine :-)
11:33:32 <syssi> is there a way to render also the parent page by v:page.menu?
11:35:59 <syssi> Set the pageUid and manipulating entryLevel & levels does not help.
12:03:19 <Daniel^^^> Hi! Can I add own FCEs? I need something like a 2 and 3 column grid layout with a variable number of rows. It will be nice if I can do colspans, too
04:54:39 <Daniel^^^> Good morning. I'm trying to add a new FCE based on Fluid. I need something, to make 2 oder 3 columns with a header over all of them and various number of FCE (Text or Image) inside each column (without separate header). What will I have to do, to build such?
06:42:31 <Daniel^^^> In my fluidcontent element I can switch to different modes. I need some different input fields, depends on what mode was selected. Is there a way to do it? or will i have to build multiple content elements?
08:40:23 <Guest|15708> Hi everyone, I have just created a fresh page with fluid powered typo3, Page templates are working fine. However, fluidcontent elements aren't working. If I use a standard CE like Text, the text is being rendered in the frontend. Custom CE within the provider extension aren't rendered at all. I am however able to select them in the Backend and add
08:40:23 <Guest|15708> them to any Grid within the Page Layout. Backend forms are also functioning perfectly. It is just that the Elements don't get rendered at all. I have created a simple test Template which resides in Resources/Private/Templates/Content/Teaser.html and has the standard Layout "Content" defined (see http://pastebin.com/zbYaKWMx). Typoscript from Provid
08:40:23 <Guest|15708> er Extension and fluidcontent_core are included. Am I missing something? Does anyone have a hint for me? Any help ist greatly appreciated.
08:53:44 <NamelessCoder_> Guest|15708 see that typo3conf/AdditionalConfiguration.php was created. If not, run upgrade script for fluidcontent_core in EM. If that doesn't work, see README.md how to edit AdditionalConfiguration.php manually
09:03:38 <Guest|15708> Running the update script in EM worked, thanks a lot!
10:57:39 <Guest|10960> Hi, i switched the fluidcontent Version from 4.2.2 to 4.3.3 (Master Branch). After that the FC Element options settings won't show up. Any idea?
08:22:06 <Razrael> I just wanted to inform you that you have an issue on the fluidtypo3 documentation: https://fluidtypo3.org/viewhelpers/fluid/6.2.0/Form/SelectViewHelper.html
08:22:28 <Razrael> Looks like something would be wrong with escaping the html.