I created a contact form with an 'email to recipient'-finisher but when the user sends the form, the message "Oops, an error occurred!" show up. However, when I use 'confirmation message' as a finisher no such error shows up. The 'page redirect'-finisher also returns an error.
Do you have any ideas how to fix this? (I'm also not getting anymore detailed error information even though I have the debug mode turned on in the configuration presets..)
I had not correctly configured the 'Mail handling settings' found under 'Configuration presets' in 'Settings'. I added custom settings to write the form replies to a local file, as the website was not live and I wanted to run tests.
Related
I know there's an earlier question with this subject here, but the OP never reported if the one answer resolved the issue. And since
Internal Server Error
is about as user-unfriendly as you can get, I would love to change this to something that feels more like "a message" than "an anvil dropped on your foot".
I have found one other SO post that tangentially relates to this issue (about that disappearing "duplicate emails" switch), but the problem is indeed not about whether or not to allow duplicate emails (or how to revive hidden admin controls) but how a very ordinary issue is communicated to the user - well, like how Keycloak notifies the user when they try and register with an existing username.
We're currently using the Docker version of Keycloak 12.0.4 with some customisations (a custom BCrypt module, some logging changes) running in IBM Cloud, using a Postgresql DB. We also added a custom theme & internationalisation. The same error occurs also when using the default Keycloak theme, though.
Here are our Login settings:
It turned out to be a configuration issue, but so deeply hidden that even the Keycloak developer who looked into the ticket I created had glossed over it.
The perpetrator was in menu Configure > Authentication > tab: Flows > choose dropdown: Registration > Profile validation radio button [o REQUIRED | o DISABLED]
This was set to disabled, which in effect prevents the duplicate email check in the registration form that the Realm settings > tab: Login form suggest are active. But then, of course, the database won't like that, with above-mentioned result.
This combination of settings should at least issue a warning, of course. I hope this will be corrected.
I tried to use angular form to validate user's input in a "ionic generated component" but error as mentioned in the title kept occurring.
Angular forms and validations used in "ionic generated pages" are working fine.
Any ideas?
Picture of :
HTML Component
Error
TypeScript Component
I managed to fix this by using the solution here https://stackoverflow.com/a/57251807/9516387
Which is:
You checking for the presence of an error where no error might exist.
You want something like this:
f.email.errors?.required
Or even:
f.email?.errors?.required
Do the same for the password field and anywhere else where the property might not exist when it is first called.
You should try to access it by f.controls.recipientName.errors
I am new to the magento, and right now, i was working one website.
I did my initial development on my local machine and everything was fine. few days ago I moved the website into test server from my localhost. after that the checkout function is not working properly.
the problem is that i have almost have nothing on that page.
if user is not logged in, then he(she) sees 2 steps as log in, and billing information, but without content. only the titles.
if user is logged in, then he(she) sees step 1 billing information title, and again no content
the website is http://guerrilla.webionaria.com/
user:teste#mail.ru
password:testtest
can anyone help me with this please
There is a 'Fatal error' on your page.
The rendering stops with
var billingRegionUpdater = new RegionUpdater('billing:country_id', 'billing:region', 'billing:region_id',
The error appears in app/design/frontend/{interface}/{theme}/template/checkout/onepage/billing.phtml or in app/design/frontend/{interface}/{theme}/template/persistent/checkout/onepage/billing.phtml (if you have cart persistence enabled).
In both of the cases, for some reason this code gives an error:
<?php echo $this->helper('directory')->getRegionJson() ?>
To find out what the error is you need to enable error reporting and display_errors.
You can do that from index.php.
error_reporting(E_ALL | E_STRICT);
...
ini_set('display_errors', 1);
You can also enable the developer mode by changing this:
if (isset($_SERVER['MAGE_IS_DEVELOPER_MODE'])) {
Mage::setIsDeveloperMode(true);
}
to this
//if (isset($_SERVER['MAGE_IS_DEVELOPER_MODE'])) {
Mage::setIsDeveloperMode(true);
//}
Then try again. If the error does not appear on your screen look at the source of the page.
If the error does not tell you anything update the question with its contents.
Just installed Magento for the first time on my Localhost. And found the same problem. I found the solution in following way:
-- Enabled the error logs in System > Configuration > Developer Tools
-- Then attempted a checkout.
Bam! found the error in var/logs/system.log
The error was due to SOAP. I needed to enable PHP's soap library. And it proceeded well.
Hope it helps someone :)
I have problem with form submission to a action of different moudule, say e.g I have a module called "mymobile" from I am calling a action in module "register" which will process the registration, if there is any error in form I am setting the error messages and forwarding to "mymobile" module's page from where I called the action of "register", so it is modifying the header and my Japanese text is getting converted to some junk. Is there any way I can show error messages on my form without change of text? Any alternative for $this->forward() method? I am using symfony 1.1 and I tried $this->rediect() it will refresh the page.
Thank you in advnace
Recently, Facebook has updated the component "request dialog" assigning responsibility to the exclusion of requests to the developers (http://developers.facebook.com/docs/reference/dialogs/requests#deleting). He also made other adjustments to the format of the request id. Thus added configuration option "request 2.0 efficient" on menu of the application developer.
The problem started after this change , the component "request dialog Multi - Friend- Selector" is in serious trouble. The component is crashed while trying to load friends. Sometimes friends loads, but the component does not resize height.
See the image of the errors:
Crashed before load friends:
http://postimage.org/image/glk2mf3bb/
Resize fail
http://postimage.org/image/iobduhn41/
In chrome browser component generates the following error:
s-static.ak.facebook.com/rsrc.php/v1/yS/r/syXGEAW5WYH.js:36 Uncaught TypeError: Cannot read property 'origin' of undefined
In firefox generates following error:
Erro: Permission denied to access property 'DocRPC'Arquivo-fonte: https://s-static.ak.facebook.com/rsrc.php/v1/yS/r/syXGEAW5WYH.js Linha: 36
Can you reproduce the error with the code itself Documentation
http://developers.facebook.com/docs/reference/dialogs/requests
Help please.
Seeing same errors here, but I can add some info:
It does seem to work if you use the basic example in https://developers.facebook.com/docs/reference/dialogs/requests, which opens up the dialog in a new browser window.
In Chrome, I found an additional error message to the one you posted:
"Unsafe JavaScript attempt to access frame with URL [...] from frame with URL [...]facebook.com/dialog/apprequests. Domains, protocols and ports must match."
From all that I guess the error may be related to the dialog display mode (read https://developers.facebook.com/docs/reference/dialogs). Within my app, I am getting this error exactly as you do, unless I set display to something like 'popup', in which case everything works (but a new borwser window is opened). The docs do state that "Because of the risk of clickjacking, [iframe] is only allowed for some certain dialogs, and requires you to pass a valid access_token." Well, passing access tokens did no good for me.
Little question: are you using some toolkit like GWT?