User talk:Hoggwild5

Please leave comments about any extensions I have submitted to www.mediawiki.org on the extension discussion page. If you have questions about MediaWiki code hacks, please leave them on the code hack discussion page. I don't check my personal talk page very often.

Thanks!

UserPageEditProtection
Hi, Lisa

I found the UserPageEditProtection extension does not work on 1.11, Can you update this extension for 1.11? thanks a lot!

Done --Hoggwild5 20:09, 6 December 2007 (UTC)

Custom Edit Article w/ Fields
Hi Lisa,

Can you elaborate on your concerns over User_talk:Barrylb/Custom_article_editing_form_with_fields? I noticed that the $wgReadOnly parameter is bypassed but what are the other potential issues? Also, is there an easy way to incorporate them?

Any other thoughts would be appreciated. Blckdmnd99 00:07, 4 June 2007 (UTC)

Sure, I'll be happy to. The hook that this extension uses hooks into the beginning of the edit code in Editpage.php. This coding goes through a number of checks and balances both when you start to edit a page (either by using a custom form or by using the MediaWiki edit screen). This extension is performed in place of the processes in EditPage.php. Since it is a replacement for the edit function in EditPage, and the checks and balances in the code have not been included in Barry's code (checking for edit conflicts with another user is a primary one), there is the possibility that data can be lost, or the appropriate warning messages that you would normally see for edit conflicts would not get delivered to the user. The possibility that this would happen gets larger as a site has more users; if your site has relatively few editors, most likely it will perform fine. I have actually implemented a number of forms based on this code on a couple of sites that I have, but I have restricted my editors to approved users only so I know that the chances of conflicts are minimal.

Hope this helps!

--Hoggwild5 02:14, 4 June 2007 (UTC)

Indeed. Thanks for the scoop. Better than learning the hard way. :) I'm going to take a closer look here but do you think it would be possible to incorporate the Editpage.php checks into the customedit code? Or would this cause additional conflicts? If I can come up with anything I'll give you a shout as well.

Thanks much. Blckdmnd99 03:20, 4 June 2007 (UTC)

Well, you could incorporate the code from EditPage.php, but you will need to make sure you understand PHP's object-oriented programming process (for example, all of the "$this->" instructions will need to be changed to "$editpage->") to make it work properly. It will be quite a bit of work. A better method would probably be to make a new class that extends EditPage -- this way all of the functions outside of edit would not have to be recreated, and would instead be part of the new class.

I have sent a request that EditPage.php be rewritten to make it more modular and thus easier to write extensions for, but it hasn't made it on the priority list yet. --Hoggwild5 18:01, 4 June 2007 (UTC)

CreateArticle suggestions
See Extension talk:CreateArticle for the start of some suggestions (and there are other questions by other people that need answering too). —Eep² 11:39, 20 August 2007 (UTC)

Article Creation Question
Hey there-

I am an instructor of Animation ,and was wondering a few things about your extension "CreateArticle". I wanted to know how difficult it would be to alter this extension to do the following:

Lets say that my user types in: CharacterDesign, the extension would:

1. Automatically detect the user and use that as the "prefix" parameter.. (ie - User:Sstudent)

2. Secondly, it would need to create the page using the name they type in as the subpage parameter (User:Sstudent/CharacterDesign)

Ultimately, I have restricted the creation of pages for the students to their user and usertalk including subpages. This allows me to keep it all managed easier. I would eventually like to register all of the Courses we are teaching into an index that the student could select from. This would then create the article as a subpage of their User page. To fine tune it, I would have the WIKI automatically list any immediate subpages of the page they are attempting to create their article, so that they could easily keep track of where things are going. I know that this is a tall order, but I thought I would get your input, so that I can let our IT guys know how much work it would be.

Thanks

Scott

--sheriffcicada 18:34, 7 February 2008 (UTC)

Hi Scott:

I think that's definitely doable. It would require modifications to the extension to make it work, but they shouldn't be too difficult.

I'm gonna give you some technical information that may help your IT people get there quicker...

Just off the top of my head:

The user information for the current user gets stored in the global container $wgUser, which is of the class type User (the details on the class are in the script includes\User.php). You could get the current username from $wgUser->mName.

All User pages are stored in the "User:" namespace. So, the CreateArticle script could be modified to get the username of the current user, like so:

The CreateArticle input box that users see on the screen is where they would enter the CourseName of the page they're wanting to create; for example: CharacterDesign.

The CreateArticle script can then be written to take the user input and append it to $ArticlePagePrefix, and use the result to create the new article in the User: namespace as a subpage of their username.

That would be where I would start.

Let me know if there's anything else you need.

--Hoggwild5 20:35, 7 February 2008 (UTC)