A pie for you!

edit
  ...testing WikiLove + LQT. Dantman 22:28, 25 September 2011 (UTC)Reply

A barnstar for you!

edit
  The Civility Barnstar
test 晒太阳的冰 03:11, 14 November 2011 (UTC)Reply

Cheers

edit
  Thanks for the NamespacePaths extension. Frug (talk) 01:42, 21 May 2012 (UTC)Reply


CreateRedirect

edit

Hi I saw you were possibly going to make a similar extension to CreateRedirect. Are you still planning on doing that? I have a few suggestions. --Bluesoju 04:47, 28 June 2009 (UTC) 22:18, 25 September 2011 (UTC)Reply

edit

Hallo Daniel,

ich krieg den Link http://wiki-tools.com/wiki/Wiki_Category_Tag_Cloud nicht geöffnet.

Kannst Du mal nachschauen, was da krumm ist? --Martin 12:29, 1 July 2009 (UTC) 22:21, 25 September 2011 (UTC)Reply

Hallo Martin, sofern ich es richtig verstanden habe, ist das Wiki endgültig aufgegeben worden. Der aktuelle Code kann hier gefunden werden. Gruß --Marbot 11:57, 5 July 2009 (UTC) 22:21, 25 September 2011 (UTC)Reply

Extension SidebarDonateBox

edit

Hallo Dantman. Ich habe bei mir das Extension SidebarDonateBox (siehe thrunk) installiert und ein bisschen aufgepeppt. Es unterstützt nun nach Wahl WikiText und holt die Einstellungen (z.B. Navigation nur für ein Wiki in einer Farm) aus Mediawiki:DonateBox (auch konfigurierbar).

<?php
/**
 * SidebarDonateBox
 * @package SidebarDonateBox
 * @author Daniel Friesen (http://mediawiki.org/wiki/User:Dantman) <mediawiki@danielfriesen.name>
 * @license http://www.gnu.org/copyleft/gpl.html GNU General Public License 2.0 or later
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * as published by the Free Software Foundation; either version 2
 * of the License, or (at your option) any later version.
 *
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with this program; if not, write to the Free Software
 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
 */

if ( !defined( 'MEDIAWIKI' ) ) die( "This is an extension to the MediaWiki package and cannot be run standalone." );

$wgExtensionCredits['parserhook'][] = array (
	'name' => 'SidebarDonateBox',
	'url' => 'http://mediawiki.org/wiki/Extension:SidebarDonateBox',
	'version' => '1.1a',
	'author' => "[http://mediawiki.org/wiki/User:Dantman Daniel Friesen]",
	'description' => "Adds a custom donate box to the sidebar"
);

$wgHooks['SkinBuildSidebar'][] = 'efSidebarDonateBox';

///! Edit Mediawiki:Sidebar to include. (e.g. * Navigation if $efSidebarDonateBoxTitle is 'Navigation')

$efSidebarDonateBoxParse=true;//Whether to parse the page or not.
$egSidebarDonateBoxTitle='Donate';//The Title of the Box like those "Search", "Toolbox", etc...
$egSidebarDonateBoxPage='DonateBox'; //The page Mediawiki:___ contains the contents for the Box.

function efSidebarDonateBox( $skin, &$bar ) {
	global $wgParser, $egSidebarDonateBoxPage, $egSidebarDonateBoxTitle, $efSidebarDonateBoxParse;
	if($efSidebarDonateBoxParse==true)
	{
		$title = Title::newFromText( $egSidebarDonateBoxPage, NS_MEDIAWIKI );
		$article = new Article($title);
		$text = $article->getContent();
		$options = new ParserOptions;
		$out=$wgParser->parse($text,$title,$options);
		$bar[$egSidebarDonateBoxTitle]=$out->mText;
	}
	else
	{
		$bar[$egSidebarDonateBoxTitle] = $egSidebarDonateBoxContent;
	}
	return true;
}

--Wersonst 22:22, 25 September 2011 (UTC)

WikiVid SQL

edit

Why is mine doing this? 192.197.54.28 18:57, 15 January 2010 (UTC) 22:23, 25 September 2011 (UTC)Reply

RESOLVED:Extension:Theme Designer

edit

I was wondering if you knew how to fix an error in SpecialThemeDesigner.php line #75 echo Html::closeElement('body'); ?
I can not read all the error message as it is displayed behind the skins dropdown. Here is the link to my wiki's Special pages [2]. Also the extension is not showing up on the version page here [3]. You can leave a reply (if you would) Here or my main account Here.
Thank you Mlpearc powwow 05:36, 30 May 2011 (UTC) 22:24, 25 September 2011 (UTC)Reply

Extension SidebarDonateBox (2)

edit

