00:02:05 <Outdoorsman> I cleared most but not alllll
00:02:24 <danilobuerger> ah we removed all deprecated view helpers for the vhs 2.0.0 release... so if you are still using deprecated view helpers you need to fix that
00:03:11 <danilobuerger> go to install tool and choose the development environment so that you see exceptions in the frontend
00:09:17 <Outdoorsman> Fatal error: Class 'Tx_Vhs_ViewHelpers_Page_Content_RenderViewHelper' not found in /ROOT_FOLDER/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4280
00:18:23 <Outdoorsman> I'm not exactly sure what this means here.
00:22:42 <Outdoorsman> I just updated flux, fluidcontent, fluidpages to latest dev as well.
00:29:10 <Outdoorsman> So is this message an indication I'm using deprecated view helpers?
00:53:36 <Outdoorsman> I see that it says "Will be removed in 2.0" at the top of this page: http://fluidtypo3.org/viewhelpers/vhs/development/Page/Content/RenderViewHelper.html
01:27:02 <Outdoorsman> OK @danilobuerger I found that fluidbootstraptheme and fbtcustomiser both had many references to the deprecated page.content.render. I updated them to all be content.render and flush the entire typo3temp/* folder and things are displaying again and loading much faster too.
01:27:55 <Outdoorsman> I'll put a ping in here for randomresult too just to make sure he knows about this update that needs to happen to be vhs 2.x compatible.
01:29:45 <Outdoorsman> I am still not getting navtitle to show up though for shortcut or normal pages? I don't think I'm doing anything wrong.
07:24:44 <Rawai> gibt es einen weg die doppelt generierten CEs so wieder aus der original language zu entfernen dass dabei nicht der ganze Content verloren geht?
07:25:18 <Rawai> Are you sure you want to delete this record? (This record has 1 translation(s) which will be deleted, too!)
07:26:02 <Rawai> natuerlich wollen wir das nicht nur all diese Elemente die nun uebersetzt wurden sind NICHT im Column Row generiert worden sonder als kopie darueber
07:26:48 <Rawai> versucht man jedoch das Element in Column Row zu loeschen dann erhaelt man die gleiche Meldung: Are you sure you want to delete this record? (This record has 1 translation(s) which will be deleted, too!)
07:27:04 <Rawai> somit sind dies wohl die gleichen Elemente die hier doppelt dargestellt werden
07:27:14 <Rawai> und die nur einmal uebersetzt wurden
07:28:00 <Rawai> setzt man ein Element auf hide dann wird auch die kopie gehidden
07:29:34 <Rawai> ein weiteres Problem ist das einige der Uebersetzungen (nicht alle) auch als kopie auf der Original seite angezeigt werden.
07:49:20 <Rawai> hmm wir haben gerade den content column row verschoben und beim reload der page im Backend ist er verschwunden samt dem darin enthaltenen content
07:49:39 <Rawai> jedoch sieht man nun jedes ce nur einmal
07:54:57 <Rawai> Every Element exists in list view only once but in Page View 2 versions - one nested inside a column row and the other one above it outside the container on the original language page
07:58:23 <danilobuerger> Rawai what that means is that the colPos of that element is wrong in the DB
07:58:50 <Rawai> in the translated language only the container and its elements gets shown in backend (Page) - but in frontend none of those translated elements shows up,
09:39:11 <fizelchen> Is it possible, to link content Elements to the created Accordionelements in the backend, so when i rearrange the accordeon, the Content Elements are correctly reordered as well
09:40:15 <fizelchen> right now, when i add a new accordeon panel and move it to the first position, i have to move all content elements in the backend, because they are in the "wrong" accordeon element
09:40:51 <randomresult> which t3-version, which version of the extensions (TER or Git)
11:08:10 <Guest|44425> i just migrated a fluidpages site from TYPO3 4.7 to 6.2. there were no backend layouts configured. now we don't see any columns in the backend anymore
11:09:06 <Guest|44425> i remember that i read a news post from claus saying that with TYPO3 6.2 the backend layout can be automatically provided by fluidpages (so no need to set up one as a record in TYPO3)
11:13:07 <danilobuerger> Guest|44425 are you registering with flux as described here :http://fluidtypo3.org/documentation/templating-manual/templating/provider-extension/registration-in-php.html
13:10:09 <RudyGnodde> Quick question: Is it possible to limit the content element types that can be inserted in a fluid content fce? Or at least remove/hide them in the wizzard when adding content to a fluid content fce?
13:11:18 <BenjaminR> Hi Guest, meant as freelancing task - but yes - right now especially for one where 6.2 should/can be utilised.
13:11:53 <BenjaminR> RudyGnodde: yes you can limit them by content areas in page template and content elements grids