Returning players! Wiki accounts were reset in late 2014. If you haven't played since then and wish to edit the wiki, you'll need a fresh account.

Admin Manual

From BlogNomic Wiki
Jump to: navigation, search

This is meant to be a brief tutorial on basic admin tasks for new or forgetful admins.

Adminning Proposals

You'll find an edit button in the top-right corner of a blog post. In the screen that pops up, you'll have to do two things:

  • In the admin text box, report your name and the vote count (e.g. "Reaches quorum at 8-1. Adminned by Bob") or the fact that the proposal was self-killed or vetoed, as per rule "Enactment".
  • Under the Options menu, update the proposal's status (enacted, failed etc.).

Now all you have to do is update the ruleset and gamestate if the proposal passed.

Adding or unidling a player

  • Enter the Templates menu (it should be in the sidebar under "Admin Things"). We'll be editing the 'playerlist' template.
  • To add a new player, simply add a line to this list, keeping the syntax intact. Make sure the link points to the correct user page. To unidle an existing player, simply move their entry from the idle list to the active list. Be sure to remove the comma.
  • Update the player count and quorum, and press "Update and Finished" to save your changes.
  • Enter the GNDT config editor and enter the password (if you don't have it, ask a fellow admin to provide it for you).
  • Again, to add a new player, add a line to the player list. Make up a password for that player, preferably one that's easy to remember. To unidle an existing player, remove the '#' in front of their name to uncomment that line.
  • Save your changes and leave the config page.
  • Be sure to initiate the new player's GNDT stats at this point.
  • If you've added a new player, don't forget to send them an e-mail or ExpressionEngine private message to welcome them and provide them with their GNDT password.

Idling a player

  • Enter the Templates menu and select the 'playerlist' template.
  • Move the idled player's entry to the idle list, adding a comma at the end.
  • Update the player count and quorum, and press "Update and Finished" to save your changes.
  • Enter the GNDT config editor and enter the password (again, ask a fellow admin for it if you don't have it).
  • Comment out their entry by putting a '#' in front of it.
  • Save your changes and leave the config page.

Notice: Always try to keep the lists of players in the sidebar and GNDT in alphabetical order, for convenience's sake.

Dynasty Changeover

  • Templates that have Dynasty info include
    • dynastic_banner (usually an h1 until an image is provided)
    • index (in the title tag)
    • sidebar, if there are Current Documents other than the ruleset
  • Don't forget to take us out of hiatus, in the sidebar
  • Update the main page's dynasty index, if not done
  • Update the Template:Dynastic_Histories box
  • Move Current Game Documents on the wiki front page down to Older Core Game Documents

Editing the GNDT configuration

Right underneath the table on the sidebar, but you'll need the admin password. If you don't have it, ask.

Changing the sidebar, site HTML, etc.

All of these are found under Templates in EE. The list of players is under the Template 'PlayerList'. If you want to idle or unidle someone, move their line from one column to the other. If you want to change the colors, fonts, and such things, look under the stylesheet for the appropriate data--and change the CSS. Don't go plonking colour and style exceptions in the individual templates. Again, backups are useful here. If you are adding image files, stick them in the image directory--you can use FTP for this if you have a lot of files to transfer.

Server access

(Only a couple of very trusted players currently have shell access to the server.)

Shell scripts

You can run shell scripts as a cronjob if you like. If you upload CGI or PHP scripts, make sure that the ~/.htaccess file is updated to reflect your directory. Similarly for applets. Stick javascript in the appropriate template.


[ This information may be obsolete as of 2015, as EE has been updated to a much newer version. ]

To change the CAPTCHA trivia question, edit mbr_captcha in ee/system/language/english/lang.member.php, and edit the answer in ee/system/modules/member/mod.member_register.php.

There's also some commented out code and messages for ReCAPTCHA, which we tried using for a while but which didn't do anything to stop the creation of spam accounts (it seems likely we're just dealing with human spammers who can jump through a few simple hoops to set up an account). If you reenable ReCAPTCHA, the system messages you need to change are captcha_required and captcha_incorrect in ee/system/language/english/lang.core.php.

As of 2015, the BlogNomic wiki uses a CAPTCHA question upon account creation. This can be changed in the wiki's LocalSettings.php on the server.

Don't Break Anything

As a general rule, don't mess around with things unless you know what you're doing.

If you do manage to break something, or find something broken by someone else, you should either post a blog entry about it or head onto Slack to discuss it with other players, so that we know who's broken what, what they were changing when it broke, and can coordinate our efforts to fix it.

Making new admins

1. Go into your control panel, then "Admin". Click on "Members and Groups", then "Member search". Search for the member you want to make an admin. Under "Member Administration", click on Member Preferences, then change the Member Group Assignment to "Administrator".

2. Go to the player list. Find the member to be made an admin, then add ' class="admin"' to the end of their member link, and an asterisk to the end of their name (so <a href="/member/15">Josh</a> would become <a href="/member/15" class="admin">Josh*</a>).

3. PM them the password for the GNDT. Make sure that they have a wiki account.

4. Anything else? Specifically - how to get the "admin things" links in the sidebar? (I think that "Admin Things" is automatic.)

Known ExpressionEngine bugs

This hasn't been tested exhaustively for similar edge cases, but it seems to be the case that writing flavour text which contains a link with a title tag that contains an apostrophe, such as:

<a href="" title="it's this">test</a>

... causes the blog front page to crash displaying the error message "Parse error: syntax error, unexpected T_STRING in /home/blognomic/www/ee/system/core/core.functions.php(634) : eval()'d code on line 66"