When I am hiding a layout in German language it gets contents from default language (English). Its not hiding in German language.
In the above image I have made it hidden. But when I run a page in German language the default english content is loaded for this layout
Typo3 Version : 4.7.4
Extension is Grid Element
Any idea on this?
The behavior you are describing is intended. When you hide a translation of the page, the default language is shown (because there is no translation). To hide the page if no translation exists, there is an option called "Hide page if no translation for current language exists" in the page properties.
If you want this behavior to be true for all your pages, you can also add this to your localconf.php in the typo3conf folder:
$TYPO3_CONF_VARS['FE']['hidePagesIfNotTranslatedByDefault'] = '1';
Checkout the settings for sys_language_mode. The documentation is for version 8 but it should work for version 4.7, too.
https://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Config/Index.html#sys-language-mode
Related
There are options to select an language from the list of Language in my application i.e. English, Gujarati, Hindi.
After the selection, all the texts inside app should change and display according to language selection.
Note that This is not normal localisation (means selecting language from settings and then it reflects in app)
The question is How can I change the text content according to selected value of Language?
Thanks.
You can use this article: https://medium.com/#podcoder/flutter-localization-a39402757a42 (https://github.com/podcoder/flutter_localization)
This is an easy way to localize an application without using the system language.
Hope this helps.
I am currently using this method and it works very well.
We have an extension in TYPO3 8.7, which we're updating to TYPO3 10.4. One thing the extension does is alter the page tree in the backend so for some page types a different field than title is shown. For TYPO3 8 we're using a hook for that: $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['t3lib/tree/pagetree/class.t3lib_tree_pagetree_dataprovider.php']['postProcessCollections'] where we could loop through the page tree nodes, check the doktype and replace the text.
The page tree has been completely rewritten in TYPO3 9, so this hook doesn't exist anymore. I've looked in the new TYPO3\CMS\Backend\Controller\Page\TreeController class, but don't see any Signal Slot or PSR-14 event in that class we can use.
Is there a way to manipulate the page tree in this way in TYPO3 10?
If you use the Navigation Title field (nav_title) provided by TYPO3 out of the box, you can use the Page TSConfig option showNavTitle to prefer that in the page tree if set for a page:
pageTree {
showNavTitle = 1
}
If nav_title is empty, the regular title is shown instead.
How can one play around with TypoScript code shown in documentations about TypoScript?
Tested with a local Typo3 test instance, Typo3 version 9.5.5, Official Introduction Package installed.
In the backend, create a new page in the tree. Rightclick -> enable it (the red overlay should disappear). Make sure it is selected in the tree.
Click on the blue Template button on the left. Usually it will show you the blue No Template message.
Make sure on the top Info/Modify is selected from the drop down.
Click the gray + (New record) button under the drop down.
On the bottom, click Edit the whole template record.
Optionally give it a speaking template and website title, like 'Playaround' and 'Play Around'.
Optionally, under tab Options -> Clear, select Constants and Setup - this will clear everything this Template has inherited from parent templates, but will also disable the debug infos at the bottom of the frontend for this page (if you have installed the Official Introduction Package).
Under the tab General -> text entry Setup, enter the following TypoScript:
page = PAGE
page.10 = TEXT
page.10.value = Hello World
press the Save and then the View button.
A new tab opens, showing you the frontend for your page, printing the text 'Hello World'.
Now you can play around with the code examples given in eg. the TypoScript Reference.
Funnily enough, I just found out that Typoscript is by definition not a programming language, but a configuration description. That's why Typo3 is needed as a substructure for this, I think. There seem to be online demos of Typo3 on the net, but I don't know whether they are up to date and whether you can test TypoScript there. Therefore access local containers / installations as suggested. Or if the possibility exists a dev subdomain.
When adding a certain tyle of link in TYPO3 RTE. We always have to resize the wizard window because we can't see all the options on the right.
Is there a way to set the height and width of the RTE wizard in TYPO3 when adding a link ?
Current setup:
- TYPO3 7.6.23
The following code has to be inserted in the field "Page TSConfig" in the page-properties of the root-page, then the configuration is available for all pages.
After saving the windows to create / modify links have the defined size.
The numbers can be adjusted to the own needs but is then configured for all users.
RTE.default {
buttons.link.dialogueWindow.width = 800
buttons.link.dialogueWindow.height = 800
}
To adjust the windows related to further buttons the lines can be copied and then link has to be replaced by the name of the button.
A full list can be found here:
https://docs.typo3.org/typo3cms/extensions/rtehtmlarea/Configuration/PageTsconfig/interfaceConfiguration/Index.html#showbuttons
An explanation of all options related to buttons.[ button-name ].dialogueWindow can be found here. Scroll down to see all the options, they're listed and explained one by one.
In typo3 4.7 (cannot upgrade this instance) I often need to put a few lightweight extensions on one page. In the backend, I quickly lose track of all these extensions.
I wonder if there is a way to attach a label to such an extension placeholder.
I want a similar functionality as the freetext field: "Name (not visible in frontend)" which is available for "Default HTML" content elements, but not for "Plugin" content elements.
Here is an illustration of what I mean. In the backend, WEB Module/Page, editing any page:
... or can they?
Answering my own question:
The "Behavior" tab contains a deprecated textfield "Plugin Mode" that can be used as a label. Internally the value from this field will be stored in a column called "CODE".
According to the context-sensitive help for this field, it can function aas a label unless the plugin uses this value.
And indeed, the text from the 2nd red box above appears in the backend and facilitates orientation.
But here I am talking about my own extensions where I know that this field is unused.