Skip to content

Typo3 – Powermail – Deutsche Uebersetzung wird ignoriert

PROBLEM
====================
Deutsche Uebersetzung in 
EXT:powermail/Resources/Private/Language/de.locallang.xlf
wird ignoriert


URSACHE
====================
Es wird die globale Übersetzung in 
typo3conf/l10n/de/powermail/Resources/Private/Language/de.locallang.xlf
verwendet


LÖSUNG 1
====================
Keine Lösung via XLF-Datei
- Die Uebersetzungshierarchie scheint so zu sein. 
- Andererseits sollte man auch keine eigene de.locallang.xls in EXT:powermail anlegen, weil sie beim nächsten Update von Powermail verloren geht. 
- Für FLUID Templates kann man die Varianten auslagern. Wie geht das für Language files?

LÖSUNG 2
====================
Via Typoscript geht es natürlich

plugin.tx_powermail {
        _LOCAL_LANG.default.validationerror_mandatory = Please insert a value
        _LOCAL_LANG.de.validationerror_mandatory = Bitte Pflichtfeld ausfüllen
}
https://docs.typo3.org/typo3cms/extensions/powermail/ForAdministrators/GoodToKnow/ChangingLabels/Index.html

Dass es mir dabei die chinesischen Zeichen im Frontend nicht mehr richtig anzeigt liegt wohl eher an einem anderen Problem (DB/UTF-8/bytes per char)



WORKAROUND 1
====================
DE-DE
Die globale Übersetzung für DE nicht installieren
(Typo3 Backend > Admin Tools > Sprachen)

ZH-CN
EXT:powermail/Resources/Private/Language/zh.locallang.xlf
anlegen. Dann werden die chinesischen Zeichen nicht zerhauen.


ENVIRONMENT
====================
Typo3 6.2.18, Powermail 2.4.3, php 5.5

Download statically linked imageMagick 6.x

Original post
http://lists.typo3.org/pipermail/typo3-german/2010-January/065202.html

Original download
http://typo3.camlann.de/imagemagick-6.5.9-0-static-i386.tgz

Alternative download
https://www.sendspace.com/file/y12lpo

realUrl: Allow chinese chars in url

Add this to your realUrl configuration