Hallo Dantman - super Extension! Dazu habe ich zwei Fragen:

  1. Wie kann ich den Donate Button OHNE Hauptmenupunkt direkt im Sidebar platzieren? (D.h.: Statt "Donate"->Donate Button nur "Donate Button" - also auf Stufe "Main page")
  2. Wie kann ich die Reihenfolge ändern? Ich möchte den Donate Button nämlich ganz oben anzeigen lassen...

Im SidebarDonateBox.php vermute ich, dass man $bar['Donate'] = $egSidebarDonateBoxContent; anpassen müsste, nur leider kenne ich mich mit PHP (noch) nicht so gut aus...

P.S.: Ich verwende MW 1.16 mit dem Vector Skin.

Viele Grüsse --Mrnett1974 08:22, 18 August 2011 (UTC) 22:25, 25 September 2011 (UTC)Reply

Realnames

edit

Thanks for the feedback! I just released 0.1.1 of Extension:Realnames. It should address everything you mentioned (save 1.18 integration and possible slowdowns on RC and History -- waiting for feedback for those). Quadir 22:29, 17 September 2011‎ 22:26, 25 September 2011 (UTC)Reply

A barnstar for you!

edit
  The Technical Barnstar
Self-gifting ;) Muahahaha... Dantman 11:27, 25 September 2011 (UTC)Reply

Post to social media feeds

edit

Left a message on talk page for /Post to social media feeds - great interested for a project - let me know if you want help/support.  :) Varnent 20:42, 29 November 2011 (UTC)Reply

Url for special pages pointing to previous host

edit

I've been having one little problem with the Monaco skin (which I love) and left a question here about it:

Project:Support desk/Flow/2011/12#h-Url_for_special_pages_pointing_to_previous_host's_path-2011-12-02T00:03:00.000Z

and:

http://monaco.wikkii.com/wiki/Talk:Monaco_port#Url_for_special_pages_pointing_to_previous_host.27s_path

Thanks, Andrewrutherford 10:33, 3 December 2011 (UTC)Reply

Skin-Synagonism

edit

Synagonism greatly improves page-READING by moving the table-of-contents on the left and showing the position the reader is reading! You can find it at SorceForge. It needs testing and commit. If you are interesting, do it! Synagonism 07:31, 10 December 2011 (UTC)Reply

I'm not really interested in skins that look as hacked together like that. Daniel Friesen (Dantman) 16:45, 10 December 2011 (UTC)Reply

Enhancement of Extension CentralNotice

edit

Hello, I have made a proposal on enhancement of Extension CentralNotice. Please comment Gsoc Proposal Nischayn22 (talk) 19:14, 12 March 2012 (UTC)Reply

Manual:Short URL/wiki/Page title -- GoDaddy Shared Linux Subdomain

edit

Why was this page (I created) deleted?! John Navas (talk) 16:14, 24 March 2012 (UTC)Reply

The multitude of bad shorturl pages we have is only serving to cause people to have more issues setting up short urls. All these manual pages are being replaced with a few well written guides.
This one contained bad rewrite rules including ?title=$1 that create bugs in a wiki's url. And had other things unrelated to shorturl configuration. Daniel Friesen (Dantman) (talk) 02:22, 25 March 2012 (UTC)Reply
edit

Ack! An extension I'm using has been marked as a "Code Injection" risk.

http://www.mediawiki.org/wiki/Extension:BreadCrumbs2

Why was it marked and how do I fix it?

Also, is it an issue of the wiki or the MediaWiki:Breadcrumbs page are read-only to all but Administrators? 70.95.182.249 02:14, 3 April 2012 (UTC)Reply

The hole is due to the use of preg_replace's /e flag.
Frankly the whole code of the extension is a poorly coded mess. The extension is all over the place with bad string comparisons instead of using Title methods, hardcoded url building, etc... Daniel Friesen (Dantman) (talk) 02:22, 3 April 2012 (UTC)Reply
I have fixed the code injection issue with BreadCrumbs2. Please review the changes. Tback (talk) 19:54, 13 April 2012 (UTC)Reply

Unexpected behaviour ReplaceSet

edit

Hi Daniel. I left a question at Extension talk:ReplaceSet, which I hope you're able to answer. It looks like you have a powerful tool there for automatic string replacement, which can alleviate a good deal of manual work, but I ran into a slight problem while using it in conjunction with a magic word. Regards, Cavila MW 1.17, MySQL 5.5.16, Php 5.3.8 11:05, 21 May 2012 (UTC)Reply

Extension:SecureHTML - XSS risk?

edit

You added an XSS warning to Extension:SecureHTML. I don't think it's a risk since html can only be added to protected pages, so only trusted users can add html. Subfader (talk) 07:45, 31 July 2012 (UTC)Reply

