User talk:Kotra

From PortlandWiki
Jump to: navigation, search

For older discussions (pre-LiquidThreads), see the archive.


Thread titleRepliesLast modified
Move920:01, 26 April 2012
template transclusion600:54, 10 November 2011
Additional possible .htaccess errors.222:09, 30 October 2011
Potential Page Title Conflicts?: / vs _-_022:08, 3 October 2011

am I missing it or is the move function gone? Best,

MarkDilley00:30, 2 November 2011

ahh, something weird seems to have happened - I am unable to upload now as well. Best,

MarkDilley01:10, 2 November 2011

Sorry Mark,

We're still in the middle of upgrading the wiki and attempting to stomp out dysfunctions that keep popping up. Had to break off last night so Kotra could get back to his family and so I could get some rest.

Going back to the grindstone now...


WikiMaster (talk)06:58, 2 November 2011
The dingo ate my Namespace.
Code Pulled From LocalSettings
# September 18, 2011 - Added by Dave Myers.
# Extension:Lockdown - Source:
require_once( "$IP/extensions/Lockdown/Lockdown.php" );
$wgSpecialPageLockdown['Export'] = array('user');
$wgNamespacePermissionLockdown[NS_MAIN]['edit'] = array('*');
$wgNamespacePermissionLockdown[NS_TALK]['edit'] = array('*');
$wgNamespacePermissionLockdown[NS_USER]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_USER_TALK]['edit'] = array('*');
$wgNamespacePermissionLockdown[NS_PROJECT]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_PROJECT_TALK]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_FILE]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_FILE_TALK]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_MEDIAWIKI]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_MEDIAWIKI_TALK]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_TEMPLATE]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_TEMPLATE_TALK]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_HELP]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_HELP_TALK]['edit'] = array('*');
$wgNamespacePermissionLockdown[NS_CATEGORY]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_CATEGORY_TALK]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_SPECIAL]['edit'] = array('user');
$wgNamespacePermissionLockdown[NS_MEDIA]['edit'] = array('user');

# November 2, 2011 - Added by kotra
$wgGroupPermissions['user']['upload'] = true;
$wgGroupPermissions['admin']['upload'] = true;
$wgGroupPermissions['autoconfirmed']['upload'] = true;
See Also
Please Note

We'll want to fix our installation of Lockdown as quickly as we can, or find a suitable replacement.

WikiMaster (talk)05:24, 3 November 2011

Hey Kotra,
Will you please ask the Dingo if it'd stop eating the Liquid Threads messages?
Thanks a bunch!

WikiMaster (talk)19:57, 26 April 2012

no, Dave (aka WikiMaster). You are not welcome. Please refrain from existing. Thanks.

kotra (talk)20:00, 26 April 2012

Oh my god! I saw that lockdown code, thought it was strange, but didn't think it could be causing the problem. In hindsight, it fit my knowledge of the problem perfectly!

What were we using that for anyway? Is there a newer version of the extension that we could install, in hopes that it would work?

kotra (talk)08:23, 3 November 2011