array (
   'init' =>
      array (
         ...
         // Allow chinese chars in url
         // otherwise realUrl converts all to ASCII
         'enableAllUnicodeLetters' => true,
         'doNotRawUrlEncodeParameterNames' => true,
         ...
      ),
      ...

Links
http://www.arxia.com/blog/2012/09/how-to-configure-a-typo3-website-for-arabic-language/

iTunes > iCloud Status: Inelegible > Bitrate

PROBLEM

iCloud Status: Inelegible
(iCloud Status: Nicht qualifiziert)

CAUSE

  • song file is larger than 200 MB
  • song is longer than two hours
  • song was encoded at 96 Kbps or less

In my case, it was the last cause:
Song was encoded at 96 Kbps or less.
I.e. is were some mp3 files of an audiobook, encoded at 64 Kbps

SOLUTION

Change the encoding.

To fix this in the terminal:
Install lame (e.g. brew install lame)

For one mp3 file

lame --mp3input -b 96 ./in/001.mp3 ./out/001.mp3

For many mp3 files

# Encode with 96 Kbps, or ...
for f in *.mp3 ; do lame --mp3input -b 96 "$f" ../out/"$f" ; done

# ...encode with 128 Kbps
for f in *.mp3 ; do lame --mp3input -b 128 "$f" ../out128/"$f" ; done

LINKS

https://support.apple.com/en-us/HT203564
https://support.apple.com/de-de/HT203564
http://lame.cvs.sourceforge.net/viewvc/lame/lame/USAGE

Error message in typo3 backend: “Wrong configuration in table xxx”

PROBLEM

Error message in typo3 backend: "Wrong configuration in table xxx"
https://github.com/FluidTYPO3/flux/issues/478

CAUSE

You want to use an image via FAL in your extension with the following code
<flux:form.section name="slides">
    <flux:form.object name="slide">
        <flux:field.inline.fal name="settings.images" multiple="FALSE" maxItems="1"/>
    </flux:form.object>
</flux:form.section>

SOLUTION

This is a bug in the typo3 core. 
https://forge.typo3.org/issues/57956
There is no solution as of typo3 version 6.2.14 or 6.2.15.
Maybe it will be fixed in later versions?
Maybe it is fixed in typo3 version 7.x?

WORKAROUND

Don't use image via FAL in your extension.
Use the old, legacy approach, given in the following code

<flux:form.section name="slides">
    <flux:form.object name="slide">
        <flux:field.file name="image" label="Bild" allowed="jpg, jpeg, png, gif" maxItems="1" showThumbnails="1"/>
    </flux:form.object>
</flux:form.section>

LINKS

https://github.com/FluidTYPO3/flux/issues/478
https://forge.typo3.org/issues/57956

How to create a new extension for a fluid powered typo3 content element

Summary
===========================================================================
-Create the new extension with "builder", not "extension-builder"
-Use flux in fluid templates for functionality


Prerequisites
===========================================================================
1. Install typo3 6.2.x
2. Install fluid powered typo3 extensions
3. Install extension "builder"


Step 1/4 - Create skeleton of the extension
===========================================================================
1. Login to typo3 backend
2. Click on Admin tools > Builder (not "Extension-Builder")
3. Create new extension 

Extension key
test

Author name and email
<test@example.org>

Brief title
Test title

Brief description
Test description


Toggles
[ ] Include page templates 
[X] Include content templates
[ ] Include backend module templates
[ ] Create controllers for enabled FluidTYPO3 features
[X] Set the VHS extension as dependency

Build behavior
[ ] Dry run - do not build actual files
[ ] Be verbose about actions taken 



Step 2/4 - Install the extension
===========================================================================
Install the extension in the extension manager. 


Step 3/4 - Refine the FLUID Templates
===========================================================================
Add label, description and group to the flux:form.

label       = "Test FE Plugin" --> This will be shown, in the new content element wizard
description = "Bla bla bla..." 
options     = "{group: 'FCE'}" --> In which tab in the new content element wizard

FILE
typo3conf/ext/test/Resources/Private/Templates/Content/Example.html

CODE
    ...
    <f:section name="Configuration">
        <flux:form id="foo" label="Test4 FE Plugin" description="Bla bla bla..." options="{group: 'FCE'}">
            ...
        </flux:form>
    </f:section>
    ...


Step 4/4 - Add some fields
===========================================================================
FILE
typo3conf/ext/test/Resources/Private/Templates/Content/Example.html

CODE
    ...
    <f:section name="Configuration">
        <flux:form id="example" label="Test4 FE Plugin" description="Bla bla bla..." options="{group: 'FCE'}">

            <flux:field.text name="settings.myCopy" label="My copy" enableRichText="true" defaultExtras="richtext[bold|italic|link]:rte_transform[flag=rte_enabled|mode=ts_css]"/>
            <flux:field.checkbox name="settings.myCheckbox" label="My checkbox" requestUpdate="TRUE"/>

        </flux:form>
    </f:section>
    ...

DOWNLOADS
test5.zip 
http://www.filedropper.com/test5_1

REFERENCES & THANKS GO TO
https://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/content-element.html
https://jkphl.is/articles/dating-fluid-powered-typo3/

TASK
Enable custom rte configuration for EXT:speciality, Version 1.2.0-dev in Typo3 6.2.14

HOWTO
Add this code to EXT:speciality/ext_tables.php

# Add Page TSConfig
$pageTsConfig = \TYPO3\CMS\Core\Utility\GeneralUtility::getUrl(
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::extPath($_EXTKEY) . 'Configuration/TsConfig/Page/config.ts'
);
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPageTSConfig($pageTsConfig);

VERIFY THE NEW PAGETS SETTINGS

  • Log in to typo3 backend
  • Goto Web > Info > Page-TSconfig
  • Make sure, your new settings appear there

ENVIRONMENT
Typo3 6.2.14 + EXT:speciality v1.2.0-dev
PHP 5.5.18
Mac OS X Yosemite

Follow

Get every new post delivered to your Inbox.

Join 89 other followers