I took a look at the code. It relies on Title::isProtected, which appears to return true if a page is semi-protected. That means that untrusted users who have simply become autoconfirmed are capable of making XSS attacks on the wiki. Daniel Friesen (Dantman) (talk) 07:46, 31 July 2012 (UTC)Reply
Ah ok. Since Jean-Lou Dupont is inactive, I'd like to fix it for myself.
I don't autopromote e-mail-confirmed users. Editing is allowed for registered users only:
$wgGroupPermissions['*']['edit']              = false;
$wgGroupPermissions['user']['edit']           = true;
Is that safe enough?
I protect all pages for "Administrators only". How could I check isProtected() against that? Subfader (talk) 09:34, 31 July 2012 (UTC)Reply
Well you'll need to semi-protect a page to test it.
But this isn't emailconfirmed, it's autoconfirmed. And it's a default part of the system you can't remove it.
Presumably a half-decent fix might be to use $title->isProtected( 'edit' ) && !$title->isSemiProtected( 'edit' ).
That said the premise of these extensions is horrible. Allowing arbitrary pages to have raw html can never truly be secure. No mater what the protection.
To top off the issue with isProtected this extension relies on modifying a wg global in order to work. This isn't local. If something else is parsed on the same page as a protected page an unsafe page could potentially be parsed allowing raw html in it. Daniel Friesen (Dantman) (talk) 10:00, 31 July 2012 (UTC)Reply

Negref.php is not compatible with MediaWiki 1.19

edit

This post by Kghbln was moved on 2012-09-26. You can find it at Extension talk:Negref#c-Eloy.wikia-2012-07-03T16:07:00.000Z-Negref.php_is_not_compatible_with_MediaWiki_1.19. [[kgh]] (talk) 22:49, 26 September 2012 (UTC)Reply

Manual:Short URL

edit

It would be civil to provide an explanation when reverting someone's non-vandalism changes. [4] Matma Rex (talk) 22:11, 7 October 2012 (UTC)Reply

Sorry.
That page linked to contains bad advice. Ancient misinformation from people who don't understand how rewrites or MediaWikis' url routing works which I am trying to eliminate from the wiki and replace with actual good advice.
The most particular problem there is the use of ?title=$1 inside the url. That is absolutely unnecessary. MediaWiki extracts the article from the url itself, there is no point to specifying a title. That kind of rewrite rule originates from someone who doesn't understand that fact. To top it off not only is it unnecessary but it actually causes bugs. Apache's query rewriting capabilities are broken. It does not properly escape things. As a result when you do a rewrite like that instead of letting MediaWiki do the parsing itself thanks to Apache's broken rewrites characters such as + and & inside of your page titles become completely broken. Daniel Friesen (Dantman) (talk) 23:21, 7 October 2012 (UTC)Reply

Subskin 'overrides' happening before original css

edit

I've follow your tutorial on subskinning Vector, and I've verified using FireBug that the overrides I'm applying in my own skin are being added by the ResourceLoader, but not after all the Vector screen.css stuff is applied so the changes aren't showing up on screen, but they are in the minified css. Any ideas on what might be causing this or how I might force my css to the end of the line so it overrides the Vector stuff? --anon (anna.brooks-1nupkkj@yopmail.com) 00:36, 12 October 2012 (UTC)

