User talk:Jack Phoenix/Archive 5

Special:Import not working

I tried to upload a 578 KB unzipped db dump. But I got a message that the 'import size is bigger than maximum allowed'. --Hockeyben - Talk 19:34, 2 February 2011 (UTC)

You need to ask staff to make large imports. Make a report at Bugzilla. ☆The Solar Dragon☆ 21:51, 2 February 2011 (UTC)

I know. But 578 KB is far under the 2.1 MB manual import limit. --Hockeyben - Talk 22:42, 2 February 2011 (UTC)

shoutwiki

http://zh.shoutwiki.com REDIRECT to http://zh-tw.shoutwiki.com --Yyaootw (talk) 06:28, 3 February 2011 (UTC)

Done. --Jack Phoenix _(contact) 23:18, 16 February 2011 (UTC)

Wiki Adoption

Despite my already busy wiki schedule, I have been helping out on some other wikis to get them looking pretty and looking clean, so as to attract people to begin editing and have a fun time (to be honest its partly because I want wikia to die painfully), anyway I am currently doing up the Charmed Wiki and its a little hard to do without admin abilities. I talked to the guy who made it but received no reply and that was 19 days ago, i tracked him down on wikia and asked but still no reply. I understand if you feel one person having too much power around here could be a bad thing, but you are more than welcome to remove said powers after I am done. ESCYOS - YOUR GOD! ^{talk | contribs} 09:02, 3 February 2011 (UTC)

• Hey there Escyos,
  KhanWiz seems to be active again, have you still not received a reply? --Jedimca0^(talk) 00:29, 5 February 2011 (UTC)

hardly, he just uploaded a pic. I noticed he is still active on the wikia one yet doesnt seem so interested in the shoutwiki one. technically i got a reply, which was just about the logo and nothing else. I sincerely doubt he has any interest in this wiki however if the wikia one is any indication of their style of writing, thats a good thing. ESCYOS - YOUR GOD! ^{talk | contribs} 01:21, 5 February 2011 (UTC)

• As you have probably noticed, I have contacted him and he replied and granted you admin rights. Happy editing. --Jedimca0^(talk) 12:33, 6 February 2011 (UTC)

Vector, Monaco, ads and longterm financial stability

At Wikia there is this forum: Forum: You guys suck

Some thoughts I have adapted from that thread.

I prefer the Vector skin. Maybe Wikia will allow wikis to make it the default skin. Shoutwiki will allow it as the default skin when they upgrade to MediaWiki 1.16. Competition is good.

In any case, wiki farms have to figure out how to make money. Paying for Monaco and other "premium" skins will not work in my opinion. It almost always comes back to ad revenue, and where to put the ads. Otherwise wiki farms don't survive profitably. Left sidebars at 300 pixels wide would work, along with header ads, and bottom of the page ads. But then the content space is squeezed if a fixed-width is used that is too narrow (as at Wikia).

A wider left sidebar is fine if content space has a fluid width up to a certain maximum width. This way the content space expands or shrinks to work with smartphones, laptops, PC monitors, and wider screens. But that maximum width has to be wider than the current fixed width at Wikia. The ratio of content space width to sidebar width will more and more be the determining factor in popularity of wiki farms in my opinion.

A possible solution for any wiki farm is to put the ads (marked clearly as "ads") in content space, and to use a narrow sidebar, or no sidebar. Monaco has a narrow left sidebar, and Wikia used Monaco to put ads in content space. In spite of those ads people could live with it because logged-in users could turn the ads off in preferences. Ads are fine in content space as long as they are marked in the top or bottom caption as "ads".

There is a near-religious war between people who think they can survive with narrow sidebar text ads (which is not financially possible in the long run), and people who think they can squeeze content space way too much (Wikia lately) in order to plaster the rest of the space with ads, "spotlights", fluff, bling, you-name-it. And right sidebars make it even worse. They block large images and tables.

Vector has a narrow left sidebar and a fluid, flexible width. It is good in my opinion to always use the latest MediaWiki skin since they have been fairly well tested. There is also an extension for nested sidebar site navigation that works with Vector: Extension:CSS MenuSidebar. For more info, and to see it in use go here: Forum:Sidebar Menus working now. There is also a way to add a nested menu sidebar without an extension just by adding some CSS and JS. Halopedia has one that could be adapted to the Vector skin.

Vector, like any skin, is infinitely customizable via CSS and JS. It can have one or two sidebars of any width. It can have content space of any width, fixed width, flexible width, or any combination. It can have any color text, and any number of background colors and images. --Timeshifter (talk) 08:17, 5 February 2011 (UTC)

• Hello there, thank you for your thoughts.
  Competition is indeed good, as it forces people to be more and more creative and find new ways to do things. Money is an issue that is always relevant. However, we at ShoutWiki believe in the concept of premium features. It's strange that you can say that it will not work when in fact no-one has seen premium features in action, as we have not yet released them. It is our strong belief that ads are not the only way to make a wiki farm profitable.
  
  We also believe that users prefer control over their wiki instead of obtrusive ads — even if the control costs a few dollars. On ShoutWiki, only anonymous and very new users will see advertisements. Autoconfirmed users (the majority of registered users) will not see ads, although they can force ads to display by adding forceads=true to the URL query string.
  
  In addition to this, ads are normally displayed only on content pages in order to comply with the ad providers' terms of use. As Jack wrote to another user a while ago, there is no need to install an extension to create folding sidebars, similar to what the Monaco skin has. It is entirely possible to achieve this effect with some JavaScript and CSS.
  
  While we realize that people like Vector, we won't be forcing it down the users' throats, in a manner that Wikimedia sites did. When Vector was deployed on Wikimedia projects, such as the English Wikipedia, it was not only made the site default skin, but also the default skin for all users, which many found annoying. Simply put, we believe in choices — in freedom. --Jedimca0^(talk) 18:58, 5 February 2011 (UTC)

I hope you are right about the premium features bringing in enough money to justify the staff time to maintain them. Wordpress.com makes a substantial amount of money from their Custom CSS Upgrade. See: http://en.support.wordpress.com/custom-css

This allows them to minimize the ads they show. See http://en.wikipedia.org/wiki/WordPress.com

But there are millions of blogs on Wordpress.com and so there is a large pool of people willing to pay for premium features. There are not nearly as many admins on wikis. I assume admins are the ones most likely to pay for premium features on wikis.

Freedom is good of course. I assume you will let people use Monobook or Vector for free. Maybe some other skins too that come with MediaWiki. --Timeshifter (talk) 20:54, 5 February 2011 (UTC)

Please import

NBA Wikia to NBA ShoutWiki, NFL Wikia to NFL ShoutWiki, and College Basketball Wikia to College Basketball ShoutWiki Thanks! --Hockeyben - Talk 15:58, 7 February 2011 (UTC)

You should file bug reports under Imports on Bugzilla for these. ☆The Solar Dragon☆ 21:05, 7 February 2011 (UTC)

Thanks Solar Dragon. I forgot about Bugzilla. I've filed the bugs. --Hockeyben

Please note that these wikis are not very active, so the DB Dump does not need to be updated, the early February updated will work fine --Hockeyben

Slate

Please change the Monaco theme on NFL Wiki to Slate. Thanks --Hockeyben

• I informed the techs about your request, they should change it for you soon. --Jedimca0^(talk) 15:04, 13 February 2011 (UTC)

• • This has now been done. --Jack Phoenix _(contact) 23:18, 16 February 2011 (UTC)

Permissions

Please give me sharedhelp permission.--Z135793 (talk) 08:11, 9 February 2011 (UTC)

• Hi there,
  Before we grant the rights of help page editors, we usually want to see what type of help pages you would write and what their quality would be. To do this, you can write a few help page you would like to add to our help pages on a user subpage. Once those pages are done, we will review them and then move them to the help namespace. Once we see you are writing good help pages, we will grant you the rights. --Jedimca0^(talk) 17:34, 12 February 2011 (UTC)

Support Center for the English and French Eureka Wikies and a very old request.

Hi Jack,
I still have no answer for 3 requests, this one, this one and that very old one. Do you have any answer please? Thank you very much for your answer. --LIMAFOX76 (talk) 17:25, 9 February 2011 (UTC)

• Limafox, Jack, I replied to this on my talk page after receiving the same question. Sorry it took so long to get back to Limafox. --Jedimca0^(talk) 15:27, 14 February 2011 (UTC)

Create a wiki

Is there a way to create a wiki without giving away my e-mail address? --Silver Knight (talk) 06:12, 14 February 2011 (UTC)

