I have a set of languages that I would like to be visible in the Language Grid under http://localhost:4502/libs/cq/i18n/translator.html. I am following the directions given here at the URL http://docs.adobe.com/docs/en/aem/6-0/develop/components/i18n/translator.html under "Managing Supported Languages". The issue is when I am trying to add the property "languages" to the node /etc/languages, the AEM is showing a red mark with the message "No property definition found." I am using AEM 6. How do I go about this ?
Thanks in advance
Just create a sling:folder instead of nt:folder.
Related
I tried to translate the Content Fragment content but that content is not sent for translation.
Let's take an example, suppose, we have a Content fragment model, named "Press Release" and there are 2 fields "title" and "description". Once we create a content fragment based on the "Press Release" model and Create a Translation project then content fragment fields are not going for translation,
I am using AEM 6.5.12.0 version,
I tried to add some translation rules but that also does not help, I am sure there are some issues with writing a Translation rule for translating against the Content Fragment Model.
Can anyone please help me with this?
First did you create the target language folder in the assets? it is necessary for AEM to know where it needs to create the target.
Assets language structure
How do you add translation rules?
for title and description the properties in translation config UI should be: jcr:title and jcr:description
Translation config UI
Check this file in the CRXde /conf/global/settings/translation/rules/translation_rules.xml that:
is at after
you have those 2 properties under content/dam
hope it will help
Seb
I have to implement a media download feature. The backend user should be able to upload a media file, set the title, description, release date and so on... The result should then be visible and the file available for download in the frontend.
I am not sure what is the best way to achieve this: Plugin or Custom content element ?
Whats the main difference between the two and what would be the best solution for my task ?
Plugins are used for more complex rendering of records with different views (for example a list and a detail view of records stored somewhere in a storage folder). A custom content element (CE) should be preferred if all relevant data is stored in the record.
For your case, a Content Element seems to be the right solution. This kind of custom content elements can also be easily created with helpful extensions like "mask" which may takes you 10 minutes to create a custom CE.
https://typo3.org/extensions/repository/view/mask
If I understood you properly.
You can define plugin as type of "list_type", or as "CType" (if you need to code specific function, which is hard or unable to achieve using eg. Fluid contents) or even as another menu type defined as "menu_type".
These all types can be the same way made plugin, this separation for types are basically only for making it appear in different selectors. So:
your plugin defined as menu_type is to be selected in "Special Menus" content type in "Menu type" selector,
defined as list_type (so called) is to be selected in "Insert Plugin" content in "Selected plugin" selector,
defined as CType is totally new content type.
But they work the same way and this is easily to be switched using parameter in ext_tables plugin register call:
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPlugin( ['Label', $_EXTKEY.'_myPluginSuffix'], 'CType');
1) You can use the "File Link" content element and adapt its TypoScript (tt_content.uploads.20.renderObj) to your needs.
2) You can use the file_list extension and adapt its Fluid templates to your needs
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.
I'm writing a menu bar made up of icons.
The easiest way, in my opinion, is relying on the icon attribute of the ace:menuItem component.
Unfortunately, I couldn't find, neither in the showcase nor in the documentation, a complete list of the built-in values allowed for that attribute (i.e. ui-icon, ui-icon-contact etc.).
Where could I find it? In case there isn't such a list, how could I work it out?
You can check the source of the page, then open theme.css
Have a look at:
http://jquery-ui.googlecode.com/svn/tags/1.6rc5/tests/static/icons.html
I want to display a text field with the description of the transition, not only input fields. Where can i configure it?
Regards!
João.
You might use the JIRA Toolkit plugin to create a message custom field which are used "to add arbitrary HTML to edit and view pages"
https://plugins.atlassian.com/plugin/details/5142
Given that it supports velocity, it should be possible to retrieve the description of the transition from the context ...
AbstractWorkflowTransition.getDescription()