I have installed 4 mediawiki wikis. And one mediawiki with wikibase installed, this wiki is being used for the global userdatabase and some other stuff. Now we have all our interwiki links like this
[[en:Main Page]]
However we want to have a global database with all the interwiki links, they have did this on wikipedia too.
http://www.wikidata.org/wiki/Q727#sitelinks-wikipedia
So what extension do we need for this?
As Tgr wrote: You need to install Wikibase Client on the other 3 wikis.
Related
Is it possible to make the version control repository and use it within a local network using SourceTree or Mercurial. Didn't find any relevant info for this. Is it at all possible to use only lan for this?
Yes, using it in a local network instead of the Internet is possible as well.
You need some kind of server - there are plenty of possibilities, see Publishing Mercurial Repositories for an exhaustive list.
From personal experience, I know only two of the non-internet options listed there:
network share ("shared disk" in the list) used at work for about three years without problems
hgweb, Mercurial's default web interface (looks like this)
I wrote some more about my "Mercurial hosting experience" here.
I built a blog with Jekyll , I write technical posts and something about my daily life. I want to make my technical posts available to anybody but posts about myself only available to my friends for privacy. How can I achieve this?
With Jekyll itself, you can’t (barring some arcane JavaScript client-side encryption). You can use your webserver’s access control settings, though. If you use Apache, you can use the .htaccess file to protect a certain folder with a password. And then you would need to set up Jekyll to output the protected posts into this folder only.
With latest phpStorm 9 we have new feature called simultaneous tags editing.
This is generally very nice feature that i'd like to use, but i have one old project with very bad code with a lot of mixed PHP, HTML and JS code, where it breaks code.
I know i can disable this in settings->editor->General->simultaneous tag editing, but it disables this feature for whole phpStorm. Is there way to disable it only per one project?
Is there way to disable it only per one project?
Nope -- this is an IDE-wide setting.
The only possible solution I can think of is to have separate PhpStorm installation that will use custom folders to store IDE settings (look into idea.properties file from PhpStorm distribution, e.g. on Windows 7 it would typically be %PhpStorm-Install-Folder%\bin\idea.properties).
With IDE settings stored in different location you can now configure this installation with different settings (e.g. have that option turned off). Obviously, all settings here will be different to your original setup, unless you configure it the same way or will keep certain config files synced (e.g. Keymaps, Color, Web Servers, Live Templates and other things could easily be synced on file level).
Just remember to launch this installation when you want to work with that specific project.
I created a plugin for sublime and I called it "sublimecastling".
The main idea is to replace 2 selected fields.
So I'll be glad to know whether it's possible to add it to your Sublime repository in order users could install the plugin via package-control.
The github link is provided below,
https://github.com/unknownuser88/sublimecastling
If you want to make a plugin available via Package Control, visit the documentation page on the Package Control website and click on Submitting a Package. There are a number of steps, which can be summarized as follows:
Search Package Control to ensure your package fulfills an unmet need, or greatly improves upon an existing package - don't create a new one (especially a very simple one) when you could work with the author of an existing one to add a particular feature.
Pick a name - there are several requirements here.
Decide how to host - Github? Bitbucket? Your own SSL server?
my own note here: Github is easiest
Pick a versioning strategy using semantic versioning. Note that all new packages must release by using versioning tags, not by branches or commits.
Prepare your repo - several things to do here.
Fork the Package Control Channel on Github and add your repo to the default channel - detailed instructions included.
Run the ChannelRepositoryTools package in Sublime to make sure everything is OK.
Note: Test your package with both ST2 and ST3 to make sure it works with both versions of Sublime. If you can only support one version due to the language differences between Python 2.6 and 3.3, pick ST3 - it is the future of Sublime, has a very large user base already, and will get you maximum exposure. If you haven't personally upgraded to ST3, now is the time to do so. If you are a registered user—which you should be :)—test with both the public beta and the latest dev build.
Finally, you can submit your pull request.
Be patient, it may take a little while for it to be reviewed, and it is not uncommon at all for changes to be requested. It is by following strict procedures that the community maintains the high quality of the packages available for users.
GeSHi Sourceforge group redirects MediaWiki-related issues to MediaWiki. MediaWiki redirects requests & features back to SourceForge.
I modified my install to parse PHP blocks allowing to highlight HTML/JS/CSS as well.
As you know, the MediaWiki extension lives in a directory named SyntaxHighlight_GeSHi, and contains a subdirectory geshi. If your patch is to the files inside geshi, submit the patch to the GeSHi Sourceforge group. If your patch is to the files not in geshi, submit it to MediaWiki's bugzilla.
If your patch is to both, hopefully the part of the patch to files inside geshi is independently useful. If so, submit that part to the Sourceforge group and the other part to MediaWiki. If the patch to the geshi files is not independently useful, you may have problems convincing either group to take it.
I don't know this extension but you can try:
MediaWiki's BugZilla
The mailing lists, probably mediawiki-l
The MediaWiki IRC channel on Freenode