Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Mon, Jul 2, 2018 01:43 PM UTC:

While checking the error logs this morning, I came across errors in index/tagsinfo.php. It is accessing both the TagDetails table and the Tags table. The Tags table is something I recently started, and the TagDetails table is something that someone else (Ben?) had started previously. I notice it was last updated today. So, someone is still working on this. In the database backup, there are some old tables called TaggedItems and Tags. It looks like maybe I renamed Tags to TagDetails, got rid of TaggedItems, and started a completely new tagging system with a new Tags table. The current Tags table is unrelated to the old one, and it has no connection with TagDetails. The current Tags table is a many-to-many table of user-created tags, and each tag is just a string, not something with a description or an ID. This implements an open-ended system for allowing users to add any tag they wish to any page.

It looks like the original tables for tags were trying to implement a closed system of select tags. I'm not sure if they were meant only for editors to add or for anyone to add, since the code never got that far.

I have been thinking of using tagging to better organize the pages, but this may involve making tags less open than they are right now. Any thoughts on how this could be done?

Anyway, when someone else is coding something here, I need to be updated on what is going on. This will help keep things coordinated.


Edit Form
Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.