Ticket #50 (Fixed)Sun Oct 15 16:12:46 UTC 2006
Serious Instiki faults
| Reported by: | Andrew Hodgkinson | Severity: | Normal |
| Part: | Web site: Instiki (documentation Wiki) | Release: | |
| Milestone: | Status | Fixed |
Details by Andrew Hodgkinson:
No Textile escape mechanism working; backslash escaping does not work. Can’t do “C++” for example – the next “+” gets interpreted as terminating an INS section. See also http://dev.instiki.org/ticket/134.
Never expires cache; Instiki doesn’t seem to ever let the RAM cache go. There are no bugs about this that I’ve found in the Instiki bug tracker but it’s not clear how this could possibly be related to the local environment. Basically, any modification to a page seems to currently require a web server restart to be reflected visibly!
Changelog:
Modified by Andrew Hodgkinson Sun, October 15 2006 - 16:13:17 GMT
The above is a good example of escaping stuff! Textile can be quite annoying. C\\ <- backslashes used as a test.
Modified by Andrew Hodgkinson Sun, October 15 2006 - 16:13:36 GMT
Again, that failed; there may well be a system-wide Textile problem.
Modified by Andrew Hodgkinson Sun, October 15 2006 - 16:21:31 GMT
Difficult to know where to start. Instiki routes are broken; fixing them breaks the Home page; don’t understand insistance on “?web=documentation” when DEFAULT_WEB is set; main heading link seems to break Instiki internally…
Modified by Andrew Hodgkinson Mon, October 16 2006 - 15:14:39 GMT
I’m looking at replacing Instiki with I2. Working well so far.
Textile by default appears to have no escaping mechanism. I’ve added one for the quick modifiers (e.g. “thing”, “thing”, “thing”) – use a backslash. That’s in Instiki as a custom v3.0.3 presently.
Modified by Andrew Hodgkinson Mon, October 16 2006 - 16:49:06 GMT
- Severity changed from Critical to Normal
Moved over to i2. Undergoing testing. Far fewer features, but that means far less to go wrong.
Want to understand why Radiant is so much better at Textile than i2 though…
Modified by Andrew Hodgkinson (6) Mon, October 23 2006 - 16:45:13 GMT
- Status changed from Open to Fixed
Ticket #69 created to track issues of Textile performance. Meanwhile, i2 is working well. It lacks Instiki’s features, such as, sadly, PDF export; but it is has far fewer quirks, too. Over time, perhaps Instiki features might get migrated into i2 (see Ticket #70), but i2 is certainly sufficient for now.
Modified by Andrew Hodgkinson (6) Mon, October 23 2006 - 17:28:04 GMT
Footnote – I2 integrated with Hub; see Changeset #110.