Oops, I thought I had responded to this. Belated but sincere thanks for doing this, Dave! I had noticed that lockdown code in the localsettings and thought it was strange (I'd never seen it before), but didn't put 2+2 together (I've recently been informed that the answer is 4!). Question: what is lockdown and what do we need it for? I'm guessing it's there to make certain namespaces like templates restricted to admins?

kotra (talk)20:59, 9 November 2011

Hey kotra,

As I recall, we installed Lockdown to restrict anonymous editing to just a handful of namespaces. I've noticed that we're getting vandalized on some of the formerly restricted namespaces after inactivating the extension. Will look into this...

WikiMaster (talk)21:11, 9 November 2011

Alright, thanks! Meanwhile, I'll look into the bandwidth issue you mentioned in another thread...

kotra (talk)21:14, 9 November 2011

template transclusion

hola, the Template:Occupy_Portland_Event you made is very cool. i have one thing i'd like to make better for other users.

i gave each event its own page, and am transcluding some events on OccupyPortlandEvents. But, since those events are now using your template, when a person clicks the "improve" button next to the event - it takes them to editing the template not the event content.

i've found this page about the issue, but can't figure out the best approach.

Some options might be:

  • use __NOEDITSECTION__ to suppress the improve button
  • add a link to the transcluded page in the template.
    • would {PAGENAME} do that? if so: where would that link go?
      • could the the title by a link to the page?
      • could there be a boxed section at the end of the template with the words "the events page"?
      •  ??
  • remove the header from the template, and force people to manually put a header/title on the event's page. this header would wind up appearing above/outside of the template's box, perhaps the template could always say "Details" as its first item ( would look like "Purpose" does ). the downside is on the page itself you'd see the page name immediately followed by the header; might look a little messy.

Of all of them, i think i like the last one best, but wanted to see what you thought first.

Ios (talk)10:39, 3 November 2011

I see the issue... thanks for bringing it up! I didn't quite understand all your options, but I've been trying to replace the "improve" link with one that works. You can see my attempts in the Template:Occupy Portland Event history. My attempt successfully created an edit link... to the OccupyPortlandEvents page (not the transcluded single-event page). Obviously not good enough, so I removed it. I have to take a friend to the hospital now but I'll give it another shot when I get back in a few hours. In the meantime, by all means if you want to give it a shot, feel free. The transclusion is confusing the issue a little but there may be a way to link to the transcluded page that I haven't found yet.

kotra (talk)11:31, 3 November 2011

Also, I made you an administrator so you can edit templates (if you couldn't already).

kotra (talk)11:32, 3 November 2011

Thanks Simon for working on fixing the edit link on Template:Occupy Portland Event, and sorry for not getting back to this sooner! It looks like you've come to the same conclusion I have: that automatically linking to the transcluded page is impossible (confirmation from one of the developers here). I saw that you added another field to the template ("page"), which allows the editor to hardcode the page name, allowing an edit link to come up. Thanks for doing that! Though it's an imperfect solution, it's the best one I've been able to think of too. Do you mind if I take that edit link and tweak it so it looks like one of the "[improve]" links beside section headers? You're the main person who uses the template so I'll defer to your preference.

Thanks again for working on this.

kotra (talk)22:22, 7 November 2011

kotra: sorry for forgetting to send you a heads-up that i had changed the template to include that link. you're right it's not a perfect solution, but yeah: seems like it may be our best option. you're more welcome to change it to look more like "Improve". ( Mark, I think, changed the language of the generated link slightly already. ) I just wanted *something* in there to be able to jump to the page...

I think the template really improves the look of the events. It definitely seems like a win!

Ios (talk)16:22, 8 November 2011

No problem Simon, and thanks! I just added the [improve] link, leaving the old edit link alone.

kotra (talk)20:49, 9 November 2011

looks great!

Ios (talk)00:54, 10 November 2011

Additional possible .htaccess errors.

Hey ’tra,

(I've chosen to knock your user name down to one syllable in compliance with my self-imposed verbiage reduction initiative.)

The .htaccess "fix" we used several weeks ago (Potential Page Title Conflicts?: / vs _-_) may have open up another "can of worms" (although it's unclear of our previous "fix" is creating the issues described in this thread).

It appears that PortlandWiki URLs now break when there's a "." (dot) somewhere in the URL. More specifically, they're accessible via the "ugly" URL format, but not the "clean" format.


Terry D. Schrunk

Since your regex skills are more advanced than mine, would you mind looking into this?


WikiMaster (talk)13:06, 28 October 2011

Thanks 'ster! Yeah, I've been aware of this issue for a few days now, but haven't had time to work on it. I actually left you a board message a couple hours ago about it, trying to pass the buck to you. But I may have some time tonight to look at it.

As for my regex skills, it's pretty hard to be less advanced than me at it, but I'll do my best.

kotra (talk)14:45, 28 October 2011
Current .htaccess
RewriteEngine On

RewriteCond %{REQUEST_URI} ^/.*&.*
RewriteRule ^/?(.*)&(.*)$ /index.php?title=$1\%26$2 [L,NE]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule ^(.+)$ index.php?title=$1 [L,QSA]
Articles that now seem to function
WikiMaster (talk)22:05, 30 October 2011

Potential Page Title Conflicts?: / vs _-_

Before your .htaccess fix, this one worked:

Occupy Portland - Press Releases

This one didn't:

Occupy Portland/Press Releases
MediaWiki r65286 - Code Review
WikiMaster (talk)22:08, 3 October 2011