Changes for page Print-Service-Plugin


From version 8.1
edited by sas
on 02.03.2022, 14:51
Change comment: There is no comment for this version
To version 7.1
edited by sas
on 02.03.2022, 14:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -92,7 +92,7 @@
92 92  
93 93  Translated with www.DeepL.com/Translator (free version)
94 94  
95 -=== Uninstall ===
95 +==== Uninstall ====
96 96  
97 97  To uninstall the Print Server, open a command line (cmd) with administrative privileges and execute the following commands:
98 98  
... ... @@ -133,17 +133,17 @@
133 133  
134 134  This completes the setup of the print service plugin and it is available as an action in the [[workflow processing>>doc:Formcycle.Designer.Workflow.WebHome]].
135 135  
136 -== Troubleshooting ==
136 +=== Troubleshooting ===
137 137  
138 -=== Command npm not found ===
138 +==== Command npm not found ====
139 139  
140 140  Under Windows it is possible that after the NodeJS installation the environment variables are not set correctly and so npm install cannot be executed. This was also the case if the default path under C:/Programs was not used during the NodeJS installation. So check in the path if these are existing. The following must be done for this:
141 141  
142 142  * Call up the environment variables via Control Panel > System > Advanced System Settings > Environment Variables button.
143 143  * In Path you should find the following entries: {{info}}C:\Users\{username}\AppData\Roaming\npm;C:\Program Files\nodejs{{/info}}
144 -* Confirm everything with Ok. The console then be opened again with admin rights.
144 +* Confirm with Ok. The console then be opened again with admin rights.
145 145  
146 -=== Command npm install leads to timeout ===
146 +==== Command npm install leads to timeout ====
147 147  
148 148  If the npm install command does not work due to a proxy, then the general proxy setting is not sufficient. Therefore, the following must be executed via console:
149 149  
... ... @@ -161,15 +161,15 @@
161 161  
162 162  More information can also be found here: http://www.fladi.de/2014/02/06/howto-npm-hinter-einem-proxy-verwenden/
163 163  
164 -=== Printing does not work ===
164 +==== Printing does not work ====
165 165  
166 166  If printing via {{formcycle/}} is not possible, the cause could be that the print service is not reachable. This can be solved by the loopback URL. Under System > General > Loopback URL, loopback base URL: {{code language="none"}}http://localhost:<port>/formcycle{{/code}}
167 167  
168 -=== PDF is printed, but the message 404 appears ===
168 +==== PDF is printed, but the message 404 appears ====
169 169  
170 170  In this case the print service works correctly because a PDF is already created. It must be checked whether the loopback URL is entered correctly so that the URL to the print service is resolved correctly.
171 171  
172 -=== Downloading Chromium fails ===
172 +==== Downloading Chromium fails ====
173 173  
174 174  The following error message appears on the console after running "npm install":
175 175  {{code language="none"}}Error: unable to verify the first certificate{{/code}}
... ... @@ -235,6 +235,8 @@
235 235  }
236 236  {{/code}}
237 237  
238 +
239 +
238 238  === Avoid page break ===
239 239  
240 240  The default setting for printing is that a page break is inserted after each page of the form: