Re: [TYPO3-english] Formhandler localization problem. Typo3 6.1.5
Hi Andrei,
this may be a silly question, but is the page with the form translated
to the other languages?
Regards,
Reinhard
Am 26.11.2013 09:03, schrieb Andrei Shishkin:
Hello.
Have 3 languages, setup:
config {
linkVars = L
sys_language_uid = 0
uniqueLinkVars = 1
language = en
locale_all = en_EN
sys_language_overlay = 1
sys_language_mode = ignore
htmlTag_langKey = en-EN
}
[globalVar = GP:L=1]
config {
sys_language_uid = 1
language = id
locale_all = id_ID
htmlTag_langKey = id-ID
}
[global]
[globalVar = GP:L=2]
config {
sys_language_uid = 2
language = ru
locale_all = ru_RU
htmlTag_langKey = ru-RU
}
[global]
Menus and content translating works good. Trying to use formhandler
extention for organise contact form. Installing it like said in
www.typo3-formhandler.com/documentation/articles-howtos/b/how-to-set-up-a-simple-form/
using xml langFile, with this sructure:
?xml version=1.0 encoding=utf-8 standalone=yes ?
T3locallang
meta type=array
descriptionLanguage labels for my form/description
/meta
data type=array
languageKey index=default type=array
label index=error_message_requiredEnglish/label
/languageKey
languageKey index=id type=array
label index=error_message_requiredIndonasian/label
/languageKey
languageKey index=ru type=array
label index=error_message_requiredRussian/label /languageKey
/data
/T3locallang
As result - default english version works, russian version - works.
Indonesian - NO. It just do not whant to take translation from
languageKey index=id type=array section. In the same time all site
showing indonesian version of the site, but formhandler showing default
version of lang, english. What can do to solve this problem?
Thanks for looking.
--
http://www.typo3-formhandler.com
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Formhandler localization problem. Typo3 6.1.5
It seems my last message got lost, so here it is again:
Hi Andrei,
I did a little research:
***
* Problem:
***
I found out that TYPO3 can only translate messages in language files
using a known language.
Currently, these languages are set in
typo/sysext/core/Classes/Localization/Locales.php:
'default' = 'English',
'af' = 'Afrikaans',
'ar' = 'Arabic',
'bs' = 'Bosnian',
'bg' = 'Bulgarian',
'ca' = 'Catalan',
'ch' = 'Chinese (Simpl.)',
'cs' = 'Czech',
'da' = 'Danish',
'de' = 'German',
'el' = 'Greek',
'eo' = 'Esperanto',
'es' = 'Spanish',
'et' = 'Estonian',
'eu' = 'Basque',
'fa' = 'Persian',
'fi' = 'Finnish',
'fo' = 'Faroese',
'fr' = 'French',
'fr_CA' = 'French (Canada)',
'gl' = 'Galician',
'he' = 'Hebrew',
'hi' = 'Hindi',
'hr' = 'Croatian',
'hu' = 'Hungarian',
'is' = 'Icelandic',
'it' = 'Italian',
'ja' = 'Japanese',
'ka' = 'Georgian',
'kl' = 'Greenlandic',
'km' = 'Khmer',
'ko' = 'Korean',
'lt' = 'Lithuanian',
'lv' = 'Latvian',
'ms' = 'Malay',
'nl' = 'Dutch',
'no' = 'Norwegian',
'pl' = 'Polish',
'pt' = 'Portuguese',
'pt_BR' = 'Brazilian Portuguese',
'ro' = 'Romanian',
'ru' = 'Russian',
'sk' = 'Slovak',
'sl' = 'Slovenian',
'sq' = 'Albanian',
'sr' = 'Serbian',
'sv' = 'Swedish',
'th' = 'Thai',
'tr' = 'Turkish',
'uk' = 'Ukrainian',
'vi' = 'Vietnamese',
'zh' = 'Chinese (Trad.)'
As you can see, there is no 'id' = 'Indonesian'.
***
* How to fix it:
***
Fortunately, you can set additional languages in ext_localconf.php in a
custom extension (or in AdditionalConfiguration.php):
$TYPO3_CONF_VARS['SYS']['localization']['locales']['user']['id'] =
'Indonesian';
Unfortunately, this setting is not taken into account because of a bug
in
typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php:
This block:
$locales =
\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\Localization\\Locales');
// Language is found. Configure it:
if (in_array($this-lang, $locales-getLocales())) {
$this-languageDependencies[] = $this-lang;
foreach ($locales-getLocaleDependencies($this-lang) as
$language) {
$this-languageDependencies[] = $language;
}
}
Should look like this:
$locales =
\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\Localization\\Locales');
$locales-initialize();
// Language is found. Configure it:
if (in_array($this-lang, $locales-getLocales())) {
$this-languageDependencies[] = $this-lang;
foreach ($locales-getLocaleDependencies($this-lang) as
$language) {
$this-languageDependencies[] = $language;
}
}
As you can see, the line $locales-initialize(); was missing.
***
* Conclusion:
***
I will have a look, if this bug still exists in the GIT repository and
request a fix then.
So, this has nothing to do with Formhandler, but with the translation
handling of TYPO3.
Regards,
Reinhard
Am 26.11.2013 09:03, schrieb Andrei Shishkin:
Hello.
Have 3 languages, setup:
config {
linkVars = L
sys_language_uid = 0
uniqueLinkVars = 1
language = en
locale_all = en_EN
sys_language_overlay = 1
sys_language_mode = ignore
htmlTag_langKey = en-EN
}
[globalVar = GP:L=1]
config {
sys_language_uid = 1
language = id
locale_all = id_ID
htmlTag_langKey = id-ID
}
[global]
[globalVar = GP:L=2]
config {
sys_language_uid = 2
language = ru
locale_all = ru_RU
htmlTag_langKey = ru-RU
}
[global]
Menus and content translating works good. Trying to use formhandler
extention for organise contact form. Installing it like said in
www.typo3-formhandler.com/documentation/articles-howtos/b/how-to-set-up-a-simple-form/
using xml langFile, with this sructure:
?xml version=1.0 encoding=utf-8 standalone=yes ?
T3locallang
meta type=array
descriptionLanguage labels for my form/description
/meta
data type=array
languageKey index=default type=array
label index=error_message_requiredEnglish/label
/languageKey
languageKey index=id type=array
label index=error_message_requiredIndonasian/label
/languageKey
languageKey index=ru type=array
label index=error_message_requiredRussian/label /languageKey
/data
/T3locallang
As result - default english version works, russian version - works.
Indonesian - NO. It just do not whant to take translation from
languageKey index=id type=array section. In the same time all site
showing indonesian version of the site, but formhandler showing default
version of lang, english. What can do to solve this problem?
Thanks for looking.
--
http://www.typo3-formhandler.com
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Formhandler localization problem. Typo3 6.1.5
And here are the links to be issue on Forge [1] and the RFC [2].
[1] http://forge.typo3.org/issues/53973
[2] https://review.typo3.org/#/c/25685/
Regards,
Reinhard
Am 26.11.2013 11:42, schrieb Reinhard Führicht:
It seems my last message got lost, so here it is again:
Hi Andrei,
I did a little research:
***
* Problem:
***
I found out that TYPO3 can only translate messages in language files
using a known language.
Currently, these languages are set in
typo/sysext/core/Classes/Localization/Locales.php:
'default' = 'English',
'af' = 'Afrikaans',
'ar' = 'Arabic',
'bs' = 'Bosnian',
'bg' = 'Bulgarian',
'ca' = 'Catalan',
'ch' = 'Chinese (Simpl.)',
'cs' = 'Czech',
'da' = 'Danish',
'de' = 'German',
'el' = 'Greek',
'eo' = 'Esperanto',
'es' = 'Spanish',
'et' = 'Estonian',
'eu' = 'Basque',
'fa' = 'Persian',
'fi' = 'Finnish',
'fo' = 'Faroese',
'fr' = 'French',
'fr_CA' = 'French (Canada)',
'gl' = 'Galician',
'he' = 'Hebrew',
'hi' = 'Hindi',
'hr' = 'Croatian',
'hu' = 'Hungarian',
'is' = 'Icelandic',
'it' = 'Italian',
'ja' = 'Japanese',
'ka' = 'Georgian',
'kl' = 'Greenlandic',
'km' = 'Khmer',
'ko' = 'Korean',
'lt' = 'Lithuanian',
'lv' = 'Latvian',
'ms' = 'Malay',
'nl' = 'Dutch',
'no' = 'Norwegian',
'pl' = 'Polish',
'pt' = 'Portuguese',
'pt_BR' = 'Brazilian Portuguese',
'ro' = 'Romanian',
'ru' = 'Russian',
'sk' = 'Slovak',
'sl' = 'Slovenian',
'sq' = 'Albanian',
'sr' = 'Serbian',
'sv' = 'Swedish',
'th' = 'Thai',
'tr' = 'Turkish',
'uk' = 'Ukrainian',
'vi' = 'Vietnamese',
'zh' = 'Chinese (Trad.)'
As you can see, there is no 'id' = 'Indonesian'.
***
* How to fix it:
***
Fortunately, you can set additional languages in ext_localconf.php in a
custom extension (or in AdditionalConfiguration.php):
$TYPO3_CONF_VARS['SYS']['localization']['locales']['user']['id'] =
'Indonesian';
Unfortunately, this setting is not taken into account because of a bug
in
typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php:
This block:
$locales =
\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\Localization\\Locales');
// Language is found. Configure it:
if (in_array($this-lang, $locales-getLocales())) {
$this-languageDependencies[] = $this-lang;
foreach ($locales-getLocaleDependencies($this-lang) as
$language) {
$this-languageDependencies[] = $language;
}
}
Should look like this:
$locales =
\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\Localization\\Locales');
$locales-initialize();
// Language is found. Configure it:
if (in_array($this-lang, $locales-getLocales())) {
$this-languageDependencies[] = $this-lang;
foreach ($locales-getLocaleDependencies($this-lang) as
$language) {
$this-languageDependencies[] = $language;
}
}
As you can see, the line $locales-initialize(); was missing.
***
* Conclusion:
***
I will have a look, if this bug still exists in the GIT repository and
request a fix then.
So, this has nothing to do with Formhandler, but with the translation
handling of TYPO3.
Regards,
Reinhard
Am 26.11.2013 09:03, schrieb Andrei Shishkin:
Hello.
Have 3 languages, setup:
config {
linkVars = L
sys_language_uid = 0
uniqueLinkVars = 1
language = en
locale_all = en_EN
sys_language_overlay = 1
sys_language_mode = ignore
htmlTag_langKey = en-EN
}
[globalVar = GP:L=1]
config {
sys_language_uid = 1
language = id
locale_all = id_ID
htmlTag_langKey = id-ID
}
[global]
[globalVar = GP:L=2]
config {
sys_language_uid = 2
language = ru
locale_all = ru_RU
htmlTag_langKey = ru-RU
}
[global]
Menus and content translating works good. Trying to use formhandler
extention for organise contact form. Installing it like said in
www.typo3-formhandler.com/documentation/articles-howtos/b/how-to-set-up-a-simple-form/
using xml langFile, with this sructure:
?xml version=1.0 encoding=utf-8 standalone=yes ?
T3locallang
meta type=array
descriptionLanguage labels for my form/description
/meta
data type=array
languageKey index=default type=array
label index=error_message_requiredEnglish/label
/languageKey
languageKey index=id type=array
label index=error_message_requiredIndonasian/label
/languageKey
languageKey index=ru type=array
label index=error_message_requiredRussian/label /languageKey
/data
/T3locallang
As result - default english version works, russian version - works.
Indonesian - NO. It just do not whant to take translation from
languageKey index=id type=array section. In the same time all site
showing indonesian version of the site, but formhandler showing default
version of lang, english. What can do to solve this problem?
Thanks for looking.
--
http://www.typo3-formhandler.com
Re: [TYPO3-english] Formhandler - multistep form question
Hi Adrian, Am 02.08.2012 09:59, schrieb Adrian Marcinkowski: Hi Everyone, I have made a form with 4 steps. Is it possible to configure the formhandler in that way: 1 step - form on home page (id=1) 2 step - form is redirect to another page with id=12 3,4 step - rest steps of form is on page id=12 Thanks for any help. Adrian you can't do this with only one form. You would have to build two forms: * The one on ID 1 redirects to ID 12 (Finisher_Redirect) passing the parameters along. * The second form on ID 12 loads the parameters (PreProcessor_LoadGetPost) so that they are usable in the form. Regards, Reinhard ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Formhandler and validating generic radio buttons
Hi Michael,
Am 17.05.2012 16:12, schrieb Michael Lykke:
I create the field in step1.html like this:
###master_radio-yesno_question1###
Which generates this markup:
div class=type-check
label for=radio-yesno-question1-yesSome question? /label
div
input type=radio id=radio-yesno-question1-yes
name=form-multistep[radio-yesno-question1] value=Yes
label for=radio-yesno-koncert-yesYes/label
/div
div
input type=radio id=radio-yesno-question1-no
name=form-multistep[radio-yesno-question1] value=No
label for=radio-yesno-question1-noNo/label
/div
/div
And validating it like this:
1.validators {
1.class = Validator_Default
1.config.fieldConf {
question1.errorCheck {
1 = required
}
}
}
Can anyone help, please?
If the generated field has the name radio-yesno-question1 shouldn't
the validator config look like this?
1.validators {
1.class = Validator_Default
1.config.fieldConf {
radio-yesno-question1.errorCheck {
1 = required
}
}
}
Regards,
Reinhard
--
http://www.typo3-formhandler.com
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] jumpurl.secure files lager 10mb
Hi Gernot, Am 19.04.2012 15:24, schrieb Gernot Hofer: Hello List! i use a password secure file download like: jumpurl = 1 jumpurl.secure = 1 here i have the problem, when a file (zip, exe,...) is lager than10mb, i get a download of 0 bytes. when i set: jumpurl = 1 jumpurl.secure = 0 it works. is the problem a wrong server configuration or a bug with the .secure feature? I had this behavior once. The problem was that the memory limit was too low. PHP needs to load the file completely before returning it. This seems to need a lot of memory for larger files. For details have a look here: http://stackoverflow.com/questions/5249279/file-get-contents-php-fatal-error-allowed-memory-exhausted Kind regards, Reinhard -- http://www.typo3-formhandler.com ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] EXT:formhandler :: 500 internal server error when using loggers with Interceptor_AntiSpamFormTime.
Hi Roland
Am 12.03.2012 14:42, schrieb Roland:
hi everybody,
i have some problems with logging of spam while using EXT:formhandler -
this is the not working part of my typoscript configuration of the
formhandler plugin:
plugin.Tx_Formhandler.settings.predef.singlestep_example {
saveInterceptors {
1 {
class = Interceptor_AntiSpamFormTime
config {
minTime {
value = 15
unit = seconds
}
}
loggers {
1 {
class = Tx_Formhandler_Logger_DB
}
}
}
}
}
if i submit the form in less than 15 seconds i get a 500 internal server
error message. without the loggers configuration part everything works
great - exept the logging of course.
after some investingation it seems that the error is produced in line 38
of Tx_Formhandler_AbstractInterceptor.php.
i use TYPO3 4.6.4 and EXT:formhandler 1.2.0.
what goes wrong here?
kind regards.
roland
This seems to be a bug in Formhandler. The line you mentioned is:
$this-utilityFuncs-Message('calling_class', array($className));
This is wrong because the method Message() doesn't exist.
It should be:
$this-utilityFuncs-debugMessage('calling_class', array($className));
I created a ticket for myself in the bug tracker on Forge [1].
Regards,
Reinhard
[1] http://forge.typo3.org/issues/34754
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] formhandler, value.current, CASE...understanding problems
Hi Sören
Am 10.02.2012 15:36, schrieb Sören Kracker:
Thank you Reinhard,
but this means, that it's not possible to do something like my
switch/case depending on the value except using a userfunction? Is that
right? A plain example: value can be A or B (nothing else), I want to
change it to C (if it's A) and to D (if it's B).
I haven't tested it, but something like this should be possible:
mydbfield {
preProcessing = TEXT
preProcessing {
value =
stdWrap.cObject = CASE
stdWrap.cObject {
key.data = GP:myvar
val1 = TEXT
val1.value = a
val2 = TEXT
val2.value = b
}
}
mapping = myvar
}
Of course, if you have set a formValuesPrefix in your TS, then
GP:myvar should probably be GP:prefix|myvar.
Regards,
Reinhard
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] formhandler, value.current, CASE...understanding problems
Hi Sören,
Am 09.02.2012 15:01, schrieb Sören Kracker:
Hi list,
Seems that, the current value isn't present there.
Another question regarding formhandler and this example: Is it somehow
possible to get the values using .field? Something like that (which is
not working):
I think the answer to both questions is that Formhandler sets value to
the value of the field configured in mapping automatically.
Additionally, current isn't set by Formhandler because of this reason.
So, f.e. in this case:
mydbfield {
preProcessing = TEXT
preProcessing {
wrap = asdf|asdf
}
mapping = myvar
}
The TS which Formhandler creates looks like this:
mydbfield {
preProcessing = TEXT
preProcessing {
value = Value of the field myvar
wrap = asdf|asdf
}
mapping = myvar
}
If you set the value yourself in TS, Formhandler will not set it
automatically.
Regards,
Reinhard
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] formhandler
On 06.12.2011 14:30, Lamb, Brian wrote:
Hi all,
I'm migrating from the old mailformplus extension to the new formhandler
extension. I've been using the website http://www.typo3-formhandler.com/ which
has a good bit of documentation but it doesn't quite answer all of my questions.
With mailformplus, I could call a PHP script when the form was submitted like
so,
plugin.tx_thmailformplus_pi1.saveUserFunc =
fileadmin/template/main/scripts/php/class.form_processing.inc:form_processing-post_process
Is there a way to do that with formhandler? I can replicate most of what that
script does with TS but not everything and I think it would be easier to set a
couple of the variables like where the email goes inside a PHP script.
That leads me to my next question. On
http://www.typo3-formhandler.com/documentation/articles-howtos/a/how-to-set-up-a-multistep-form-with-conditions/,
it demonstrates how you can use conditionals to set different variables. My
question is is this specific to formhandler or can this just general
typoscript. Either way, if there is more documentation about this, that would
be fantastic. I have something in place but it seems very convoluted and there
has to be a better way to do it that the way I'm doing it. Specifically, I'm
looking to set up an if, else/if, else/if, else/if, else type structure.
Thanks for all the assistance.
Brian Lamb
Hi Brian,
as Stano said, you have to write your own saveInterceptor.
The easiest way to do this:
* Create the interceptor somewhere in fileadmin (e.g.
fileadmin/script/Tx_Formhandler_Interceptor_MyInterceptor).
* Write the PHP code:
class Tx_Formhandler_Interceptor_MyInterceptor extends
Tx_Formhandler_AbstractInterceptor {
public function process() {
print $this-settings['param1'];
return $this-gp
}
}
* Tell Formhandler where to search for custom components:
plugin.Tx_Formhandler.settings(.predef.myForm) {
additionalIncludePaths.1 = fileadmin/scripts/
}
* Use the class:
plugin.Tx_Formhandler.settings(.predef.myForm) {
saveInterceptors {
1 {
class = Interceptor_MyInterceptor #You can omit the Tx_Formhandler_
config {
param1 = asdf
}
}
}
}
As you can see, the settings made in the config section of the
interceptor are available in $this-settings in the PHP code.
The submitted data is accessible in $this-gp.
Make sure the interceptor returns $this-gp or your form will not work
anymore.
Regarding the if/else config for Formhandler:
This is no standard TypoScript code. This is for Formhandler only.
I hope this helps.
Regards,
Reinhard
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] mailformplus - change mail address
Hi, On 01.12.2011 12:25, Kay Obermueller wrote: Nevertheless at some place also mailformplus must listen to typoscript. But where? I think it depends. In older versions of mailformplus, there was no possibility to configure it with TypoScript, but by inserting a configuration record on the page. It seems that you are still using these records and that the configuration set in such a record overrides the TypoScript configuration. To make sure you could backup the database table and remove the record in question. Or you are using predefined forms. Then you would have to set the TypoScript option for the predefined form only, not globally: plugin.tx_thmailformplus_pi1.predef.[key_of_the_form].default.email_to = em...@example.tld Regards, Reinhard ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] mailformplus - change mail address
Hi,
Am 30.11.2011 18:48, schrieb Victor Livakovsky:
Hi, Kay.
Can someone lead me to the front door for this task in version 4.0.15
of mailformplus and 4.5.3 of TYPO3?
Well, you better switch to 'fromhandler' extension, which is a successor
of 'mailformplus'. And it contains 'Tx_Formhandler_Finisher_Mail' class,
where you can set up needed stuff in your TS. I don't remember, if
mailformplus contains this finisher class alerady or it was added in
formhandler, but you may have a look at the source code anyway.
as far as I remember, mailformplus allows only configuration with
TypoScript.
Example (This may not be working, but should give you a hint where to
search in the manual):
plugin.tx_thmailformplus_pi1 {
default {
email_to = ad...@domain.tld
email_subject = My subject
}
}
Formhandler allows to do this configuration in TypoScript as well as in
the plugin on the page.
Regards,
Reinhard
--
http://www.typo3-formhandler.com
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] formhandler - jump to step via gp / call finisher without submitting?
Am 2011-03-22 17:34, schrieb Andreas Kiessling: Hi, i'm having trouble with the auth code feature from formhandler: What we tried with current (0.9.12) version and did not succeed: First: - save some values in db - send a mail with a link containing an auth code (using Tx_Formhandler_Finisher_GenerateAuthCode) and a parameter to jump to the second step 2) The user can click on the link and jumps to a page with another form that verifies the code, updates the db and generates yet another mail (e.g. an admin mail) The second step obviously does not need any real form to be displayed, but using formhandler to generate all the mails is straight forward and easy to use The function to determine the current step changed some time ago (with 0.9.8 i think), and if the submitted step does not match the step in the session (there will be no session for that form, so it will be 0) you jump to step 1 - finisher will not be called We already thought about extending / replacing Tx_Formhandler_Controller_Form to preset a step in the session if the submitted parameters are valid to proceed. Are there any other ways to handle double-opt-in completely in formhandler? Updating db can be of course be put to a custom class, but i would like to keep the mailing parts in one place. Regards and thanks in advance, Andreas Hi Andreas, I am currently working on a PreProcessor which validates the auth code. I never thought about how nice it would be to just skip the form and go right to the finishers. I created a ticket on Forge. Please join the discussion. http://forge.typo3.org/issues/13978 Regards, Reinhard ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] formhandler: pre-loading values from file
Am 2011-03-21 14:02, schrieb Claudio Strizzolo:
Hi all,
I am trying to update a mailformplus setup to formhandler.
I need to load the values to be used in aselect form field from a text
file:
Donald|donald.d...@example.com
Mickey|mickey.mo...@example.com
Basically, I need the first field to appear in the select menu, and the
sedcond field to be assigned as the value.
In mailformplus a preprocUserFunc was used:
plugin.tx_thmailformplus_pi1.preprocUserFunc = fileadmin/somewhere/
my_preproc.php:my_preproc-doit
How can I do the same using formhandler? I read about the
Preprocessor_LoadDB preprocessor, but that is a different case (DB instead
of text file).
Any hints?
Thanks in advance,
Claudio
Hi Claudio,
you can write a custom PreProcessor instead of the userFunc.
Example:
Put the PreProcessor in fileadmin/scripts/.
In TS:
plugin.Tx_Formhandler.settings {
# Tell Formhandler to look in other paths than typo3conf/ext/ for
class files too
additionalIncludePaths.1 = fileadmin/scripts/
# User your own PreProcessor
preProcessors {
1.class = Tx_Formhandler_PreProcessor_DoSomething
1.config {
foo = bar
}
}
}
The PreProcessor has to extend AbstractPreProcessor.
You have access to the GET/POST values via $this-gp.
You can access the configuration for your PreProcessor (everything in
the config section) via $this-settings.
For all other stuff you can have a look at the existing PreProcessors to
understand how it works.
NOTE: The PreProcessor MUST return $this-gp!
Regards,
Reinhard
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] formhandler multistep form
Am 2010-10-04 23:25, schrieb Toshiyuki Toda:
Hi list.
I use extension formhandler.
I want to make multistep form with conditions below.
pattern 1: FORM1 - FORM2 - FORM3
pattern 2: FORM1 -- FORM3 ( skip FORM2 in some condition )
Can I do ? if you know, please tell me how to do.
Hi Toshiyuki,
yes, you can do this with Formhandler.
In your HTML template you can double define steps.
Example:
###TEMPLATE_FORM1###
Step 1 is always the same in your case.
br /
form action=###REL_URL### method=post
###HIDDEN_FIELDS###
input type=radio name=formhandler[pattern] value=1
###checked_pattern_1### /Pattern 1br /
input type=radio name=formhandler[pattern] value=2
###checked_pattern_2### /Pattern 2br /
input type=submit ###submit_nextStep### value=next /
/form
###TEMPLATE_FORM1###
###TEMPLATE_FORM2###
This will only be shown in pattern 1.
br /
form action=###REL_URL### method=post
###HIDDEN_FIELDS###
input type=submit ###submit_prevStep### value=prev /
input type=submit ###submit_nextStep### value=next /
/form
###TEMPLATE_FORM2###
###TEMPLATE_FORM2_B###
###TEMPLATE_FORM3###
This will be shown as step 3 in pattern 1 and as step 2 in pattern 2.
br /
form action=###REL_URL### method=post
###HIDDEN_FIELDS###
input type=submit ###submit_prevStep### value=prev /
input type=submit ###submit_nextStep### value=next /
/form
###TEMPLATE_FORM3###
###TEMPLATE_FORM2_B###
You can configure these patterns with conditions:
plugin.Tx_Formhandler.settings.predef.conditions_example {
name = Conditions example
templateFile = fileadmin/path/to/your/template/template.html
formValuesPrefix = formhandler
# Conditions for step 1
1.if.1 {
conditions {
OR1 {
# If the user entered a special value
AND1 = pattern=2
}
}
isTrue {
2 {
# set the suffix to _B, so ###TEMPLATE_FORM[X]_B### is taken
templateSuffix = _B
# Optional: Reconfigure error checks if needed
#validators.1.config.fieldConf.phone.errorCheck.1 = required
#validators.1.config.disableErrorCheckFields = street
}
}
}
}
This is actually a working example. You can just copy paste the code,
configure the path to the template file and try it out.
Kind regards,
Reinhard
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] webkitpdf - CSS For print
Hi, I tried it myself using: plugin.tx_webkitpdf_pi1.scriptParams.print-media-type = The '=' is important because otherwise the setting seems to be removed by the TS parser. Regards, Reinhard De Contardi Riccardo schrieb: A little issue about webkitpdf The pdf is generated with the css for screen output, but I'd like to use my css for printing devices I've tried with: plugin.tx_webkitpdf_pi1.scriptParams.print-media-type But this is not working. Instead: plugin.tx_webkitpdf_pi1.additionalStylesheet = fileadmin/templates/assets/myprintcss.css works,but it ADDS the print css to my screen css, whereas I'd like so swap them. Any ideas? Thank you and regards ** Riccardo De Contardi B Human Srl - www.bhuman.it file:///C:\Documents%20and%20Settings\riccardo.decontardi\Dati%20applic azioni\Microsoft\Firme%20elettroniche\www.bhuman.it Via Canzio, 15 - 20131 Milano Tel +39.02 20 23 271 - Fax +39.02 20 240 561 Chi riceve il presente messaggio e' tenuto a verificare se lo stesso non gli sia pervenuto per errore. In tal caso e' pregato di avvisare immediatamente il mittente e, tenuto conto delle responsabilita connesse all'indebito utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso contenute, voglia cancellare l'originale e distruggere le varie copie o stampe. The receiver of this message is required to check if he/she has received it erroneously. If so, the receiver is requested to immediately inform the sender and - in consideration of the responsibilities arising from undue use and/or disclosure of the message and/or the information contained therein - destroy the original message and any copy or printout thereof. ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Formhandler: Validating via JSON?
Hi Benni, you could either use an interceptor entered in the saveInterceptor section or you could extend View_Form since the view gets information about the errors, but the interceptor won't AFAIK. Kind regards, Reinhard Benjamin Mack schrieb: Hey all, I'm currently implementing a form with this amazingly new extension formhandler. However, since my HTML form is built in a way to send the form via AJAX that expects JSON with either the missing fields or a success flag (already predefined, not by me ;-)), I was wondering if anybody knows where to hook in the Formhandler process to change the output of the sent form to return JSON of something I want instead of the HTML form again. This ain't a Validator but also not a Finisher, right? Could anybody point me in the right direction? Thanks a ton! Benni. ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] New TYPO3 Videos for Editors
Hello, I guess this is the link: http://typo3.org/documentation/videos/tutorials-v4/ And to make sure, that everyone is able to read your posts, you should stick to English on the English mailing list. :-) Reinhard Andreas Becker schrieb: Hallo Daniela Damit die user die Videos auch finden waere es sinnvoll wenn du einen direkten Link posten wuerdest und nicht einfach typo3.org Danke Andi On Mon, Nov 9, 2009 at 10:11 PM, Daniela dani...@a7digital.de wrote: I just wanted to let you know that we have finally managed to complete the series of video tutorials for v4.2 in English. Just like the German videos, the new English series consists of 21 consecutive videos taking approx. four to eight minutes each. Step by step, they impart the knowledge an editor needs for working with TYPO3. The series, as well as a 4 minutes quick guide, and a step-by-step quick reference are available for free in the videos section of typo3.org. If you are interested in translating the videos into another language as well, please, let me know. Kind regards, Daniela Koenig dani...@a7digital.de www.a7digital.de ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