No, but if you don't trust shoutwiki, what you can do is make another email address. ESCYOS - YOUR GOD! ^{talk | contribs} 06:44, 14 February 2011 (UTC)

• Part of the reason why we ask for users to have a valid email address when making a wiki is because spambots usually do not have valid email addresses, it prevents spam wikis from being created. It also ensures that we always have a way of contacting a wikis founder should there ever be a need to contact him or her. And per Escyos, there are many places where you can make an email address for free if you do not want to use your private email for ShoutWiki. --Jedimca0^(talk) 13:56, 14 February 2011 (UTC)

Splitting up CSS

Hi Jack. I am wondering if you know of a way to split CSS into separate files, rather than have it all in Common.css.

I have made a template that requires quite a bit of CSS that is not used elsewhere. It would be nice to be able to put that CSS in a separate file, and then use

@import url('path/to/Template.css')

(or similar) to get it into Common.css. Is this possible?

Thanks in advance

btw, you might find the template interesting, although it is purely decorative. - Malice (talk) 05:13, 20 February 2011 (UTC)

Please be aware that splitting up common CSS/JS into multiple pages means that more HTTP requests = slower pageloads. It can also make some JS scripts fail. That being said, it's possible to split up CSS into multiple pages. Use @import "/w/index.php?action=raw&ctype=text/css&title=MediaWiki:Your_custom.css"; in your MediaWiki:Common.css to import the contents of MediaWiki:Your_custom.css into it.

In JavaScript, you can use importStylesheet function to import a page as CSS; for example, importStylesheet( 'MediaWiki:Your_custom.css' );

--Jack Phoenix _(contact) 15:41, 20 February 2011 (UTC)

Great, thanks! - Malice (talk) 20:52, 20 February 2011 (UTC)

"What links here" problem

An example of the random page it returns - this being "WhatLinksHere"

Hi Jack, I'm having a problem with the "What links here" on the Monaco skin on Wikisimpsons. The link, in the sidebar, produces a "what links here" for a random page. If you reload the cache (CTRL + F5) it produces another random page, being "Abraham Simpson" for the example. It's fairly annoying and difficult to work with, although it seems to work fine in the Monobook skin. Thanks, Jordan (George (talk) 10:57, 20 February 2011 (UTC))

Now that's an odd problem! It seems that the problem occurs only in some pages; I tested the Homer Simpson page and it was totally OK, while the template page in the picture was not. I tweaked the MediaWiki:Monaco-toolbox message on Wikisimpsons; let's hope that that fixes the problem. We should be seeing the changes in about 4 hours, as the MediaWiki messages are cached if and when your language is the same as the wiki's content language. --Jack Phoenix _(contact) 15:41, 20 February 2011 (UTC)

It seems to be working fine now. --George (talk) 17:37, 20 February 2011 (UTC)

Thanks Jack. I asked a couple of times on IRC but was ignored and gave up eventually. Didn't cross my mind to ask on your talk page :P ☆The Solar Dragon☆ 21:02, 20 February 2011 (UTC)

Monaco

Can change the default skin of the Dutch HP wiki tom Monaco.{{SUBST:Gebruiker:Samben/signature}} 22:06, 20 February 2011 (UTC)

Done. --Jack Phoenix _(contact) 22:10, 20 February 2011 (UTC)

Hosting

Will/Is Shoutwiki going to be hosting wikis with their own address (e.g stargate-wiki.org :D )? ESCYOS - YOUR GOD! ^{talk | contribs} 04:42, 21 February 2011 (UTC)

Yes, it's certainly something that we're planning to offer, either as a premium feature or as a normal one (I'm thinking that premium might be a bit easier on the techs, I'm not sure how easy/difficult setting up such a thing is). You might want to ask Misza about his plans regarding custom domains, as those aren't exactly my domain (no pun intended!). --Jack Phoenix _(contact) 23:35, 21 February 2011 (UTC)

Delete http://monaco.shoutwiki.com/wiki/Monaco_Wiki

Hello!

Please delete http://monaco.shoutwiki.com/wiki/Monaco_Wiki - we have moved to another host.

AWAMember (Talk page, Mail me). 17:13, 21 February 2011 (UTC)

It's very sad to see a wiki go, especially for the Monaco wiki as you don't even seem to have the Monaco skin on your new wiki...in any case, I've deleted the wiki as per your request. Best of luck with the wiki on the new address! --Jack Phoenix _(contact) 23:35, 21 February 2011 (UTC)

Request

• in 網站百科全書

• require_once("$IP/extensions/ChangeAuthor/ChangeAuthor.setup.php"); $wgGroupPermissions['sysop']['changeauthor'] = true;

• request add Permissions 隱藏員 (Manual:RevisionDelete)。

• $wgAddGroups['bureaucrat'] = array('隱藏員','巡查員','巡查豁免者','跨维基导入者');
• $wgRemoveGroups['bureaucrat'] = array('隱藏員','巡查員','巡查豁免者','跨维基导入者');
• $wgAddGroups['sysop'] = array('巡查員','巡查豁免者');
• $wgRemoveGroups['sysop'] = array('巡查員','巡查豁免者');
• $wgGroupPermissions['跨维基导入者']['import'] = true;
• $wgGroupPermissions['隱藏員']['deleterevision'] = true;
• $wgGroupPermissions['隱藏員']['hideuser'] = true;
• $wgGroupPermissions['隱藏員']['suppressrevision'] = true;
• $wgGroupPermissions['隱藏員']['suppressionlog'] = true;
• $wgGroupPermissions['隱藏員']['hiderevision'] = true;
• $wgGroupPermissions['隱藏員']['abusefilter-hide-log'] = true;
• $wgGroupPermissions['隱藏員']['oversight'] = true;
• $wgGroupPermissions['隱藏員']['abusefilter-hidden-log'] = true;

• request add Permissions 巡查豁免者(autopatrol)、巡查員(patroller)。

• $wgGroupPermissions['巡查豁免者']['autopatrol'] =true;
• $wgGroupPermissions['巡查員']['patrol'] =true;
• $wgGroupPermissions['巡查員']['autopatrol'] =true;
• $wgAddGroups['巡查員'] = array('巡查員','巡查豁免者');
• $wgRemoveGroups['巡查員'] = array('巡查豁免者');

--Yyaootw (talk) 14:38, 22 February 2011 (UTC)

I've added the first $wgAddGroups and $wgRemoveGroups definitions (without overwriting the defaults), with some changes and the autopatrol and patrol groups. Most of the permissions which you requested for one of the new groups, such as revisiondelete and such, are staff-only for the time being. They may, in extraordinary circumstances, be given out to some trusted users. Of course we'll naturally hope that there will be no need for revisiondelete etc. but if there is, ShoutWiki staff are here and willing to help you.

I'd also suggest using English names in configuration settings; it's the easiest for everybody. The English group names can be customized/translated by editing the appropriate system messages (i.e. s:w:zh-tw.website:MediaWiki:Group-autopatrol, s:w:zh-tw.website:MediaWiki:Group-autopatrol-member, s:w:zh-tw.website:MediaWiki:Grouppage-autopatrol and so on). --Jack Phoenix _(contact) 18:24, 22 February 2011 (UTC)

Sockpuppeting

What do you guys class as sockpuppeting? Would someone creating another account to get past the 5 wiki thing be a violation of this? ESCYOS - YOUR GOD! ^{talk | contribs} 04:54, 23 February 2011 (UTC)

Vide Wiki deletion policy that means deleting all your wikis. Misiek (talk) 05:02, 23 February 2011 (UTC)

Yea thats what i thought, and i noticed you let admin2 know this. ESCYOS - YOUR GOD! ^{talk | contribs} 05:09, 23 February 2011 (UTC)

Inaccessible pages

Hi Jack You recently installed the DPL forum extension for me on pathofexile.shoutwiki.com, thanks for that. There is a problem though - there are some pages that were created using Special:Import which were in the forum namespace. It seems when they got imported, they went into the Main namespace as Forum:xxxx, and now that a Forum namespace has been created, they are no longer accessible. I would be grateful if you could move all twelve Forum:xxxx pages into the forum namespace, or failing that, delete them.

Also, there is a user called Tpapp157 who is trying to register at shoutwiki. He had contributions on the imported pages. He tells me that he when he tries to register it tells him that his name is in use. To quote him directly: "It says something about transferring my account but I can't figure out how to do this. Am I missing something? Do I just need to make a new account? I tried but apparently my username is in use."

