|
632
|
1 |
Enano 1.1.4 - Known Bugs and Issues
|
|
|
2 |
|
|
|
3 |
These are the issues in Enano 1.1.4 that the development team knows
|
|
|
4 |
about, but did not have time to fix before this release was
|
|
|
5 |
scheduled. Hopefully all of these will be fixed in the next release.
|
|
|
6 |
|
|
|
7 |
- Username and page name auto-complation does not work
|
|
|
8 |
These components were moved to a new framework - Spry data sets - in
|
|
|
9 |
Enano 1.1.4. We're having a lot of issues with this due to the
|
|
|
10 |
requirement for loading the data only on demand (e.g. when the user
|
|
|
11 |
starts typing in the form field). We also need to be able to create
|
|
|
12 |
username autocompletion fields with DHTML, which spry is also
|
|
|
13 |
failing at. Now if only Spry's effects library wasn't so damn nice,
|
|
|
14 |
we'd probably swap it out for something else entirely.
|
|
|
15 |
|
|
|
16 |
- Several expected ACL management features are missing
|
|
|
17 |
We know, we know. You want ACL presets and more ways to debug
|
|
|
18 |
existing rules. The good news is that the latter is fully implemented
|
|
|
19 |
on the backend level. The bad news is that creating a good frontend
|
|
|
20 |
is a hard thing especially with the standard that the existing ACL
|
|
|
21 |
editor sets. We'll have both presets and ACL rule tracing done for
|
|
|
22 |
Enano 1.1.5.
|
|
|
23 |
|