Getting started with woocommerce bookings
Check out the 30days free try out on the product page.
Getting started with woocommerce bookings
Check out the 30days free try out on the product page.
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
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
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/
iCloud Status: Inelegible
(iCloud Status: Nicht qualifiziert)
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
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
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" https://github.com/FluidTYPO3/flux/issues/478
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>
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?
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>
https://github.com/FluidTYPO3/flux/issues/478 https://forge.typo3.org/issues/57956
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
ENVIRONMENT
Typo3 6.2.14 + EXT:speciality v1.2.0-dev
PHP 5.5.18
Mac OS X Yosemite
PROBLEM
PHP Error:
Fatal error: Call to a member function getFileReferences() on a non-object in … /typo3/sysext/core/Classes/Resource/Service/FrontendContentAdapterService.php on line 90
CAUSE
This is where the fatal php error occurs
Why? Because self::getPageRepository() returns null instead of an object when content elements with images are involved (and EXT:speciality, EXT:fluidcontent, EXT:flux is used)
$files = self::getPageRepository()->getFileReferences($table, $migrateFieldName, $row);
SOLUTION/WORKAROUND
Replace above line with these lines
$dvsPageRepositoryObj = self::getPageRepository();
if ($dvsPageRepositoryObj) {
$files = $dvsPageRepositoryObj->getFileReferences($table, $migrateFieldName, $row);
} else {
// If $dvsPageRepositoryObj is null (e.g. not an object) return an empty array
$files = array();
}
ENVIRONMENT
Typo3 6.2.12 + EXT:speciality (fluidcontent_core, vhs, …)
PHP 5.5.18
Mac OS X Yosemite
PROBLEM
Make parts of your typo3 fluid template uncached. E.g. disable the cache for them, without using “no_cache” or USER_INT or COA_INT.
Why? To display different FLUID templates for mobile and desktop clients. Or simply to display the current time on the website.
CAUSE
The fluid template engine offers no native command to uncache partials.
SOLUTION
Install this Extension: “vhs”
Get it here: http://typo3.org/extensions/repository/view/vhs
It provides a viewhelper called “render.uncache”, that allows uncaching of partial.
See https://fluidtypo3.org/viewhelpers/vhs/2.1.4/Render/UncacheViewHelper.html for more information.
USAGE
<v:render.uncache section="MySection" partial="MyPartial" arguments="{_all}"/>
RELATED
http://lists.typo3.org/pipermail/typo3-project-typo3v4mvc/2012-September/012878.html
http://typo3.3.n7.nabble.com/Do-not-cache-part-of-Fluid-template-How-to-td251880.html
You must be logged in to post a comment.