I can't find a user with that name in the user list of pathofexile.shoutwiki or the shoutwiki hub. Any idea what is going on there? Malice (talk) 05:46, 23 February 2011 (UTC)

The forum pages should now be accessible. I ran a maintenance script (namespaceDupes.php) to fix the issue, it reported that everything "Looks good!" so I assume that the issue has been resolved.

As for the user registration issue, the underlying issue is a bit more complicated, but I'll try to explain it anyway.

Short version: I've enabled the MediaWikiAuth extension on the Path of Exile wiki and the user should now be able to register.

Longer version: the MediaWikiAuth extension requires patching a core file of the MediaWiki software, namely the login/signup page (includes/SpecialUserlogin.php). MediaWikiAuth adds some of its own checks there. It checks if the revision table in the database has some entries where rev_user_text = name of the user who is trying to sign up. If it finds any entries (as it now did), it prevents registration — to prevent imposters, as the user name is reserved for the "original user".

Of course this is only useful for imported wikis, for which we manually enable MediaWikiAuth on a case-by-case basis, normally after importing the wiki's content and files. MediaWikiAuth is not enabled by default for all new wikis, as it would be pointless and most likely even counterproductive — after all, we can safely assume that most wikis created via Special:CreateWiki are entirely new wikis, not imports from other sites.

The issue here is that even though MediaWikiAuth is not always active, the core patches will always be there. In most cases, those small bits of code will not cause any issues. Sometimes there are what could be called "edge-cases", such as your case here, and they will cause problems. It should be noted that the user was unable to register on the Path of Exile wiki before MediaWikiAuth was actived, but s/he could have gone to any other ShoutWiki-hosted wiki (such as this one, for example :-) to "cheat" MediaWikiAuth, because ShoutWiki accounts are global (shared between other ShoutWiki sites). --Jack Phoenix _(contact) 16:07, 23 February 2011 (UTC)

Thankyou very much for the long version, and of course the solution (both issues are fixed now). If I understand correctly he will still not be able to create a new account with that name, but when he tries to log in the old account will automatically be imported remotely into the shoutwiki. Very interesting. Thanks again. - Malice (talk) 18:11, 23 February 2011 (UTC)

Yep, the user will not be able to create a new account but rather log in with their old account. --Jack Phoenix _(contact) 21:14, 25 February 2011 (UTC)

Problem

Same problem here. :( --Silver Knight (talk) 12:27, 23 February 2011 (UTC)

The problem is unclosed div tags. I fixed this by placing an extra </div> at the bottom of the page. ☆The Solar Dragon☆ 12:49, 23 February 2011 (UTC)

Thanks for helping :-) --Silver Knight (talk) 12:56, 23 February 2011 (UTC)

Another problem even when I added div tags. --Silver Knight (talk) 13:08, 23 February 2011 (UTC)

There are two unclosed <div> tags in the colors section. - Malice (talk) 14:40, 23 February 2011 (UTC)

Honda CR-V now. --Silver Knight (talk) 09:27, 24 February 2011 (UTC)

Fixed. ☆The Solar Dragon☆ 10:31, 24 February 2011 (UTC)

And the Saturn ION. --Silver Knight (talk) 10:34, 24 February 2011 (UTC)

The easiest way to find the unclosed tags is to CTRL + F "<div", then look to see if there is a closing tag, if not, add one. --George (talk) 11:52, 24 February 2011 (UTC)

These, like the problems we had on Wikisimpsons with unclosed div tags, are usually a result of templates so that won't do anything. ☆The Solar Dragon☆ 11:57, 24 February 2011 (UTC)

Thanks... --Silver Knight (talk) 12:53, 24 February 2011 (UTC)

What if the Stewards (wiki creator) have the permission of editing Special:Interwiki?

First, I thought a wiki creator will have the permission of editing Special:Interwiki, but after viewing some wikis (such as:zh-tw.shoutwiki.com), I find most of the Interwiki-table setting was edited by you and I haven't the permission to edit the "Special:Interwiki" page of the wiki I creat.

So, I wonder if what will happen when the wiki creator have this permission. Will it lead to a spam site or a phishing site?

Well, maybe it is a useless in most of wiki, so I just wonder why there is a limit on that. I am a beginer, and edit my wiki at random to be familiar with wiki language and wikimedia system. If you tell me you can help add Interwiki-table, I am sorry but I think I don't need that. I am just out of curiosity. --Summerking (talk) 20:38, 25 February 2011 (UTC)

