Is there a way to add more column to TYPO3?
In the past I used to add additional column in ExtTables.php (http://www.lacisoft.com/blog/2009/11/06/additional-columns-in-typo3s-web-page-module/), but since TYPO3 6.x.x the mod.SHARED.colPos_list is no longer support, so in backend I only see 4 standard column and nothing else...
Any sugestions, manuals?
I have found the solution - Beckend Layout - and tutorial on http://blog.sebastiaandejonge.com/articles/2012/july/26/implementing-typo3s-backend-layouts/ site
Related
Extension versions:
Flux: Fluid Integration - 9.3.2
Gridelements - 8.6.3
During an upgrade from 6.2 to 8.7.32, a website uses gridelements extension and Flux. We have some gridcontainers created with the gridelements extension and flux (CE's) nested inside these. Now the content elements are created but they don't get set properly inside the gridelement containers. Unless I create the flux elements outside the gridelement and then drag in inside.
In the database I can see that the fields are not properly assigned when created inside the gridelement:
Don't mind the typo, "Created outside parent container"
So that element with 0|0 on tx_gridelements_container and tx_gridelements_columns respectivly is not displayed in the backend and only visible in the list mode.
Now, this is strange because I checked the data types on the database and it seems alright. I had other similar pages that I've upgraded as well and no one had this issue after migrating to 8.7.32, since this issue only occurred in 6.2.x versions.
The allowed elements are set to all, as well as in the other TYPO3 where this issue is not occurring. Does anyone know what could I try to fix this? I'm running out of options and I couldn't find much at TYPO3 Slack, stack overflow and similars.
Are the necessary fields displayed in the editing form of those Flux elements?
To make Gridelements and their children work properly, you will need the Gridelements backend-layout, container and column fields defined for those elements. Otherwise they will get their default values, which is 0 in case of Gridelements.
I updated a typo3 site from version 6 to version 7 and now to version 8 heading for 9 or 10. Now some contents on my page are missing. When I look in the page editor all elements have errors like [INVALID VALUE ('ce_head-image')] or [INVALID VALUE ('ce_product')]. What does this mean?
Your content elements (CEs) have no rendering definition.
the rendering definition can be missing because of:
the basic rendering extension is missing
EXT:CSC leaves the core and is an TER extension
the names of the CEs is changed inside the basic rendering extension (there should be an upgrade wizard)
the same for CE types defined by additional extensions
extension is no longer supported for the newer TYPO3 version
changed names in newer versions (upgrade wizard?)
the registering of additional CEs does not work any longer as it has been changed in the core
As the names you have sounds unfamiliar my firsst guess would be the last reason.
I have a new TYPO3 9.5.15 installation and added gridelements 9.5.0 and t3sbootstrap 4.4.5 to make content elements with 3 columns in a own 1 column backendlayout which is defined in PageTsConfig.
In older TYPO3 versions, this is working fine (i.e TYPO3 7) but in TYPO3 9 I get the following error in FE:
Tried resolving a template file for controller action "Standard->three_columns" in format ".html", but none of the paths contained the expected template file (Standard/Three_columns.html). The following paths were checked:
xxx/typo3/sysext/fluid_styled_content/Resources/Private/Templates/, xxx/typo3conf/ext/gridelements/Resources/Private/Templates/, xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/Content/, xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/, ,
I've double checked and can confirm, that both, gridelements and t3sbootstrap are included in the roottemplate of the website.
As far as I found out, the templates are available in xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/Gridelements/
but are called ThreeColumns.html
Has anyone an idee what causes the error and how to resolve it?
Thanks in advance
At a first look it seems that there are 2 problems with your combination here:
The message "Standard->three_columns" points to a wrong static template, so I guess you included the new DataProcessing static of Gridelements, while t3sbootstrap depends on the old Plugin and USER based static.
The root path xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/Gridelements/ is missing in your setup.
At a second look it might even be enough to change the Gridelements static, since t3sbootstrap takes care of the root path based on that setup.
i'm updating a project from TYPO3 7.6.32 to ^8. in the deprecation log i can find a lot of entries where the issue is:
29-04-19 12:13: EXT:form: Do not use "layout." anymore. Deprecated since TYPO3 CMS 7, this function will be removed in TYPO3 CMS 8.
questions:
what is EXT:form (its not an extension in typo3conf/ext/...)
what is "layout."
do anyone have any resources on how to rework that case
if any further information is needed just drop a comment, thanks - any help is much appreciated
This is probably usage of the FORM content object / content element.
See:
https://docs.typo3.org/typo3cms/extensions/core/Changelog/7.5/Deprecation-69401-AdoptFormToSupportTheExtbaseFluidMVCStack.html
You might have the following somewhere:
10 = FORM
10 {
layout {
containerWrap = <div><elements /></div>
elementWrap = <div><element /></div>
}
}
The "layout" part can be removed completely.
The extension "Form" mentioned is a system extension and located in typo3/sysext/form. The layout part was the configuration older versions used to configure the layout - which is nowadays done with FLUID templates.
The form extension layouts can be customized by configuring your own templates in TypoScript - see https://docs.typo3.org/typo3cms/extensions/form/I/FAQ/Index.html#how-do-i-override-the-frontend-templates
import from tt_news in TYPO3 8 LTS with actual news and news_ttnewsimport is working fine. But we had some individual fields in tt_news and i want to import theese fields too in individuel fields in news.
So i made a new extension which extends news with individual fields. It is working fine: i can edit them in the backend and print content in the frontend.
Then i modified getImportData() in TTNewsNewsDataProviderService of news_ttnewsimport and added my new fields. The content of the individual fields of tt_news is fetched, i controlled it with a log-file. But the content was not written in the database ... I controlled the getter and setter in my configuration of news but all seems correct.
After some debugging i found that all commands which write the content in news are hardcoded in news/Classes/Domain/Service/NewsImportService.php:
$news->setAuthor($importItem['author']);
After adding my fields all works:
$news->setMyNewField($importItem['my_new_field']);
So my problem is fixed ... well some how: it seems dirty to change a class of an extension in order to handle individual fields.
Is there a correct possibility to make the import work with individual fields, without patching news?
Thanks!
In version 7 of tx_news i found the answer of my question ... i don't know wether it exists in older versions but in 7.1 it is possible to use a signal slot for this task:
link to the manual: Prehydrate slot