This is a static dump of issues in the old "Flyspray" bugtracker for DokuWiki. Bugs and feature requests
are now tracked at the issue tracker at Github.
FS#2237 The indexer pixel is matched and removed by Privoxy
CSS, XHTML, JS, Browsers
The indexer pixel is matched by the standard Privoxy configuration. This means that there won't be any search index created at all (and e.g. the first heading won't be displayed anymore in some cases, too). The problem is that it tries to match tracking pixel by using a regex to find the height/width attributes (<img[^>]*\s(?:width|height)\s*=\s*['"]?(?=\D)[^>]*\s(?:width|height)\s*=\s*['"]?(?=\D)[^>]*?>). I can imagine other add/tracking pixel blockers are matching it, too. Some suggestions:
- talk to the Privoxy developers explaining them that at least in DokuWiki core we don't use that pixel for any tracking and that it is really needed and asked them to whitelist it
- try to work around by using a 1x2 or 2x2 image (or at least set the attributes to that)
- remove width/height and just use CSS in order to work around the tracking pixel detection
I would prefer displaying a warning as this could detect broken templates, too, and I don't like the workarounds. Thx to amee2k in the IRC-channel who had and debugged the problem. I'm btw. convinced this is actually a problem as in private wikis there might only be one user who visits certain pages and if that user uses Privoxy or another tool the search (and in the future also some more features like tagging) won't work for him without an easy way to find out what's wrong.
Fixed in e20ddf03 (1x2 pixel) and in 26f7dbf5 a check has been added if the search index exists that can detect if the pixel is completely missing or blocked and thus no search index has been created at all.