Interwikis (as shown on Special:Interwiki) are shared between all ShoutWiki sites, which is why stewards will not be able to edit them. You can request a new interwiki link to be added by leaving me or another staff member a message and we will consider adding it; these requests are handled on a case-by-case basis.

Because interwiki links and interlanguage links are stored on the same table, it means that we currently can't allow local stewards to modify interlanguage links either, which is unfortunate. If you need interlanguage links added between two wikis (for example, s:w:fi.24 and s:w:fr.24), please contact us (see Customer Support Team#Contact us for more info). --Jack Phoenix _(contact) 21:14, 25 February 2011 (UTC)

I see. Now I know the difference between "global interwiki" and "local interlanguage", thanks for your reply.

Now I want to konw that any sites(more than shoutwiki sites) are allowed to add to the list of local interlanguage? Do you have the way to separate those two table? (With a certain extension which creat a page only have a editable interlanguage table?) And is this item(let local stewards to modify interlanguage table) on your todolist? If each time I need add a site to the table I have to contact you, maybe it means that is a serious thing which I should think carefully before I do. --Summerking (talk) 13:41, 26 February 2011 (UTC)

It is technically possible to add wikis that are not hosted by ShoutWiki as interlanguage link destinations and this has been done a few times in the past (see Jedipedia for an example), but we'd prefer not to link to competiting sites, obviously. :-)

I'm not sure, but I think that it could be possible to create a new permission which would allow local stewards to modify interlanguage links and interlanguage links only. I realize that it's a bit annoying to have to request a staff member to add interlanguage links between two wikis, but I don't see it as a major issue.

As for interwiki links, yes, you have to contact a staff member to request that we add a site to the interwiki table. We're interested in the reasons why you think that a site should be added into the interwiki table. In most cases, you can just use external links to link to the site you wish to. --Jack Phoenix _(contact) 17:44, 26 February 2011 (UTC)

I know it is strange that I insist on a permission of editing interlanguage table. I just think it is cool that there is a list of "other language" wikis in the left bottom :-) And it seem to be an advanced use that use [[:en:XXX]] in articles. So it is just self-inflicted setbacks(折腾). (*^ ^*)

Sorry to disturb you. --Summerking (talk) 21:16, 26 February 2011 (UTC)

Nothing to apologize. :-) For the time being, you can ask me or another staff member to add the interlanguage links for you; in the future, it might be possible for local stewards to add interlanguage links...I'll need to look into that after we have upgraded our version of MediaWiki to 1.16. --Jack Phoenix _(contact) 22:48, 26 February 2011 (UTC)

面板

希望您可以將[[教育wiki]]的Skin Monaco 更改 Skin Vector。--王大偉 (talk) 08:01, 26 February 2011 (UTC)

Sorry, I don't understand Chinese. Could you please write your message in English instead? --Jack Phoenix _(contact) 17:44, 26 February 2011 (UTC)

Help page editors(sharedhelp)

request add Permissions sharedhelp in shoutwiki(zh).--Z135793 (talk) 08:27, 26 February 2011 (UTC)

Done, I've added the sharedhelp group to the s:w:zh-tw wiki and made it so that only administrators, ShoutWiki staff and users in the sharedhelp group can edit pages in the help namespace. --Jack Phoenix _(contact) 17:44, 26 February 2011 (UTC)

Wiki Deletion

Can you delete the Create a universe Wiki started out as a good idea but i would just be plagerising my own work from another one of my wikis there. thanks ESCYOS - YOUR GOD! ^{talk | contribs} 09:48, 26 February 2011 (UTC)

Done. --Jack Phoenix _(contact) 17:44, 26 February 2011 (UTC)

Hide a History

• Please Hide a History--王大偉 (talk) 13:45, 26 February 2011 (UTC)

Done. --Jack Phoenix _(contact) 17:44, 26 February 2011 (UTC)

SUBPAGENAME and BASEPAGENAME issue.

Hi Jack,
I think there is a big issue with the BASEPAGENAME and The SUBPAGENAME magic words in ShoutWiki in general. For an example, you see this page as normaly his BASEPAGENAME equals to "Str left" but not here. It equals "Str left/doc". That makes a big issue for transcluded pages and with templates which has to find the BASEPAGENAME. That was a problem I noticed month ago with Stargate Wiki. Do you have an answer for this?
Thanks. Regards. --LIMAFOX76 26 février 2011 à 10:30 (UTC)

