09:09:33 <batjony> mrboe: I just made a fresh install of typo3, the dev versions of the main fedext, clear all caches, typo3temp, but still I do not see both tabs: Grid and Bootstrap when I create a new CE
09:10:02 <mrboe> @randomresult do you have any idea
09:10:04 <harwin> Hi, we have build a website with TYPO3 6.0 in the past with fluid and flux, and we used flux for the page templates. Is it possible to migrate this to 6.2 with the new flux?
09:10:09 <batjony> are you sure, that this tabs are not comming for some other fed extension
09:10:49 <batjony> currently I have: flux, vhs, fluidpages, fluidcontent, fluidbootstraptheme, builder
10:44:23 <mrboe> i think it depends on the project
10:47:02 <mrboe> @xaver perhabs ypu could be so kind and change the version in FBT - i think i wouldn't be the best choice if i do that - or randomresult could do?
11:15:41 <batjony> i think you can assume fixing the version in ext_emconf.php as a hotfix, so fixing it at development then merge back to v1.0, and set a tag 1.0.1
11:17:16 <batjony> or create a fix branch from v1.0, then make the fix, then merge it back to both v1.0 and development :)
11:18:01 <batjony> history rewriting is not a good practice
11:18:14 <batjony> since other guys may already pulled it
11:23:32 <batjony> so maybe just fix it directly in branch "v1.0" and then merge it back to "developmen"
11:31:44 <batjony> btw i am wondeting why if I skip the inclusion of the bootstrap static templates in the root page template - FBT does not work
11:32:02 <batjony> i see in ext_tables.php \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile($_EXTKEY, 'Configuration/TypoScript', 'Bootstrap Theme');
11:32:12 <batjony> and \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile($_EXTKEY, 'Configuration/TypoScript/Settings', 'Bootstrap Theme Settings');
11:32:43 <batjony> which should include the typoscript templates automatically when installing the FBT extension
11:39:39 <mhmli> Hi all. Are @bjo3rnf or @outdoorsman in?
11:41:04 <mhmli> I have a question relating to the use of the titleFields attribute on v:page.menu, as discussed on https://github.com/FluidTYPO3/vhs/issues/555
11:42:34 <mhmli> @outdoorsman's answer from 1st May works fine for a single-level menu, but I'd like to know whether it's essential in this instance to then manually build the nested submenus. as i can't see a way to specify use of {page.linktext} instead of {page.title} through automatic generation.
11:58:24 <xaver> batjony: added it in templates static stuff
14:34:09 <xaver> to replace normal content elements of T3?
14:41:44 <Guest|21632> no, I mean the normal fluidcontent, I place my elements into a "insert records" element on a site and want to change their layout with the field layout of "insert records"
14:43:37 <fger> i cannot change the RTE field configuration via attribute defaultExtras in flux-vh (flux develop branch)
14:43:51 <fger> maybe a bug ? does anyone have it working ?
15:00:07 <xaver> NamelessCoder: can Guest|21632 access the record
15:04:57 <xaver> NamelessCoder: maybe we should make the uid accessible and if you want a record you can load it via vhs.
15:05:40 <NamelessCoder> content.get works but that's not the issue - the issue is that the child record doesn't know the parent record
15:08:58 <mhmli> hi again! i'm trying to use the page menu view helper but when i build a menu using a secondary language, and a page isn't available in that language, it always falls back to use the page title and slug from the standard language. i've checked the docs but can't find a way to stop this. the functionality is like hideNotTranslated in v:page.language
15:09:19 <mhmli> am i missing something or is this not possible?
15:10:46 <NamelessCoder> mhmli page menu fetching should respect your language settings in TYPO3, the page properties and whichever default language you configured
15:11:38 <NamelessCoder> if the menu contains unexpected output a corresponding TS menu would also contain the same - I think you need to look into your language setup for fallback behavior
15:11:50 <mhmli> @namelessCoder that's what i'd thought, but config.sys_language_mode = strict which is working fine for the content. just not for the v:page.menu
15:12:46 <mhmli> the topic is listed at http://fluidtypo3.org/search.html?q=page+menu+translated at 20140204 15:56:08 but the linked page doesn't contain the content of that discussion…
15:13:21 <NamelessCoder> yeah for some reason the IRC log indexer I wrote builds bad/skewed URLs
15:15:04 <mhmli> hm. and google site-specific search doesn't find anything for the former question "would I need to realize parameters such as hideNotTranslated="1" myself?"
15:16:43 <NamelessCoder> you may want to ask bjo3rn about this behavior
15:23:43 <mhmli> @NamelessCoder You're right about the TS. I've replaced the Partial with a TS script to generate the menu and the same error occurs. So I guess it's a non-VHS issue.
15:24:17 <NamelessCoder> mhmli if in doubt, bet that I am right ;)
15:24:25 <NamelessCoder> I have a pretty good track record
15:26:08 <NamelessCoder> you could try to search the core bug tracker, there HAS to be something about it there
15:47:16 <mhmli> @NamelessCoder Perhaps it would work better if the content editor hadn't checked "Seite anzeigen, auch wenn keine Übersetzung vorhanden ist". #FFS
18:19:31 <bjo3rn> in your face, cyclomatic complexity ^^
18:19:49 <NamelessCoder> but if you want title to be more weighty than nav_title you must set titleFields="title,nav_title" since default is that nav title is more important if set
18:20:14 <NamelessCoder> beware any related language rendering bugs; VHS will only know what the record contains *after* it's delivered from TYPO3
18:21:02 <NamelessCoder> high cyclo is like a built-in mental capacity stress test
18:30:14 <mhmli> re. priority, thanks, got it. patched but the problem still occurs. it seems that if i overwrite the nav_title in language 2 then it takes. if i then empty it again, the field l18n_diffsource in the pages_language_overlay table contains the nav_title from the page in language 0 again
18:30:25 <mhmli> bit complex but that sounds like a core bug, yes?
18:31:17 <NamelessCoder> from what I understand about it yes, that would be some sort of inter-language inconsistency
18:32:28 <mhmli> ok. i'll look into it further next week as this is in 6.1.10 and so may be fixed in 6.2.x.
18:32:35 <mhmli> thanks so much for your help, as always
18:34:45 <Outdoorsman> Interesting... after updating all dev versions of fluidtypo3 extensions I suddenly have this phrase showing up all over the place...
18:34:56 <Outdoorsman> This is before a CE... <{v:variable.get(name: 'content.settings.container.types.{record.CType}') -> v:or(alternative: content.settings.container.types.default}>
18:35:09 <Outdoorsman> This is after the CE... v:or(alternative: content.settings.container.types.default}>
18:35:28 <NamelessCoder> might be a merge problem in the layout
18:35:32 <NamelessCoder> there was a conflict there
18:35:33 <Outdoorsman> Looks like vhs issue. I'm suspecting it came from fluidcontent_core which I'm just trying for the first time.
18:36:31 <Outdoorsman> Looks like a missing "<" to me. I will try doing another pull
23:42:57 <ltrebing> Hmm, http://fluidtypo3.org/documentation/templating-manual/installation/unattended-installation.html states “A Provider Extension is also capable of loading TypoScript without requiring the static TypoScript to be included manually”
23:43:28 <ltrebing> and refers to http://fluidtypo3.org/documentation/templating-manual/introduction/configuration-usage.html for a detailed explanation, but on that page I find nothing about automatic TS inclusion