im using the new EXT:form extension from Typo3 8. I put it in my own extension folder so i made a custom template for it. This works fine until the point i want to integrate Google recaptcha into it.
I want to use the EXT:recaptcha for this:
https://docs.typo3.org/typo3cms/extensions/recaptcha/Index.html
In the sample EXT:form layout the recaptcha works without problems. But when im switching back to my layout i get the following error message:
Oops, an error occurred! The validator preset identified by
"Recaptcha" could not be found, or the implementationClassName was not
specified.
What i have to do? Anyone has an idea?
I know this question is quite old, you probably found the solution already.
I'm quite sure you did not include the static template. After adding the recaptcha template to my root template the validator was available.
Related
The file of an image I used in an productbox cannot be resolved anymore.
I used this tag f:uri.image(src:bild.url,crop:bild.crop)} and PhpStorm throws me this error from now on, I did not recognize this message when I used it in other projects, but it`s also happening there.
Seems to be a current problem maybe with some Viewhelper Updates or the TYPO3 Version, I used TYPO3 v8.7.18 and v.8.7.4.
Anyone got a similar issue?
by default PhpStorm does not know about fluid. So PhpStorm probably tries to validate the fluid against HTML syntax which will fail, as there are tags not included in HTML. Also if you use fluid-variables where in HTML strings are used PhpStorm will fail.
I have a strange problem:
TYPO3 7.6 with realul 2.2.1
I got a page with a form. One field of the form gets prefilled via get-parameter (sysid=xxxxx).
The site is multilanguage: german->0, english->1, mapped via prevars '' and en.
When I call the page via www.domain.tld/form-page/?sysid=xxxxx I can fetch the get parameter and fill the field.
When I call the page via www.domain.tld/en/form-page/?sysid=xxxxx I get a 404. That's weired because www.domain.tld/en/form-page/ works without any problems.
I tried several settings (e.g. exclude sysid from chash generation) but nothing worked.
Any hints what I could do?
One additional note: the getvar links are not generated in TYPO3, the are called via barcodes.
I cannot reproduce your problem on the same versions of T3 and realurl.
And I guess (wild guess), it is not a realurl problem, but a TYPO3-core problem.
Could you try calling the page via:
www.domain.tld/index.php?id=XX&L=1&sysid=xxxxx
Furthermore investigate and tell us your settings of
[FE][pageNotFound_handling] and according (installtool/LocalConfiguration).
Nevermind. Error occured because I didn't adjust the realurl-setting for the domain after moving to live. Therefore automatic configuration took place and that didn't work. With manual conf it works.
I have installed upload_example extension in TYPO3 7.6.11. It works very well from admin. However, when i try to submit form with images it throws the error: 1298012500: Required argument "newExample" is not set for Helhum\UploadExample\Controller\ExampleController->create.
I checked every configuration, everything is set. I stuck. I am new in typo3.
Can you help please?
Thank You
You can debug using debugutility inside initializeMethodAction(). I must be called in such case when model argument is not found.
Or as a reference for file uploading you can refer this link. hopefully, it will help you
http://blog.typo3servers.info/show/typo3-extbase-fal-image-upload/
i am using zend framework, i use auto loader to load the class, i create a Zend_Form in this page http://tedxnanjing.com/displayevent/TEDxNanjing%2Bcoming%2Bsoon%2B11%252F27
but the form is not loading, this page works fine in my own local environment , except i am using php 5.3 , but i check that it should work with php 5.2.4 and later.
why this happening?
this is a test page with more detail http://zend.anpingsiwang.info/events/TEDxNanjing%2Bcoming%2Bsoon%2B11%252F27
found the bug. it is the addFilter('HTMLEntities') that keeps the form not being rendered.
haven't found why this happening , may something with my environment or a zend bug, just point it out first.
I need to use ZendAMF on a symfony project and I'm currently working on integrating the two.
I have a frontend app with two modules, one of which is 'gateway' - the AMF gateway. In my frontend app config, I have the following in the configure function:
// load symfony autoloading first
parent::initialize();
// Integrate Zend Framework
require_once('[MY PATH TO ZEND]\Loader.php');
spl_autoload_register(array('Zend_Loader', 'autoload'));
The executeIndex function my the gateway actions.class.php looks like this
// No Layout
$this->setLayout(false);
// Set MIME Type
$this->getResponse()->setContentType('application/x-amf; charset='.sfConfig::get('sf_charset'));
// Disable cause this is a non-html page
sfConfig::set('sf_web_debug', false);
// Create AMF Server
$server = new Zend_Amf_Server();
$server->setClass('MYCLASS');
echo $server->handle();
return sfView::NONE;
Now when I try to visit the url for the gateway module, or even the other module which was working perfectly fine until this attempt, I only see a blank screen, with not even the symfony dev bar loaded. Oddly enough, my symfony logs are not being updated as well, which suggests that Synfony is not even being 'reached'.
So presumably the error has something to do with Zend, but I have no idea how to figure out what the error could be. One thing I do know for sure is that this is not a file path error, because if I change the path in the following line (a part of frontendConfiguration as shown above), I get a Zend_Amf_Server not found error. So the path must be correct. Also if I comment out this very same line, the second module resumes to normality, and my gateway broadcasts a blank x-amf stream.
spl_autoload_register(array('Zend_Loader', 'autoload'));
Does anyone have any tips on how I could attach this problem?
Thanks
P.S. I'm currently running an older version of Zend, which is why I am using Zend_Loader instead of Zend_autoLoader (I think). But I've tried switching to the new lib, but the error still remains. So it's not a version problem as well.
got it...
I was not using
set_include_path()
while loading Zend. It's still odd that it would give such a cryptic error, but this was the missing piece indeed.