Making Wikia work for me

My goal: Set up a Wikia wiki for my Vygis Stories museum.

The museum will consist of stories, and photos of objects and people.

I want to use tagging to create pages that group the contents of the wiki several different ways and have Table Of Contents pages that show those groupings.

Blogger has tags, but apparently a 127 tag limit (need to re-find the reference for this). My memory blog has a long tag list and it's easy to click on a tag link and see all entries with that tag, so for that blog I'm pretty satisfied.

In Wikia, they don't have tags, but have something called categories.

I want to have a hierarchy of categories: Top level categories, the following list:

Stories
Traditions
Themes
Things
Year
Date
People
Places
Nicknames
Author

In Wikia, when you add a category to a page that you've made, the category seems to have its own page too. So if I add a category named "Oldsmobile", there must be a page named "Oldsmobile". That "Oldsmobile" page can have a category "Things". At this point, the "Things" page will show "Oldsmobile" as a subcategory.

I would like categories like "Oldsmobile" to contain the name of the top-level category as well, like "Things: Oldsmobile" which would rigidly enforce the relationship of top and bottom categories at the bottom level, and make the meaning of the categories attached to a story clearer. The downside of this is that it breaks the lovely category alphabetization that seems to be built in to the listing of subcategories.

I guess what will happen is that all subcategories, particularly things, will be entered directly. The top level category being added to the bottom of the subcategory page will immediately get them added to the top level. These can all be then referenced in stories.

An issue seems to be that all things have stories attached. Should the stories be separate from the thing or be part of the thing's page? There are hundreds of Oldsmobile stories, which is an example of it being better to have the stories be separate. The Red Green Show DVD has only one story, and it seems ungainly to have to go to the Red Green DVD's thing page to get to the story.

PuTTY -batch Authentication Denied

New system. PuTTY pscp is not working right. Normal pscp -v -batch in the code is failing with an unhelpful "Authentication Denied" message. Directly logging into the remote system with PuTTY is working fine.

What I learned to fix it:

1. Get the most current version of PuTTY. Googling the problem revealed that many online thought that there was a "bug" in version 0.60 that caused this, and upgrading to 0.62 (apparently the most recent version) fixes it. Here's a few links of many in which this assertion is made:

http://www.derkeiler.com/Newsgroups/comp.security.ssh/2009-02/msg00070.html

https://groups.google.com/forum/#!topic/comp.security.ssh/GbAEXzBD8hE

http://earthwithsun.com/questions/312197/putty-0-61-why-do-i-see-access-denied-message-after-i-enter-my-login-id

2. After performing the upgrade it still gets me Authentication Denied, but also better error messages. Now it also says "GSSAPI authentication request refused". Whatever the hell that is. From the following links, I learned that I mostly just need to disable GSSAPI authentication, and the best way to do this was through the PuTTY configuration:

http://superuser.com/questions/465709/getting-access-denied-error-in-putty-with-a-normal-user

http://superuser.com/questions/312197/putty-0-61-why-do-i-see-access-denied-message-after-i-enter-my-login-id

Here is the same explanation applied to a slightly different situation (not trying to use pscp):

http://nolabnoparty.com/en/access-denied-ssh-error-with-putty-in-windows-7/

3. I was able to make a PuTTY configuration that had GSSAPI turned off and pscp started working, but my configuration was poorly named. I had made two configurations, one named @ and the other being named . The one with GSSAPI turned off was @, and if I did pscp -v -batch -load @ it worked. After looking at how I had PuTTY configured on my other systems I realized that for pscp with the private key authentication to work automatically without having to feed it the parameter for which configuration to load, I needed the configuration to be set up with the user name as the default username in the Connection->Data parameters. So I deleted the @ configuration, and corrected the configuration to have the username as the default username, the private key selected under Connection->SSH->Auth and GSSAPI turned off under Connection->SSH->Auth->GSSAPI.

4. Now the new system is set up like my other systems. Except that arguably they are all wrong now; what I should have is a custom named configuration that the code calls using pscp -load rather than having the default pscp configuration for automatically using the username and keys.

5. I should upgrade PuTTY to version 0.63 now for security reasons:

http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html