typo3

I have setup a site to use flux / FLUIDCONTENT for templates and have it working using the tutorial here: http://thomas.deuling.org/2011/06/create-base-html-fluid-templates-for-typo3-4-5/ It's all working well but now I want to be able to choose an image per page and use it to build a big header. With templavoila I could create fields that were available in the page properties but can't seem to get it working with FLUIDCONTENT. I am using Typo3 6.1 and here is my inside page flex template: {namespace v=Tx_Vhs_ViewHelpers} {namespace flux=Tx_Flux_ViewHelpers} <f:layout name="main" /> <f:section

I use for the T3 Backend a TCA type select in a renderType = selectMultipleSideBySide Here the TCA Code: 'features' => array( 'label' => 'Zusatz', 'config' => array( 'type' => 'select', 'renderType' => 'selectMultipleSideBySide', 'size' => 10, 'minitems' => 0, 'maxitems' => 999, 'items' => array( array( 'Parkplätze', 'parking' ), array( 'Freies Wlan', 'wlan' ), ) ) ), it works fine in the Backend! But, how can I read the data properly now? I dont now the right way for the Domain/Model. /** * Features * * @var string */ protected $features = ''; /** * Returns the features * * @return string

I'm trying to set up a multilanguage site with typo3, but Im having some trouble. The default language of the site is German, but I also want to have it in English and French. So I went to define 2 more languages: English with ID=2 and French with ID=3 Next I added this typoscript to my template: config.linkVars = L config.uniqueLinkVars = 2 config.sys_language_overlay = content_fallback config.language = de config.locale_all = de_DE config.htmlTag_langKey = de-DE config.sys_language_uid = 0 [globalVar = GP:L = 2] config.language = en config.locale_all = en_EN config.htmlTag_langKey = en-EN

I have a website with two languages e.g de and en. De is my default language with no path prefix. En, the second language, has /en/ as prefix in the url. Now when I switch to the en language, the menu item links have /en/ in the url, which is fine. But when I click on a menu item, which is not explicit translated in the backend, then I get a 404 error. I cannot say this behavier is wrong, because there isn't a page with this slug path before I create one. But what should I do? Create a translation for each page, which is not helpful, if there are already hundreds of pages. Is there no fallback

How can i get items from an extbase respository in a different language? What i tested: findByUid($childUid) $query->getQuerySettings()->setRespectSysLanguage(FALSE); $query->getQuerySettings()->setSysLanguageUid(3); But the result is always the parent (lang) object. I tried it with "matching" and with "statement" but the result query uses the active language or searches for sys_language_id in (0,-1) = (default/all). It seems that this is a bug in extbase which will not removed until TYPO3 7.1: https://forge.typo3.org/issues/45873 For me this solves the problem: https://forge.typo3.org/issues

I am trying to implement my navigation with typoscript and I am having problems to understand how to wrap right. I already have a base navigation with 1 level that is working fine. Now I have pages that has subpages and other that don't have. For the ones without subpages I want the behavior that I have now. For the pages with subpages I want to add this as an dropdown menu. The HTML code should look like this. <ul class="nav"> <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown"> Test0 <b class="caret"></b> </a> <ul class="dropdown-menu"> <li class=""><a href="#"

Is there a possibility to add Bootstrap table-classes to tables created in Typo3 v6.1? I have noticed the setting "Additional CSS Class" when creating a page of type "Table", but: it doesn't add any classes to my table it doesn't support adding multiple classes (commas, spaces etc. get stripped when saving) I would to add class="table table-hover" to any table I create. Also, I don't think that I need the default class "contenttable". lorenz From your post, I assume that you are using the content element table, not a table in the RTE. Overriding the classes of the RTE would be easy (in

I created an extension with a domain model Message . This model has a relation m:n with the TYPO3 pages (the one which has the details of the pages, like title, issite_root etc) table. However, by using the mapping to existing tables option, it gives me type error saying page : The configured type field for table "pages" is of type int(11) unsigned This means the type field can not be used for defining the record type. You have to configure the mappings yourself if you want to map to this table or extend the correlated class So I just create the relation without mapping, so that I can later