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...