04:07:19 <mneuhaus> drlimbo: did you take a peek at my pull-request? i didn't include some automatic srcsets based on typoscript though, because nothing typoscript similar is done in vhs yet
09:40:38 <Guest|75998> does anybody know whats wrong with this piece of code: <v:if stack="{0: '{iterator.cycle} % 3', 1: '==', 2: 0}">Hello</v:if> it does not return hello at all within my for loop with 7 results
09:41:52 <NamelessCoder> Guest81064 did you ask the v:if.stack question?
09:42:49 <NamelessCoder> if you did, and for everyone else: '{iterator.cycle} % 3' is not valid Fluid. Not yet, anyway.
09:43:37 <NamelessCoder> it results in the following comparison stack: $result = ("3 % 3" == 0)
09:44:12 <NamelessCoder> future Fluid will support mathematical operations in object accessor nodes but with a slightly different syntax: {iterator.cycle % 3}
09:44:44 <NamelessCoder> what you need here and what works perfectly find: <f:if condition="{iterator.cycle} % 3">
09:46:11 <Guest81064> allright! but what if i need a multi condition like: {iterator.cycle} % 3 || {iterator.isFirst} ?
09:47:29 <NamelessCoder> if I remember it right, v:if doesn't support modulo in conditions so that wouldn't work - but you are welcome to submit a feature request on github, asking for that to become supported. It shouldn't be too difficult (and it should replicate the f:if behavior of "0" actually meaning "TRUE".
09:48:30 <Guest81064> ok i will do that! thank you very much for your help!
04:35:29 <jagmanetta> After updating my fluid/vhs extensions I have an error while editing pages from backend
04:35:45 <jagmanetta> This is the exception message: #1289386765: Could not analyse class:Tx_Vhs_ViewHelpers_Extension_Path_ResourcesViewHelper maybe not loaded or no autoloader?
04:36:36 <jagmanetta> I readed that I need to disable extensions that contains the namespace declaration like {namespace v=FluidTYPO3\Vhs\ViewHelpers}
04:37:14 <jagmanetta> I've done it, but the only one extension that use that namespace in my extensions list now is the fluidcontent_core
04:37:31 <jagmanetta> I think I'm missing something! :) Could anyone help me? Thanks a lot :)
04:37:56 <JohPie> I think you use the old namespaces
04:41:57 <jmverges> did you update the ft3 extensions from development version?
04:43:04 <jagmanetta> clear caches by filesystem, nothing changes
04:43:17 <JohPie> If I update to the develop versions, nothing works anymore
04:43:39 <jagmanetta> I confirm: I've updated the extension via the extensions manager and I'have my typo3 in development mode
04:45:09 <jagmanetta> The problem still exists with the Page/List module selected
04:45:52 <NamelessCoder> jagmanetta you probably have a {namespace v=Tx_Vhs_ViewHelpers} somewhere. That must be changed to {namespace v=FluidTYPO3\Vhs\ViewHelpers}
04:45:56 <JohPie> jmverges: after switch to flux develop, I get '#1257246929: "" is not a valid template resource URI' Page Modul
04:47:00 <jagmanetta> @NamelessCoder thanks, I'm gonna find and change it
05:04:03 <JohPie> I try to debug, but I don't have much time right now :(
05:04:44 <JohPie> Is there anything changed with Template Files and Path from master to develop?
05:05:17 <JohPie> or something that I "must have" in develop?
05:16:45 <jmverges> I really don't know JohPie, you could try to download all the ft3 extensions from github development branch and try to install uninstall them and clear caches
05:17:51 <jagmanetta> @NamelessCoder, something has changed now the error is #1289386765: Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Var\SetViewHelper maybe not loaded or no autoloader?
05:18:17 <jmverges> jagmanetta: try to install uninstall the extension
05:51:33 <jagmanetta> @jmverges sorry, but i see that the helper still exists https://github.com/FluidTYPO3/vhs/blob/development/Classes/ViewHelpers/Variable/SetViewHelper.php
05:52:10 <jagmanetta> many extensions in my installation use it, why should be no more available if is still in the vhs extension?
05:53:57 <jmverges> you are using var instead of variable jagmanetta
05:54:15 <jmverges> you only need to change all your .var. to .variable.
06:13:18 <featdd> how do I render a image in a fluid template fetched from an local filemount as a \TYPO3\CMS\Core\Resource\File
06:13:24 <featdd> can only get the dump file link but not display the real image :-/
06:30:45 <BennyS> Hi guys! Im trying to integrate a page template using fluidpages. How can render the party outside <body>? For head-meta-data i found viewhelpers. But how to render for example: <!DOCTYPE html>
14:33:02 <sitegeist_alex> Hi @NamelessCoder, could you have a look at my comment on https://github.com/FluidTYPO3/flux/commit/c4046ffb87ffd081b0abdaad9896a9653c37e5f5 please? Do you have any hint for me to bypass this error?
16:49:30 <xaver> sitegeist_alex: i can provide only a workaround
16:53:26 <pedda> anyone already dealed with #1257246929: "" is not a valid template resource URI. in latest ft3 extensions (development branch)
17:04:39 <pedda> NamelessCoder the latest version of EXT:builder generates provider extensions where typoscript configuration starts with plugin.tx_MyVendor.MyExtKey. is this the way to go for 7.x ?
17:08:32 <pedda> in fact i was trying latest master core in a working project, related to the core update i updated all ft3 extensions too. I'm facing a few issues now, which i tried to solve by generating a dummy extension, to see how a "modern" extbase extension should look like now
17:09:54 <pedda> i was setting up websites by the help of EXT:view by now, this seems obsolete since stdWrap was introduced to view.templateRootPath for example. am i correct ?
17:32:23 <pedda> i use a php based provider in an extension called profiles
17:33:41 <pedda> i have 2 fe plugins, so i do have 2 php classes in Classes/Provider/Configuration/CarouselPluginProvider and register those in my ext_tables by the help of 2 lines
17:34:01 <jmverges> however, if you are trying to overlay you need your extension https://gist.github.com/jmverges/86a8f49f6921f976d355
17:34:51 <pedda> i will need to deal with overlays afterwards, the EXT:profiles uses its "own" templates atm
17:40:12 <pedda> worked until i upgraded from 6.2 LTS to 7.x
17:40:38 <pedda> to be more precise: 7.5-dev and edgy ft3 tools
17:41:56 <pedda> i used the ts based "flux de plugin settings" approach for a while, but i moved back to php based as the ts based one failed several times after EXT:flux upgrade
17:42:24 <pedda> do you use flux for fe plugin settings in your custom extensions?
04:09:09 <pedda> it's rather like i've been cleaning up some code after someone else messed it up.. and i realize i stumble on the same issues periodically
04:10:00 <pedda> i should document any solutions to problems i solved in the past somewhere ..
04:11:25 <pedda> the symptoms of such a broken flexform are backend messages appearing at the top or extdirect debug messaages while hiding a page via context menu in the page tree
04:12:10 <pedda> Fatal error: Cannot use string offset as an array in /var/www/public_www/example.com/typo3conf/ext/fluidpages/Classes/Provider/PageProvider.php on line 244
04:12:25 <pedda> which is obvious if flexform contains empty lines
04:34:17 <pedda> if my root page has a flux setting set to true, and this setting also appears in a different page template on a page beyond the root page, the value of the setting (set to true) is inherited when i begin to edit the page properties of that child page
04:36:47 <pedda> if i set that property to false only this property gets saved to flexform
04:36:55 <pedda> others are replaced by empty lines
04:37:33 <pedda> nut sore if i get inheritenca right..
09:25:18 <BennyS> Hi guys! I have a question regarding vhs. Is it possible to render HTML like that using the v:asset Viewhelper? <script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
09:26:13 <BennyS> When i try <v:asset.script external="1" path="//url"> i get an error, because i didnt use http:
10:43:27 <Guest|89401> Hello! I am using a TYPO3 System in Version 7.3.1. It is not possible to install the fluid site kickstarter package because the version of typo3 is higher than the extension is. nevertheless i could install the extensions, but get the error message in frontend. does anybody know if updates of the extension "fluidcontent", "fluidpages", "builder" an
10:43:27 <Guest|89401> d "fluidcontent_core" are planned?
11:15:13 <rosieres> Have a guy here with a problem with his DS as hierarchy. Can I pass him to you, because it seems a bit complicated.
13:15:38 <pedda> is it possible to use v:content.render to render a formhandler plugin and assign data to the element via loadRegister="{recipient: '{company.email}'}" attribute and use that register within formhandler ??
13:16:10 <pedda> or is this rather usable for csc elements
11:02:57 <galoppi> Hello everybody! Could someone please have a look at the code checker? I think that all of the TYPO3SniffPool rules are not executed. Try for example something like "Class Bla Extends Blupp" in your sourcecode what should be forbidden because of the upper cases in Class and Extends (just one example).
11:03:46 <galoppi> I tried the check with calling ./vendors/bin/checkstyle
11:04:25 <galoppi> I have a local Ubuntu 14.04 environment as vagrant box
11:25:09 <galoppi> ZipArchive::extractTo(C:\workspace\projects\flux/vendor/composer/9306f281/TYPO3-TYPO3.CMS-2e7ea60\typo3\sysext\impexp\Tests\Functional\ImportFromVersionFourDotFive\PagesAndTtContentWithRteImagesAndFileLink\DataSet\Assertion/importPagesAndRelatedTtContentWithRteImagesAndFileLink.csv): failed to open stream: Invalid argument
11:25:40 <galoppi> after Installing typo3/cms (6.2.14) in fluidtypo3/flux
11:26:40 <galoppi> With Linux there is no problem - but I would like to call the ./vendor/bin/make for the pre-commit hook on my windows machine
15:30:49 <mneuhaus> regarding the frontend simulation in the AbstractImageViewHelper i can keep that in for now if you like it just kinda screamed at my face since you guys already pulled that out into a static function for other instances :)
15:33:02 <mneuhaus> but yea, you might be right, the simulateFrontendEnvironment looks more comprehensive in the AbstractImageViewHelper than in the FrontendSimulatorUtility
16:28:31 <NamelessCoder> I'm doing a huge project these days and it is almost exclusively pibase. I get to work with just two fluid implementations there. It sucks. :)
16:28:37 <NamelessCoder> {somevariable as integer}
16:28:49 <NamelessCoder> {somestupidobject as upcastedclass}
06:09:20 <alexxB> hey all. I would like to overwrite an existing fluidcontent item from the fluidbootstrap theme. how can that be done? just using typoscript "view.templateRootPaths" does not seem to do the trick but doubles the content element in the backend
08:00:19 <xaver> kempfe: you can try to fix it in schemaker and create a PR
08:10:21 <NamelessCoder> two things about that: 1) if you wish to fix this for 6.2.x schemas the fix has to be submitted to the core. The problem is that the phpdoc contains an unescaped HTML tag which is not valid even in the RST standard the core uses. 2) This soon becomes a non-issue because I'm fixing this in standalone Fluid that becomes a dependency. That will use Markdown, possibly also decouple the documentation from the classes.
08:11:25 <NamelessCoder> basically, you wouldn't be able to fix this even if you enabled RST support in schemaker which I'm not a big fan of... RST is hugely complex and requires secondary tools and 90% of the ViewHelpers we document are either in markdown or already markdown-compatible.
08:18:47 <xaver> NamelessCoder: possible improvment is only render tags with <[a-z]\: + viewhelper
08:19:52 <kempfe> y makes no sense - i ve checked the templates - a fast fix would be to escape the select element with regular expression in the template .. but thats no real fix
08:30:20 <NamelessCoder> what do you guys think about syntax like <f:if condition="{variable1 -> f:condition(and: variable2) -> f:condition(and: variable3)}">?
08:36:54 <mneuhaus> without the condiception, but i like it :)
08:37:15 <mneuhaus> the condition logic feels quite briddle to me anyway
08:38:48 <mneuhaus> would love a "rocksolid" boolean etc, i know you hate the approach i'm going to mention, but hey ^^ https://review.typo3.org/#/c/31707/
08:40:06 <NamelessCoder> that's what ExpressionNodes are for ;)
08:40:38 <NamelessCoder> so you make a plugin that provides this expressionnode type and has a dependency on Eel (if that's decoupled?)
08:54:51 <mneuhaus> but currently lost a bit of "momentum" since i invested quite a bit into flow, but kinda feel at a crossroads, i love a lot about flow, but some things feel like a dead-end to me i don't like. most stuff keeps getting more complex, barely anything kiss anymore
08:55:24 <mneuhaus> yea, you rock, you shove out far to much code :)
08:55:24 <NamelessCoder> imho it went the way of all monolith frameworks and it's extremely hard to change from that
08:55:51 <NamelessCoder> just take a look at the battle inside TYPO3's core right now... phew
08:56:06 <NamelessCoder> and Fluid is just one component that was easy to decouple.
10:02:05 <drlimbo> i just upgraded vhs, flux, etc. to the newest TER-Version, and now i got an error on every page (only if there is a fluid element) - also in backend
10:02:26 <drlimbo> Template could not be loaded. I tried ........ /Resources/Private/Templates/Content/Index.html
10:07:42 <Guest|80291> Hi, guys! Can someone please fix https://fluidtypo3.org/viewhelpers/fluid/master/Form/SelectViewHelper.html
10:11:17 <mneuhaus> hey Guest|80291 that issue is known of, yet not that easy to fix, there was a bit of discussion a few hours ago, you can read that up from here downwards:
10:19:49 <drlimbo> mhh, maybe the templateRootPath etc doesnt get loaded correct?
10:20:04 <drlimbo> mh nope, the page templates are correct
10:23:06 <drlimbo> i found that in Deprecation Log mneuhaus TYPO3\CMS\Core\Utility\GeneralUtility::loadTCA() - since 6.1, will be removed two versions later
10:27:33 <BeTyp> Hi everybody! Can somebody please help me with ke_search extension, how could i implement a search for an user selected year, some kind of multiple search with the "search word" too,...
10:28:14 <mneuhaus> drlimbo: you couldn't imagine how often this question has "cleared" things up ;d
10:28:28 <mneuhaus> kinda like, "did you try turning it off, and on again?"
10:28:41 <BeTyp> i configured the extension with the news and categories and it's working but i need a year search to implement there...
10:31:02 <mneuhaus> did you check for hooks to alter the query/results?
10:32:25 <BeTyp> i'm kind a new in typo , i could change in the view template and css to show me a date input,..but in the backend code i could need some (time)help to figure this out, how it's working
10:33:41 <BeTyp> yes, but it's not very clear that too,..i just need to know where to add that extra 'and' clause for that year option...
10:35:15 <mneuhaus> phew, ok best start by digging into ke_search to find the spot where the results are fetched from the database and keep an eye out for code containing the word "hook" it's mostyl a if enclosed foreach around 5-10 lines long
10:35:28 <mneuhaus> in general you can read up about hooks a bit here:
10:38:17 <BeTyp> thank you i've already watched something like this, i laso installed ke_search_hooks an extension for the Search ...but i'm stucked for the next step...
10:38:53 <BeTyp> i thought some of you made a change already on this extension and have a concrete idea on it...
10:38:59 <mneuhaus> so, you did find a spot where you could hook into to alter the database query, or the results?
10:46:19 <mneuhaus> got one brewing in my head that *might* work without any modification to ke_search
10:47:18 <mneuhaus> afaik ke_search supports facets, so, if you manage to attach a year facet on save to every news/index you could probably filter by that
10:47:38 <BeTyp> here is a pict with how the new looks with date,..
10:48:54 <BeTyp> i tried something like that,..but it looks complicate for me...:(
10:50:40 <mneuhaus> don't be intimidated :) learning by doing is the best way to improve :)
10:51:20 <mneuhaus> first start of by finding a hook in ke_search that is called after indexing, than create a hook based on the documentation i gave you above
10:51:51 <mneuhaus> then set up some facets manually and see how they work + how they are stored in the database
10:53:18 <BeTyp> thank you very much for your answers...i will try to figure this out somehow
10:53:38 <mneuhaus> btw, you could also try if someone in the typo3 slack has something like that, lots of the typo3 devs have left irc and went for slack: https://forger.typo3.org/slack
12:39:15 <mneuhaus> fluidtypo3 wasn't planned initially, but after realizing gridelement is way to old for 7.x i convinced the agency i do this project for to use fluidcontent
12:39:34 <mneuhaus> only flux + fluidcontent used in that project
12:40:02 <mneuhaus> quite a big agency, that hasn't realized yet how got fluidtypo3 is :)
17:25:03 <NamelessCoder> seems a lot less risky in terms of required escaping and use of sub-viewhelpers
17:25:35 <mneuhaus> hmm, yea maybe, although it could be force-escaped at that node
17:25:51 <NamelessCoder> the ExpressionNodes were intended as flexible ObjectAccessorNodes, currently with one exception: the LegacyNamespaceExpressionNode which catches a definition.
17:26:32 <NamelessCoder> I have thought about permitting aliasing using {varname = some:vh()}
17:26:54 <mneuhaus> might make sense, the alias viewhelper seems clumsy
17:27:05 <NamelessCoder> but it would probably have to be made as a built-in part of the viewhelper detection pattern.
17:28:06 <NamelessCoder> {var = vh:vh1() -> v:vh2()} - it changes the logic too. Yeah, kinda scary...
17:29:24 <mneuhaus> maybe not enough on the good side of the scale :/
17:29:37 <mneuhaus> so, instead of eel, how about http://symfony.com/doc/current/components/expression_language/syntax.html
17:29:39 <NamelessCoder> more risk than gain, likely.
17:31:45 <NamelessCoder> same problem, likely too much strain on the parser. It would have to be mixed with Fluid and from the complexity of that language, it would probably be a pretty damn broad regexp to catch it
17:32:03 <NamelessCoder> that being said there are some things we could implement
17:36:19 <mneuhaus> take a peek at python best practices, the natural language like syntax isn't bad
17:37:01 <mneuhaus> especially in the fluid case, because stuff like that would be way more meaningfull to a non-coder designer that only knows some html
17:37:15 <NamelessCoder> but do you really need that much - and is it a good idea to enable it in templates?
17:37:57 <NamelessCoder> need: for 90%, probably never. Good idea in templates... phew. Man. I wouldn't want to be the one educating about secure use...
01:24:11 <jmverges> Did you have a little party yesterday? Lots of merges, cool
05:57:22 <soma> hi. can someone please point me to an example how to use an overlay for some CEs with fluidcontent_core?
11:42:29 <Guest|63438> Hello! I added a custom field (tx_ext_visual) to the pages table. I can retrieve the value of this field with {v:page.info(field: 'tx_ext_visual')}. but i want to override my custom field by typoscript. Is this possible?
08:29:18 <artisticMink> Hello, after upgrading to flux 7.1 i'll ran into the problem that my custom page controller which belongs to the provider extension get's called, but no one of the corresponding actions get called. Yet, the site renders flawlessly. Default actions seem to get used instead of my custom ones. Did some conventions change? Sadly bootstrap_pages seems t
08:29:18 <artisticMink> o be out of date. My controller is pretty straight forward: http://pastebin.com/nRQAQV8X Any help much appriciated.
08:31:42 <thierry> Hello, in a v:page.menu and the <f:for each loop inside, is it possible to access the page settings, and not "only" the standard fields ?
09:32:28 <thierry> OK, I give it a try, thanks Xaver
10:07:47 <artisticMink> xaver: Thanks for the response, so i have to announce my custom controller in ext_tables.php?
10:15:28 <artisticMink> xaver: You where right. The lines where the providers get registered was commentet out for some reason. Though, outcommenting them results in 'Class 'Tx_Flux_Core' not found in' Oh well, i'll sure have a great afternoon. Let's start digging. Thanks for your help.
10:23:31 <artisticMink> For the logs, solved the error by using the correct namespace to call flux core (FluidTYPO3\Flux\Core::registerProviderExtensionKey). Still no luck on calling controller methods.
10:46:21 <thierry> @xaver: but, a "limitation" of Fluidpages: the settings aren't available on translated pages. That means: such settings must be "language independant" (dates, colors, ...), but no fields like "title", "label", ...
11:05:16 <thierry> Big "old mistake" of TYPO3 to have a separate table for pages translations ...
11:05:42 <thierry> From the redactor point of view, having x languages version in the page is not easy easy to understand
14:59:48 <artisticMink> Hello, i upgraded to 7.1 from 6.x with the issue of old content elements getting rendered in the FE but not showing up via BE->New Content Element. I've gone trough the migration sheets as well as making sure it's not a cache issue. Tried to establish a new CE from the documentation example, no success. I'm a little lost right now.
15:05:16 <artisticMink> Got the error, my bad. Clarified in Migration to Flux 7.1, Documentation.
04:04:48 <mneuhaus> NamelessCoder: how'd you go about a "generic" way to provide access to the "request" inside viewHelpers? i know fluid standalone doesn't have a request anymore. but i kind of need a way to read request arguments like page, sortBy, order, limit, search, filter
05:46:10 <NamelessCoder> mneuhaus $this->renderingContext->getView() and let the View contain the Request if you need it. As it is default, the View is decoupled from everything Request-context related except for knowing the controller, action and format (which it uses to resolve our MVC-based template locations)
05:46:41 <NamelessCoder> alternatively, insert it into ViewHelperVariableContainer as a stored variable; inserted by the View as well
05:47:12 <NamelessCoder> and finally, if we are in TYPO3 context with your question, $this->controllerContext exists on ViewHelpers (but only in TYPO3)
05:47:13 <mneuhaus> hmm, yea kinda figured a way like that :)
05:47:40 <mneuhaus> well, i'd like to keep it open/flexible this time around ;D
05:47:51 <NamelessCoder> but you can get to the View instance from within ViewHelpers and that's an extremely transparent way of doing such a thing
05:47:59 <NamelessCoder> e.g. ControllerActionView ;)
05:48:18 <mneuhaus> yep, i think something like that makes sense, maybe even as a trait
05:48:41 <mneuhaus> i already toyed with the idea to move quite a bit of logic out of the "controller" area towards the view area
05:48:51 <NamelessCoder> Traits are good but lets avoid them since we have none at this point
05:48:54 <mneuhaus> so the controller is only used to fetch/store data
05:49:13 <NamelessCoder> hehe tread carefully now ;)
05:59:24 <mneuhaus> "all i need" is an iteratable object with a common api for rendering a table
06:00:05 <mneuhaus> so, it needs to be iteratable and i need to be able to set limit, offset, order, and maybe search/filter stuff
06:01:20 <mneuhaus> so i was thinking to use a common pattern kinda like: EntityQuery('MyEntity')->execute() which gives me an EntityResult i can iterate over and a method EntityResult->getQuery() to refine the query with limit, offset, etc
06:01:47 <mneuhaus> that's basically exactly what i do currently in the flow version of expose which makes sense imho
06:02:28 <NamelessCoder> since this *is* a View I would prefer something that only works with predefined queries or query types
06:02:40 <NamelessCoder> e.g. .all, .single.$uid, whatever
06:02:50 <NamelessCoder> (as variables accessed in template)
06:03:25 <mneuhaus> it is, the EntityResult is assigned as {items} in the template
06:03:40 <NamelessCoder> that's not what I mean :)
06:07:02 <mneuhaus> i fetch the defined objects/items from the current view, which usually was a QueryResult. i then fetch the Query from that and pass that through the QueryBehaviors to modify it if needed with limit, offset, sortBy, etc
06:07:41 <NamelessCoder> not sure I understand the logic
06:07:42 <mneuhaus> then inside the BehaviorViewHelper i override the original items/objects with the result of the modified query
06:08:06 <mneuhaus> wait, i'll sketch some pseudo code
06:08:36 <NamelessCoder> you retrieve a template variable, then overwrite it and use it, but never restore the original... so this works like a cumulative filter, i.e. the more instances of the ViewHelper you use on the same $objects, the smaller that set becomes.
06:13:00 <mneuhaus> hmm, ok, so i'll create a VariableProvider that gets objects in form of a QueryResult for example and i interact with the VariableProvider to tell it i only want 10 of the results starting from 30?
06:13:02 <NamelessCoder> what if a VariableProvider had DataSourceInterface[] and DataSourceInterface declared these unified methods you can do to a generic source of data.
06:13:55 <NamelessCoder> but why the hell not let it support more.
06:14:08 <mneuhaus> would prefer that in that case i think
06:14:34 <mneuhaus> because if you add a ExposeVariableProviderWhatever, you still might want to add generic variables
06:14:41 <NamelessCoder> you could then ship your solution as a VariableProvider, the DataSourceInterface and X number of ViewHelpers to paginate, limit, filter by attributes, etc.
06:17:08 <NamelessCoder> I'm thinking if there's a way to avoid multiple providers. It would obscure the logic in f:debug, would make it hard to predict when there are collisions too.
06:18:12 <mneuhaus> i mean the expose one could just extend the default one, would probably solve 90+% of usecases
06:18:14 <NamelessCoder> ...without making DataSourceInterface part of Fluid
06:19:28 <mneuhaus> i guess extending should be fine
06:19:50 <NamelessCoder> yeah but TYPO3 already does this so the solution would need a TYPO3-specific version too.
06:20:01 <NamelessCoder> that's the not-so-great part
06:20:36 <NamelessCoder> VariableProvider was *meant* to be replaced, to be viewed like a crazy dynamic arrayobject-type storage you can manipulate from the outside, too.
06:21:07 <mneuhaus> instead of extending i could make it a "fallback" inside it, if !hasVariable -> fallback->hasVariable
06:23:43 <mneuhaus> when it's running barebone i'll think about integrating it into extbase to test it
06:28:37 <NamelessCoder> as long as you do some sort of Request interaction I suppose that's fine. We would then trust whatever is around Expose to actually make the Request safe ;)
06:37:13 <NamelessCoder> I don't expect it to perform as well as my thunderbolt cinema display. So my expectations are as they should be, given the price, size, 4K immaturity etc.
06:39:50 <pedda> and i hope for better performance when i'm in the need of a new computer which then, hopefully, will be able to power external 4K displays at 60 Hz
06:47:05 <pedda> wel i have an imac which is used to play music a the moment
06:47:40 <pedda> i realized, syncin my dev env on two computers just takes too uch time/effort
06:48:27 <pedda> maybe i've not the best setup to work on both computers with just a short delay of transition from one computer to another
06:51:40 <NamelessCoder> I don't do it myself, but you could easily use git to track all your dot-files and Library/Xyz folders. And you could equally easily use something like composer to load every repository you work on.
06:52:04 <NamelessCoder> but I know, one machine is easier. It's also all eggs in the same basket :)
06:53:34 <pedda> all my projects are versioned so, fetching files, stying up to date is not that hard, bad as soon as you add some bookmark to sequel pro, or some editor config.. you need to extend your sync-config or add that bookmark on both computers which is a bit annoying
06:53:51 <pedda> but as you said, it's just a matter of configuration
06:54:05 <pedda> some scripting magic, and wer're in
07:00:31 <NamelessCoder> all fun and games, that button
07:02:39 <pedda> the first time i turned on my mbp (early 2015) i was like: dude! if the time, you spent waiting for your imac to finish indexing and such, was added, you could have boght two of those mbp's
07:03:50 <artisticMink> Hello, after updating to 7.1 from 6.X i'm unable to add new content elements to a page. Old CE are displayed flawlessly. I went trough the migration sheets and validated my markup. It might have to do with the issue that my custom content controller doesn't get recognized as well. Methods won't get called. Where the similiar issues in the past?
07:04:51 <pedda> artisticMink in such cases i get the latest version of EXT:builder to check if a bare extension generated by EXT:builder looks the same as my older provider extension
07:06:07 <pedda> if your controlles actions aren't called, check if the fce you're playing around is stored the correct way in the database
07:06:49 <artisticMink> pedda: I already tried examples from the documentation but you're right. I'll should give it a try.
07:07:00 <pedda> speaking of : Vendor.ExtensionNAme->MyFce.html
07:07:11 <pedda> or without vendor and stuff like this
07:07:48 <pedda> fix such a record and see if DebuggerUtility in your fce's action makes it to the frontend
07:08:52 <pedda> if it does use this to have a one liner ;)
07:24:51 <pedda> additionally you could change "Entry created! Please allow a bit of time for the web master to approve the submission." to "Entry created! Please allow a bit of time for the master to approve the submission." ;)
12:03:37 <Kaimane> When I set the icon option to a flux:form like options="{icon: '{f:uri.resource(path: \'Icons/Content/Icon.png\')}'}" the icon will not be shown in the backend. The image src is "../typo3conf/ext/myext/Resources/Public/Icons/Content/Icon.png" but the browser tries to load it from http://dev.local/typo3/sysext/cms/typo3conf/ext/myext/Resources/Public/Icons/Content/Icon.png". I'm using the latest
12:03:37 <Kaimane> vhs, flux, fluidpages und fluidcontent extensions from TER.
12:23:44 <pedda> specify ExtensionName attribute on f:uri.resource if it works then, your extension is not properly implemented regarding namespacing
13:36:36 <thierry> My fault: didn't try fcc at this time ... !
14:41:40 <mneuhaus> NamelessCoder: workin on the variableProvider stuff, hitting a first bump, what, if i want to show to lists of objects on in the same template? the way the variableProvider would be set up, it would be just for one resultSet
15:34:32 <mneuhaus> NamelessCoder: found another issue regarding using a variableProvider:
15:35:37 <mneuhaus> currently the AbstractTemplateView creates a new StandardVariableProvider for rendering sections and partials which makes the initially set VariableProvider not accessable anymore
02:11:37 <mneuhaus> i'm currently fixing various viewhelpers that extend from AbstractConditionViewHelper to work with the compiled viewhelper change in 7.3, should i create a pr per viewhelper or bunch them all together?
02:20:58 <mneuhaus> multiple commits for one pr is not ok, right?
03:24:20 <Guest|42676> Hello, i'm using <v:media.pdfThumbnail class="img-responsive" path="uploads/pics/{image}" src="uploads/pics/{image}" width="570" height="760c" maxW="570" maxH="760c" minW="570" minH="760c" treatIdAsReference="1" title="{title}" alt="{title}" forceOverwrite="1" /> but the pdf doesn't crop correctly. Is there a workaround to fix this problem?
03:24:59 <Guest|42676> The height of the images is different.
04:37:22 <Kaimane> xaver: thanks for your hint. I removed the icon property from options argument. Icon has the same name as template file (case sensitive) but in backend the icon is still expected in "http://dev.local/typo3/sysext/cms/typo3conf/ext/myext/Resources/Public/Icons/Content/Icon.png". Does it have something to do with the TYPO3 Version 6.2.14?
04:39:11 <Kaimane> No. Flux is in Version 7.2.1 from TER.
04:46:02 <Kaimane> Right frame in backend is loaded from "sysext/cms/layout/db_layout.php" (relative to http://dev.local/typo3) and the img src path to the icon is "../typo3conf/ext/myext/Resources/Public/Icons/Content/Icon.png" I think the path to the icon needs three more "../../../" If I change the path with dev tools to "../../../../typo3conf/ext/myext/Resources/Public/Icons/Content/Icon.png" then the icon
06:39:19 <Kaimane> Great. I will wait for the next flux version. Thank you.
07:06:51 <xaver> Kaimane: we added a utility to resize images and image will be now 24x24 also svg is supported
08:21:09 <Kaimane> xaver: Nice features. I think eta is "it's done when it's done"? ;-)
08:22:29 <Kaimane> Other question. If I use the "as"-attribute e.g. on v:iterator.random viewhelper do I have to register the template variable first? Debugging the variable results in NULL.
08:23:51 <xaver> yes and no to eta - next release - we added a milestone
08:28:12 <Kaimane> Using v:variable.set and everything works fine. Thanks xaver!
08:53:31 <Kaimane> Is there a possibility to convert a get-parameter string (a=1&b=2) to an array? Maybe a viewhelper?
09:00:15 <Kaimane> Something like parse_str function in php.
11:50:05 <Matt23a> I have created a second root page in my pagetree and want to use the fluid templates. I've selected the page layout in the page options, but in the page view there are still the standard columns. How can I fix this?
12:17:18 <Matt23a> Ok I found it. Had to activate backend layout in the appearence tab of the page settings.
04:44:44 <k4mi> Hey, there. Got a small problem with f:image. I got a list of high-resolution images which are getting resized with f:image. The problem is some are getting perfectly processed, but some are still refering to the original image.
15:47:49 <mneuhaus> man, vhs has quite some condition viewhelpers these days ^^ and almost all of them are fucked up the the compile static change in 7.3
17:46:43 <NamelessCoder> that's a big one, mneuhaus!
17:53:47 <mneuhaus> i mean, i have them working locally, but i needed to make the trait static for that, which has side-effects on all the other non condition viewhelpers using that trait
17:54:25 <NamelessCoder> https://github.com/FluidTYPO3/vhs/pull/894/files#diff-af35b327e3a76b27a092ced8a5a3f32bL40 you are sure the inherited property is now "protected" in all our supported TYPO3 versions including 6.2?
17:58:20 <mneuhaus> can't access $this from there anymore
17:58:38 <NamelessCoder> hmm, this reflection crap...
17:59:00 <mneuhaus> i know that's not a pretty solution, but it was the only one i could think of so far
17:59:06 <NamelessCoder> you didn't write it, not blaming you ;)
17:59:51 <NamelessCoder> at the very least you need to store "protected static $reflectionService" and check if it exists, if not, create it. That should avoid all the costly objectmanager stuff (and it is VERY costly)
18:00:29 <mneuhaus> yep, that sounds def better ^^
18:00:56 <NamelessCoder> luckily we don't have a lot of places where these types of services are implemented!
18:01:28 <mneuhaus> aside from a pageSelect in the hasSubpage and isChildpage i didn't see similar issues
18:01:47 <NamelessCoder> consciously tried to avoid injections ;)
18:09:41 <mneuhaus> got pagination + limits working
18:09:53 <mneuhaus> with a Query + QueryResult though
18:12:59 <NamelessCoder> I have to show you something. Shameless bragging :) http://i.imgur.com/XCfxZZQ.jpg - that tiny little thing on the right is my old 27" thunderbolt display...
07:50:10 <Guest|68937> Hi, do i have the possibility to change the default value of image width of fluidbootstraptheme's "Simple Responsive Image" from 1140 to a higher value except editing extension file?
07:50:30 <Guest|68937> Best would be to do that with typo3script if possible. Thanks in advance, adrian
07:58:48 <Guest|68937> I already tried plugin.tx_fluidbootstraptheme.settings.SimpleContentImageWidth = x btw, but that does not work, perhaps beause in template useTyposcript = = ?
07:58:52 <Guest|68937> I already tried plugin.tx_fluidbootstraptheme.settings.SimpleContentImageWidth = x btw, but that does not work, perhaps beause in template useTyposcript = 0 ?
06:38:17 <twistedNerv> is it possible to list files in specific folder of user uploads filelist with fluid/flux/viewhelper?
06:53:09 <NamelessCoder> twistedNerv see uploadFolder argument - https://fluidtypo3.org/viewhelpers/flux/master/Field/FileViewHelper.html#argument-uploadFolder
07:26:43 <twistedNerv> NamelessCoder: tnx, ill check ... sorry for late response...wasnt here
07:34:47 <twistedNerv> NamelessCoder: i dont see how could i use that in front end for accessing files or folders?
08:09:24 <svenDeKa> Hi guys. I would like to access settings from the tx_flux_parent of a FCE, set in the parents pi_flexform. is there a way -maybe an existing viewhelper- to access the parsed flexform? or will I have to write my own viewhelper?
08:09:55 <svenDeKa> (sorry if it already exists in the mighty vhs -then I was too blind to see)
09:10:03 <arnekolja> Is it a known "problem" (better: consequence) of fluidcontent_core, that pages with many images may take a lot of time to load in the backend?
09:11:55 <arnekolja> we are experiencing this with different sites using fluidcontent_core, but are not able to reliably determine whether it's really fluidcontent_core or not.
08:41:56 <papillon6> Hey! Any progress on the issue l10nmgr <-> fluidcontent? Newest version of l10nmgr still does not support fluidcontent-elements. @NamelessCoder: Found your GIT-repo on google. Anyone working on this?
10:41:14 <arnekolja> I just upgraded from 6.2 to 7.4 and now I'm getting file not found errors on the template files of my provider extension. I cant find anything that should have changed about referencing the templates, any idea how to troubleshoot it?
10:41:30 <arnekolja> error, e.g.: #1225709595: Template could not be loaded. I tried "/Page/Index.html", "/Page/index.html"
13:12:21 <pedda> can someone point me to the right direction?
13:12:39 <pedda> what is the best way to use extension B within extension A ?
13:13:57 <pedda> let's say: my extension A is some kind of a company "app" where each dependenc of a company has a few menu items, one of those should call extension B where extension A behaves like some kind of a wrapper
13:15:01 <pedda> not sure if i have to deal with controller and rendering context to achieve this
19:41:28 <rabe69> After updating a page from fluidcontent_core 1.1.3 to the newest TER version, i got this error in the frontend and backend on pages containing a content variant: rtrim() expects parameter 1 to be string, array given in /docker/code/typo3conf/ext/flux/Classes/View/TemplatePaths.php
03:15:48 <Guest|35438> Hi there. I'm looking for a solution to filter items in a field of type flux:field.relation analogy to the "foreign_table_where"-field in TCA while using something like "pid = ###CURRENT_PID###". Is this possible?
03:34:42 <Guest|35438> Ah, got it by myself. condition="AND tt_content.pid IN (###CURRENT_PID###)" works like a charm...
09:03:22 <Guest|71728> I'm running into a strange error: I'm using grids with flux:grid.columns
09:04:18 <Guest|71728> every time I try to add some content into a grid section it shows up above all contents in the backend and twice (one time outside the grid and the second one within) in the frontend)
09:05:14 <Guest|71728> is there a known bug or how can I prevent this behaviour?
09:06:33 <s-andersen> Hi, I'm using <v:page.breadcrumb> to render a breadcrumb menu, and this works great. But now I need to add RDFa markup to the breadcrumb menu, and I wonder what the best way to do that would be?
09:16:01 <NamelessCoder> Guest|71728 your user must have access to all Flux-related fields (parent, column, children). If you have an older version of Flux you must upgrade. If gridelements is installed there's a conflict with that which EM doesn't warn about. And finally if you're using the "save and add new after" then you need to update flux to development branch or wait for the coming TER release.
09:16:16 <NamelessCoder> s-andersen expand the tag and use the tag content like v:page.menu but with {rootLine}
09:21:43 <Guest|71728> Well I'm admin, so I think I have access to all these fields. I'm using TYPO3 6.2.14
09:38:53 <Guest|71728> I found out that the colPos 18181 is not saved to tt_content on first save. If if click save and save & close afterwards it works
09:44:58 <s-andersen> NamelessCoder: I expanded the tag and did this: <f:for each="{rootLine}" as="item" iteration="iterator">, as I would normally do with {menu} but that doesn't output anything
10:04:05 <s-andersen> I figured it out, it seems it shouldn't be {rootLine} but {breadcrumb} no matter what you specify as rootLineAs
13:00:13 <Guest|27878> I have in problem in the preparation of FCE . Elements can be filled in the back , but the front end will be no rendering . Working for some time with typo3fluid and can not find something wrong . What should I do ?
13:33:43 <Guest|27878> I have in problem in the preparation of FCE . Elements can be filled in the back , but the front end will be no rendering . Working for some time with typo3fluid and can not find something wrong . What should I do ?
13:37:36 <jost_> Guest|27878: can you check with <f:debug> if variable are set in the frontend?
13:43:16 <Guest|27878> The variables in my sections are empty. standard content elements from TYPO3 are renedered. The the elements from bootstrap will not rendered, too.
05:31:38 <Guest|89919> how can i set a typoscript value with the page options?
05:32:20 <Guest|89919> i now how typoscript set the variables of fluid bit i dont knmow the otehr way?
05:33:59 <Guest|89919> for example somthing like this: page.bodyTagCObject.value = <body id="{varOfPageOption}">
07:40:27 <t3xx> I've not working FCE in one TYPO3 Installation. In an other installation, is no problem. Both installations have the same version. How can I find and fix the error?My code is here:http://pastebin.com/vrnEMrkp
11:27:04 <papillon6> Hi! Struggling with <flux.form options="{icon: 'iconreference'} ...> The icon-reference does not work correctly. Someone has an idea what wrong? Tried "EXT:myext/Resources/Public/Icons/myicon.pg", relative path, absolute path, ...
15:25:56 <potofcoffee> Hi all. I'm using flux 7.2.1, fluidpages 3.3.1, fluidcontent 4.3.1, vhs 2.2.0 and fluidcontent_core 1.2.0 on TYPO3 6.2.9. Fluidpages work great, but inserting any fluidcontent CE gives me an error 500 on the page. Any hints on where I might start looking?
15:51:03 <NamelessCoder> potofcoffee run the install tool, the "compare DB" part. I'm guessing it's DB schema. If that's not it, give us the exact error message ;)
04:20:53 <MacPhil> you could redirect the php errors to a file
04:22:13 <MacPhil> my webserver configuration is hidding the php white errors from my log :D so i set the above
06:08:01 <potofcoffee> I think I figured it out. Looks like it was simply a timeout error with fcgi.
09:04:01 <Defos> Hey lads! Can I access nested FCEs? e.g. I have a FCE which has one grid. In this grid I have multiple other FCEs. How do I access the flux elements of the inside FCE?
09:05:38 <xaver> Defos: where do you want to access them?
09:07:24 <Defos> In the outer (wrapping) template which has the single grid
09:10:07 <xaver> you mean soemthing like this https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Content/Row.html
09:43:17 <xaver> in wizard it is mixed - use same order in element select and not based on provider
09:43:56 <xaver> you would need to split it yourself, but i would improve to build your default provider and mix is with a individual one
10:32:52 <arnekolja> I read that TYPO3 CMS 7.5 or 7.6 will provide Fluid based content elements as core functionality. What does this mean for fluidcontent_core? Will it get dropped, or does it serve a complexer purpose?
10:34:06 <xaver> arnekolja: depends on implementation - put i think it will will be continued. But we use core tables - should be no problem to switch
10:34:37 <arnekolja> okay. I'm looking forward to seeing it in action :)
10:34:38 <xaver> nested content is something else - we would like to use a nativ core feature, if it is useable in all cases...
10:34:58 <arnekolja> you mean like fces with grids?
10:35:17 <xaver> you can remove csc and install fcc - image with text is missing
10:35:54 <xaver> yes, or also accordion. 1 wrapper and content elements inside
10:35:56 <arnekolja> yeah, but missing image with text is quite a problem for editors who are used to it. tried it and failed communicating it :D
10:36:29 <xaver> most webs are responsive and text with image is horror - create needed elements as FCE
10:36:30 <arnekolja> yes, I think the timeframe wont allow it to make the first iteration an overall solution
10:36:41 <xaver> it is tested and optimized without 1000 options
10:37:07 <arnekolja> i know you're right … just fighting with the agency-internal editors.
10:37:14 <xaver> you can't test everything in image with test
10:37:23 <arnekolja> dont know right now … but image+text can be hidden, right?
10:38:13 <xaver> i build an FCE Contact with image and text or Product image and text
10:38:39 <xaver> i git it should be hiddden, i don't know if it was released
10:38:39 <arnekolja> btw, is there a performance "problem" with fcc? i noticed that pages containing multiply nested fces with images caused two installations to load the affected page for a looong time (pages module in BE)
10:39:30 <xaver> fcc is not nested - should be faster - less TS
10:40:04 <arnekolja> i mean i had fces with grids and those grids containing images added via fcc
10:40:46 <xaver> depends on cache and some other stuff - we added new caches few months ago
10:40:56 <arnekolja> e.g. a four-column grid, each col containing a two column grid with text in the one and image in the other column. that about 10 to 15 times and the page loaded around 20 seconds in BE
10:41:07 <xaver> if you have a testable reasonable performance issue - report it :)
10:41:49 <arnekolja> okay. maybe i'll reconsider using fcc again :) it's so great in theory, but i failed on image+text and performance a few months ago. maybe it is better now :)
10:42:32 <arnekolja> image+text shouldnt be a problem if its hidden. so i'll check current versions and/or permissions for that
10:43:02 <arnekolja> i'm also a fan of providing specific fces instead of offering each possible combination via generic elements.
08:17:03 <Guest|94905> hi to all the world I'm a little blocks , I worked on a rte but when I inserted an image size is 300 max width is can I configure Rte to have a larger width thank you for your help
08:17:28 <Guest|94905> hi to all the world I'm a little blocks , I worked on a rte but when I inserted an picture size is 300 max width is can I configure Rte to have a larger width thank you for your help
08:38:16 <Rabe69> I want to use extension "site" to kickstart a new project. If i try to install it, I get warnings about required extension "fluidcontent" and "fluidpages", which are not available in a version. Can i ignore this warning?
08:38:53 <Rabe69> I want to use extension "site" to kickstart a new project. If i try to install it, I get warnings about required extension "fluidcontent" and "fluidpages", which are not available in a compatible version. Can i ignore this warning?
08:39:37 <Rabe69> The following errors were found while trying to install "site":
09:26:11 <pedda> i install it, i create an fce for instance, with no label attributes defined at all, and i expect those labels to be "generated automagically"
09:26:23 <pedda> well i have an extension in my whitelist
09:32:15 <pedda> within flux at least.. it still needs to be added to the LLL file, but manually then, right?
09:32:36 <pedda> you see? i have a few questions regarding the whole magic in the background ;)
09:32:56 <xaver> flux requests the language service for the label
09:33:39 <pedda> i try to follow the "changes" of my lll file via git client, to see what is added and what is removed.. and it appears to me, as if a key is added at one point .. and removed again at some other point, depending on the backend view i access currently
09:33:56 <xaver> language service is signalSlot or similar and if an whitelisted extension access and can't find the label and it is backend it writes the requested key
09:35:37 <pedda> i access my test fce, flll writes flux.test to my lll file, and after this happened, it will reside there as long as i remove the key manually.. correct ?
09:37:46 <xaver> Language cache and stuff causes sometimes problems and i thiunk also a few bug :P but it should work that way
09:38:21 <xaver> i think i never tested it with not english backend language
09:38:30 <pedda> well .. i would expect it to work this way, the readme states the same facts somehow.. but what i actually see is a bit confusing :)
09:38:48 <pedda> agreed regarding the language cache thingy..
09:38:57 <pedda> this is definetly something i need to keep in mind
09:39:11 <xaver> create a issue with templates attached
09:39:54 <pedda> i would also expect to work with flll runnung in the background for the time of development, i then disable fll, because my LLL file is full of keys, and hand that project over to an editor who takes care of all those keys via LFEditor
09:40:39 <zaphod76> Hi, I’ve got a question about fluidpages/flux with TYPO3 7.4. I realised some configuration for the “page configuration” tab in the page properties using flux. Every change is only working after cleaning the caches by the installtool. There is noch other way to get it working. I can’t remember such behaviour in former TYPO3 versions (like 6.2). Any
09:52:42 <pedda> i use those page configuration properties based on ts properties
09:52:54 <zaphod76> If i change something in my fields in page configuration an open a page that was never opened before, I can see the correct output. Every other page shows the wrong stuff
09:53:12 <pedda> so name="settings.layouts.default.header.enableBreadcrumb" is the name of a flux:field.checkbox
09:53:41 <pedda> this way they're kind of mapped to typoscript properties which you can debug easily
09:53:52 <pedda> in fe, while dealing with your issue
09:54:14 <pedda> i never discovered some strange behaviour in relation to cache and flux at this position
09:54:38 <pedda> what might interfere and look like an issue is the feature of assigning templates for current and child pages
09:54:41 <zaphod76> I did it using TS too but today I decided to become more comfortable for the customer...
09:55:02 <pedda> as well as the parent decied option and then in addition to your flux properties which you maybe expect to become inherited
09:56:22 <pedda> you get me? maybe you deal with an "(non)issue" just due to the matter of fact, that you except page 10 to inherit some setting, which can't be inherited, as it is redefined by page 5 which is the parent page of page 10
09:57:43 <pedda> on the other hand: you only see the correct value in FE if the page is not cached is somewhat different
09:59:03 <zaphod76> I see the correct value after cleaning the cache. Then it will be build new an it shows the right value.
09:59:36 <zaphod76> But after every change you have to clean it again
10:01:55 <pedda> maybe this can help you: https://docs.typo3.org/typo3cms/extensions/news/latest/AdministratorManual/BestPractice/ClearCache/Index.html
10:02:14 <pedda> if you put TCEMAIN.clearCacheCmd = pages on your root page
10:02:42 <pedda> the pages cache should be cleared whenever you edit a record (or the page properties maybe?!)
10:02:57 <pedda> but this still looks awkward to me
10:03:36 <zaphod76> I think this will clean the same cache that I can clean from the backend. This does not have any effect. I have to use cache cleaning by installtool
10:04:46 <pedda> hmm .. sorry buddy, but i'm still sticking to 6.2 LTS version and didn't ran into this by now
10:04:46 <zaphod76> Maybe something about extbase? I jut "use" the stuff but I'm not a real developer. Therefore I'm not able to locate such kind of misterious behaviour...
10:05:25 <pedda> were speaking of resulting flexform which is generated by the help of EXT:flux and is cached that hard that you only can clear it from the installtool..
10:05:28 <zaphod76> I hadn't had such probs in 6.2... I'm using 7.4 for the first project now
10:05:53 <pedda> i don't think extbase as a general topic is the issue here
10:06:12 <pedda> maybe 7.4 has some new additional configuration options which can help you
10:06:27 <pedda> what's new 7.0 - 7.4 pdf's could help
10:06:49 <pedda> to see if something new was introduced and is causing you headache now
10:07:12 <zaphod76> I think so too. I have to decide wether to downgrade to 6.2 or wait for a fix. But for a fix it must be a bug and not wrong shit made by myself...
10:08:11 <pedda> well: if you're not in a hurry at all, i would do some more investigation
10:09:18 <zaphod76> I read about changes in caching for "AbstractConditionViewHelper" and everything that is based on it. Would be nice to unterstand what that all is about :-D
11:01:19 <drlimbo> i have a strange issue with my FCE after upgrading (vhs,flux,fluidcontent,fluidpages)
11:02:12 <drlimbo> Frontend AND backend crashes, if there is ANY FCE Element on a page
11:02:18 <drlimbo> and i get the message Template could not be loaded. I tried "xxxxxx/ext/ogbase/Resources/Private/Templates/Content/Index.html"
11:02:43 <drlimbo> all my FCE's are stored in this /Content Folder and Subfolders
11:03:02 <drlimbo> IF i add an index.html FCE - this will be choosen everywhere in backend and in frontend
11:03:48 <drlimbo> BUT in the database and while editing in the backend - i can choose the Rights FCE Elements, but after chaning the FCE-Type, it switches back to my dummy index.html FCE
11:04:53 <drlimbo> also when adding a new element on a page (without an FCE already) i can see all FCE's (with broken icons - but i didnt set an icon)
11:33:56 <pedda> if Index.html "is called" then, because fluidcontent was unable to determine the proper file or action related to the selected fce in backend
11:34:26 <pedda> adjust such a record manually in database to see if it helps
11:36:02 <pedda> if it does: https://gist.github.com/wikipeter/6e67695b143efd77d40a
11:36:41 <pedda> as you might need to adjust all occurences of extension_name: and change them to Vendor.ExtensionName:
11:38:00 <pedda> this snippet is called rename provider extension, as you could also adjuist all my_old_extensionkey: to myNewVendor.MyNewExtensionKey: for both pages and content records
11:38:37 <pedda> btw NamelessCoder you didn't review https://gist.github.com/wikipeter/6e67695b143efd77d40a by now, i added it to the library on fluidtypo3.org
11:39:23 <pedda> drlimbo: always backup your database before you go on with those sql commands!
03:40:07 <Guest|31066> I have several subtrees, which should use different provider extensions.
03:40:37 <Guest|31066> this is caused by the circumstances, that the whole instance provides s.c. stories which differ a lot
03:41:30 <Guest|31066> if i install two provider extensions, fluidcontent provides now all content elements from all used provider-extenions on every page, even though, the use different static main templates
03:42:02 <Guest|31066> is there a possibility to reduce it for subtrees, to just use the elements of the included provider extension in that subtree?
03:42:48 <Guest|31066> or do i have to write something above, to provide this functionality
09:32:18 <Guest|83134> I'm getting back to typo3 and fluidtypo3 solution and I cant make any FCE work :( I installed fluid fluidcontent fluidpage vhs and builder from GIT (branch master) and every time I try to use a FCE in the provider I created with builder, i get the same error : Call to a member function getViewHelper() on a non-object in typo3temp/Cache/Code/fluid_t
06:24:17 <braguzz> may have I some help on fluidcontent_core, here?
06:52:06 <Maren2911> Hi there! I've a small question about localization. I've some flux FAL images and I want the foreign images having the default image source. I tried the localizationMode="'keep'" attribute but it doesn't work for me. Someone who has an idea for me?
07:04:46 <braguzz> I configured fluidcontent_core to insert a new header parameter
09:35:26 <bottoni> Hi all, I´m currently encountering length issues for pages.tx_fed_page_flexform. My XML is potentially larger. Does anyone have an advice how to come around that? It seems that the field value gets truncated while persisting in T3 backend as I switched to mediumblob as a test but the xml is invalid afterwards anyway
09:48:59 <drlimbo> is it possible, that with the newest flux-family its not possible to store FCE's in Subfolders? like /Templates/Content/Subfolder/fce.html ?
09:55:15 <drlimbo> NamelessCoder: i think you should know that
10:05:23 <xaver> i think the problem is caused because of API changes for v7
10:05:47 <xaver> i use compass/less, but it runs outside of TYPO3
10:07:02 <drlimbo> xaver: what u mean with "bug issue first thing "?
10:07:33 <drlimbo> and yes, we compile the scss local and checkin (git) .scss and .css files, but it would be much nicer, to only store .scss files and let typo3 generate the .css files
10:07:52 <drlimbo> specially with a magic viewhelper =)