User talk:Kloke

From DWPriests
Revision as of 09:22, 24 July 2021 by Kloke (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Happy to chat, either here on the Disc, or email me through the wiki.




Hi Kloke,

I saw your post on Priestsguild board. I can help out some. Although I have not added much here on the DW Priest wiki in the past, I have helped Emily to update the charms info and custom bead prices on the main DW Mud wiki.

Persephone (talk) 17:51, 10 June 2018 (BST)


Welcome aboard Persephone,

I've given you Admin, validated and moderator rights.

Here's what Mishal said to me and may be informative to you:

"What I've done is set you as 'bureaucrat', 'moderator' and 'validated' on the wiki. Bureaucrat status lets you assign rights to other users as well as blocking people (a new permission that I just added); moderator status gives you much greater control over pages, including being able to delete pages, edit the wiki interface itself, edit protected pages (and mark pages as protected) and browse deleted pages; validated status simply means that I've verified that your account is of a MUD player (as opposed to a spammer, primarily) and simply allows the creation of new pages.

See http://www.dwpriests.com/wiki/Special:ListGroupRights for a full list of permissions for each group (I hope you can see that page, at least!)

Since you can now control user permissions on other people, you can assign "validated" to any wiki user who's a known MUD user (I had plans to automate that back in the day :)) in order to let them create new pages. Any registered user should be able to edit pages - if there's an issue with people not being able to register, let me know and I'll look in to it when I've got a minute. When I set up these permissions I found that the spam bots weren't interested in editing pages, they only wanted to create them, so banning unregistered users from creating pages was a good way of blocking the spammers. 6+ years later, I have no idea how effective that may be :)

Also feel free to assign other players to 'bureaucrat' and/or 'moderator' positions as you see fit. Obviously keep those to trusted people only, given that merely 'validated' users can do most editing work :)"

He also mentioned how out of date the software of the wiki is, and I suppose as long as this version is stable and doesn't have known vulnerabilities, we're OK for the time being.

I'm thinking of doing more comms to let the Disc know that we're open for business if anyone has new information - my first thoughts are town criers and an ad in the papers, which should be enough without going over the top.

Finally, for now, we'll need to update the main page to reflect us as being points of contact. I'd like your thoughts on that and anything else wiki related before I do anything though. Maybe catch up on the Disc next time we're both on?

--Kloke (talk) 09:26, 11 June 2018 (BST)


HTTPS stylesheet problem

Hi Kloke,

There seems to be a bit of a problem when viewing the wiki over HTTPS instead of plain HTTP: It tries to load the stylesheet from https://www.dwpriests.com:80/, which doesn't work, so you end up with a text-only page. (And my browser keeps insisting I look at the HTTPS version)

Hoping this is something which can easily be fixed in a template, wiki setting, or server config?

Rigrig (talk) 16:52, 11 July 2021 (BST)

Hi RigRig,
I get the same kind of behaviour. I did a bit of digging and results in https://www.mediawiki.org/wiki/Manual:Common_errors_and_symptoms#The_wiki_appears_without_styles_applied_and_images_are_missing suggest that the $wgServer variable needs to be set to the host name that people use to access the wiki - dwpriests.com. That's as far as I got so far - it isn't clear to me how that is set, and some search results suggest that it is depricated in newer versions of mediawiki. My role here is quite admin-ey (user settings and content manipulation), so this aspect of configuration is outside of my current skillset. I may need to get some help from Mishal (or guidance from someone else) on this. How much of an issue is this? I appreciate that there is a move for browsers to insist on HTTPS for all websites, so it could be that we can kill two (many?) birds with one stone here.
Best wishes,
Kloke (talk) 14:48, 17 July 2021 (BST)
From that link it looks like autodetection was deprecated, not setting the $wgServer variable manually. Apparently you need to edit the LocalSettings.php file, i.e. you'll need access to edit files on the server, so I guess that means asking Mishal? My guess is ideally it should end up containing (amongst other things) something like this:
$wgForceHTTPS = true;
$wgServer = 'https://www.dwpriests.com';
$wgCanonicalServer = 'https://www.dwpriests.com';
I suspect there's some proxy stuff complicating things, but hope this would just redirect everybody to a working HTTPS site. (Quite possibly there's a :80 somewhere in there now, which should be removed)
Rigrig (talk) 20:24, 23 July 2021 (BST)


Thanks Rigrig,
I've emailed Mishal for advice/help.
Kloke (talk) 10:22, 24 July 2021 (BST)