Can you show me the php and css you are using? Daniel Friesen (Dantman) (talk) 01:51, 12 October 2012 (UTC)Reply
I've copied your three php files verbatim. The only thing I've changed to see if this works is in the screen.css for myskin, I've got
h1, h2, h3, h4, h5, h6 {
color: red;
font-weight: normal;
}
firebug shows this being accepted and part of the computed css, but it shows it as crossed out (overridden) by the original css from Vector:
h1, h2, h3, h4, h5, h6 {
color: black;
font-weight: normal;
}
h1, h2, h3, h4, h5, h6 {
color: red;
font-weight: normal;
}
--anon (anna.brooks-1nupkkj@yopmail.com) 01:09, 22 October 2012 (UTC)
Try experimenting with adding 'dependencies' => 'skin.vector' to the resource module. Daniel Friesen (Dantman) (talk) 20:39, 22 October 2012 (UTC)Reply
Here's how I got it to work. In my skin.php file I had to add
$out->addStyle('myskin/screen.css');
to the end of the setupSkinUserCss function.
That is the only way loader would load my css after Vector's thus overriding it correctly.
That was a pain to figure out. --anon (anna.brooks-1nupkkj@yopmail.com) 00:03, 27 October 2012 (UTC)
That is not a fix. By doing that you've eliminated rtl support and performance enhancements added by RL, you're also not even tageting a media.
Did you try out the 'dependencies' bit I mentioned? Daniel Friesen (Dantman) (talk) 05:59, 27 October 2012 (UTC)Reply
Ok, I went back and revisited this, I'm not sure what I did differently this time, but it is now working as your tutorial explains. The dependencies thing did not work for me when I tried it. --anon (anna.brooks-1nupkkj@yopmail.com) 20:16, 6 November 2012 (UTC)
Hello,
The same situation as for Anna.
Tried to use solution as you suggest.
In myskin.php in $wgResourceModules['skins.myskin'] array the 'dependencies' => 'skin.vector' element have been added.
No success. The vector css have not been overridden by screen.css from myskin extension.
Any other suggestions.
Or may be something wrong with my implementation? 212.248.30.210 13:39, 2 November 2012 (UTC)Reply
Not sure. The easiest way to figure out what's wrong of course would be to see the whole code you're using so I can test it. Daniel Friesen (Dantman) (talk) 14:06, 2 November 2012 (UTC)Reply
Ok. Let's try.
I published all contents of subskin here http://yadi.sk/d/J_YjbkHN0Wy6r in one .zip file.
If you have any problems when downloading and extracting, please feel free to reply me. 212.248.30.210 15:08, 2 November 2012 (UTC)Reply
Oh, oh oh... I just remembered an old issue I ran into.
Use the 'dependencies' and try using addModules instead of addModuleStyles. Daniel Friesen (Dantman) (talk) 03:22, 16 November 2012 (UTC)Reply
You may actually want to switch back to using addModuleStyles and just deal with the issue by making stylesheet selectors stronger. Apparently using addModules will make it so that your skin's css will not be loaded for users without JS. The issue you're having is actually bug 45229}. Daniel Friesen (Dantman) (talk) 21:24, 11 March 2013 (UTC)Reply
It seems the bug haven't been fixed yet. Is there any workaround? Yigitozen (talk) 16:56, 9 December 2013 (UTC)Reply
Nope, all you can do is either make your modules sort alphabetically or use stronger selectors so that cascade order doesn't matter. Daniel Friesen (Dantman) (talk) 18:15, 9 December 2013 (UTC)Reply

ReplaceSet replacing Equals Sign

edit

Hi, for some reason I can't replace an equals sign using ReplaceSet. Everything else works. Do you know what could be the problem? I've described the problem in more detail at Extension_talk:ReplaceSet. Thanks! Mw.clearish (talk) 09:45, 10 January 2013 (UTC)Reply

Problem with modified Vector skin

edit

I used the directions here http://blog.redwerks.org/2012/02/28/mediawiki-subskin-tutorial/ to create a modified Vector skin here http://en.sturmkrieg.com but the CSS doesn't seem to work. I copied the Vector.css and some of the Common.css wiki pages into the screen.css file, and for some reason, only some of the CSS seems to work, as can be seen here http://en.sturmkrieg.com/index.php?title=Sturmkrieg_Wiki&useskin=sturmkrieg ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 07:08, 27 January 2013 (UTC)Reply

