IRC logs

20140723

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

IRC log range: 20140723*

20140723

  • 09:33:23 <fger> hi guys
  • 10:32:29 <gencha_> what's your approach to getting rid of excessive whitespace in your generated html markup?
  • 10:32:47 <gencha_> every now and then it creates rendering issues on stuff i'm working on and it drives me nuts
  • 10:58:06 <beo6> hello everyone. I updated Typo3 from 6.1 to 6.2 and alongside updated all fluid powered Typo3 extensions to the latest versions. I have multiple Page-templates using my fluidpage_bootstrap however it always uses the default template now and ignores the selected page-template
  • 11:22:41 <floxx> gencha_: sourceopt is an option
  • 11:35:18 <fger> does anybody have copy&paste probs with localized FCEs in TYPO3 6.2.4 and latest Flux dev-branch ?
  • 11:48:06 <gencha_> floxx: i was trying to get that to work earlier, but no matter what i tried, it didn't do anything. i figured it wasn't compatible with fedext
  • 11:49:29 <floxx> gencha_: mh. it worked in my last ft3 project. have a look into the source code http://regis24.de/
  • 11:49:51 <gencha_> floxx: yeah, looks great
  • 11:54:06 <gencha_> it worked fine on a project we did a couple months ago
  • 11:54:43 <gencha_> no idea what i did wrong this time. from what i remembered, in previous projects i just set config.sourceopt.enable=1 and it worked
  • 12:13:10 <beo6> anyone any idea? is plugin.tx_afmfluidpagesbootstrap.view.templateRootPath = EXT:afmfluidpages_bootstrap/Resources/Private/Templates/ no longer correct?
  • 14:23:04 <randomresult> anyone here using sass?
  • 14:23:34 <gencha_> we use less
  • 14:24:15 <randomresult> im searching for the diffrence in scss and sass
  • 14:26:01 <BenjaminR> scss and sass? two names for the same thing
  • 14:27:11 <BenjaminR> Sass has two syntaxes. The new main syntax (as of Sass 3) is known as “SCSS” (for “Sassy CSS”), and is a superset of CSS3’s syntax. This means that every valid CSS3 stylesheet is valid SCSS as well. SCSS files use the extension .scss.
  • 14:27:11 <BenjaminR> The second, older syntax is known as the indented syntax (or just “Sass”).
  • 14:38:52 <fger> yeah... we use sass/scss and compile/watch it using grunt
  • 14:44:34 <BenjaminR> I love to crawl hunderts of XING profiles per minute javascript powered ;)
  • 14:46:11 <beo6> using SASS with compass
  • 14:50:45 <gencha_> is it just me or is the addAnchor parameter in fluidcontent_core never actually used anywhere?
  • 15:14:08 <batjony> hello fluiders
  • 15:14:15 <beo6> hello
  • 15:14:17 <BenjaminR> so :) fluidpages: fluid page templates
  • 15:14:32 <BenjaminR> fluidcontent: fluid based flexible content elements (fce)
  • 15:14:48 <BenjaminR> fluidcontent core: replacement for css_styled_content means fluid core elements
  • 15:15:01 <BenjaminR> vhs: large set of useful viewhelpers
  • 15:15:01 <beo6> have still a problem with fluidpages
  • 15:15:17 <BenjaminR> flux: the core of the extensions mentioned before
  • 15:16:13 <beo6> i updated fluidpages etc. and now it just ignoes my selected template i choose in the backend... its really driving me crazy
  • 15:16:45 <BenjaminR> batjony: means you can render EVERY part of your frontend with fluid
  • 15:17:00 <BenjaminR> including your <head>
  • 15:17:22 <BenjaminR> -render +describe
  • 15:17:41 <batjony> BenjaminR: so to summerize we have: fluidpages, fluidcontent, fluidcontent core, vhs, flux
  • 15:18:09 <BenjaminR> yap these are the most important. you can see the full list of extensions we maintain on github
  • 15:18:31 <gencha_> weeee
  • 15:18:40 <batjony> BenjaminR: could you give a link
  • 15:18:57 <batjony> where are all the fluid stuffs
  • 15:19:01 <BenjaminR> https://github.com/FluidTYPO3
  • 15:19:11 <BenjaminR> fluid stuffs?
  • 15:20:10 <batjony> fluid exts :)
  • 15:20:23 <BenjaminR> what do you mean?
  • 15:20:35 <BenjaminR> fluid is a core extension located at typo3/sysext/fluid
  • 15:21:07 <batjony> https://github.com/FluidTYPO3 this is exactly what did I mean :)
  • 15:21:08 <batjony> 10x
  • 15:21:32 <batjony> where the idea of this project FluidTYPO3 comes from ?
  • 15:21:47 <batjony> is it an official TYPO3 project
  • 15:22:06 <gencha_> if you want to make a templating system for typo3 from scratch, you first have to invent the universe
  • 15:22:27 <BenjaminR> Its founded by NamelessCoder
  • 15:22:35 <BenjaminR> He has a lot of great ideas ^^
  • 15:23:16 <batjony> and is this going to become some official part of TYPO3 ?
  • 15:23:41 <BenjaminR> no i dont think so. as the most extensions wont
  • 15:23:54 <BenjaminR> i think that wouldnt be a good idea anyway
  • 15:24:12 <BenjaminR> people have to choose a solution theirselves
  • 15:27:24 <beo6> anyone can help? updated yesterday and page template selections in the backend are ignored. it always shows the default template for all pages
  • 15:27:45 <beo6> it worked fine before the update
  • 15:31:14 <batjony> BenjaminR: VHS is a flow extension http://typo3.org/extensions/repository/view/vhs, is there any difference between it and https://github.com/FluidTYPO3/vhs
  • 15:31:48 <BenjaminR> its a TYPO3.CMS extension
  • 15:32:32 <batjony> but in Flow, we also have it, is it the same
  • 15:32:59 <BenjaminR> typo3.org/extensions/repository is the extension repository. as an author you can submit extensions there and when they get approved you as can download them in the extension manager in your typo3 cms backend
  • 15:33:37 <BenjaminR> we maintain on github and for then we pack releases and publish them to the typo3 extension repository
  • 15:40:10 <batjony> BenjaminR: do all these fluidtypo3 extensions somehow decrease using the Typoscirpt ?
  • 15:40:32 <BenjaminR> no
  • 15:40:38 <BenjaminR> wait
  • 15:40:42 <BenjaminR> how do you mean?
  • 15:40:57 <BenjaminR> you will NEED LESS typoscript but you CAN use as much as before :D
  • 15:41:54 <batjony> for example as I see for menus rendering there are menus objects in typoscript http://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/Index.html
  • 15:42:08 <batjony> do we need them when switch to fluid templating
  • 15:42:29 <BenjaminR> you dont need them
  • 15:42:38 <BenjaminR> you can do all that within fluid
  • 15:42:43 <batjony> very nice :)
  • 15:44:27 <batjony> and for forms, do we have a way where we can store all the forms in files (instead of db)
  • 15:45:24 <batjony> for example in Zend, we have /forms/Contact.php, you initialize it in the controller and then pass it to the view, so in the view, we have just <?php echo $this->form; ?>
  • 15:47:55 <BenjaminR> there are multiple solutions for forms. but that doesnt depend on which engine you use for your page and content templates
  • 15:48:22 <BenjaminR> most likely you will use one of the extensions available on ter
  • 15:48:32 <BenjaminR> ter is the shorthand for typo3 extension repository
  • 15:49:13 <batjony> BenjaminR: the idea is to desribe every form in a file, and then initialize it in the controller and pass it to the view template
  • 15:49:40 <BenjaminR> theirfor look at f:form
  • 15:49:49 <BenjaminR> http://wiki.typo3.org/Fluid#f:form
  • 15:50:47 <batjony> ya this is what do I mean
  • 15:50:49 <BenjaminR> posting this to a extbase controller action will pass all values as action parameter
  • 15:51:10 <BenjaminR> one array named like the form
  • 15:54:15 <batjony> and last question for now :) I can keep all the fluid templating and configurations in files right and no DB records ?
  • 15:55:55 <BenjaminR> yes, your templates will be stores in files. also your default configuration. configuration changes done in the backend will be saved to the database
  • 15:56:07 <BenjaminR> fx changes to typoscript variables
  • 15:57:05 <BenjaminR> batjony: an example for a so called provider extension: https://github.com/FluidTYPO3/fluidtypo3org
  • 15:57:21 <BenjaminR> its the template used for fluidtypo3.org
  • 15:58:12 <gencha_> how should one format the "stack" in v:if?
  • 15:58:36 <BenjaminR> gencha_ you will have to ask danilobuerger :D
  • 15:58:54 <danilobuerger> its described in a PR somewhere
  • 15:59:08 <beo6> please can anyone help me? I am sure it must be some small issue but i haven't found anything wrong especially since it worked before the update. :(
  • 15:59:10 <danilobuerger> nobody bothered to take the info from the PR and actually write it in the class dock of v:if
  • 15:59:22 <danilobuerger> *class doc
  • 15:59:29 <gencha_> danilobuerger: could you point me at the PR?
  • 16:00:00 <fger> hi, any clue if sys_categories of page-records inherit on their childs ? :) ?
  • 16:00:03 <BenjaminR> danilobueger: not even you :)
  • 16:00:42 <gencha_> beo6: no idea about that problem. i feel like i encountered it as well recently, but it just went away while i was working on other stuff :P
  • 16:01:19 <beo6> gencha_: well. that is no solution for me. i already went avay yesterday and hoped it will solve itself today. But nothing. ;)
  • 16:01:29 <beo6> -avay +away
  • 16:02:23 <danilobuerger> gencha_ https://github.com/FluidTYPO3/vhs/pull/401
  • 16:03:02 <beo6> i checked all typoscripts and the template paths seem to be correct. It even seems to find the templates since i can see them for selection in the backend and i can select the templates. But they just don't change in the frontend...
  • 16:05:00 <beo6> i have really no more ideas what the problem might be. It is really the last remaining issue after the update... :(
  • 16:05:50 <danilobuerger> from where did you update from?
  • 16:06:05 <beo6> typo3 version was 6.1
  • 16:06:28 <danilobuerger> did you update the extensions too?
  • 16:06:32 <beo6> sure
  • 16:07:58 <gencha_> danilobuerger: hah, awesome. i think i figured it out now :)
  • 16:08:03 <gencha_> <v:if stack="{0: settings.header.hideHeader, 1: '!=', 2: 1}">
  • 16:08:10 <beo6> the fluidpages extension i updated from was version 2.1.0 with some patch for assets caching bug
  • 16:08:23 <danilobuerger> gencha yeah looks correct
  • 16:09:39 <batjony> BenjaminR: could I store also the backend layouts in files ?
  • 16:09:52 <beo6> i even compared my fluidpages bootstrap extension with the fluidpages_bootstrap from the extension. It seems there has not so much changed.
  • 16:10:05 <dalder> Hi there! Does anybody have a general solution to make VHS and PageRenderer working together? In my tests VHS files are always included after PageRenderer files. But jquery for example will be included via VHS (template). Community extension use PageRender inclusion. So in fact the script from the extension will not find jquery. Any idea? Thx! VHS
  • 16:10:05 <dalder> 1.8.5 (github)
  • 16:12:31 <gencha_> success! http://i.imgur.com/ly8emmK.png
  • 16:15:26 <beo6> might this be my issue? https://github.com/FluidTYPO3/fluidpages/commit/a9cae73400eae5d292f5bc27fac8792a91b261b4
  • 16:17:31 <danilobuerger> beo6 whats the issue anyway? you have a number of page templates and only the default one is taken? whats the default one?
  • 16:18:49 <beo6> danilobuerger: the default template is the Render.html template in my own fluidpages_bootstrap extension under ext\afmfluidpages_bootstrap\Resources\Private\Templates\Page\
  • 16:19:11 <beo6> and it is indeed the same template that is on the first page in my pagetree
  • 16:20:54 <danilobuerger> so what happens if you change the template to something else on the root page?
  • 16:21:18 <beo6> yeah. just tried that and it still is the same template... so i am back at the beginning
  • 16:22:15 <danilobuerger> what do you mean by same template? Is it still Render.html even if you change it on the root page to something else?
  • 16:22:23 <beo6> yes
  • 16:22:36 <danilobuerger> even on the root page itself?
  • 16:23:20 <beo6> interestingly yes. it even is still the Render.html on the root-page
  • 16:24:27 <gencha_> do some cache cleansing
  • 16:24:40 <danilobuerger> beo6 to 99 % then you are doing something wrong
  • 16:24:42 <beo6> i cleared the cache in the install tool. is that enough?
  • 16:25:27 <beo6> i would love to know what i am doing wrong. Because it worked before the updates
  • 16:25:48 <beo6> and i have changed nothing on the templates. just updated typo3 and all extensions
  • 16:26:39 <danilobuerger> alright set the page template on your root template to something different then Render.html .. then in the database do select `uid`, `tx_fed_page_controller_action` from `pages` where `uid` = ###YOUR ROOT UID###;
  • 16:26:43 <danilobuerger> paste result here please
  • 16:28:31 <beo6> uid = 1, tx_fed_page_controller_action = afmfluidpages_bootstrap->Empty
  • 16:28:59 <danilobuerger> so just now you set it to Empty.html right?
  • 16:29:17 <beo6> yes
  • 16:29:34 <danilobuerger> and when you access index.php?id=1 it doesnt use Empty.html?
  • 16:29:52 <beo6> exactly
  • 16:30:01 <danilobuerger> please gist Empty.html
  • 16:30:11 <beo6> gist?
  • 16:30:16 <danilobuerger> gist.github.com
  • 16:31:09 <gencha_> what is afmfluidpages_bootstrap?
  • 16:31:23 <beo6> https://gist.github.com/anonymous/1bc0c250df4c295f1ce3
  • 16:32:46 <gencha_> wow, that vsf-mail.de server lists *everything*
  • 16:33:27 <beo6> wow. indeed.
  • 16:33:35 <danilobuerger> beo6 please gist your render.html
  • 16:34:43 <beo6> danilobuerger: here you go: https://gist.github.com/anonymous/f4fb02048c980fae8e86
  • 16:35:18 <danilobuerger> so why is it that you assign both flux forms the id default?
  • 16:35:59 <beo6> oh. maybe a copy paste error
  • 16:37:23 <danilobuerger> make sure every id is unique, clear caches through install tool, try again
  • 16:37:41 <beo6> thanks. already doing that. :)
  • 16:39:41 <beo6> doesn't seem to help. :(
  • 16:40:42 <beo6> nope. does definetly not help
  • 16:41:00 <beo6> and it must have worked before the updates
  • 16:42:35 <beo6> i really hoped that was the problem.... mhhh
  • 16:43:14 <beo6> is it a problem when i have the fluidpages_bootstrap example extensions in the installation but not activated?
  • 16:43:37 <beo6> because that does have a Render.html too with id = default
  • 16:57:46 <Guest|39259> Hello
  • 16:58:02 * Guest|39259
  • 16:58:05 * Guest|39259 ip
  • 16:58:09 * Guest|39259 whois
  • 16:59:02 * beo6 format c:
  • 17:01:12 <Guest|39259> Hi, I am currently diving into Fluid/Flux but I am very stuck. Is there anywhere an up to date tutorial or comprehensive documentation? I went several times through this https://worksonmymachine.org/blog/fluidtypo3-quickstart and also http://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/content-element.html (I am usin
  • 17:01:13 <Guest|39259> g TYPO3 6.2)
  • 17:04:01 <beo6> danilobuerger: just tried to update to the develop versions of the extensions and the only thing i got was a Fatal error: Call to a member function get() on a non-object in ...BackendConfigurationManager
  • 17:05:01 <danilobuerger> beo6 that means that you didnt clear the caches in the install tool
  • 17:05:21 <beo6> i would have if i was able to go into the install tool. but the install tool also showed the error. :)
  • 17:05:43 <danilobuerger> delete typo3temp, try again
  • 17:06:10 <beo6> i did. still error. Now i revert back to the typo3 extension repository versions
  • 17:06:29 <beo6> i was able to see one template at least with these versions
  • 17:07:04 <Guest|39259> The extensions used are: flux 7.0 - fluidpages 3.0 - fluidcontent 4.0 - vhs 1.9.1
  • 17:08:16 <danilobuerger> beo6 development works just fine.. if you cant access install tool after upgrading you should delete typo3temp and truncate all cache tables
  • 17:08:42 <beo6> ok. i will try it again
  • 17:11:52 <Guest|39259> Is there anything else to do to get any advice?
  • 17:12:44 <beo6> Guest|39259: maybe if you have any specific question. But i currently have my own issue. sorry
  • 17:13:25 <Guest|39259> The specific question is: Where can I find up to date documentation or a tutorial for fluid/flux.
  • 17:13:38 <danilobuerger> fluidtypo3.org is as up to date as it gets
  • 17:13:42 <Guest|39259> The official documentation seems to have depreciated code examples as well.
  • 17:13:46 <Guest|39259> and incomplete pages.
  • 17:14:02 <danilobuerger> well if something is wrong you are more than welcome to change it
  • 17:14:19 <beo6> true. i looked here: http://fluidtypo3.org/documentation/templating-manual/templating/using-templates/selecting-page-templates.html and it is just an empty page. :)
  • 17:14:29 <Guest|39259> As a beginner it is extremly difficult to understand what exactly is wrong.
  • 17:14:58 <Guest|39259> I just see that the code does not work, even after playing it through like 6 times on a fresh install each time.
  • 17:15:15 <danilobuerger> well but then your question should be why is code XYZ not working
  • 17:15:21 <danilobuerger> that way you will probably get help
  • 17:15:32 <Guest|39259> okay, get it. will get more specific. will play it through one more time.
  • 17:15:35 <Guest|39259> thanks.
  • 17:17:17 <beo6> danilobuerger: nope. the dev versions do not work for me. i just get Fatal error: Call to a member function get() on a non-object in /../typo3conf/ext/flux/Classes/Configuration/BackendConfigurationManager.php on line 176
  • 17:17:29 <danilobuerger> which tables did you truncate?
  • 17:18:07 <beo6> ah right. forgot to truncate
  • 17:18:25 <danilobuerger> truncate every cf_ table
  • 17:19:09 <beo6> are all cf_ tables caching tables?
  • 17:19:17 <danilobuerger> ye
  • 17:20:30 <beo6> i did. still same error
  • 17:20:47 <danilobuerger> after you truncated those tables did you remove everything in typo3temp?
  • 17:20:54 <danilobuerger> and how are you accessing the install tool?
  • 17:21:30 <beo6> i was able to access the install tool, updated the database and cleared all caches. still the error. So now i truncated the tables
  • 17:21:45 <beo6> and now i am clearing the typo3temp folder again to see
  • 17:21:49 <danilobuerger> oh i thought you couldnt access the install tool?
  • 17:22:07 <beo6> yeah. somehow when i was in the backend it didnt worked. but with typo3/install it worked
  • 17:22:42 <beo6> nope. still not working. can't access the backend anymore
  • 17:22:44 <danilobuerger> alright so in the install tool click on clear all caches... if after that you still get the error.. somewhere you have a config error
  • 17:22:56 <danilobuerger> possibly LocalConfiguration or such
  • 17:23:20 <beo6> even though with the typo3 extension repository versions it works?
  • 17:23:27 <danilobuerger> yes
  • 17:24:47 <beo6> ok. must have a config error then. But don
  • 17:24:54 <danilobuerger> the error message you are getting is from a typo3 inject not working.. has nothing todo with flux, etc
  • 17:25:10 <danilobuerger> and those only stop working when you have a caching / config problem
  • 17:25:49 <danilobuerger> just to make sure... in ext:flux -> Classes/Service/RecordService.php exists right?
  • 17:26:21 <beo6> yes. the file exists
  • 17:26:51 <danilobuerger> thats what should be injected in BackendConfigurationManager, and thats what its trying to access on line 176
  • 17:27:06 <danilobuerger> could also be a permission error? or a to low php version
  • 17:27:27 <danilobuerger> somebody was hunting for 5 hours after that bug, its basically always a caching / config error
  • 17:27:50 <beo6> using PHP 5.3.23
  • 17:28:11 <danilobuerger> try with php 5.4
  • 17:28:29 <danilobuerger> thats recommended minimum for typo3 6.2
  • 17:28:32 <danilobuerger> http://wiki.typo3.org/TYPO3_CMS_6.2#System_Requirements
  • 17:28:40 <danilobuerger> well anyway i am off, happy hunting
  • 17:28:56 <beo6> thanks. i guess i need a break after this hunting. :)
  • 17:29:00 <beo6> have a nice day
  • 17:29:53 <beo6> crap. can't use a newer php version. :(
  • 17:30:49 <beo6> well. when i look on the typo3 page the minimum version is PHP 5.3.7
  • 17:31:08 <beo6> so it should work
  • 17:33:15 <bjo3rn> sheesh. why is my pagecontroller not/no longer called...
  • 17:33:42 <beo6> and why is my Page_Content_RenderViewHelper no longer called.. :)
  • 17:33:45 <bjo3rn> I triple checked all namespaces and provider extension key registration. wtf?
  • 17:33:54 <beo6> args. i need a break.
  • 17:34:01 <bjo3rn> yours is easy ^^
  • 17:34:11 <bjo3rn> v:content.render()
  • 17:34:23 <beo6> i guess i need to use namespaces now with the developer versions of the extensions
  • 17:36:53 <bjo3rn> not necessarily. in my case it only works if I use the old underscore Tx_... naming scheme :S
  • 17:38:10 <beo6> what do you use in your fluid pagetemplate for the viewhelper? {namespace v=Tx_Vhs_ViewHelpers} ?
  • 17:39:50 <bjo3rn> no, FluidTYPO3\Vhs\ViewHelpers
  • 17:40:14 <bjo3rn> this is only relevant for autoloading
  • 17:40:25 <beo6> still getting this: Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Var\SetViewHelper maybe not loaded or no autoloader? (1289386765)
  • 17:40:36 <bjo3rn> hehe. it's v:variable now
  • 17:40:37 <beo6> in the backend
  • 17:40:45 <bjo3rn> v:variable.set
  • 17:40:51 <beo6> ahh. thanks
  • 17:41:09 <bjo3rn> your custom viewhelper is part of a provider extension?
  • 17:41:10 <beo6> i am just stupid sometimes. i just read about that change and completely forgot
  • 17:41:20 <bjo3rn> happens
  • 17:41:51 <beo6> wait. i also read that you can still use the old templates
  • 17:42:43 <bjo3rn> you mean namespace declarations?
  • 17:42:57 <beo6> nope. the v:var viewhelper
  • 17:43:19 <bjo3rn> not with the new namespaces as var is a reserved word in php
  • 17:43:22 <beo6> http://fluidtypo3.org/blog/news/coming-soon-vhs-20.html
  • 17:43:39 <beo6> there they write "In both of these cases aliases have been added to allow you to continue using your templates as they are."
  • 17:45:06 <bjo3rn> if you use the new namespace FluidTYPO3\Vhs\ViewHelpers it won't be possible. maybe with Tx_Vhs_ViewHelpers but I'm not sure.
  • 17:46:17 <beo6> Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Page\Content\RenderViewHelper maybe not loaded or no autoloader? (1289386765) ???
  • 17:46:42 <bjo3rn> see above. it's v:content.render now
  • 17:46:52 <bjo3rn> (without 'page')
  • 17:47:03 <beo6> who changes these all the time. thats just crazy
  • 17:47:46 <bjo3rn> well you are using a dev branch so it's your own risk
  • 17:48:17 <bjo3rn> with a new release such things will be communicated
  • 17:48:18 <beo6> i tried the typo3 extension repository versions and still got issues.
  • 17:48:34 <beo6> i hope the dev branch fixes these. thats the reason i use it
  • 17:48:41 <bjo3rn> it does, yes
  • 17:49:00 <bjo3rn> vhs dev branch is always the most safe to use
  • 17:49:13 <bjo3rn> but you have to know the traps
  • 17:49:41 <bjo3rn> mind the gap
  • 17:49:47 <bjo3rn> let op, drempels
  • 17:50:08 <beo6> now i get no more errors in backend. but all my content is gone
  • 17:50:18 <beo6> args
  • 17:51:01 <bjo3rn> well, I'd say you fixed it ^^
  • 17:51:12 <beo6> ha...ha... ;)
  • 17:51:22 <bjo3rn> srsly: gone in fe or also in be?
  • 17:51:48 <beo6> fe is still giving error
  • 17:52:03 <bjo3rn> and content is gone in the be??
  • 17:52:08 <beo6> yes
  • 17:52:40 <bjo3rn> ok, all dev versions? flux, fluidcontent, fluidpages, vhs?
  • 17:52:46 <beo6> yes
  • 17:53:15 <bjo3rn> you switched from ter versions to dev?
  • 17:53:18 <bjo3rn> *latest
  • 17:53:23 <beo6> yes
  • 17:53:39 <bjo3rn> can you pastebin/gist your page template pls?
  • 17:53:58 <bjo3rn> did you run the update script in extension manager for flux/fluidcontent?
  • 17:54:15 <beo6> not yet
  • 17:54:50 <beo6> 0 rows have been updated
  • 17:55:10 <beo6> YAY. i see content in the frontend
  • 17:55:16 <bjo3rn> db compare in install tool?
  • 17:55:48 <bjo3rn> flushed all caches _via install tool_?
  • 17:55:53 <beo6> database is up to date
  • 17:56:18 <beo6> caches are flushed as much as flushing is possible
  • 17:56:37 <bjo3rn> via install tool?
  • 17:56:41 <beo6> yes
  • 17:56:43 <bjo3rn> ok
  • 17:57:06 <bjo3rn> can you see the grid in be or completely empty?
  • 17:58:13 <beo6> i can see the 66x33 column CE
  • 17:58:21 <beo6> but its completely empty
  • 17:58:41 <bjo3rn> go to list module, the content should be there
  • 17:58:48 <bjo3rn> and check the selected column
  • 17:59:20 <beo6> selected column is "Fluid Content Area"
  • 18:00:48 <beo6> i can see the content when i edit a multi column element and go to the Relations Tab
  • 18:01:02 <beo6> so the content must be there and correct i guess
  • 18:01:50 <beo6> is <flux:widget.grid /> no more?
  • 18:02:18 <beo6> or do i need to change anything for flux grids inside the FCE ?
  • 18:02:51 <beo6> frontend is correctly displayed
  • 18:03:04 <bjo3rn> ah, sec
  • 18:03:23 <bjo3rn> I guess you have flux:grid.row/flux:grid.column/flux:content ?
  • 18:03:30 <bjo3rn> flux:content is no more
  • 18:03:48 <beo6> <flux:flexform.grid.column style="width: 33%"> <flux:flexform.content name="column1" label="33%" />
  • 18:04:16 <beo6> ok. what is the alternative?
  • 18:04:35 <bjo3rn> aha
  • 18:05:01 <bjo3rn> it's now flux:grid.column name="column1" label="33%" style=".."/>
  • 18:05:05 <bjo3rn> self closing
  • 18:05:10 <bjo3rn> no need for flux:content
  • 18:05:27 <bjo3rn> this will fix it
  • 18:05:40 <beo6> no more flux:flexform ?
  • 18:06:47 <bjo3rn> it will still work but see http://fluidtypo3.org/documentation/templating-manual/appendix/migration/from-flux-6x.html
  • 18:09:18 <beo6> ok. thanks. i will fix that tomorrow. thank you a lot
  • 18:09:30 <bjo3rn> yw ;)
  • 18:09:31 <beo6> i need a break now. :)
  • 18:09:39 <bjo3rn> hehe.
  • 18:09:41 <beo6> have a nice day
  • 18:09:46 <bjo3rn> you too, cya
  • 18:09:50 <beo6> cya
  • 18:23:10 <Outdoorsman> Ahhh I need advice from someone that knows the TYPO3 database.
  • 18:24:24 <Outdoorsman> Before I knew that flux/etc didn't support workspaces, I edited some things in another workspace and published the changes to live workspace.
  • 18:25:52 <Outdoorsman> Now my main storage folder shows in two places in the page tree when logged in as a non-admin BE user, but when I'm logged in as an admin I see it only once.
  • 18:26:40 <Outdoorsman> When I hover over the Main Storage folder the ID of the page is the same for both instances.
  • 18:27:37 <bjo3rn> that's witchcraft!
  • 18:27:39 <Outdoorsman> I think I need to manually edit a field in the database but haven't found the golden nugget yet. Any ideas?
  • 18:27:41 <bjo3rn> sorry, no clue
  • 18:28:15 <Outdoorsman> Thanks for at least responding.
  • 18:28:58 <Outdoorsman> I'm not sure which table is responsible for the page tree in the BE... do you guys know?
  • 18:31:01 <Outdoorsman> Maybe @NamelessCoder would know?
  • 18:34:36 <Outdoorsman> It must be determined from the 'uid' field in the 'pages' table. I think 'pid' is the 'uid' of the page that the record belongs to.
  • 18:50:47 <Outdoorsman> I'm a genius... ha ha. I added two mount points for my BE users, the root page (which had the main storage folder as a subpage) and the main storage folder. This cause the page to show up twice.
  • 18:51:56 <Outdoorsman> Only one mount point was needed for that BE user group since all pages were subpages to that root page. Thanks bjo3rn for at least commenting :)
  • 19:00:31 <bjo3rn> your very welcome. I'm always happy to help =)
  • 19:00:51 <bjo3rn> *you're
  • 19:06:30 <danilobuerger> gencha i see why you needed v:if :-)