/
exportword07f4
368 lines (340 loc) · 12 KB
/
exportword07f4
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
Message-ID: <487189461.3570.1485853716474.JavaMail.confluence@ip-10-127-227-164>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_3569_524337317.1485853716473"
------=_Part_3569_524337317.1485853716473
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
<html xmlns:o=3D'urn:schemas-microsoft-com:office:office'
xmlns:w=3D'urn:schemas-microsoft-com:office:word'
xmlns:v=3D'urn:schemas-microsoft-com:vml'
xmlns=3D'urn:w3-org-ns:HTML'>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8=
">
<title>Extension load ordering</title>
<!--[if gte mso 9]>
<xml>
<o:OfficeDocumentSettings>
<o:TargetScreenSize>1024x640</o:TargetScreenSize>
<o:PixelsPerInch>72</o:PixelsPerInch>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
<w:WordDocument>
<w:View>Print</w:View>
<w:Zoom>90</w:Zoom>
<w:DoNotOptimizeForBrowser/>
</w:WordDocument>
</xml>
<![endif]-->
<style>
<!--
@page Section1 {
size: 8.5in 11.0in;
margin: 1.0in;
mso-header-margin: .5in;
mso-footer-margin: .5in;
mso-paper-source: 0;
}
td {
page-break-inside: avoid;
}
tr {
page-break-after: avoid;
}
div.Section1 {
page: Section1;
}
/* Confluence print stylesheet. Common to all themes for print medi=
a */
/* Full of !important until we improve batching for print CSS */
@media print {
#main {
padding-bottom: 1em !important; /* The default padding of 6em is to=
o much for printouts */
}
body {
font-family: Arial, Helvetica, FreeSans, sans-serif;
font-size: 10pt;
line-height: 1.2;
}
body, #full-height-container, #main, #page, #content, .has-personal-sid=
ebar #content {
background: #fff !important;
color: #000 !important;
border: 0 !important;
width: 100% !important;
height: auto !important;
min-height: auto !important;
margin: 0 !important;
padding: 0 !important;
display: block !important;
}
a, a:link, a:visited, a:focus, a:hover, a:active {
color: #000;
}
#content h1,
#content h2,
#content h3,
#content h4,
#content h5,
#content h6 {
font-family: Arial, Helvetica, FreeSans, sans-serif;
page-break-after: avoid;
}
pre {
font-family: Monaco, "Courier New", monospace;
}
#header,
.aui-header-inner,
#navigation,
#sidebar,
.sidebar,
#personal-info-sidebar,
.ia-fixed-sidebar,
.page-actions,
.navmenu,
.ajs-menu-bar,
.noprint,
.inline-control-link,
.inline-control-link a,
a.show-labels-editor,
.global-comment-actions,
.comment-actions,
.quick-comment-container,
#addcomment {
display: none !important;
}
.comment .date::before {
content: none !important; /* remove middot for print view */
}
h1.pagetitle img {
height: auto;
width: auto;
}
.print-only {
display: block;
}
#footer {
position: relative !important; /* CONF-17506 Place the footer at en=
d of the content */
margin: 0;
padding: 0;
background: none;
clear: both;
}
#poweredby {
border-top: none;
background: none;
}
#poweredby li.print-only {
display: list-item;
font-style: italic;
}
#poweredby li.noprint {
display: none;
}
/* no width controls in print */
.wiki-content .table-wrap,
.wiki-content p,
.panel .codeContent,
.panel .codeContent pre,
.image-wrap {
overflow: visible !important;
}
/* TODO - should this work? */
#children-section,
#comments-section .comment,
#comments-section .comment .comment-body,
#comments-section .comment .comment-content,
#comments-section .comment p {
page-break-inside: avoid;
}
#page-children a {
text-decoration: none;
}
/**
hide twixies
the specificity here is a hack because print styles
are getting loaded before the base styles. */
#comments-section.pageSection .section-header,
#comments-section.pageSection .section-title,
#children-section.pageSection .section-header,
#children-section.pageSection .section-title,
.children-show-hide {
padding-left: 0;
margin-left: 0;
}
.children-show-hide.icon {
display: none;
}
/* personal sidebar */
.has-personal-sidebar #content {
margin-right: 0px;
}
.has-personal-sidebar #content .pageSection {
margin-right: 0px;
}
}
-->
</style>
</head>
<body>
<h1>Extension load ordering</h1>
<div class=3D"Section1">
<p><span class=3D"status-macro aui-lozenge aui-lozenge-current">5.X=
</span></p>
<h3 id=3D"Extensionloadordering-Introduction">Introduction</h3>
<p>In eZ Publish 4.4 and higher, there is a mechanism that enables extensio=
ns to define in which order they should be loaded in regards to other, rela=
ted, extensions. The function automates the extension load ordering to help=
avoid situations where extensions does not work properly in case=
of wrong order.</p>
<p><a name=3D"eztoc131603_0_2" rel=3D"nofollow"></a></p>
<h3 id=3D"Extensionloadordering-Requirements">Requirements</h3>
<p>For the extension load ordering mechanism to be active, extensions shoul=
d be recent enough to contain the needed metadata stored in the "<code>exte=
nsion.xml</code>" file, so make sure you use the extensions certified for y=
our eZ Publish version (see: Technical manual / <version> / Inst=
allation / Requirements ).</p>
<p><a name=3D"eztoc131603_0_3" rel=3D"nofollow"></a></p>
<h3 id=3D"Extensionloadordering-Configuration">Configuration</h3>
<p>To activate the extension load ordering, the following configuration set=
ting should be enabled in "<code>site.ini.append.php</code>" in setting/ove=
rride:</p>
<div class=3D"preformatted panel" style=3D"border-width: 1px;">
<div class=3D"preformattedContent panelContent">=20
<pre>[ExtensionSettings]
ExtensionOrdering=3Denabled</pre>=20
</div>
</div>
<h3 id=3D"Extensionloadordering-Extensionordering">Extension ordering</h3>
<p>The order in which active extensions appear in the "<code>site.ini</code=
>" under <code><code><eZ_Publish_root_folder>/ezpublish_legacy</code>=
/settings/override/site.ini</code> "<code>[ExtensionSettings]</code> <code>=
ActiveExtensions=3D</code>" is important for the selection of templates and=
, possibly, configuration settings. For this reason, users must insure that=
the correct order is used for extensions that have dependencies on other e=
xtensions. For example eZ Find must be activated before eZ Webin. The same =
rule applies for the eZ Teamroom extension: eZ Teamroom and all its depende=
nt extensions, such as eZ Lightbox and eZ Event, need to be activated befor=
e eZ Webin.</p>
<p>Although extensions can be activated using the Administrator Interface, =
as for now the admin interface does not provide a way to re-order the exten=
sions, manually or automatically. This implies that the order can only be d=
efined in site.ini.</p>
<p>Defining the correct order can sometimes be tricky when many extensions =
need to be considered. By providing metadata to the extension loading, manu=
al extension load ordering is now a thing of the past.</p>
<p><a name=3D"eztoc131603_0_5" rel=3D"nofollow"></a></p>
<h3 id=3D"Extensionloadordering-Metadata">Metadata</h3>
<p>By providing metadata for the extension load ordering we enable eZ Publi=
sh to correctly determine the correct order itself. The metadata about exte=
nsion ordering is optional. These metadata are now declared using an XML fi=
le, that can also be used to replace what is currently in "<code>ezinfo.php=
</code>". This file is named "<code>extension.xml</code>", located at the r=
oot of the extension. It has the following content:</p>
<div class=3D"preformatted panel" style=3D"border-width: 1px;">
<div class=3D"preformattedContent panelContent">=20
<pre><?xml version=3D"1.0" encoding=3D"utf-8" ?>
<software>
<metadata>
<name>Extension name</name>
<description>Extension description</description>
<version>X.Y.Z</version>
<copyright>Copyright text</copyright>
<license>License type</license>
<info_url>http://url/to/extension/site</info_url>
<author>Extension author</author>
=20
<software>
<uses>
<name>Used library/software 1</name>
<license>Used library/software 1 license</licens=
e>
<copyright>Used library/software 1 copyright</co=
pyright>
<info_url>Used library/software 1 URL</info_url&=
gt;s
<version>Used library/software 1 version</versio=
n>
</uses>
<uses>
<name>Used library/software 2</name>
<license>Used library/software 2 license</license=
>
<copyright>Used library/software 2 copyright</cop=
yright>
<info_url>Used library/software 2 URL</info_url&g=
t;s
<version>Used library/software 2 version</version=
>
</uses>
=20
</software>
=20
</metadata>
=20
<dependencies>
<uses>
<extension name=3D"usedExtension" />
</uses>
<requires>
<extension name=3D"requiredExtension" />
</requires>
<extends>
<extension name=3D"extendedExtension" />
</extends>
</dependencies>
=20
</software></pre>=20
</div>
</div>
<p> </p>
<p>The first block (software/metadata) replaces "<code>ezinfo.php</code>". =
The fields are equivalent to those found in the info() method of the 'old' =
ezinfo. The sub-node software/metadata/software replaces the previous 3rdpa=
rty_libraries entry. One software/metadata/software/uses node must be used =
for each library.</p>
<p>The second block (software/dependencies) contains 3 sub-nodes:</p>
<ul>
<li>
<div>
<strong>uses:</strong> indicates that the referenced extension is used by t=
his extension.
</div></li>
<li>
<div>
<strong>requires:</strong> indicates that the referenced extension is requi=
red by this extension.
</div></li>
<li>
<div>
<strong>extends:</strong> indicates that the referenced extension is overlo=
aded by this extension.
</div></li>
</ul>
<p><strong>Note:</strong> 'uses' and 'requires' currently have the same eff=
ect, but their behavior will change when real dependencies checking is deve=
loped in the future.</p>
<p><a name=3D"eztoc131603_0_6" rel=3D"nofollow"></a></p>
<h3 id=3D"Extensionloadordering-Knowissue">Know issue</h3>
<ol>
<li>
<div>
Extension load ordering breaks possibility to define your cluster (
<code>file.ini</code>) settings for siteaccess and extensions as the functi=
onality loads cluster before extension and siteaccess settings are loaded.
</div></li>
<li>
<div>
Extension load ordering has a small impact on performance
</div></li>
</ol>
<p>In both cases work around is to disable extension load ordering.</p>
</div>
</body>
</html>
------=_Part_3569_524337317.1485853716473--