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================================================================================
Escher CMS Release Notes
================================================================================
Release 0.9.3
--
CacheMonitor plugin is now branch-aware.
--
Admin config array structure has changed for: [session, auth]. The "page_cache"
config item has been renamed "publish_page_cache." Be sure to update your copy
of admin-config.php or you will be unable to log into the admin interface.
Site config array structure has changed for: [cache, page_cache, nonce].
Be sure to update your site-config.php accordingly or your caches may not function
properly.
--
================================================================================
Release 0.9.2
--
Major new feature: Integrated branch management. Escher sites now have
production, staging and development branches that can each be independently
developed and viewed.
If you would like to take advantage of the new branching feature, you will need
to add two new subdirectories to your cache directory. Add these directories at
the same level as your existing cache/code directory, and give them the same
ownership and permissions as your existing cache/code directory:
cache/code.staging
cache/code.dev
--
Drag & Drop page reordering.
--
New default theme by Phil Wareham of Design Hive Ltd. Thanks Phil!
http://www.designhive.com/
@philwareham
--
Site search plugin.
Feed generator plugin.
--
Unlimited custom metadata for images, files and links.
--
Support for separate read-only database(s) (for load-balancing MySQL queries to replicated slaves)
--
Specifying snippets by ID when using escher tags such as <et:design:snippet> is
now deprecated and support will be dropped in the next release. Fetch snippets
by name instead.
--
The "offset" attribute used by several tags has been replaced with the "start"
attribute, which has different semantics. Whereas the "offset" attribute was a
zero-based absolute index into the resulting object list, the "start" attribute
is a one-based index that takes paging (i.e. the value of the "limit" attribute)
into account. For example, with limit=10 and start=2, the first returned object
would be the 11th object in the list. The followng tags are affected by this
change:
<et:pages:count>, <et:pages:first>, <et:pages:last>, <et:pages:each>
<et:children:count>, <et:children:first>, <et:children:last>, <et:children:each>
<et:siblings:count>, <et:siblings:each>
<et:files:count>, <et:files:each>
<et:comments:count>, <et:comments:each>
<et:archives:count>, <et:archives:first>, <et:archives:last>, <et:archives:each>, <et:archives:dates_each>
--
New tags have been added to assist with generation of next/previous links in
concert with the pagination plugin.
<et:pages:if_any>, <et:pages:if_any_before>, <et:pages:if_any_after>
<et:children:if_any>, <et:children:if_any_before>, <et:children:if_any_after>
<et:siblings:if_any>, <et:siblings:if_any_before>, <et:siblings:if_any_after>
<et:files:if_any>, <et:files:if_any_before>, <et:files:if_any_after>
<et:archives:if_any>, <et:archives:if_any_before>, <et:archives:if_any_after>
<et:comments:if_any>, <et:comments:if_any_before>, <et:comments:if_any_after>
--
Comments Plugin
The <et:comments:if_comments> tag has been removed. Use <et:comments:if_any> instead.
The default comment snippets have changed. These are **not** updated during an upgrade.
Backward-incompatible change in behavior: By default, comment processing (escaping of input, etc.)
now occurs prior to saving the comment to the database. Previously, processing was performed
dynamically during page view. The new method provides improved site performance. To continue
with the previous behavior, change your comment code to pass attributes as follows:
<et:comments:if_add_comment escape="false" nl2p="false" pretty="false" />
<et:comments:content escape="true" />
If you decide to use the new method of comment processing, be aware that any comments currently
stored in your site database may contain data that is unsafe to render. You should check
your existing comments and potentially escape the contents of the `message` column for each
existing comment before enabling the new behavior in your site.
--
Miscellaneous bug fixes.
--
================================================================================
Release 0.9.1
--
Spark/Plug now uses the PHPass library for password hashing. As a result, any
Escher user password hashes stored in Escher 0.9.0 databases will no longer
be recognized. This will cause login to fail once you install a version of
Escher CMS newer than 0.9.0. The easiest fix is to use the "Forget your Password?"
link on the Escher CMS login screen to regenerate the password hashes for each
user account.
--
The folllowing tags have been removed:
<et:ns:meta>
<et:meta:keywords>
<et:meta:description>
<et:meta:author>
<et:meta:distribution>
<et:meta:robots>
<et:meta:custom>
They have been replaced with the more general purpose tags:
<et:pages:meta>
<et:images:meta>
<et:files:meta>
<et:links:meta>
--
Note the following change to publish-config.php (be sure to update your copy):
The following route:
':any' => 'publish/index',
has changed to:
':all' => 'publish/index',
--
There has been a minor adjustment to the default location of the main Spark/Plug
directory. As a result, the "sparkplug_dir" config parameter has changed.
If you are using a custom installation layout you may need to adjust the value
of this parameter in the following config files:
config/admin-config.php
config/install-config.php
config/publish-config.php
If you are using the standard installation layout, the new versions of the above
files have already been adjusted for you.
--
================================================================================