11:39:21 <dasFelix> okay :) thx BenjaminR - I just tried to replace all 'v:var.' to 'v:variable.' in templates fluidBootstrapTheme. But I get some exception thrown out.
11:40:21 <dasFelix> hehe let me specify in a sec :D
11:43:28 <dasFelix> BenjaminR - when I replace the line in FrontPage.html I get a #1289386765: Could not analyse class:Tx_Vhs_ViewHelpers_Variable_SetViewHelper maybe not loaded or no autoloader?
11:43:38 <dasFelix> TYPO3\CMS\Extbase\Object\Container\Exception\UnknownObjectException thrown in file
11:44:06 <BenjaminR> well how did you define the namespace - because vhs 2.0 is namespaced
14:08:17 <dasFelix> what do you recommend during dev of fluidtypo3 templates regarding CACHE settings? I mean to avoid deleting cache in BE and/or Install-Tool? Using ext: uncache or other something else?
14:23:51 <cedricziel> uncache overrides all caching implementations with a null backend-that approach works best
14:24:30 <cedricziel> other than that-there's aswitch in the extension settings of flux to re-eval all templates at any time
15:04:49 <dasFelix> thank u cedricziel. Will try both ways :)
15:20:13 <Benny84> Hello everybody. I've a problem with fluidbootstraptheme. On a local installation everything works fine, but on my webserver nothing shows under Page Layouts if I edit a page. I'm using typo3 6.2.3 and all extensions are git releases.
15:21:46 <SuburbanWorrier> Hi Benny84, I've got exactly the same issue on my mac having recently reinstalled apache/php
15:22:16 <SuburbanWorrier> not looked into it properly yet but I suspect a php version issue
15:40:20 <cedricziel> what php version are you using?
15:40:59 <SuburbanWorrier> cedricziel: hang on I'll fire up the mac
15:41:00 <gencha_> cedricziel: we're on 5.4.4 on our server
15:41:25 <Guest|20973> Hey there. Does anyone know a way of changing the body's class?
16:01:33 <nimius|thephpjo> Hi there. I just pulled the latest Version of flux. getting the following error when trying to access the backend
16:01:34 <nimius|thephpjo> Fatal error: Call to a member function get() on a non-object in/Users/thephpjo/NIMIUS/AHM/typo3conf/ext/flux/Classes/Configuration/BackendConfigurationManager.php on line 171
16:02:34 <Benny84> @cedricziel: everything's fine after your bugfix
16:04:06 <cedricziel> nimius|thephpjo: the crux with living on git is that you dont get a clean cache after updating. normally EM does that for you, but with git, typo3 will still use the already reflected _old_ classes
16:04:31 <cedricziel> use the "important action" -> clear all cache emergency button
16:08:48 <cedricziel> 4.) cache in db if caching framework is told to do so
16:08:55 <cedricziel> and a lot more in between those
16:09:22 <cedricziel> so clearing all caches is the solution to almost any of those problems-but you never know which one to clear :)
16:10:33 <nimius|thephpjo> cedric, you just earned a place in our confluence – explaining caches for future reference
16:10:45 <cedricziel> that's where the saying comes from: There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton
16:10:58 <cedricziel> cool, put a picture next to me :)
16:11:22 <nimius|thephpjo> i'll take the worst picture of you i can find
16:14:05 <SuburbanWorrier> cedricziel: fyi for my introduction package based install I get a working BE Page module when I uninstall all the fedext extensions
16:14:34 <cedricziel> the bootstrap distribution is meant to play well on its own
16:14:49 <cedricziel> it shows you how to create custom CE's the hard way
16:15:14 <cedricziel> could be there's some Implementation injected somewhere instead of an interface
16:15:32 <cedricziel> like with the recent trouble with yag
16:15:35 <SuburbanWorrier> "hard way" .yep - can see that now I'm a few months down the line
16:16:06 <SuburbanWorrier> ..but it all works for me on other servers
16:16:19 <cedricziel> just to make it clear: hard in this case doesnt mean "bad". the hard things are those that are srong enough to survive the winter
16:23:00 <SuburbanWorrier> cedricziel: uninstalling/reinstalling extensions show that fluidpages is what breaks the Page module for me in this case
16:23:27 <cedricziel> then there's an incompat in any of those
16:23:58 <SuburbanWorrier> and I *don't* have fluidpages in my working servers (like I thought I did)
16:24:20 <cedricziel> yes well. then there's something (tm) in there
16:25:29 <SuburbanWorrier> ... one issue down - on to the real deal breaker :-\
19:26:32 <dasFelix> with v:asset.style I include some CSS of several things like font-awesome, a skin, a lightbox, and of course a content.css. Now I have a file like "vhs-assets-awesome-skin-anmiate-slider-contentcss.css" because of the different "name" attribute of VH. Is there a switch which appends the stylesheet and does NOT create such a name-stylesheet-filename? Just "vhs-assets-site.css" or something like
19:28:35 <cedricziel> why does this matter to you?
19:29:03 <cedricziel> you can flip the standalone switch or create a group with just one asset
19:29:11 <dasFelix> cedricziel - it doesn't matter. Just cosmetic issue :D
19:29:58 <dasFelix> it's great when all those stylesheets are merged. I am not using the standalone attribute. I'll try
19:30:22 <cedricziel> you could try grouping then as well
19:31:19 <dasFelix> they are all already in one group="css"
19:33:35 <dasFelix> ahh I see... standalone saves them in own temporary files. But I like it merged. The less HTTP requests the better for server/client communication. As I wrote... just cosmetic issue. I just wondered if I can take influence on the generated typo3temp/vhs-asset..xxxxx.css file name