IRC logs

20141117

Logs from channel #fedext on freenode - our official support channel.

IRC log range: 20141117*

20141117

  • 09:06:03 <batjony> hello fed-ers
  • 09:08:22 <batjony> when you have a custom fluid content element and edit it, there is a select box "Fluid Content type", which can be set to value "Fluid Content type", which breaks the site with message error
  • 09:08:32 <batjony> " Template could not be loaded. I tried "/home/momchil/www/html/site/typo3conf/ext/fluidcontent/Resources/Private/Templates/Content/Default.html"
  • 09:09:54 <batjony> I know there is no sense the client to set it like that, but is there a way to preserve it, for example to remove this option and the FE editor would be not able to break the FE ?
  • 09:48:32 <macro11> good morning, i've problem with me fluidcontent fce's displaying them in a wizardTab. i've tried to use the new options option, but no difference: options="{group: 'Raster Elemente', icon: 'Icons/layout-50-50.png'}"
  • 09:48:54 <macro11> typo3 6.2.6 -> all extensions to latest ter versions
  • 09:50:00 <macro11> can anyone give me a hint where to search next?
  • 10:17:06 <jmverges> good morning mates, I'm having a problem, I don't know if you also saw it. The first space in a grid into a grid, for example, FluidCE Three columns, has not t3-page-ce-dropzone
  • 10:19:14 <mrboe> @jmverges it works when you drop the item on the right side
  • 10:19:23 <mrboe> and then pull it into the left
  • 10:19:35 <mrboe> think this is a CSS problem
  • 10:19:41 <jmverges> you are talking about columns, don't you?
  • 10:19:56 <mrboe> yes
  • 10:20:06 <jmverges> the problem for me is that right now I have other element, that is not a Three columns
  • 10:20:12 <jmverges> and only have a Grid space
  • 10:20:46 <jmverges> do you think that is CSS?
  • 10:21:04 <mrboe> i have not checked it
  • 10:21:13 <mrboe> but it looks like a css problem for me
  • 10:21:14 <jmverges> okey, I will take a look later
  • 10:21:52 <mrboe> because the dropzone is shown when a content is in there
  • 10:27:51 <erredeco> Hi, I'm facing some problems with FCE on TYPO3 6.2.5 and Flux 7.1.0, Fluidcontent 4.0.0
  • 10:28:21 <erredeco> The first problem I faced was this: https://github.com/FluidTYPO3/flux/issues/686
  • 10:28:30 <erredeco> but I managed to solve it as suggested :)
  • 10:29:38 <erredeco> the second problem: after creating the FCE, I don't see the fields I see only:
  • 10:29:39 <erredeco> Plugin Options
  • 10:29:39 <erredeco> DEF:
  • 10:29:39 <erredeco> The Title:
  • 10:31:35 <erredeco> no other field is shown :S :S :S :S
  • 11:11:18 <erredeco> please, help :)
  • 11:17:46 <NamelessCoder> erredeco you may want to upgrade flux etc.
  • 11:54:50 <macro11> @erredeco i have the same problem, do you delete the wizardTab and icon attribute when you use the options attribute?
  • 11:56:41 <macro11> @all can i use v:extension.path.resources in array? options="{group: 'Raster Elemente', icon: '{v:extension.path.resources(path: \"Icons/layout-50-50.png\")}"
  • 11:56:46 <macro11> seems not to work :(
  • 11:59:07 <mrboe> <flux:form id="accordion" options="{useTypoScript: 0, group: 'Bootstrap', Fluidcontent: {sorting: 300}, icon: '{f:uri.resource(path: \'Icons/bootstrap/glyphicons_113_justify.png\')}'}">
  • 12:00:14 <macro11> thanks mrboe, will try
  • 12:00:24 <mrboe> welcome
  • 12:37:28 <NamelessCoder> Snake Plissken agrees with your escaping.
  • 12:38:18 <Akii> gta v ready?
  • 12:38:23 <Akii> or are you screaming :D
  • 12:38:29 <NamelessCoder> 11:22 to go
  • 12:38:36 <NamelessCoder> but I bet I will be screaming
  • 12:38:46 <NamelessCoder> it downloaded 2g, total size reported as 44g
  • 12:39:01 <Akii> well, cya in a week or two
  • 12:39:02 <Akii> ^^
  • 12:57:14 <rosieres> is there any vh for the treeLevel?
  • 13:00:32 <rosieres> or a possiblity to build a condition that is true to a certain treeLevel?
  • 13:52:36 <Guest|35541> Hi
  • 13:52:39 <Guest|35541> flux:flexform.field.multiRelation
  • 13:53:02 <Guest|35541> is this implemented in flux Version?
  • 14:14:05 <rosieres> Guest|35542 https://fluidtypo3.org/viewhelpers/flux/master/Field/RelationViewHelper.html -> multiple="1" -> is in Master .... dive the versions through to see where it disappears
  • 14:14:18 <rosieres> Guest|35541 see above
  • 14:22:17 <Guest|35541> thx i will read and test it
  • 14:32:43 <Guest|35541> <flux:form.object name="slideNews" label="Slide News">
  • 14:32:43 <Guest|35541> <flux:field.relation table="tx_news_domain_model_news" maxItems="1" name="news" label="News" /></flux:form.object>
  • 14:34:12 <Guest|35541> if i use this i get a select box, but i want to use something like the wizzard to select a news from a directory
  • 14:34:49 <Guest|35541> because if i have 1000 or more news ist difficult to select the new
  • 15:15:25 <erredeco> I upgraded all version of flux
  • 15:15:32 <erredeco> fluidpages, vhs, fluidcontent
  • 15:16:06 <erredeco> now I have this problem: In a multisite enviroment, it seems that the templateRootpath cannot be changed
  • 15:19:35 <rosieres> erredeco -> templateRootPaths !
  • 15:20:06 <erredeco> yes, of course
  • 15:20:15 <erredeco> I mean templateRootPaths
  • 15:21:21 <rosieres> templateRootPaths is nothing from fluidtypo3 - it core stuff and should be working. Check TSOB if you have any TS issues
  • 15:21:38 <erredeco> sorry
  • 15:21:47 <erredeco> I'm confused
  • 15:21:53 <rosieres> why
  • 15:21:55 <erredeco> I'll try to explain
  • 15:22:10 <erredeco> I have a pagetree configuration like this
  • 15:23:17 <erredeco> [ID=1] Home
  • 15:23:17 <erredeco> [ID=8] Home 2
  • 15:23:17 <erredeco> [ID=9] Home 3
  • 15:23:17 <erredeco> [ID=10] Home 4
  • 15:23:47 <erredeco> Each of this pages are set as root pages, have a domain record and a Typoscript root template
  • 15:24:44 <erredeco> the extension I use to provide the FE is called bhsiteconf
  • 15:26:32 <erredeco> on each site I want to use a different templateRootPath
  • 15:26:35 <rosieres> BTW: did you wipe the reflection caches?
  • 15:26:41 <erredeco> how?
  • 15:26:57 <rosieres> installtool -> clearAllCaches
  • 15:28:00 <erredeco> yes. but with no results
  • 15:28:35 <erredeco> in the BE it seems that in the layout tab the templates listed are taken from the 1st domain
  • 15:28:38 <erredeco> ID=1
  • 15:28:42 <erredeco> ??!?!?
  • 15:29:13 <rosieres> What does the TSOB on ID=8 say?
  • 15:31:02 <erredeco> Let's say that the templates for the ID=1 are in
  • 15:31:26 <erredeco> plugin.tx_bhsiteconf.view.templateRootPath = EXT:bhsiteconf/Resources/Private/Templates/
  • 15:31:33 <erredeco> while for ID=8
  • 15:31:43 <erredeco> plugin.tx_bhsiteconf.view.templateRootPath = EXT:bhsiteconf/Resources/Private/Templates-edetail/
  • 15:31:50 <rosieres> you have been advised to use templateRootPaths
  • 15:32:24 <erredeco> Sorry I don't understand
  • 15:32:42 <rosieres> plugin.tx_bhsiteconf.view.templateRootPaths instead of plugin.tx_bhsiteconf.view.templateRootPath
  • 15:33:00 <rosieres> the (s) makes the diffderence
  • 15:33:59 <erredeco> :S
  • 15:34:02 <rosieres> Check this -> http://www.dennislizarzaburu.de/blogs/16/Mehrere+Pfade+f%C3%BCr+Templates,+Layouts+und+Partials+in+Typo3+6.2
  • 15:34:59 <erredeco> but this is the fallback syntax
  • 15:35:11 <rosieres> yep
  • 15:36:01 <erredeco> I don't need a fallback...
  • 15:36:49 <erredeco> I want to specify a different path because each domain has its own templates
  • 15:37:59 <erredeco> btw with fluidpages 3.0.0 everything worked
  • 15:38:07 <rosieres> afaik templateRootpath is deprecated - and for your inheritance issue why dont you wipe the ts with a pagesettings - options - clear ts
  • 15:38:10 <erredeco> I had problem after an update to the latest TER version
  • 15:38:48 <rosieres> then every inheritance is gone
  • 15:39:08 <erredeco> each page have TS template with
  • 15:39:08 <erredeco> Constants Setup
  • 15:39:21 <erredeco> sorry... with clear constants, clear setup
  • 15:39:24 <erredeco> checked
  • 15:39:52 <rosieres> So normally any inheritance should be avoided
  • 15:40:39 <rosieres> if not, check TSOB if it throws any errors and look if yout contant is in tsob present
  • 15:42:08 <rosieres> TSOB -> Web -> Template -> Rootpage (id=8 in you case) -> Submodule: Typoscript Object Browser -> SubSub Module Constants -> then traverse the tree for your things
  • 15:42:08 <erredeco> on TSOB no typoscript error
  • 15:43:10 <oschulz> hey volks, i made an proof of concept to render a one pager frontend. in my backend i have serveral single pages with individual page layouts ... i ended in following solution: https://gist.github.com/tv-schulz/5fbd0a1e68f77d7bd73f
  • 15:44:36 <rosieres> In TSOB if your constant is not visible in Setup -> plugin -> tx_bhsiteconf -> there's then something wrong. But it must not be the fluitypo3 package
  • 15:45:18 <erredeco> in TS setup the template rootpath is correct, and is set as it has been set in constants
  • 15:46:29 <erredeco> and in Frontend I have the error:
  • 15:46:36 <erredeco> Oops, an error occurred!
  • 15:46:36 <erredeco> "C:/wamp/www/congresintesi.local.it/typo3conf/ext/bhsiteconf/Resources/Private/Templates-edetail/Page/HomePageTemplate.html" is not a valid template resource URI.
  • 15:47:07 <erredeco> which is strange because the file IS present and the path is correct
  • 15:48:36 <rosieres> erredeco: yeah but you collide with the conventional expectation from fluid.
  • 15:49:50 <erredeco> ?
  • 15:50:20 <erredeco> I don't know where the conflict arises :S
  • 15:54:10 <rosieres> I always put my templates to Resources/Private/Templates/Page/tpl_file.html and do not run into any problems. It's a try worth to go with that naming convention
  • 15:55:21 <NamelessCoder> sorry rosieres but fluid naming convention would call for filename TplFile.html
  • 15:55:47 <gbod> oschulz: Without controller stuff and things - https://worksonmymachine.org/blog/onepage-design-with-fluidtypo3
  • 15:55:54 <NamelessCoder> erredeco your problem most likely is the renamed "Templates-edetail" folder
  • 15:56:06 <erredeco> umm you mean the "-" ?
  • 15:56:15 <rosieres> That's what I meant
  • 15:56:19 <NamelessCoder> yessir
  • 15:56:24 <erredeco> I'll try
  • 16:01:37 <Akii> nice domain
  • 16:02:21 <rosieres> NamelessCoder is there a equivalent in fluid or vhs for the TS treeLevel condition?
  • 16:03:22 <rosieres> couldn't find anything
  • 16:03:38 <erredeco> nope. no luck
  • 16:03:51 <oschulz> gbod, thanks, but we need for some pages several layouts, in your example you have to make much if then else stuff to get ohter css classes and so in
  • 16:04:48 <erredeco> "C:/wamp/www/congresintesi.local.it/typo3conf/ext/bhsiteconf/Resources/Private/TemplatesEdetail/Page/HomePageTemplate.html" is not a valid template resource URI.
  • 16:07:06 <erredeco> it seems that the template path is set wrong in the backend
  • 16:11:12 <erredeco> I really don't know what to think
  • 16:11:19 <NamelessCoder> rosieres {v:page.breadCrumb() -> f:count()}
  • 16:11:40 <rosieres> DAMMIT :-)
  • 16:12:16 <NamelessCoder> mind you, you probably need the tag based usage of v:page.breadCrumb + "as" argument then f:count that variable
  • 16:12:26 <NamelessCoder> not sure breadcrumb from VHS supports returning the array
  • 16:15:17 <erredeco> What else can I try?
  • 16:19:49 <rosieres> erredeco: I'd do the naming like Private/TemplateOne/Templates/Page/DetailTemplate.html AND Private/TemplateTwo/Templates/Page/DetailTemplate.html
  • 16:27:33 <erredeco> nope the problem is always the same
  • 16:28:21 <erredeco> now, for reason that I don't know I can't even see nothing on the page module, even if the BE layout is set as "fluidpages" (both page and subpages)
  • 16:31:02 <rosieres> erredeco: I'd wipe all Template folders from that extension and move them step by step in again. Always check that they are working each. Then go ahaed with the implementation of the next one. You have anywhere built a bogus. But from here itÅ› hard to determine
  • 16:35:27 <erredeco> :S :S
  • 16:35:40 <erredeco> Ok I've discovered this
  • 16:36:11 <erredeco> the ID=1 page takes the templaterootpath (as "default") from a constant.txt file in bhsiteconf
  • 16:36:33 <erredeco> it seems that the constant set in the TS template of ID=8 is not taken into account
  • 16:37:03 <rosieres> But you should see this in TSOB if it is like this or not
  • 16:38:03 <erredeco> I repeat that in TSOB both constants and setup) I see the correct path
  • 16:40:27 <rosieres> and you are sure that you are in id=8 in TSOB?
  • 16:40:44 <NamelessCoder> and you have enabled the TS conditions if you use TS conditions?
  • 16:41:16 <NamelessCoder> do you have a TS condition that is not closed by a [global]?
  • 16:50:26 <erredeco> as far as I can see...no there are no condition without an ending [global]
  • 16:50:36 <erredeco> I've done another experiment:
  • 16:51:18 <erredeco> remove the template, layout, partials path from constant.txt and put them in the TS template
  • 16:51:28 <erredeco> result: they are not read
  • 16:52:02 <erredeco> it seems typoscript TSOB reads the correct path, but fluidpages don't
  • 16:52:58 <erredeco> and it always uses the path in constant.txt
  • 16:54:05 <NamelessCoder> I repeat: if you use TS conditions in your constants or setup - are you enabling the TS conditions in the TSOB when inspecting this?
  • 16:54:40 <NamelessCoder> otherwise you're checking the wrong resulting TS setup
  • 16:59:43 <erredeco> I use conditions to change the baseurl on FE, but even checking it in TSOB, the path remains the one I set in TS constants
  • 17:00:35 <erredeco> And everything worked with fluidpages 3.0
  • 17:11:56 <erredeco> the question as far as I can see is
  • 17:12:55 <erredeco> why TYPO3 in the TSOB takes the correct path from the constant set in the TS template; while fluidpages sees the path from constant.txt
  • 17:16:25 <rosieres> erredeco: my only advice is to create a new provider extension with builder and recreate your scenario. Your problem has never been seen here so far.
  • 17:25:27 <erredeco> I Think I'm going to cry
  • 17:32:14 <NamelessCoder> erredeco are you sure you are using the latest versions?
  • 17:32:21 <erredeco> latest from TER
  • 17:32:26 <erredeco> let me see
  • 17:32:50 <erredeco> VHS 2.1.4
  • 17:33:07 <erredeco> FLUX 7.1.2
  • 17:33:24 <erredeco> fluidpages 3.1.2
  • 17:33:28 <erredeco> fluidcontent 4.1.1
  • 17:34:32 <NamelessCoder> looks good
  • 17:37:03 <NamelessCoder> how exactly are you setting these paths?
  • 17:38:38 <erredeco> Ok, let's see
  • 17:38:53 <erredeco> 1. Provider extension for FE: bhsiteconf
  • 17:39:30 <erredeco> in ext_tables.php:
  • 17:40:04 <erredeco> TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile($_EXTKEY, 'Configuration/TypoScript', 'My Provider extension for pages and content');
  • 17:40:04 <erredeco> Tx_Flux_Core::registerProviderExtensionKey('bhsiteconf', 'Page');
  • 17:40:04 <erredeco> Tx_Flux_Core::registerProviderExtensionKey('bhsiteconf', 'Content');
  • 17:40:30 <erredeco> 2. so, in bhsiteconf/Configuration/Typoscript:
  • 17:40:58 <erredeco> constants.txt
  • 17:41:21 <erredeco> plugin.tx_bhsiteconf.view {
  • 17:41:21 <erredeco> templateRootPath = EXT:bhsiteconf/Resources/Private/Templates/
  • 17:41:21 <erredeco> partialRootPath = EXT:bhsiteconf/Resources/Private/Partials/
  • 17:41:21 <erredeco> layoutRootPath = EXT:bhsiteconf/Resources/Private/Layouts/
  • 17:41:21 <erredeco> }
  • 17:42:12 <erredeco> then, in every root page with ID=1,7,8,10 I set a TS template
  • 17:42:30 <erredeco> please note that bhsiteconf is loaded as last in "include static from extension"
  • 17:43:02 <erredeco> sorry I forgot: bhsiteconf/Configuration/Typoscript/Setup.txt
  • 17:43:14 <erredeco> plugin.tx_bhsiteconf.view {
  • 17:43:14 <erredeco> templateRootPath = {$plugin.tx_bhsiteconf.view.templateRootPath}
  • 17:43:14 <erredeco> partialRootPath = {$plugin.tx_bhsiteconf.view.partialRootPath}
  • 17:43:14 <erredeco> layoutRootPath = {$plugin.tx_bhsiteconf.view.layoutRootPath}
  • 17:43:14 <erredeco> }
  • 17:43:18 <NamelessCoder> why do you have a TS template on all "root" pages? Are those pages actually root pages?
  • 17:44:00 <erredeco> they are all root pages
  • 17:44:21 <erredeco> "world" icon and "Behavior > Use as Root Page"
  • 17:44:38 <NamelessCoder> and all TS templates on those pages have the "ROOT" flag set as well?
  • 17:45:12 <erredeco> all have a TS template with "options > Clear:constant, setup" and Rootlevel
  • 17:45:20 <erredeco> all checked
  • 17:46:58 <erredeco> so, for example in the page with ID=10
  • 17:47:00 <erredeco> plugin.tx_bhsiteconf.view {
  • 17:47:00 <erredeco> templateRootPath = EXT:bhsiteconf/Resources/Private/Templates-medmadquiz/
  • 17:47:00 <erredeco> }
  • 17:47:16 <erredeco> I also tried with EXT:bhsiteconf/Resources/Private/TemplatesMedmadquiz/
  • 17:47:26 <erredeco> and EXT:bhsiteconf/Resources/Private/Medmadquiz/Templates/
  • 17:47:48 <NamelessCoder> is this your problem? https://github.com/FluidTYPO3/flux/commit/5ffaf4662e2b9e6a3069d38ac82f88d9072d7417
  • 17:47:52 <erredeco> obviously, insite /Templates-medmadquiz/ there is the /Page/
  • 17:47:55 <erredeco> subfolder
  • 17:52:42 <erredeco> mhh
  • 17:58:45 <erredeco> a colleague of mine is debugging the code of fluidpages and flux and he says that it does not even enter in that function
  • 18:03:18 <NamelessCoder> so this is not a BE problem...
  • 18:03:33 <NamelessCoder> well of course not in FE - the class is called BackendConfigurationManager ;)
  • 18:06:26 <erredeco> :S
  • 18:10:50 <NamelessCoder> try debugging in fluidpages' PageService->getPageConfiguration
  • 18:11:13 <NamelessCoder> - that it resolves the correct action
  • 18:11:32 <NamelessCoder> and in PageProvider that it resolves the correct template paths (through FluxService I think it is)
  • 18:19:30 <erredeco> umm
  • 18:35:17 <erredeco> I think I'll do a revert to the old versions
  • 18:49:39 <erredeco> The old version WORK
  • 18:49:49 <erredeco> don't know why
  • 18:57:37 <erredeco> I will wait for flux 7.1.9 before the next update