I searching translated versions of the tx_news translation files. When I open ext/news/Resources/Private/language/ all I find are the default (english) versions of the xlf Files.
I am sure there are translation files in other languages for tx_news, but I was not able to find them. How can I find them? Or can I get them somehow in the backend?
You can get them in the backend - there is the Language module in the menu, where you can set the list of languages for your installation, and download or update the translation files.
Just to be more complete. The translations are served by the translation server, therefore only the default translations are shipped with the extension itself.
As for the core and most extensions, translations are fetched by the Language module in the TYPO3 backend
Related
I am a maintainer of the TYPO3 extension QFQ.
Our extension accesses many of its files directly by links relative to index.php of TYPO3. For example it requests the following API file via JavaScript in the frontend:
/typo3conf/ext/qfq/Classes/Api/file.php
Since the upgrade to spoken URLs with TYPO3 v9 these relative paths stopped working. For example the above relative path would result in the following url when clicked on in the browser:
example.com/en/.../typo3conf/ext/qfq/Classes/Api/file.php
instead of:
example.com/typo3conf/ext/qfq/Classes/Api/file.php
We have seen that one can add static routes to single files in the TYPO3 backend (Sites > Edit > Static Routes > Create new) but this does not seem to allow us to set the whole extension directory /typo3conf/ext/qfq as a static route. Since many files are accessed this way, it is way too tedious to set a static route for every single fie on every installation of TYPO3 which uses our extension.
Our own "dirty" solution to this problem would be to add a new rewrite rule to the .htaccess which rewrites any url containing typo3conf/ext/qfq. It would remove any path before typo3conf.
My question is: Is there a better way to solve this problem? How do other extensions create links directly pointing to the files inside the extension directory? Are we missing something obvious?
I have a form with an Upload file field on a Kentico 9 website. Form files are currently stored in the default folder (BizFormFiles). I would like to store those files in a place where I can easily manage and delete them on the CMS. Would it be possible to store them automatically in a media library folder?
Thanks!
No, as far as I'm aware. It can't be configured this way. The only way to make this manageable via CMS interface is to develop a custom module with a custom interface.
I have created a new media library in my instance and then I have used that folder path as the custom form files folder in the Settings.
The form files are then placed inside this library folder in a subfolder. And then, I can also see the file in the Media library UI - just with the yellow exclamation mark that the files was not "imported" into the Kentico DB.
The only downside I see here is multi-site environment. While the media library is assigned to a particular site, the form files from all sites will be stored in that media library folder.
I build a TYPO3 Extension. And I use for the TypoScript Folder the Files as .ts. For the IDE PhpStorm is this better I use .ts.
But I see in other Extensions the File as .txt.
What is better?
There was a voting recently at decisions.typo3.org to agree on a file extension for TypoScript files.
This voting relates to how to distinguish between TSconfig (User + Page), TypoScript and defining best practices
to be used completely throughout the TYPO3 Core.
.typoscript was voted for by two thirds of participators. If it‘s really a decision and not a mere poll then that‘s what TYPO3 core will be heading for. Refer to the voting to see further details like how to distinguish between TypoScript and TSConfig.
You should use the file ending .typoscript for newer TYPO3 versions.
This was introduced in TYPO3 8.7, see changelog: Feature: #78161 - Introduce .typoscript file extension
Using .txt was deprecated in 9.3, see Changelog Deprecation: #81686 - Accessing core TypoScript with .txt file extension has been deprecated
As already mentioned, .ts is not such a good idea as it is used for Typescript.
See also the official TypoScript coding guidelines
I use the TypoScript Plug-In from Stefan Galinski in PhpStorm. In preferences I add the following file types:
*.t3c for Constants
*.t3s for Setup
*.ts for TSconfig
So I can load constants and setup files from same folder.
Template Constants
<INCLUDE_TYPOSCRIPT: source="DIR:fileadmin/TypoScript" extensions="t3c">
Template Setup
<INCLUDE_TYPOSCRIPT: source="DIR:fileadmin/TypoScript" extensions="t3s">
Page TSConfig
<INCLUDE_TYPOSCRIPT: source="DIR:fileadmin/TSconfig/Page" extensions="ts">
I have installed TYPO3 on my web server and it use the "Introduction Package" template.
The problem is that I have to work on another TYPO3 online website that use a custom template.
Can I obtain the template of the online website and use it on my local website? (to perform some test in local).
I saw that TYPO3 uses various templating systems and I do not know how this could affect the export\import operation. In Joomla or WP I simply take the template directory and then I copy it into the themes directory but I think that in TYPO3 this operation could be more complex.
The fastest way is to copy these directories:
fileadmin
uploads
typo3conf/ext
and the complete database, then you have "cloned" the original website locally. (assuming that the core stuff is loaded the default way, with symlinks)
Then you just need to edit the database connection stuff and maybe some paths for image magick and so on in the typo3conf/LocalConfiguration.php.
I use extension builder for creating my extensions in TYPO3 V 6.1.1. The default location where the extensions are stored is in typo3conf/ext/ folder.
I would like to change this location to some other path, say /MyExtensions/MyExtName. From this location I'll give symbolic links to ext/ folder.
The problem is changing the default location of extensions from typo3conf/ext/ to /MyExtensions/MyExtName.
How do I do this ?
EDIT
Is it possible to create a directory MyExtensions under typo3conf/ext/ and then MyExtensions will contain all my custom-made extensions. It's just that it'd be easy to have extensions organized this way. My custom extensions would be in typo3conf/ext/MyExtensions/MyExtOne , typo3conf/ext/MyExtensions/MyExtTwo etc...
That's not possible. Also do not try to circumvent the default typo3 paths but learn to live with them.
Create/Save the extension and copy&paste the content to the location you want to have them. Then create the symlink back to typo3conf/ext. It doesn't matter where the ExtensionBuilder writes the files when the target points to an other directory.