There's also an "extensions/examples/Content_action.php" file, which sounds like it may be particularly interesting to you. It's viewable via the web at: http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/examples/Content_... tion.php?revision=12179&view=markup

Hope that helps.

All the best, Nick.

Thanks for finding the file and finding instances of the content_actions array.

That helps some. Point of confusion #1 for me appears to have been whether the referenced file was in the distribution I downloaded, or on the CVS/viewvc directory you cited. I had looked there as well, but it has moved from extensions/... to extensions/examples... , thus my confusion.

I'm not up to altering things over there just yet, but for someone who makes it easy, that path might best be revised in the hooks.txt file where I found the reference.

Point of confusion #2 was my hope that content_action.php would be a repository of keys to the instantiation logic, rather than an example of how to add tabs. I was hoping to find something like MediaWiki:Sidebar where I could use text to describe what tab appears when. Unfortunately, it seems I'll have to think my way out of this one instead.

The example in content_action.php of how to add an edit tab might illuminate my study of how to remove the tabs. I only want them to appear on particular pages for users who have edit privileges for those particular pages. The if/else that replaces "edit" with "view source" is one place to start poking around, but that only seems to respond affirmatively to page protection. Conceptually, it seems easy enough to change the "else" action that returns "view source" so it simply doesn't render the tag at all, but that only allows the tag to be removed from protected pages. I'll probably need to find the logic that returns a "not logged in" message when log-in is required, then move the check-for-log-in status (or other edit permissions) so that it checks before rendering the tab. My code might not be pretty, but if nobody else has developed this functionality, it might be worth my while to carve it out.