Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>

[[ 🗃 ^yEzqv rel4tion-wiki ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

Tags

master :: tickets / general /

1.mdwn

[[!template id=ticket class=problem done=yes]]

[[!meta title=“Fix ticket system templates”]]

In ikiwiki, the special tests supported by the [[/ikiwiki/PageSpec]] can only have a glob inside them, not a general nested PageSpec. The templates related to the ticket system do assume (erronously) that nested PageSpecs work, and the result it that the generated pages contain many errors (most not visible yet because many page counts are 0).

Without the power of nested pagespecs, ikiwiki’s pagespecs aren’t expressive enough for use in the ticket system. But I’m not yet planning to install any “real” issue tracker. My solution will be a dirty workaround. One of the following is possible:

  1. Go over the problems and see if all of them are a result of putting the nested pagespec “tickets/* and !tickets/done” inside tagged(). If yes, one solution is to move tickets/done and tickets/general somewhere else, or make a parent page for classes. So the hierarchy will be:
    • tickets
      • class
        • task
        • idea
        • …
      • general
      • done
  2. Another solution to this is write the class names explicitly, but that’s quite dirty, since adding or removing or renaming a class will require careful and error-prone updates to the templates.

But there may be other issues - go over them and see if the above suggestions can fix them all. If not, add suggestions here.

The pagespecs have been fixed. Indeed it required a bit more than the tagged() issue, but it definitely was the main issue. Everything works now. The classes have been moved into a subpage /tickets/class/.

[See repo JSON]