01:41:17 <Outdoorsman> Hello again @NamelessCoder. You mentioned that to future-proof, it may be better to use fluidbootstraptheme instead of fluidpages_bootstrap and fluidcontent_bootstrap. Is fluidbootstraptheme more up to date?
01:44:00 <Outdoorsman> Regardless, I'm getting this error from fuildpages_bootstrap TER and git dev versions as well as from fluidbootstraptheme... #1371069824: Arguments useShortcutData, useShortcutTarget and useShortcutUid are mutually exclusive. Please use only one at a time.
01:44:55 <Outdoorsman> Am I just missing some TS configuration somewhere or is this really an error from the extension?
01:51:13 <NamelessCoder> I fixed this bug just here tonight (2am here currently) - if you check out VHS from git, branch development, all should be will
01:57:55 <NamelessCoder> it would be perfect if you can confirm the fix by checkout out VHS from git - I can then make the next TER version to fix this regression
02:10:02 <Outdoorsman> Ha ha NamelessCoder... I like your search and replace s/will/well comment. Haven't seen that before, made me laugh :) The when I updated to vhs dev from git it fixed the issue. Thanks!
02:11:47 <NamelessCoder> a tradition from the good old irc days :)
02:17:09 <Outdoorsman> So this applies to most all your extensions or just the page ones?
02:17:26 <NamelessCoder> your template may already contain a Templates/Page folder in which case you could get some conflicts or unwanted duplicate selection options (from your page + from the overlayed ext)
02:17:47 <NamelessCoder> applies natively to all Flux-powered extensions; requires EXT:view to work on others.
02:18:47 <NamelessCoder> if you want to avoid colissions you can for example create "Overlay" subfolders in your resources folders - e.g. EXT:myext/Resources/Private/Overlay/Templates, EXT:myext/Resources/Private/Overlay/Partials, EXT:myext/Resources/Private/Overlay/Layouts
02:18:48 <Outdoorsman> So should I adopt a different folder strategy as I move forward? Typically I just use fileadmin/templates/blahblahblah
02:19:23 <NamelessCoder> switch that strategy *now* :)
02:19:50 <NamelessCoder> always store your templates in an extension, use more than one if you need to
02:20:14 <Outdoorsman> Does this also require me to abandon my typical TS methods to and put them in myext as well?
02:20:17 <NamelessCoder> there's a bit more about why, on http://fluidtypo3.org/documentation/templating-manual/introduction/extension-base.html
02:20:45 <NamelessCoder> basically it means your paths now should use the EXT:myext... prefix when you reference files and folders
02:21:22 <NamelessCoder> and that settings specific to your template(s) will be located under plugin.tx_yourext.settings and view paths configured in plugin.tx_yourext.view
02:21:26 <Outdoorsman> I've read that page before so I *sort of* get it.
02:21:58 <NamelessCoder> and that you can use translation files which can be referenced using short labels instead of full paths like LLL:EXT.path/to/file.xlf
02:22:58 <Outdoorsman> So this means that when I'm using fluidbootstraptheme it has page templates that autoload, but order of precendence would look to my myext first to see if there are any overrides.
02:23:59 <Outdoorsman> Can I safely use fluidbootstraptheme for production?
02:24:10 <NamelessCoder> you simply say via TS that "hey, I've got some extra paths you have to check first, then fallback to whatever you did before"
02:24:41 <NamelessCoder> it is beta quality so far - I would wait about a week before using it, and after that would expect to maybe have to update once or twice before launching your projects
02:24:49 <Outdoorsman> Cool, thanks. It sounded like fluidbootstraptheme is the one that's going to be the new extension right?
02:25:06 <NamelessCoder> I only cooperate on that ext, I don't manage it (randomresult and mrboe do)
02:25:49 <NamelessCoder> yep, we merge the two _bootstrap exts into that and make the successor more suitable as base which you overlay selectively from project to project
02:26:42 <Outdoorsman> Maybe I should wait a little since the fluid code may change a bit before they release the real thing.
02:27:16 <Outdoorsman> I guess I could diff it too... just don't know how extensive that would turn out to be.
02:27:42 <Outdoorsman> OK... I'm testing this stuff out now.
02:28:15 <NamelessCoder> I think a fair amount of changes are expected in this ext from beta->stable. I would ask randomresult and mrboe how close to the end result they are currently
02:30:26 <Outdoorsman> What's the best way to contact?
02:31:40 <NamelessCoder> both of them are usually here during the day - it's 2:30 here so another ~6 hours and they should start to show up
02:32:12 <Outdoorsman> Ya... go get some sleep, you'll be better off for tomorrow. Thanks.
02:32:15 <NamelessCoder> I always prefer irc to get a lot of q/a done fast
09:17:59 <Tjark> I trying my first steps with fluidbackend. But i cant get this running on TYPO3 6.2 ... Always throws the following error : "PHP Fatal error: Call to undefined method FluidTYPO3\Fluidbackend\Service\ConfigurationService::getFlexFormConfigurationFromFile()"
10:58:59 <xaver> hi, i tried to update TYPO3 and get this error in ext manager - #1395614959: Version number in composer manifest of package "fluidcontent" is missing or invalid -> i removed already -dev in ext_emconf + cache clear
10:59:51 <Denyerec> xaver did you bump the version numer in ext_emconf ?
11:40:03 <randomresult> FT3BOT1 shoud translate @team into the teamNames
11:41:38 <mhmli> anyone have an idea about using fluid vars in a flux:field.relation condition? https://gist.github.com/permanenttourist/49ca21f44a6102263022
11:42:27 <mhmli> i've searched sysext, fluidcontent, fluidpages and others, to no avail.
11:42:48 <randomresult> @mhmli did u try plugin.tx_frpfce.settings instead plugin.tx_frpfce.settings.pid ?
11:43:28 <randomresult> so the whole settings will be put into that variable ? !?
11:50:34 <mhmli> condition="AND tt_address.pid in ({addressPID})"
11:51:32 <mhmli> you have to use in() syntax in the query. "equals" (=) comparator is what throws the error. https://gist.github.com/permanenttourist/49ca21f44a6102263022
11:51:45 <xaver> Arguments useShortcutData, useShortcutTarget and useShortcutUid are mutually exclusive. Please use only one at a time Oo
12:06:08 <randomresult> xaver its a breaking feature :)
12:07:38 <xaver> i wnat the update to work after 3 weeks of holiday
12:08:27 <randomresult> then simply change the one file in VHS. bjo3rn and NamelessCoder work on a fix - so with the next update of vhs you will be fine anyway
12:09:02 <xaver> randomresult: i have already another problem - repo -_-
12:45:16 <anhadikal> hmm looks like transform dont work
13:26:04 <mhmli> anyone got an example of $GLOBALS['TSFE']->cObj->RECORDS working please?
13:28:16 <mhmli> can i use this as-is, or do i need to to a manual query (exec_SELECTquery) to get address records?
13:35:51 <limboo> randomresult looks like the flux bugfix https://github.com/FluidTYPO3/flux/commit/43bc0c0cccb65b501a8ac31a1bf4239ba0f3ba0e is for flux 7.x
13:35:58 <limboo> is there also something for flux 6?
13:41:57 <danilobuerger> limboo why dont you just upgrade to flux 7 ?
13:42:33 <limboo> i think that isn't very easy? i think a lot of syntax changed from 6 to 7
13:42:44 <mrboe> @danilobuerger can u tell me hows the man for "workspaces"
13:44:20 <danilobuerger> limboo there are alias maps in place so you wont even notice if you are on 6.2... if you are on 6.1 there is a update script.... and the only real change is the colPos which you can also update through a script in EM
13:44:26 <danilobuerger> mrboe dont understand your question?
13:46:40 <mrboe> there are problems using workspaces in 6.2 and fedext
15:37:12 <mhmli> looking through many extensions, i cannot work out whether i should be using underline syntax for class names (Tx_Fluidcontent_Controller_AbstractContentController) or namespaces with backslash. is there any logic to it?
15:37:55 <mhmli> many of the core extensions in 6.1.7 use underlines
15:50:50 <NamelessCoder> mhmli if you come across bad examples in docs please message me in private - just spam all the links you find. I've got the documentation repository open currently ;)
15:51:09 <danilobuerger> randomresult i told you earlier that i will take a look at it...
15:51:44 <NamelessCoder> regarding your flux:field.relation question: how you actually *render* the variables depends on what you pointed to in the relation. Example: relations to tt_content are either rendered with v:content.render or records are retrieved with v:content.get (which returns an array you can then for example iterate in Fluid)
15:51:59 <randomresult> as i told earlier its not an offence.
15:52:09 <Guest|40384> hey claus, new site and documentation -> SPLENDID work!!
15:52:19 <randomresult> but right now, none of my webs can place plugins in FCE
15:52:20 <Guest|40384> just wanted to say thank you :)
15:52:23 <NamelessCoder> pages can be rendered as links pointing to the page or you can use it for v:page.menu, v:content.render and many others
15:55:39 <Denyerec> I'd like a content element that you can drop in to generate a snippets / teaser menu
15:55:39 <Denyerec> So to take the title and abstract from all subpages in a section and render it.
15:55:39 <Denyerec> I *think* I can just create a FCE and use the page.menu with a custom rendering
15:55:39 <Denyerec> But wasn't sure how to get to the page abstracts and images
15:55:39 <Denyerec> (I was going to use the page's media field to assign the image for the teaser)
15:55:39 <Denyerec> Will that data be available in "item" in the menu iterator ?
15:55:58 <Denyerec> If you didn't know it already "Besmirched" is an awesome word.
15:56:41 <NamelessCoder> Denyerec you already used v:resource.record - v:page.resources is the version to use on page records. And yep, v:page.menu would work great for your use case
15:56:44 <mhmli> (sorry: not all pages. from 3.2.3 on.)
15:56:59 <Denyerec> Used it, yes. Understood it, no :)
15:59:34 <NamelessCoder> aaah mhmli, that explains a lot. In this case you actually do need a controller (since viewhelpers aren't supposed to do SQL queries - it's considered quite unsafe)
16:02:41 <NamelessCoder> I assume you need only the data in the address record itself?
16:02:56 <mhmli> and even forcing it with an sql statement doesn't seem to want to work. debug() ing the query result times out. i have managed to build a simple view helper, but the result is that i need to hard-code the html output. (eww.)
16:03:29 <mhmli> yes, i need to select an address record in BE (flux:field.relation working fine) and then output a vcard for it inside an fce
16:06:44 <mhmli> but i get the feeling that's a hack.
16:06:47 <NamelessCoder> your viewhelper should...
16:06:58 <NamelessCoder> 1) accept the UID argument that you use in the query
16:07:09 <NamelessCoder> 2) Manually sanitize the argument value, before
16:07:21 <NamelessCoder> 3) Using the UID in a SQL query like you described, to load the record
16:07:58 <NamelessCoder> 4) Use $this->templateVariableContainer->assign('address', $addressRecord); then $content = $this->renderChildren(); and finally $this->templateVariableContainer->remove('address');
16:08:31 <NamelessCoder> result: viewhelper tag content can be used to define the HTML + Fluid that renders a vcard with address data, viewhelper assigns the data you need so it can be used as variables
16:08:45 <mhmli> sounds much cleaner. so the viewhelper is actually doing domain work instead of view work.
16:08:58 <mhmli> is $this->cObj->RECORDS an option?
16:09:09 <NamelessCoder> examples are in all viewhelpers which support the "as" argument - and you may want to include an "as" argument on your VH too (it helps avoid colissions if they arise)
16:09:32 <mhmli> i've tried about a hundred thousand variations on ->RECORDS to no avail.
16:09:40 <NamelessCoder> RECORDS will, afaik, actually attempt to *render* the objects if they have TS rendering instructions and you'll need the *data* so you can render it yourself, using Fluid
16:09:51 <NamelessCoder> selectGetRows() is not a hack ;)
16:10:29 <NamelessCoder> tt_address has no Extbase domain model and you are not expected to create one manually. Some extensions *do* provide such a model but in your case I would judge it is not necessary to introduce this much overhead to read a few address records.
16:10:45 <mhmli> i meant, that it feels hacky to be calling db requests from inside a view.
16:11:02 <NamelessCoder> in addition: implementing an extbase domain model for a record means you introduce new possible problems in other extensions which extend the tt_address table
16:11:21 <NamelessCoder> you are 100% correct and this is where you should use a controller (possibly even a service you inject in your controller)
16:12:07 <NamelessCoder> however, achieving a ContentController is a bit harder than the viewhelper approach and you can later refactor what you create as viewhelper, to work in a controller
16:12:33 <NamelessCoder> nono, this is actually relevant for people working with these features ;)
16:12:48 <mhmli> this is really exceptional support, thank you so much. almost done :) in this context, i've used http://t3-developer.com/extbase-fluid/themen/tt-content-in-extbase/ before to reference tt_content
16:13:28 <mhmli> but using it and adapting it for tt_address gives me no result at all. the best i've had is a timeout; the worst is nothing at all.
16:13:45 <NamelessCoder> you're welcome - I would personally avoid a tt_content / tt_address model because of all the difficulties which it implies, being single-table inheritance in nature
16:14:52 <mhmli> i guess going into the detail of the controller is too much for here and now. given that from what you've said, the viewhelper will work.
16:16:25 <mhmli> p.s. re. documentation from before: i was referring more to the typo3.org docus. which are sloooooowly being improved, but still empty, incomplete or non-existent for some critical stuff. if the work on the core was as well documented as fluidtypo3.org, myy day would be a lot easier.
16:17:51 <tom_at> is it possible to set the localization mode for an fce flux form? i have some simple adjustment fields which must not be translated. like l10n_mode='exclude' etc.
16:18:20 <mhmli> examples are the best tutorial. an i'll be more than happy to share my end result via github if (when) i ever get it to f****** work :)
16:19:05 <NamelessCoder> great - like you said: examples are great tutorials and anything we can point to, helps ;)
16:26:12 <mhmli> Call to undefined method TYPO3\CMS\Fluid\Core\ViewHelper\TemplateVariableContainer::assign()
16:27:36 <mhmli> could this be a conflict with the backslahes vs. underlines?
16:28:46 <Guest|71762> ext:fluidbackend cannot CRUD records, it's rather meant to be used for creating flux config files, right?
16:30:44 <NamelessCoder> correct, Guest|71762 - it's purpose is to write the information you enter into various destinations: json file, xml file, TS record, etc.
16:32:30 <Guest|71762> background: I'm looking for a way to easily create a backend module which allows sorting of records by drag n drop
16:33:33 <Guest|71762> i fear i have to do that "manually" via Jquery/fluid/extbase...
16:34:39 <Guest|71762> of course the module shall also be able to create new records, edit existing, remove existing... (maybe use ordinary TCA for these actions)
16:40:43 <anhadikal> getting Call to undefined method FluidTYPO3\\Flux\\Form\\Container\\Section::getStopInheritance() in flux/Classes/Provider/AbstractProvider.php on line 802
16:40:57 <anhadikal> with TYPO3 6.2 and latest TER flux
16:48:10 <anhadikal> okey there is already a bugfix in development branch, when it is merged to master?
16:54:23 <NamelessCoder> anhadikal we're collecting a few more bugfixes, then it's 7.0.1-time
16:54:54 <mhmli> claus, almost got it. do i need to instantiate anything to have access to templateVariableContainer ?
16:55:06 <mhmli> my viewhelper is extending \TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper
16:55:35 <mhmli> but it's telling me that the method assign is undefined
16:55:46 <anhadikal> NamelessCoder: what is the best solution now? should I just checkout development, cherry pick the commit?
16:57:08 <danilobuerger> mhmli see switch view helper in vhs as example on how to access templateVariableContainer
16:58:15 <danilobuerger> anhadikal interhitance fix needs some time to get into master... if you dont want to use development branch you will have to cherrry pick
16:58:56 <mhmli> namelesscoder identical to what i have.
16:59:06 <anhadikal> the problem is, that the site is not working anymore after update tp Typo3 6.2 and Flux 7.0
17:02:59 <NamelessCoder> anhadikal checkout development, the release cycles will be much shorter from now on. You can switch back in a week or so - with no breaking
17:04:26 <NamelessCoder> $this->templateVariableContainer is available in every viewhelper regardless of type, as long as you access it from the render() method or a method called after that
17:12:36 <Outdoorsman> Hello randomresults, I was speaking with NamelessCoder last night and he said to ping you about fluidbootstraptheme. Do you have an eta on when a stable release will be coming? I'm wanting to start developing with extensions that will be around for a while due to the number of sites I have.
17:13:39 <randomresult> @Outdoorsman i hope as soon as possible.
17:13:55 <randomresult> need some work to be done from NamelessCoder and then testing
17:14:12 <Outdoorsman> I guess I'm not sure how much things are still changing there or if it's getting close. I'm seriously itching to start using 6.2 and the FluidTYPO3 system right now.
17:15:08 <Outdoorsman> I have it installed and at least at the moment am not seeing errors. So it's really quite close then?
17:15:08 <Tjark> NamelessCoder can i already use fluidbackend within TYPO3 6.2 ?
17:15:39 <NamelessCoder> Tjark no - not yet, sorry.
17:15:41 <randomresult> you installed which one? fluidbootstraptheme? dev or master
17:16:24 <randomresult> and you havent insert a progressbar.
17:16:31 <randomresult> well, i think we are close to beta
17:16:44 <randomresult> and stable will only be someoptimisations for now
17:17:20 <randomresult> we will then add more elements - but this should not affect the old ones.
17:17:39 <Outdoorsman> thanks for the tips. I don't know if I will be able to avoid using useTYpoScriptsetting or not... since I'm coming from TS/Templavoila background.
17:19:38 <randomresult> you will see... TV and TS ... man i tell u... you will love Fluid.
17:20:03 <randomresult> anyway, i would be glad to get feedback. reported issues ... featurerequests and all...
17:21:46 <Outdoorsman> I'm looking forward to this. I've seriously lamented the lack of conditional options and programming logic in TV. I'm really looking forward to fluid. I just have yet to see how quickly I can implement a site using the new methods as time is money around here.
17:22:56 <NamelessCoder> Outdoorsman FluidTYPO3 exists because time is money ;)
17:23:04 <Outdoorsman> So anyway, here's a +1 or +10 for an up to date bootstrap extension that we can develop from in 6.2. Thanks again for the vision! I love it.
17:29:11 <cb|thomas> @danilobuerger Have already tried to get fluidpages run with pageoverlay?
17:29:11 <randomresult> we should add a bootstrapped version too !
17:29:11 <danilobuerger> cb|thomas you mean with localization?
17:29:11 <danilobuerger> randomresult well i am the wrong guy to talk about bootstrap since i hate it ;-)
17:29:11 <cb|thomas> Yes, in order to get form values of page configuration translated
17:29:11 <Outdoorsman> Yes TYPO3 is happening in the United States too. I'm a consultant for this site which has over 87,000 indexed pages on www.wallawalla.edu and 240,000 indexed pages on the root domain wallawalla.edu. That's the biggest implementation I'm aware of.
17:29:11 <cb|thomas> We talked about this a few days ago
17:29:12 <danilobuerger> cb|thomas i didnt get any further yet... i might get around to it this week... but to be save, please file a feature request here -> https://github.com/FluidTYPO3/flux/issues
17:57:21 <NamelessCoder> Denyerec maybe you are attempting to render an f:section inside a partial but did not specify both the partial AND section arguments...
17:57:30 <Denyerec> All I have done so far, is copy the MyContentElement.html in /Resources/Private/Templates/Content/ and rename it.
17:57:49 <NamelessCoder> it needs adjustment as well - namespace and viewhelper tags
18:21:51 <Denyerec> Flux View FluidTYPO3\Flux\View\ExposedTemplateView is able to read stored configuration from file /home/denyerec/htdocs/alba/typo3conf/ext/albatemplate/Resources/Private/Templates/Content/TeaserMenu.html
18:23:47 <Denyerec> NamelessCoder on the New content wizard I only see this message:
18:23:55 <NamelessCoder> if you put me on any other keyboard I will make 50% errors :/
18:23:55 <Denyerec> Flux View FluidTYPO3\Flux\View\ExposedTemplateView is able to read stored configuration from file /home/denyerec/htdocs/alba/typo3conf/ext/albatemplate/Resources/Private/Templates/Page/Page.html
18:24:07 <Denyerec> Wheras on the page overview page I see it mention my TeaserMenu
18:37:52 <NamelessCoder> but check: ext_localconf.php must have regsterProviderExtension call with Content as type. Static TS of your extension must be included and should set the plugin.tx_yourext.view.templateRootPath at the very least. DB compare should be run if you updated the site (fluidcontent cache tables need writing).
19:06:34 <tom_at> hey, i have a problem with flux:field.select items="". in flux 6.0 i this worked: <flux:flexform.field.select ... default="0.75" items="{ 0: {0: '0', 1: 'Source format'}, 1: {0: '0.75', 1: '4:3 Landscape'}}" />
19:07:00 <tom_at> now with the new flux it isn't, how should i define the items?
19:09:38 <NamelessCoder> tom_at when ¥ou say doesn't work, do you mean an error, incorrect options, no options, or something else entirely?
19:12:08 <tom_at> no error, the values are incorrect in the select field, i get as select options: "0, 0.75" but i want "Source format, 4:3 Landscape"
19:12:27 <tom_at> an as value for the field the factor, exp 0.75
19:12:45 <NamelessCoder> reverse the order of label and value ;)
19:15:50 <NamelessCoder> if content, the fields are translated along with the element itself and will only be used in the localized version if it exists - but will then override all values
19:16:08 <NamelessCoder> there's a chance danilobuerger and I may get this done over the weekend
19:48:52 <Denyerec> Where does one put an extended description for an FCE?
19:49:00 <Denyerec> just throw in a description="" attribute ?
19:49:21 <danilobuerger> fx if you had a template <flux:form wizardTab="Heimspiel" id="absolute"> then you would put the name in flux.absolute and the description in flux.absolute.description
19:53:43 <soee> is it possible to hide this Page Configuration tab until Layout is selected ?
19:54:02 <danilobuerger> ? if its hidden you wont be able to select the layout?
19:55:06 <danilobuerger> ah i see what you mean, sorry we recently split those into 2 tabs
19:55:29 <danilobuerger> i dont know if its possible, but it will most likely require some ancient typo3 voodoo magic... thats NamelessCoder area of expertise ;)
20:09:01 <Denyerec> I take it a recommendation would be to keep icons within the same dimensions as the page.gif for consistencies sake ?
20:10:01 <danilobuerger> 18*16 or something like that i think
20:15:34 <Denyerec> So less like the page template thumbnails
20:15:39 <Denyerec> and more just an abstract icon
20:45:53 * randomresult sometimes wonders why he is not here when the channel is on fire... ?!?
20:49:38 <gernot_h> hi! i just copied 2 typo3 6.1 flux 1 installations with flux to localhost. when i got to installtool i got this errors: https://gist.github.com/aphex13/9899367
20:50:54 <danilobuerger> hey gernot_h so does the file /var/www/html/typo3conf/ext/flux/Classes/Utility/Version.php exist?
22:27:37 <Denyerec> I'm trying to establish what the best approach is.
22:27:51 <danilobuerger> ok because i had a similar decision to make a few days ago
22:28:14 <danilobuerger> i went with the content element in sysfolder and reference approach..
22:28:23 <Denyerec> Ok well at least I'm not insane
22:28:33 <Denyerec> They want to generate google maps for their addresses though.
22:28:46 <Denyerec> SO I thought... maybe... using tt_address would kill birds with the same stone
22:29:00 <danilobuerger> you could also just use a custom content element
22:29:06 <Denyerec> Could I pull a tt_address record into a fluid template ?
22:29:41 <danilobuerger> the reason i used CEs in the sysfolder & referenced was because in 80% the CEs should be there and on certain pages they shouldnt...
22:29:49 <danilobuerger> so i couldnt have a general rule
22:30:12 <Denyerec> well... could the CE's grab their data from tt_address records ?
22:36:53 <Denyerec> you've then got the whole "Man that's gonna be a lot of effort" factor.
22:37:02 <Denyerec> Especially as I'm making no money on this site.
22:37:11 <Denyerec> Tho TBH I never make any money anyway, so that's not really unusual :)
22:37:12 <danilobuerger> in that case just do it manually ;-)
22:37:22 <Denyerec> Then I get bogged down in wanting to do things the right way.
22:37:29 <Denyerec> As I get itchy when I hardcode stuff :)
22:37:59 <Denyerec> I thought I'd look in AbstractContentViewHelper->getContentRecords
22:38:03 <danilobuerger> well you dont need to hardcode it… just do a custom content element.. one of its fields is the link to google maps and then render it
22:38:09 <Denyerec> and I start seeing things like TSFE and LOAD_REGISTER
22:38:16 <Denyerec> then realise I know nothing about Typo3 extension development ;)
22:38:46 <danilobuerger> AbstractContentViewHelper is obscure ;-)
22:38:59 <Denyerec> Well I tried to think of a VH that would pull typo content records
22:42:02 <danilobuerger> well it would probably work for tt_address
22:42:10 <danilobuerger> but thats not what i intended it for ;-)
22:43:18 <danilobuerger> if you really want to go down the tt_address route, you should write your own view helper or content controller (i would go for the view helper) .. but i am telling you its so not worth it
22:49:57 <Denyerec> (Seirously, I'mnot going to write it, but I AM curious)
22:53:05 <danilobuerger> alright, if you want something from the database and you dont have a repository (like the case of tt_address) take a look at fluidcontent ConfigurationService getAllRootTypoScriptTemplates ... this shows you best practice how its done
23:22:21 <Outdoorsman> randomresults I just got this flux error... The template group "bootstraptheme" has been configured to use the templateRootPath "EXT:bootstraptheme/Resources/Private/Templates/Page/" but this directory does not exist.