Try adding 'skin.vector' to the dependencies of your skins RL module. And use addModules instead of addModuleStyles. Daniel Friesen (Dantman) (talk) 16:19, 27 January 2013 (UTC)Reply
Where is the RL module? Is that in the skin files or one of the core files?
EDIT
I found this in sturmkrieg.php
$wgResourceModules['skins.sturmkrieg'] = array(
	'styles' => array(
		'sturmkrieg/screen.css' => array( 'media' => 'screen' ),
	),
	'remoteBasePath' => &$GLOBALS['wgStylePath'],
	'localBasePath' => &$GLOBALS['wgStyleDirectory'],
);
Where should I add it? ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 19:48, 27 January 2013 (UTC)Reply
Make that:
$wgResourceModules['skins.sturmkrieg'] = array(
	'styles' => array(
		'sturmkrieg/screen.css' => array( 'media' => 'screen' ),
	),
	'dependencies' => 'skin.vector',
	'remoteBasePath' => &$GLOBALS['wgStylePath'],
	'localBasePath' => &$GLOBALS['wgStyleDirectory'],
);
Btw, your url shouldn't have []'s in it.
And remember to update addModuleStyles to addModules. Daniel Friesen (Dantman) (talk) 21:16, 28 January 2013 (UTC)Reply
Thanks. I added the 'dependencies' => 'skin.vector', line. Are you say this line $wgResourceModules['skins.sturmkrieg'] = array( should not have the [] in it?
EDIT
I have this
$wgResourceModules['skins.sturmkrieg'] = array(
	'styles' => array(
		'sturmkrieg/screen.css' => array( 'media' => 'screen' ),
	),
	
	'remoteBasePath' => &$GLOBALS['wgStylePath'],
	'localBasePath' => &$GLOBALS['wgStyleDirectory'],
	'dependencies' => 'skin.vector'
);
It doesn't seem to work. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 21:20, 28 January 2013 (UTC)Reply
You've done something strange. Your skin isn't even loading 'skins.sturmkrieg' anymore. Daniel Friesen (Dantman) (talk) 22:23, 28 January 2013 (UTC)Reply
I changed addModuleStyles to addModules. For some reason, it doesn't load any of the sturmkrieg/screen.css when I set that. I'm guessing maybe I should change it back to useModuleStyles? I'll set it back to that for now. When it does that, some of the CSS for the new skin loads, but most of it seems to be the Vector CSS.
I'll update this code here, that lists the code for the skin.
Do you know what to do when only some of the CSS is loading? useModuleStyles seems to load some of the CSS from the new skin, while useModules doesn't use any of it. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 20:26, 29 January 2013 (UTC)Reply
I'm using MW 1.17.5. Is there anything I need to do differently? ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 21:52, 30 January 2013 (UTC)Reply
Please upgrade, 1.17 is EOL. And lots of the skinning stuff is not available. Daniel Friesen (Dantman) (talk) 21:54, 30 January 2013 (UTC)Reply
Will the method work for MW 1.19? If so, I will upgrade to that. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 21:56, 30 January 2013 (UTC)Reply
I was saying that the 'url' in $wgExtensionCredits['skin'][] shouldn't have '[]' around the url. It's a plain url, not wikisyntax expecting external link syntax. Daniel Friesen (Dantman) (talk) 22:21, 28 January 2013 (UTC)Reply
Ok, I see. Thanks. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 23:57, 28 January 2013 (UTC)Reply
I have this for the files:
sturmkrieg.php
<?php
/**
 * Sturmkrieg skin
 *
 * @file
 * @ingroup Skins
 * @author Sasha Ehrenstein (http://www.sturmkrieg.de/User:Inquisitor_Ehrenstein)
 */
if( !defined( 'MEDIAWIKI' ) ) die( "This is an extension to the MediaWiki package and cannot be run standalone." );
$wgExtensionCredits['skin'][] = array (
	'path' => __FILE__,
	'name' => 'Sturmkrieg',
	'url' => "[http://www.sturmkrieg.com]",
	'author' => '[http://www.sturmkrieg.de/User:Inquisitor_Ehrenstein Inquisitor Ehrenstein]',
	'descriptionmsg' => 'mywiki-desc',
);
$wgValidSkinNames['sturmkrieg'] = 'Sturmkrieg';
$wgAutoloadClasses['SkinSturmkrieg'] = dirname(__FILE__).'/Sturmkrieg.skin.php';
$wgExtensionMessagesFiles['Sturmkrieg'] = dirname(__FILE__).'/Sturmkrieg.i18n.php';
$wgResourceModules['skins.sturmkrieg'] = array(
	'styles' => array(
		'sturmkrieg/screen.css' => array( 'media' => 'screen' ),
	),
	'remoteBasePath' => &$GLOBALS['wgStylePath'],
	'localBasePath' => &$GLOBALS['wgStyleDirectory'],
);
Sturmkrieg.i18n.php
<?php
/**
 * Internationalization file for skin Sturmkrieg.
 *
 * @file
 * @ingroup Skins
 */
$messages = array();
/** English
 * @author Inquisitor Ehrenstein
 */
$messages['en'] = array(
	'skinname-sturmkrieg' => "Sturmkrieg",
	'sturmkrieg-desc' => "The default skin of Sturmkrieg.",
);
Sturmkrieg.skin.php
<?php
/**
* Skin file for skin Sturmkrieg.
*
* @file
* @ingroup Skins
*/
require_once( dirname( __FILE__ ) . '/../Vector.php' );
/**
 * SkinTemplate class for Sturmkrieg skin
 * @ingroup Skins
 */
class SkinSturmkrieg extends SkinVector {
	var $skinname = 'sturmkrieg', $stylename = 'sturmkrieg';
	/**
	 * @param $out OutputPage object
	 */
	function setupSkinUserCss( OutputPage $out ){
		parent::setupSkinUserCss( $out );
		$out->addModuleStyles( "skins.sturmkrieg" );
	}
}
ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 19:55, 27 January 2013 (UTC)Reply

Working with Lockdown

edit
Do you know if it's possible to allow registered users to view particular special pages, but prevent users in the banned user group (made with $wgRevokePermissions) from viewing them? I'd like for all users to have access to RecentChanges, but not for the troll who has been stalking it. I don't think there's a need for anons who can't edit to read it. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 20:32, 29 January 2013 (UTC)Reply
I don't use Lockdown at all. And I don't really see any reason to hide recent changes. Daniel Friesen (Dantman) (talk) 08:50, 16 February 2013 (UTC)Reply
Ok. I'll see if anyone else knows if there's a solution. I'm hiding it from a troll who has repeatedly spewed racist interpretations of our content, and from what we can tell, has been stalking the recent changes page literally every day for over a year. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 20:43, 24 February 2013 (UTC)Reply
Imaj 165.50.15.85 (talk) 00:27, 12 October 2016 (UTC)Reply

Extension:NoBogusUserpages

edit

Heiya Dantman, I believe that this extension is a real goody. This is why I am asking if it will be possible to add it to Git. Cheers [[kgh]] (talk) 11:19, 31 January 2013 (UTC)Reply

Added to the list. Daniel Friesen (Dantman) (talk) 16:32, 2 February 2013 (UTC)Reply
That's great news. Thank you. [[kgh]] (talk) 17:10, 2 February 2013 (UTC)Reply
Oops, the extension was unfortunately not migrated since this process changed after you added the extension to the list. Now you will have to request a new repository. Again, it would be cool to have this one in Git. Cheers [[kgh]] (talk) 16:27, 30 May 2013 (UTC)Reply

delted page please restore

edit

Can you restore:


http://www.mediawiki.org/w/index.php?title=Manual:Short_URL/Ampersand_solution&action=edit&redlink=1

please? Errectstapler (talk) 23:13, 1 February 2013 (UTC)Reply

That page was full of bad advice. Every last section on that page had horrible recommendations that are 100% unnecessary if one uses proper rewrite rules without the ?title=$1 from the start.
Try using the rules at Manual:Short URL/Apache they should work without having any issues with & or +. If you have any issue with the rule try to describe it to me and I'll see if I can fix it.
If your wiki is 1.17+ and publicly visible you can also use http://shorturls.redwerks.org/ to get basically the same rules as those on that page. Daniel Friesen (Dantman) (talk) 16:28, 2 February 2013 (UTC)Reply

A user is clearly not happy about your deletion of it; I can't even offer him or her an explanation why because you didn't supply a deletion rationale. Jasper Deng (talk) 18:26, 9 February 2013 (UTC)Reply

All those pages includes outdated and bad bad instructions with rewrite rules that would typically break various titles on the wiki. They were all deleted together and replaced with a complete manual for Apache.
I suppose if there are Google links to that page we can redirect it to Manual:Short URL/Apache. Daniel Friesen (Dantman) (talk) 08:46, 16 February 2013 (UTC)Reply

March Grants News

edit
 

Grants News
VOLUME 1 MARCH 2013 ISSUE 1

Eight projects have been awarded grants in this pilot round of the Individual Engagement Grants program. You can read more about them in our blog post. Many thanks to everyone who participated in this round! We look forward to seeing even more of your ideas and input in preparation for round 2, which begins on August 1st.

Grants News is brought to you by the Wikimedia Grantmaking Team. You can change your subscription to this update on the list.

Sbouterse (WMF) (talk) 06:24, 1 April 2013 (UTC)Reply

ampersand

edit

Hi. I must have the old configuration, because I still have this problem. Can you please explain what I can do to fix this, and I can relegate the solution to talk, so if other people have the same problem?

Thank you very much. Igottheconch (talk) 13:05, 16 October 2013 (UTC)Reply

Could you paste the config you used into a <pre> or <syntaxhighlight> block here. Daniel Friesen (Dantman) (talk) 13:26, 16 October 2013 (UTC)Reply
thank you for your reply sir!
I always enjoy working with you.
It appears I may transfer my wiki to wikia, so I dont need to solve this problem. Igottheconch (talk) 14:12, 23 October 2013 (UTC)Reply

db table template

edit

Oh my gosh, that Template:db table is so much of a better way to link to those fields. I wish I'd known about it earlier! Thanks for the edit. Leucosticte (talk) 02:19, 25 October 2013 (UTC)Reply

;) No no, there was no way to do that. I just created that template now. Daniel Friesen (Dantman) (talk) 03:28, 25 October 2013 (UTC)Reply