Replied on s:w:fr:Discussion utilisateur:Jack Phoenix#SUBPAGENAME and BASEPAGENAME issue.. --Jack Phoenix _(contact) 17:56, 26 February 2011 (UTC)

I think you are not permit a template page to have a SUBPAGE. In other page ,such as User_talk:Summerking/SUBPAGE, {{BASEPAGENAME}} work well. And it will diaplay a tagline "< User talk:Summerking" to let visitor go back to the 'parent' page. But in template page, it's not. Just like what LIMAFOX76 say. So I have to use {{#titleparts: {{BASEPAGENAME}} | 1}}. --Summerking (talk) 21:43, 26 February 2011 (UTC)

Good catch, Summerking! I've enabled subpages in the template namespace (added NS_TEMPLATE => true to $wgNamespacesWithSubpages; now the only namespaces where subpages are not enabled are File, MediaWiki and Category), so maybe it works now. --Jack Phoenix _(contact) 22:48, 26 February 2011 (UTC)

I consider main namespace should NOT have sub-pages, or the article like [[GNU/Linux_naming_controversy]] will be treated as the sub-page of [[GNU]]. See also Wikipedia:Subpages, and it suggest a temp pages(workpages) should be the sub-page of talk namespace, e.g. [[Talk:Example Article/Temp]]. --Summerking (talk) 11:28, 27 February 2011 (UTC)

I consider page names like GNU/Linux naming controversy as edge cases; it's possible that such problems occur, but relatively rare. If I were to turn off subpages in the main namespace, I'd assume that soon either my talk page or Bugzilla or both would be filled with requests to re-enable subpages in the main namespace. --Jack Phoenix _(contact) 13:56, 1 March 2011 (UTC)

Vector

I need to Skin Vector in my wiki ,my wiki is 電影維基百科。--王大偉 (talk) 09:37, 27 February 2011 (UTC)

The Vector skin will be available once we've upgraded to MediaWiki 1.16; it was written for 1.16 and it's not compatible with earlier versions of MediaWiki. --Jack Phoenix _(contact) 11:12, 27 February 2011 (UTC)

interlanguage links

• hi need add interlanguage links zh to http://zh.shoutwiki.com/wiki/$1--王大偉 (talk) 14:14, 28 February 2011 (UTC)

I think we should not need two wikis in Traditional Chinese. As we have a Traditional Chinese Shoutwiki now, But maybe we should have a Simplified Chinese version, or a Cantonese version.

Or maybe we should turn this wiki to a Chinese version including Traditional Chinese and Simplified Chinese, like Wikia中文. --Summerking (talk) 15:36, 28 February 2011 (UTC)

Please move zh-tw(台灣) to zh(中文)，And increase interlanguage links zh-hk(香港)、zh-cn(中國)、zh-mo(澳門) to zh ,Thanks.--Z135793 (talk) 04:30, 1 March 2011 (UTC)

This is actually more complicated than I thought; please open a new ticket on Bugzilla about this so that our technical staff can handle it and make sure that no data gets lost. --Jack Phoenix _(contact) 13:56, 1 March 2011 (UTC)

Please add extensions

Please add extensions FlashMP3、Embed_Document、Drafts、FLVPlayer、Semantic_Forms、AWC Forum、Admin_Links、FlaggedRevsand <DPL> </DPL> in網站百科全書。--Z135793 (talk) 13:07, 1 March 2011 (UTC)

Please open a new ticket on Bugzilla about this so that our technical staff can handle it; they will review the extensions for any and all possible security vulnerabilities etc. before the extensions are enabled. I can already say that many of these are not even listed on our Help:Extensions page; we most likely will not be offering FlashMP3, Embed Document, FLVPlayer (for security reasons) and AWC's Forum (unnecessary and IIRC its license was a Creative Commons one that forbids commercial use); Drafts, Semantic Forms, Admin Links and FlaggedRevs might be possible. FlaggedRevs is huge, but it's used on many Wikimedia wikis, such as MediaWiki.org, so it's probably safe. --Jack Phoenix _(contact) 13:56, 1 March 2011 (UTC)

• see #id160.