Changes for page Troubleshooting

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.jdr
	1	+XWiki.gru

Content

...	...	@@ -31,7 +31,7 @@
31	31	)))|This error message is shown for general errors. See the issue 2.2 below.
32	32	|2.2|(((
33	33	* Error message: An unexpected error has occurred while processing the submitted form data. / Submission failed
34		-)))|The data that have been submitted could not be processed. Usually this is caused by an action in the [[workflow>>doc:Formcycle.Designer.Workflow.WebHome]] that could not processed correctly. such as when a mail could not be sent, no mail server has been configured, a PDF could not be created. When you are using custom plugins, check whether they are throwing any uncaught errors. To resolve this issue, a detailed examination of the [[log>>doc:Formcycle.UserInterface.Protocol]] and {{formcycle/}}'s internal log files may be required.
	34	+)))|The data that have been submitted could not be processed. Usually this is caused by an action in the [[workflow processing>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.WebHome]] that could not processed correctly. such as when a mail could not be sent, no mail server has been configured, a PDF could not be created. When you are using custom plugins, check whether they are throwing any uncaught errors. To resolve this issue, a detailed examination of the [[log>>doc:Formcycle.UserInterface.Protocol]] and {{formcycle/}}'s internal log files may be required.
35	35	|2.3|(((
36	36	* Error message: This form has already been sent.
37	37	)))|When you would like to submit the form again and create a new form record, open the original link to the form in a new browser tab or window. Do not use a link that has been generated when saving the form for later editing.
...	...	@@ -39,9 +39,9 @@
39	39	|2.4|(((
40	40	* Error message: Invalid form data
41	41	)))|(((
42		-After the form has been submitted, the submitted data failed to validate, eg. when an invalid mail address has been provided. You can activate or deactivate server validation for each form field in the designer, section [[contraints>>doc:Formcycle.Designer.Form.ElementProperties.Constraints]]. Usually a form cannot be submitted when the data is invalid, but from a technical point of view, it is possible to send invalid forms. Activating the server validation is recommended.
	42	+After the form has been submitted, the submitted data failed to validate, eg. when an invalid mail address has been provided. You can activate or deactivate server validation for each form field in the designer, section [[contraints>>doc:Formcycle.FormDesigner.ElementProperties.Constraints]]. Usually a form cannot be submitted when the data is invalid, but from a technical point of view, it is possible to send invalid forms. Activating the server validation is recommended.
43	43
44		-In case you have overridden a [[a validator with Javascript>>doc:Formcycle.Designer.Form.CodingPanel.Validators]], the option //server validation// must not be checked or the form will always fail to validate.
	44	+In case you have overridden a [[a validator with Javascript>>doc:Formcycle.FormDesigner.CodingPanel.Validators]], the option //server validation// must not be checked or the form will always fail to validate.
45	45	)))
46	46	|3|When trying to open the form, only a spinning wheel shows up.|There is an error in some custom Javascript that has been added to the form. Check the [[script tab>>doc:Formcycle.Designer.Form.CodingPanel.ScriptTab.WebHome]] and any Javscript files that have been uploaded in the [[files menu>>doc:Formcycle.UserInterface.MyForms.Files]]. To analyse the error, it helps to open the JavaScript console of your browser, it will display any errors that may have occurred. How to open the console in [[Chrome>>url:https://developers.google.com/web/tools/chrome-devtools/debug/console/console-ui?hl=en#opening-the-console]], [[Firefox>>url:https://developer.mozilla.org/en-US/docs/Tools/Web_Console/Opening_the_Web_Console]], [[Internet Explorer / Edge>>url:https://msdn.microsoft.com/en-us/en-en/library/gg589530(v=vs.85).aspx]], [[Opera>>url:http://help.opera.com/Mac/9.62/de/devtools.html]], [[Safari>>url:https://developer.apple.com/library/mac/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/GettingStarted/GettingStarted.html]].
47	47	|4|No mails can be sent.|See [[mail issues, issue 1>>doc:WebHome||anchor="HE-Mailing"]].
...	...	@@ -51,7 +51,7 @@
51	51	== Inbox ==
52	52
53	53	|= |=Problem|=Lösung
54		-|1|Form records in the inbox cannot be deleted.|Form records are deletable if they are selected and a //Delete// icon {{ficon name="trash-alt2"/}} appears in the form record list. Contact your administrator or check whether the option [[Form records in this state can be deleted>>doc:Formcycle.Designer.Workflow.States.WebHome]] has been set for the form's current state.
	54	+|1|Form records in the inbox cannot be deleted.|Form records are deletable if they are selected and a //Delete// icon {{ficon name="trash-alt2"/}} appears in the form record list. Contact your administrator or check whether the option [[Form records in this state can be deleted>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.States.WebHome]] has been set for the form's current state.
55	55
56	56	== Frontend server ==
57	57
...	...	@@ -102,4 +102,3 @@
102	102
103	103	|= |= Issue|=Solution
104	104	|1|Application servers, eg. Tomcat or JBoss, crashes with the error message //OutOfMemory//.|You need to increase the available RAM for the Java virtual machine. For Tomcat, these settings are described on the [[help pages for setting up Tomcat>>doc:Formcycle.SystemSettings.TomcatSettings.LimitUploadSize]].
105		-|2|It is not possible to log in to {{formcycle/}} as sadmin with the default password directly after the initial installation on a Linux-based system.|{{formcycle/}} needs to store certain settings in the file system. Some Linux-based systems do not set a home directory for the tomcat user by default. This can usually be configured in the {{code language="none"}}/etc/passwd{{/code}} file. After the tomcat user has been modified, a restart is required.