This page lists old bugs in 'Tavi that have since been fixed. It is kept around for historical purposes. Eventually, old bugs may be purged. An alternate page which serves a similar purpose to this is TaviBugsResolved. See also TaviBugs for bugs yet to be fixed. See TaviReleaseNotes for a more complete listing of changes to each version.
Fixed in version 0.26
Fixed in version 0.25
- International characters in summaries. There was a problem with names like CursosFormació in the summaries, but this seems to have been fixed, somehow. :-)
- Running in PHP Safe Mode. See TaviBugs/PhpSafeMode for explanation, and please comment if this bug is not fully fixed!
- TaviBug:802784 : Using quotes in summary comments
- TaviBug:802780 : Category adding
- TaviBug:802781 : Disabling free links
- TaviBug:827658 : Second URL not recognized
- TaviBug:809733 : Free links vs WikiNames in TaviCategories
- TaviBug:802786 : Adding of ((0)) sends to home page?
- TaviBug:836525 : Handling of negative timezones
- TaviBug:840624 : Tavi doesn't validate as strict XHTMl 1.0 anymore
- TaviBug:840627 : Problems using URLs ending in &
- TaviBug:829113 : Pages deleted when $ExpireLen=0. See also TaviBugsFixed/ExpireLenBug for a fix to apply to previous versions
Fixed in 0.23
- Macro Names appear in WantedPages. WikiNames mentioned within [[ ]] are no longer mentioned at WantedPages
- Some InterWiki and SisterWiki quirks. To avoid the nickname of an InterWiki from appearing in WantedPages it's now allowed to use lowercase characters to start the nickname, or use ! in front of it. In addition it's now allowed to use https-references as InterWiki's or SisterWiki's.
- <code> now allows whitespace. It was not allowed to have whitespace in front or after <code>-tags. This now allowed.
- ActualNonExistentPage?[1]: This construct used to create interesting text, but should not do so anymore. ActualNonExistentPage[http://tavi.sourceforge.net/]. This was solved by removing chr(255) as an uppercase character. Please notify us if that is untrue for some language.
- Space between InterWiki links. Construct like Tavi:TaviBugs Tavi:TaviBugsFixed Tavi:TaviBugsResolved with only one space between links fails to be properly shown.
Fixed in 0.22
- A PHP regex bug in versions 4.03pl1 and earlier causes free links to render with a trailing "\5" on the URL. The fix is either to:
- Upgrade PHP to 4.04 or better.
- Edit parse/transforms.php. Find the parse_freelink function. Change the second assignment of $ptn by adding '()' as indicated in bold:
- $ptn = "/\\(\\(([-A-Za-z0-9 _+\\/.,']+)((\|[-A-Za-z0-9 _+\\/.,']+)?)((\#[-A-Za-z0-9]+)?)()\\)\\)/e";
- If you use single quotes (apostrophes) in link names, you will get a lot of database query errors. Various files failed to add slashes to page names before executing an SQL query. An interim bugfix release is expected very soon to resolve this issue; until then, you can grab the fix out of CVS. Contact ScottMoonen if you need help doing so.
- In Mozilla, when saving preferences, a blank page appears (unlike Netscape and IE, which redirect back to the wiki). The fix is a quick one-liner: add the following to the list of variables pulled from $HTTP_POST_VARS in lib/main.php:
- $referrer = $HTTP_POST_VARS['referrer'];
- PHP 4.1 (or any level of PHP with error_reporting=8 turned on) complains about various undefined array members and variables.
- configure.pl doesn't escape single quotes in strings. For example, if your Meta Description is 'Tavi it will be written to config.php as $MetaDescription? = ''Tavi';, which will result in parse errors.
- configure.pl silently writes an empty config file when settings.cnf is in DOS format.
- Title markup sometimes does not "take". The heading regular expression was too restrictive; have changed it to allow arbitrary whitespace before the first equal sign, and after the last equal sign.
Fixed in 0.21
- When viewing diffs between pages using Mozilla, the background colors used to highlight the differences aren't displayed. This appears to be caused by the lack of hash mark (#) preceding the color. For example, it's currently bgcolor="cfffcf", and it should be bgcolor="#cfffcf". Netscape 4.x and IE work around it, but Mozilla ignores the malformed attribute.
- Won't accept a free links variety of UserName in [Preferences] - no error message generated, redirects back to referer page, but does not retain cookie value, or at least recognize it. Using Galeon browser on Linux (well, at least this evening I am ... I could be using one of a half dozen different browsers at any point in time) ... -Naum
- Aaah... Looks like lib/init.php is forcing the username to be interpreted as a WikiName, even though action/prefs.php is happy saving it (sort of -- it should urlencode first). I could've sworn I've fixed this very bug before.
- In other news, there seems to be a bug in how validate_page works... I'll see about fixing both of these relatively soon. -- ScottMoonen
- Certain patterns cause false matches in parse_diff_message.
- The following renders wrong: {{abc}
- This is because the abc maps to \{n}. This then allows the completion of the {{ .. } syntax to map the contained text to teletype. Oops. Maybe we should do teletype before everything else.
- Later... CVS now uses chr(255) to flag parser entities, so there's no collision between parsing's internal markup and wiki markup.
- Images that are included in a document (see FormattingRules) don't have an 'alt=' property, which is required by XHTML-Transitional. Fixed in CVS.
- Double indented text shows up as single indented in Mozilla.
- This was our one biggest area of XHTML non-compliance. Turns out there were two problems: one, a bug in which lists were ended in reverse order from their starting (e.g., <dl>..<ul>...</dl>..</ul>). And two, we were starting lists inside of lists, instead of inside of list items.
- This has now been reworked to be compliant and still render wiki markup in the expected sense. Get the fix from CVS.
- Fixed. Woohoo! :-) In addition to lists and alt tags on images, we needed to emit a charset. Which is now done unconditionally.
- This brace } isn't monospace. This {{funny{thing}}} becomes this <tt>funny{thing</tt>}. I guess technically this could be my problem and not the parsers, but ScottMoonen uses this syntax on TaviOnWindows.
- Changed the parse_teletype regular expression so that any leading and trailing curly braces are viewed as being within the teletype section, e.g., {test}. To achieve the opposite effect, use nowiki markup: {test}.
- Raw HTML tags (<html> .. </html>) are only permitted in lowercase.
- Fixed. Uppercase (and mixed-case) now recognized for raw HTML.
![[Home]](/tavi.png)
