User talk:Egfrank/2007-2015
Template:Extension changes
editHi - I believe you may have messed up Template:Extension because pages in the namespace Extension just don't look ok anymore. I am using FF v2.0.0.6. Jean-Lou Dupont 17:56, 6 September 2007 (UTC)
- Hi - I have left you a reply on my talk page. Jean-Lou Dupont 13:26, 7 September 2007 (UTC)
Backup related extension category
editIs there such a thing? Jean-Lou Dupont 19:45, 9 September 2007 (UTC)
Hmm, I was trying to figure out this edit and why the {{Speedy }} was added to a page which is used as a preload=
on the {{Extension }} page. It seems like that page is needed or the preload will fail. Thanks, still trying to figure this stuff out. — MrDolomite • Talk 00:43, 10 September 2007 (UTC)
- Heh, no problem. At least now I think I have the path of how that Extension:Inputbox stuff works right in my head. That's too bad that the
preload=
andeditintro=
parameter pages do not actually show up as real links. 1) it would prevent any kind of accidental deletion and B) it would make it a lot easier to figure this stuff out. :) — MrDolomite • Talk 16:04, 10 September 2007 (UTC)
Extension:NukeDPL type
editAre you sure that type should have been changed to "page action" from "special"? It's a special-page which allows you to select a list of articles based on a DPL query and then delete them along with their histories. --Nad 00:47, 18 September 2007 (UTC)
New "SMW extensions" category
editHi,
Thanks for creating the new "SemanticMediaWiki extensions" category - it's already useful, and will be more so in the future. However, you should probably rename it to "Semantic MediaWiki extensions", since the original extension has that space in its name. Yaron Koren 15:24, 18 September 2007 (UTC)
Wiki configuration
editGreetings, thank you for your comments on the support desk. I tried a few different versions of the wikipedia software and all yield the same result with munged tables as a result of included gt lt at various points. Still havent figured it out. For example I looked at Navbox and dug into it and the documentation states it relies upon Template:Qif which is deprecated by ParserFunctions.
I was pondering this and am wondering if there might be some magic within the php.ini or LocalSettings.php and am hoping you could send me yours so I could emulate your configuration and pinpoint what may be the problem. I feel there must be something I dont understand that Ive missed.
Many thanks. Nick
My email is nickdwaters@gmail.com
Should you wish to call me 623-330-5199
Re: How is search a page action?
editdiscussion moved to Template_talk:Extension#How is search a page action?.
hi, I have noticed you have been doing a lot of clean up of Template:Extension information for extensions. Can you have a look and add any other relevant information to the Extension:Calendar (Cdamian) article please? --Zven 22:10, 18 September 2007 (UTC)
hi - the aforementioned 'extension' addresses, I believe, all the per-page access restrictions. It does because I included the necessary patches to the stock MediaWiki in the distribution. So, could you please remove the disclaimer ? Jean-Lou Dupont 12:36, 19 September 2007 (UTC)
- The disclaimer isn't personal to your extension, but rather has been added to all extensions that try to limit rights per-page. I'm not really in a position to judge whether or not your particular system is suitable for storing privileged information (trade secrets, credit card info, and the like). If you think it is, you might want to talk to the MediaWiki development team about adding in your patches to the core. You've done something that the entire MediaWiki development team doesn't think it can accomplish at this point. It seems to be the opinion of the MediaWiki guru's that *no* extension to mediaWiki should be judged suitable for privileged content management, even despite some core patches to MediaWiki's RSS and search functions - see the link on the disclaimer for more information.
- I added it to extensions of this class because I really don't want either the extension author or MediaWiki to get sued for loss of trade secrets, income or identity theft. Egfrank 16:49, 19 September 2007 (UTC)
The Plexcel extension has removed page based access control. Please remove the disclaimer at the top of the Extension:Plexcel page.
Extension categories
editGday, I like what you are doing with the extension categorization, I tried doing it for a long time but I got nowhere. Is there some way I can help? Bouncingmolar 13:56, 21 September 2007 (UTC)
- I'd just like to add that what i meant is that I'm at your disposal to do any menial tasks (eg going through every extension to add things to the template) or anything else you think i might be able to do. I don't have much programming knowledge so I can't help much with assigning types. Bouncingmolar 22:39, 22 September 2007 (UTC)
Extension:Wiki Category Tag Cloud
editViorel 07:15, 26 September 2007 (UTC)
Hi, Egfrank, nice work ! :) . I'm the original creator of the YetAnotherTagCloud extension, thank you for the code improvements ! May I replace the (still buggy) YATC on orangedino.org with the WCTC ?
PS: As history, YATC was my first contact with PHP and Mediawiki :) (I've developed it for http://www.mondoflavours.com and http://www.myhobbymodels.com, two of my hobbies).
Unfinished extensions
editHi, I was thinking that another value for extension status would be good for extensions which are still in their discussion or development phase. Extensions are usually in a working state before being put onto this wiki, but some are collaborative efforts or ideas which have begun through discussion here. For example one I've recently started is Extension:PublicRevision which has come about through requests and conversation on the support desk. --Nad 00:47, 6 October 2007 (UTC)
- I see your point. I think the status "Experimental" was meant to handle extensions under development. Do you think there might be a better name for that status? I'd recommend you suggest one on Template_Talk:Extension where those who are especially interested in template classification tend to have a watch set. Please feel free to copy this query to that page, yourself. Best, Egfrank 08:28, 7 October 2007 (UTC)
KeepYourHandsToYourself
editHi Egfrank, I removed the {{Page security extension disclaimer}}
which you had added to the Extension:EditOnlyYourOwnPage and Extension:KeepYourHandsToYourself pages because it contains the following language:
- "... and almost all hacks or patches promising to add them will likely have flaws somewhere, which could lead to exposure of confidential data"
This unfortunately seems to imply that simply because the extensions relate to access control, they are somehow more likely to contain security flaws. I take great pride in the safety and security of all extensions I release, and if there is a specific vulnerability in any of my extensions, I'll be happy and eager to address them. Thanks! --Jimbojw 03:57, 6 October 2007 (UTC)
- My understanding is that the security problems are related to the core of MediaWiki and not to the care you take in developing your extension. Until they address those issues, page security extensions in general are a problem. The disclaimer is meant to protect you and the MediaWiki foundation. It does not in any way make a statement about the quality of your code (which I agree, having read it) seems to be quite careful. So for your own protection, I would recommend you reconsider the decision to remove it. I hardly think you would want to get sued for a problem that is rooted in code over which you have no control. Best, Egfrank 08:38, 7 October 2007 (UTC)
- PS You might also want to look further up this talk page and at User_talk:Robchurch#Per-page access restrictions - advice requested for User:Jldupont's request to remove the extension. He eventually decided to keep it. Egfrank 08:46, 7 October 2007 (UTC)
Your account will be renamed
editHello,
The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.
Unfortunately, your account clashes with another account also called Egfrank. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Egfrank~mediawikiwiki that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.
Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.
Sorry for the inconvenience.
Yours,
Keegan Peterzell
Community Liaison, Wikimedia Foundation
03:29, 18 March 2015 (UTC)
Renamed
editThis account has been renamed as part of single-user login finalisation. If you own this account you can log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: Special:GlobalRenameRequest. -- Keegan (WMF) (talk)
07:38, 22 April 2015 (UTC)