Board Thread:Support Requests - Getting Technical/@comment-4189499-20160701065354/@comment-4189499-20160701094535

Thanks Dessamator! I'll have a look through the table tutorial because I'm not the most familiar with Lua and so I can see that there will be mistakes. I just can't tell what they are easily because the error on publishing is vague and only being thrown from the first line. I've already confirmed that the brackets are matched.

The Lua editor isn't showing up at all for me for some reason, even when there's only the one current comment on the page. I've got syntax highlighting turned off for the regular source mode editor, but I don't know why that would affect the Lua editor since it doesn't affect the CSS or JS editor. Hang on, that's now affecting the CSS and JS editors too! It never used to, and that was how I liked it. Why on earth would we want syntax highlighting in wikitext, where it is just a nuisance that clutters the page, but force it to be linked to syntax highlighting in CSS and JS, where it's actually useful? But I digress. Still, if you think it's too much for a single module to handle, we'll investigate splitting it up into groups to improve performance. That is, if we decide to keep the Lua method.

I haven't even heard of WikiData before. When I was looking up a way to integrate an actual database into the wiki, all I could find was WikiDB and AccessPostgres, neither of which seemed like good options, hence the fallback to Lua tables (which are themselves hash tables so lookup theoretically is quick). But now you've pointed out WikiData, we'll definitely investigate that before continuing with the current attempts! Thanks for that!