Requests for comment/Allow styling in templates

edit

Hi, Requests for comment/Allow styling in templates is being considered as one of the RFCs to be discussed at the RFC review on 2013-11-06 via IRC. You are receiving this notification because you edited or discussed this RFC. We hope to see you there. Qgil (talk) 00:43, 5 November 2013 (UTC)Reply

edit

How to redirect the Privacy Policy (in the footer) to an external link in other website? I am using Vector skin in Mediawiki 1.20 .please reply soon. Nehapant19 (talk) 08:25, 7 January 2014 (UTC)Reply

setimage meta tag for Facebook not working

edit

Hi there,

I just downloaded and successfully installed the OpenGraphExtension. Unfortunately it doesn't seem to work.

I tried Facebook Debugger but it doesn't show the correct image from the main page: Auslandssemester-Bali.de.

The code is used is:

[[File:{{#setmainimage:Leben_auf_Bali.gif}}|65px|link=Leben auf Bali]]

My MediaWiki Version is 1.22.8. Any ideas? 110.136.225.132 12:46, 21 July 2014 (UTC)Reply

I won't deny the extension is buggy in some cases. But in this case it looks like you've got two different things inserting og: data into your page and because of the double og:url FB is considering the data invalid.
Try uninstalling the unmaintained Extension:Facebook you have. Daniel Friesen (Dantman) (talk) 05:18, 22 July 2014 (UTC)Reply

An important message about renaming users

edit

Dear User talk:Dantman/An important message about renaming users,

I am cross-posting this message to many places to make sure everyone who is a Wikimedia Foundation project bureaucrat receives a copy. If you are a bureaucrat on more than one wiki, you will receive this message on each wiki where you are a bureaucrat.

As you may have seen, work to perform the Wikimedia cluster-wide single-user login finalisation (SUL finalisation) is taking place. This may potentially effect your work as a local bureaucrat, so please read this message carefully.

Why is this happening? As currently stated at the global rename policy, a global account is a name linked to a single user across all Wikimedia wikis, with local accounts unified into a global collection. Previously, the only way to rename a unified user was to individually rename every local account. This was an extremely difficult and time-consuming task, both for stewards and for the users who had to initiate discussions with local bureaucrats (who perform local renames to date) on every wiki with available bureaucrats. The process took a very long time, since it's difficult to coordinate crosswiki renames among the projects and bureaucrats involved in individual projects.

The SUL finalisation will be taking place in stages, and one of the first stages will be to turn off Special:RenameUser locally. This needs to be done as soon as possible, on advice and input from Stewards and engineers for the project, so that no more accounts that are unified globally are broken by a local rename to usurp the global account name. Once this is done, the process of global name unification can begin. The date that has been chosen to turn off local renaming and shift over to entirely global renaming is 15 September 2014, or three weeks time from now. In place of local renames is a new tool, hosted on Meta, that allows for global renames on all wikis where the name is not registered will be deployed.

Your help is greatly needed during this process and going forward in the future if, as a bureaucrat, renaming users is something that you do or have an interest in participating in. The Wikimedia Stewards have set up, and are in charge of, a new community usergroup on Meta in order to share knowledge and work together on renaming accounts globally, called Global renamers. Stewards are in the process of creating documentation to help global renamers to get used to and learn more about global accounts and tools and Meta in general as well as the application format. As transparency is a valuable thing in our movement, the Stewards would like to have at least a brief public application period. If you are an experienced renamer as a local bureaucrat, the process of becoming a part of this group could take as little as 24 hours to complete. You, as a bureaucrat, should be able to apply for the global renamer right on Meta by the requests for global permissions page on 1 September, a week from now.

In the meantime please update your local page where users request renames to reflect this move to global renaming, and if there is a rename request and the user has edited more than one wiki with the name, please send them to the request page for a global rename.

Stewards greatly appreciate the trust local communities have in you and want to make this transition as easy as possible so that the two groups can start working together to ensure everyone has a unique login identity across Wikimedia projects. Completing this project will allow for long-desired universal tools like a global watchlist, global notifications and many, many more features to make work easier.

If you have any questions, comments or concerns about the SUL finalisation, read over the Help:Unified login page on Meta and leave a note on the talk page there, or on the talk page for global renamers. You can also contact me on my talk page on meta if you would like. I'm working as a bridge between Wikimedia Foundation Engineering and Product Development, Wikimedia Stewards, and you to assure that SUL finalisation goes as smoothly as possible; this is a community-driven process and I encourage you to work with the Stewards for our communities.

Thank you for your time. -- Keegan (WMF) talk 18:24, 25 August 2014 (UTC)Reply

--This message was sent using MassMessage. Was there an error? Report it!

MediaWiki message delivery (talk) 18:24, 25 August 2014 (UTC)Reply

The future of skins

edit

Hi.

An RfC on the future of skins is open here:

I am notifying you as you're written (at least) this page:

Please consider participating and reaching out to any friends who could be interested. Thanks. :-) Gryllida 05:17, 28 August 2014 (UTC)Reply

Subskin tutorial

edit

Hello,

I’ve followed your tutorial for creating subskins and it seems not to work on MW 1.24

Did I do something wrong? I copied your files as they are creating a skin called 'My Skin', but when I choose the skin in preference I get a blank white page.

Does this tutorial not apply to the new version of Mediawiki? Wissamkhatib (talk) 14:25, 11 February 2015 (UTC)Reply

Nothing should have changed. If everything is completely white that sounds like you have an error in your code.
Could you show me what you put together? Daniel Friesen (Dantman) (talk) 15:55, 11 February 2015 (UTC)Reply
I didn’t know whether I should post the code here or not, so apologies in advance if I did something wrong. I posted the three files here:
goldvector.php
GoldVector.i18n.php
GoldVector.skin.php
I left the screen.css empty for now.
Thanks for your help. Wissamkhatib (talk) 13:01, 12 February 2015 (UTC)Reply
require_once( dirname( __FILE__ ) . '/Vector/Vector.php" );
That string is opened with but closed with ", that's the issue.
However you should really just drop that whole line. Vector is auto-loaded now and that's the wrong file, in multiple ways.
Also note that after fixing that you're probably going to run into a vector-specific error related to Vector's use of a configuration object. Daniel Friesen (Dantman) (talk) 19:51, 12 February 2015 (UTC)Reply

{{#setmainimage:FOO}} puts FOO at the top of the page before other text?

edit

The correct meta tags are generated, but the page source starts with:

<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><div class="mw-parser-output"><p>FOO

I must be doing something wrong, but I can't seem to figure out what. (OpenGraphMeta and Description2 are both installed and loading properly)


Any thoughts? 2605:E000:63D1:CB00:81FA:A006:5089:E96D (talk) 20:29, 14 November 2020 (UTC)Reply

How to create a wiki?

edit

How do I create a wiki? I want to create a wiki for Demon Accords like the people who created the Supernatural wiki. How do I go about that? RerumTrading (talk) 05:08, 20 November 2020 (UTC)Reply

@RerumTrading: Your best bet, for free, is an application at Miraheze's wiki-request queue. --Slgrandson (talk) 00:16, 20 July 2021 (UTC)Reply

Short URL hero

edit
 
[1]

Dantman, you saved my bacon with that Short URL conifig generator at https://shorturls.redwerks.org/ (I found it linked to in Manual:Short_URL#External_links). Thank you. For some reason my wiki's short URL config broke when I upgraded from MW1.31.1 to MW1.35.1, but I made a new Short URL config with your generator and it works! Thank you! When I was young I believed in flying carpets. Later I believed in root level Short URLs (and set up teflpedia.com wiki accordingly). Now I rely on heros like you to save my bacon. I am upgrading that wiki in a test area and was stumped on some short URL problem but your tool has my wiki magically levitating again. So I can proceed with my upgrade, tomorrow. Thank you! Visual editor is throwing an error, "Error contacting the Parsoid/RESTBase server (HTTP 404)"[5] -- maybe I will have to disable visual editor, alas. --Rogerhc (talk) 05:11, 27 January 2021 (UTC)Reply

Fixed that for my root level short URL with this added rewrite condition in .htaccess:
RewriteCond %{HTTP_USER_AGENT} !^(VisualEditor)
See https://www.mediawiki.org/w/index.php?title=Extension%20talk%3AVisualEditor/2020#c-LapisLazuli33-2020-10-03T09%3A59%3A00.000Z-Chitinlink-2020-10-02T19%3A05%3A00.000Z
Here's what the https://shorturls.redwerks.org config I'm using + that^ looks like, and it's working! :)
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} !^(VisualEditor)
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/index.php [L]
RewriteCond %{HTTP_USER_AGENT} !^(VisualEditor)
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^/?images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/([0-9]+)px-.*$ %{DOCUMENT_ROOT}/thumb.php?f=$1&width=$2 [L,QSA,B]
RewriteCond %{HTTP_USER_AGENT} !^(VisualEditor)
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^/?images/thumb/archive/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/([0-9]+)px-.*$ %{DOCUMENT_ROOT}/thumb.php?f=$1&width=$2&archived=1 [L,QSA,B]
Rogerhc (talk) 07:49, 27 January 2021 (UTC)Reply
Dang, that works for http:// but not for https://. When I switch to https:// I get this error when I click the VisualEditor "edit" link on a page:
Error contacting the Parsoid/RESTBase server: (curl error: 60) SSL peer certificate or SSH remote key was not OK
I am using a self-signed SSL certificate. Don't know if that is an issue. Rogerhc (talk) 00:47, 28 January 2021 (UTC)Reply
Yes, it works on my production wiki!
My production wiki has a properly authorized SSL certificate. Visual Editor is working there!
My test wiki only has a self authorized SSL certificate, and throws the above error when trying to open a page with Visual Editor.
Thanks again for the short URL config tool at https://shorturls.redwerks.org ! Very helpful! Rogerhc (talk) 03:49, 1 February 2021 (UTC)Reply
That one single line worked for me with https. I no longer have to choose between short URLs and Visual Editor. Thanks a million. 2603:8080:5701:887D:2150:6BB4:FA4E:926B (talk) 00:29, 11 August 2021 (UTC)Reply

How we will see unregistered users

edit

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:17, 4 January 2022 (UTC) MediaWiki message delivery (talk) 18:17, 4 January 2022 (UTC)Reply