Changes for page Print-Service-Plugin

From version 4.6
edited by gru
on 02.09.2021, 08:10
Change comment: There is no comment for this version
To version 6.1
edited by sas
on 02.03.2022, 14:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.gru
1 +XWiki.sas
Content
... ... @@ -117,6 +117,7 @@
117 117  In order for the plugin to be available in {{formcycle/}} as an action in the workflow, it must be deployed in the System Plugin section of the management interface. Instructions for installing plugins can be found [[here>>doc:Formcycle.UserInterface.Client.Plugins.WebHome]].
118 118  
119 119  If the old version of the print service plugin (phantom plugin) was already installed, the following procedure is recommended for installation:
120 +
120 120  * Disable the phantom plugin
121 121  * Delete the phantom plugin
122 122  * Upload new print service plugin
... ... @@ -134,6 +134,13 @@
134 134  
135 135  === Troubleshooting ===
136 136  
138 +==== Command npm not found ====
139 +
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 +
142 +* Call up the environment variables via Control Panel > System > Advanced System Settings > Environment Variables button.
143 +* In Path you should find the following entries: {{info}}C:\Users\{username}\AppData\Roaming\npm;C:\Program Files\nodejs{{/info}}
144 +
137 137  ==== Command npm install leads to timeout ====
138 138  
139 139  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:
... ... @@ -163,9 +163,7 @@
163 163  ==== Downloading Chromium fails ====
164 164  
165 165  The following error message appears on the console after running "npm install":
166 -{{code language="none"}}
167 -Error: unable to verify the first certificate
168 -{{/code}}
174 +{{code language="none"}}Error: unable to verify the first certificate{{/code}}
169 169  
170 170  The described steps are only a workaround and the environment variables should be set back to the default values after the successful installation!
171 171  
... ... @@ -192,6 +192,7 @@
192 192  : Additional URL parameters added to the URL used when opening the form with Selenium. You can use URL parameters to [[prefill form fields>>Formcycle.Designer.Form.URLParameter]] or access them from within JavaScript.
193 193  
194 194  == CSS-Anpassungen für Druckbild ==
201 +
195 195  === Input elements ===
196 196  
197 197  To optimize the form for printing, form elements of type [[input field>>Formcycle.Designer.Form.FormElements.Input]], [[text area>>Formcycle.Designer.Form.FormElements.Textarea]] und [[select>>Formcycle.Designer.Form.FormElements.Selection]] (Drop-Down) may be converted to plain text fields, if the print mode is set to Input elements as text.
... ... @@ -227,6 +227,31 @@
227 227  }
228 228  {{/code}}
229 229  
237 +
238 +
239 +=== Avoid page break ===
240 +
241 +The default setting for printing is that a page break is inserted after each page of the form:
242 +
243 +{{code language="css"}}
244 +@media print {
245 + .CXPage:not(:first-child ), .page-break {
246 + display: block !important;
247 + page-break-before: always;
248 + }
249 +}
250 +{{/code}}
251 +
252 +In order to avoid breaks, the following rule needs to be defined in the CSS tab of the form:
253 +
254 +{{code language="css"}}
255 +@media print {
256 + .CXPage:not(:first-child ) {
257 + page-break-before: avoid;
258 + }
259 +}
260 +{{/code}}
261 +
230 230  === Usage of other fonts ===
231 231  
232 232  ==== Technical requirements ====