10:03:21 <denis_droid> What is the correct way to link to the public folder of the extension inside the ts setup?
10:09:55 <denis_droid> Is the section named "<f:section name="MetaTags">" a special section or how do I include it correctly? In the end I want to define some content of the head in a fluid template.
10:23:06 <batjony> bjo3rn: i found where is the issue, about v:page.resources.fal from the discussion yesterday :)
10:23:28 <batjony> v:page.resources.fal doesnt not work in a page layout, only it works in a page template
10:24:44 <batjony> and yes - the other helper v:content.resources.fal could be also used but you have to specify the "table" property
10:30:28 <denis_droid> danilobuerger: Could you tell me the right place to use this example partial: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=6&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=f4a1b1516be74eff5e15641fdaa18d49 ? Where do I place the partials containing meta information correctly in the layout?
10:32:10 <danilobuerger> do you want to use them in your page layout denis_droid ?
10:33:41 <denis_droid> Well I'm not quite sure where to put the meta tags in the fluid templating context. Should I do it in the typoscript setup or is it better to put it in the page layout. I'm a bit confused about the right way to do it.
10:34:16 <danilobuerger> it depends on what you want to achieve... what is it exactly you are trying to do?
10:36:12 <denis_droid> Ok. For example adding the favicons. Not just the default one but also the apple touch icons. The first thing I thought was something like that: https://gist.github.com/DenisMir/1e1bbaea4be86590e06f
10:37:03 <denis_droid> But what is the correct way to link to the icons in the public folder of the extension. At the moment I'm getting rendered: EXT:….
10:38:46 <danilobuerger> ok so this only applies if you are using the page renderer (which seeing your TS you are): if you want to share the meta tag across all your page templates you can put the v:page.header.meta in your page layout, if you just want the meta tag in one page template you can put it in your page template
10:40:20 <denis_droid> Ok as a noob I have to ask what does "page renderer" mean? Which other renderes exist. :-)
10:41:03 <denis_droid> So the vhs meta tag helpers can be placed wherever I want in the layout and don't have to exist in one special section or sth like that.
10:41:32 <danilobuerger> its either the page renderer or you are completely on your own... with config.disableAllHeaderCode... i always set that to TRUE to disable the page renderer, but thats just my preference...
10:42:14 <danilobuerger> IF you are using the page renderer, the meta tag helper can be placed wherever you like. they will always end up in the right place _IF_ they are read
10:42:35 <denis_droid> Ok understood. What would be the way to render the meta tags on your own with config.disableAllHeaderCode set to true?
10:43:30 <danilobuerger> well you write the <head> html yourself... so you would put them inside your <head>..</head> code and for a meta tag probably without the view helper just write <meta .... />
10:47:17 <batjony> guys, i have extended the table "pages" with some additional fields, and now i have now a field "related_pages" which is actually mm relation to the pages and everything is working fine in the backend, so for example if you edit page X, you can add some related pages page Y, page Z....
10:47:41 <batjony> and i am wondering how can I render the related pages for particular page in a page template ?
10:48:02 <danilobuerger> you mean render a page inside a page ?
10:49:30 <batjony> the field "related_pages" is an extended property of a page and i have a page template, where I render some of the page properties
10:50:11 <batjony> and i dont have any idea how to get this related pages in this template
10:50:15 <denis_droid> danilobuerger: Ah ok the head rendering gets disabled completely with that. So I'm completely free. :-)
10:50:28 <danilobuerger> batjony so again you want to render a page template inside another page template?
10:51:06 <danilobuerger> denis_droid exactly, so the advantage is that oyu have complete control, the disadvantage is that you loose the features of the page renderer to collect css / js / meta / etc..
10:51:55 <denis_droid> ok understood so compression and combining of css/js is on your own
10:52:22 <danilobuerger> well for that you can use v:asset
10:52:28 <denis_droid> And extensions like seo basics won't work since the rendering of the head is now gone
10:59:10 <danilobuerger> you need to resolve your relation ship
10:59:24 <danilobuerger> and that you should not try todo in fluid but a proper controller
11:00:23 <danilobuerger> for example in your PageController
11:00:36 <batjony> danilobuerger: you are sure that there is no such helper, because for example for FAL files where again another mm table is involved, there is a helper like v:page.resources.fal which can be used ?
11:01:58 <danilobuerger> no i am not sure that no such view helper exists for your use case, but i guess i am 99% sure
11:03:31 <batjony> danilobuerger: and do you have idea how can I do this in PageController
11:04:02 <batjony> the relations work fine in the Backend, my extended TCA is OK
11:04:52 <danilobuerger> resolve the relationship inside your PageControllers action and assign the pids to a variable
11:06:50 <batjony> i mean this "relationship resolve", do you know is there some internal typo3 class/methods which I can use, or I should create my own query
11:07:33 <danilobuerger> you could do it like v:resource.* view helpers do
11:16:31 <batjony> danilobuerger: do you know if its possible automatically to attach particular page template to specific doktype
11:16:57 <batjony> so for example pages with doktype 197 to have page template X
11:18:22 <danilobuerger> batjony yes for code example look at fluidpages Raw template feature
11:20:05 <batjony> what is this "fluidpages Raw template feature", could you point me with some link
11:38:05 <gbod> fger: Hint - If you prefix your flux field names with 'settings." they're available automagically in you're controller via $this->settings
11:39:44 <fger> ok, but 1 thing: if i have a ContentController in my provider extension, will this replace the ContentController, that is shipped with the fluidcontent extension ?
11:41:05 <batjony> gbod: https://github.com/FluidTYPO3/fluidpages/blob/development/Configuration/TypoScript/setup.txt i still cant catch it, how can I set automatically specific page template to specific doktype
11:41:47 <fger> gbod: i saw, all the additional stuff is put into the abstractController.. thx
12:20:49 <fger> hmm... so there is no API for resolving sys_categories related to a cObj in TYPO3 6.2 ... strange
12:21:32 <danilobuerger> fger just the other way around
12:24:41 <fger> yeah, just thought there is a core/extbase model already present
12:29:07 <NamelessCoder> fger \TYPO3\CMS\Core\Category\Collection\CategoryCollection and \TYPO3\CMS\Extbase\Domain\Repository\CategoryRepository. The optimal way of getting these is to use a proper domain model for the source side of your relation, then have proper TCA pointing to sys_category (or using the "make table categorizable" API thingie). The object property mapper then takes care of it.
12:31:08 <NamelessCoder> sys_category.items column in TCA will contain the "consumers" of categories.
12:33:00 <fger> ok thx - seems to be the most clean way to get this yes
12:53:37 <batjony> NamelessCoder: i have extended the table PAGES with a field "related_pages" where we have a MM relation, so for example for page X could be set related pages: page Y, page Z......, which works fine in the backend, now I have a page template, which renders the page properties
12:54:03 <batjony> is there some helper which can be used to render the related page records for particular page record inside a page template
12:57:29 <NamelessCoder> batjony please ask such questions to the whole channel, that way 1) you don't unnecessarily ping me with notifications and 2) people don't wait for me to answer your Qs.
12:58:18 <NamelessCoder> you can trust what danilobuerger tells you
12:58:25 <batjony> no sense to make something custom, if it already exist..
13:00:53 <batjony> on my previous question for "how can I assign page template for specific doktype", the danilobuerger's answer was just the link https://github.com/FluidTYPO3/fluidpages so I am sceptical about his answers...
13:01:35 <batjony> and said something about raw templates, info which I cant find on https://github.com/FluidTYPO3/fluidpages
13:02:18 <danilobuerger> why should i help you more in my own free time if you are being so rude ?
13:02:29 <danilobuerger> go read the source code of fluidpages, the information you seek is in there
13:02:33 <batjony> then better not to answer anything
13:02:44 <NamelessCoder> batjony there are numerous ways you could achieve that - one way is how fluidpages does it.
13:02:50 <batjony> of course everybody knows the link for fluidpages https://github.com/FluidTYPO3/fluidpages
13:03:01 <NamelessCoder> hint: the "raw template" doktype added by fluidpages
13:03:02 <danilobuerger> so go and look at the source code
13:03:41 <NamelessCoder> but you could also achieve the same by using oldschool typoscript with conditions
13:04:31 <NamelessCoder> ...but in both cases since this is your custom typeNum, it's outside our scope of features.
13:06:04 <danilobuerger> and in any case if people take their personal time and answer questions in here you should be grateful for each answer and say thanks and not be rude
13:07:20 <batjony> danilobuerger: i am pretty sure everybody here knows the github link of fluidpages, so I cant thank you for this, sorry
13:08:22 <danilobuerger> that wasnt my only answer to you as this wasnt your only question
13:09:21 <danilobuerger> i also told you to look at the raw template feature
13:09:26 <NamelessCoder> well the feature is undocumented at this point so it's not really obvious. On the other hand, it's only a dozen lines total so it should be fairly transparent.
13:10:01 <NamelessCoder> as always: we greatly appreciate contributions to documentation, just as much as contributions to code!
13:12:48 <batjony> NamelessCoder: btw about the discussion from yesterday , i found why v:page.resources.fal doesnt work
13:13:10 <batjony> because it was in a page layout
13:13:16 <batjony> seems that works only in page templates
13:14:17 <batjony> which is actually not a issue, so just to mention it... :)
13:14:52 <NamelessCoder> should work fine in both places. You maybe forgot to import the vhs namespace and it was ignored.
13:15:05 <Momodedf> Is there something wrong with this PR https://github.com/FluidTYPO3/fluidcontent_core/pull/99 or is it just because people are occupied elsewhere ?
13:16:07 <Momodedf> I'm new to open source and contributing, any advice about whats is good or never to be done is welcome
13:16:28 <batjony> NamelessCoder: no, already checked it, namespace are fine, the variables are debugged.....
13:17:03 <mrboe> @soee it there anything new about the icons?
13:17:29 <batjony> but anyway like I said its not an issue for me, i am just sharing some info.. :)
13:27:33 <Akii> why does the json.encode VH return an empty object if given an empty array?
13:30:59 <soee> mrboe: can't tell till the next week, my colegue is working on them but this week hes on vacation so i have to wait to get info
14:07:27 <batjony> Does the @inject repository way works in a PageController
14:22:51 <fger> we had the issue yesterday, that with flux 7.1.0 / fluidcontent latest the new content element wizard tabs were gone
14:23:20 <fger> normally all extbase related caching data goes to a redis backend, but i discovered some 15 entries in the db
14:23:25 <danilobuerger> fger did you try with latest flux already and did you change usage of wizardTab which is deprecated?
14:23:40 <fger> after clearing that db table the wizard tabs worked again
14:24:18 <fger> danilo: no as we dont have time to intensively test the latest flux version on stability and bugs and flux sits in a central place affecting nearly all authoring actions
14:24:45 <fger> therefore atm never touch the running system, which works fine for all standard tcemain actions
14:24:56 <fger> the website has about 300 authors working with it
14:25:17 <danilobuerger> ok, well if it works now everything is good, but as i said remember that the wizardTab is deprecated and was replaced with the options argument
14:26:27 <fger> yeah, we got flux working in v7.1.latest with the options-array
14:27:00 <fger> just was wondering if flux has any caching mechanism bypassing the caching-framework and writing directly into DB tables cf_extbase_object or sth
14:32:18 <fger> hmm yeah will do that , was just wondering about the 15 entries in cf_extbase_object table after truncating that
14:32:27 <fger> everything should be persisted in redis
14:33:41 <fger> the cf_fluidcontent is in redis already i saw
14:33:51 <NamelessCoder> few things... you should set this value in AdditionalConfiguration.php to properly protect it from overwrites and allow you to set line-by-line parameters
14:35:06 <denis_droid> Is it possible to create a extension dependency which links to a github repository?
14:35:31 <NamelessCoder> and if after setting the backend here, and the cache entries reappear: it's likely that something is creating class instances at some point before the core cache configurations are loaded
14:36:06 <fger> claus: yes that's what i thought too, thats why i was asking if you know/suspect any process inside flux/fluidcontent that could do so
14:36:31 <fger> the caches are set in AdditionalConfiguration.php
14:37:04 <NamelessCoder> hmm, many many possible causes
14:37:28 <NamelessCoder> eID might, if they happen before core cache warmup
14:39:40 <NamelessCoder> with the exception of unit tests if executed without bootstrapping
14:39:51 <NamelessCoder> but I'm assuming you don't run those on your production site ;)
14:39:55 <batjony> what is the best way to achive exactly if (!empty($var)) in Fluid ?
14:40:09 <denis_droid> gbod: Ok but you have to use composer to install right? Or how is the installation workflow for the extension.
14:40:36 <gbod> denis_droid: yes, you have to use composer
14:41:11 <denis_droid> gbod: Ok so no automatic dependency resolution when installing the plugin with a github dependency via the EM
14:41:53 <NamelessCoder> denis_droid depends on the version constraints that apply to the branch you attempt to install
14:42:13 <NamelessCoder> on development: no, those dependencies cannot be resolved to currently published TER extensions and therefore can't be satisfied
14:42:30 <NamelessCoder> on master: sure, but EM will then download TER versions of the other exts
14:42:44 <NamelessCoder> if you want all dependencies to come from github, composer is your tool
14:44:21 <denis_droid> NamelessCoder: Ok fine. Well I just wanted to make some changes to an extension which is available on github. The changes can't be merged back to the original extension. And now it would be useful to be able to have my forked extension as a dependency in some custom extension.
14:44:40 <thyri0n> Did you ever come upon the issue that the backend page is empty when trying to edit content inside a fluidcontent FCE?
14:45:08 <NamelessCoder> denis_droid this sounds to me like you're taking a fairly dangerous route you might be able to avoid
14:45:19 <NamelessCoder> what's the purpose of the change you made and why can it not be merged back?
14:46:02 <NamelessCoder> thyri0n you'll have a proper error message hidden away in logs, either in typo3, in apache error logs or your system's logs
14:46:25 <thyri0n> Oh yeah right, I'll see what I can get from those
14:47:17 <denis_droid> NamelessCoder: Well at the moment I'm just thinking about different solutions. I know that this route is not really the way it should work. Well the problem is that seo_basics depends on realurl but works as well with cooluri. But realurl conflicts with cooluri. With this kind of dependency setup it is not possible to use seo_basics together with cooluri :-)
14:48:36 <thyri0n> Although the typo3 site which is affected by the issue is hosted on some managed hosting account, so I can't really say if we got access to all the logs we need
14:50:10 <NamelessCoder> denis_droid then the correct approach would be to let EXT:seo_basics suggest both realurl and cooluri and let the integrator choose - I would try to get that patch in.
14:50:41 <NamelessCoder> thyri0n if all else fails: TYPO3_CONF_VARS.SYS.displayErrors in install tool
14:51:34 <denis_droid> NamelessCoder: Ok fine so the "suggests" in the ext_emconf would be the way to go. Sounds good.
14:52:22 <NamelessCoder> if it's not a real dependency - and it probably isn't fatally dependent on realurl - then yep, suggest along with alternatives
14:52:52 <denis_droid> NamelessCoder: Yeah fine. I will try to get that one in.
15:03:16 <thyri0n> Figures we got the error wrong, it's the other way around - fluidcontent FCE's are perfectly editable, standard content elements are not
15:04:47 <NamelessCoder> just in case: make sure you use a recent core version, there's a potentially related bug fix in 6.2.5+
15:14:28 <denis_droid> NamelessCoder: Do you know why there are two "suggests" properties generated in the config file. One inside "constraints" and one on the root level?
15:17:27 <denis_droid> NamelessCoder: Ok here is the issue: https://forge.typo3.org/issues/42824
16:29:12 <gbod> denis_droid: Well, you can render it via vhs:page:menu but that way you have to built the xml structure basivly by yourself, so the existing extension based approach seems to be easier.
16:36:26 <gbod> The censor must have been fallen asleep that day.
16:45:53 <NamelessCoder> we do still get some CSC related questions - but let's hope those go away completely ;)
17:33:47 <fger> guys, can i remove the csc static template when using fluidcontent/flux/fluidpages in latest TER versions ? or will frontend rendering crash on some details ?