Tuleap - how to turn on mediawiki - mediawiki

I'm running Tuleap™ 9.16.99.13. I see in the Tuleap Wiki documentation that MediaWiki is now available. Is there some way to turn on or activate MediaWiki or will that require upgrading?

Mediawiki is a Tuleap plugin , you need to install it as site admin :
administration >> manage all plugins >> available plugins and click on install.
After this, you need to activate on your project. As project admin go on :
Youre project >> admin >> Services and enable it.
FYI Tuleap 9.16 is now an old version, some change have been made since.

Related

Some extensions of MediaWiki does not work

I have installed MediaWiki CMS from Debian.
Before update OS from Squeeze to Jessie, all extensions worked fine.
After the upgrade, some of the extensions stopped working: Gadgets, WikiEditor. The "Gadgets" extension is in the list of extensions used on the version page. The Gadgets configuration page is in the list of seperate pages, as well as in the user settings in full. But on the pages with wiki articles, gadgets do not appear (for example Gadget-UTCLiveClock). I do not see the call to this script in the source code of the page.
enter image description here
<script>(window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"Заглавная_страница","wgTitle":"Заглавная страница","wgCurRevisionId":774,"wgRevisionId":774,"wgArticleId":1,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":"Ярослав","wgUserGroups":["bureaucrat","svnadmins","sysop","*","user","autoconfirmed"],"wgCategories":[],"wgBreakFrames":false,"wgPageContentLanguage":"ru","wgPageContentModel":"wikitext","wgSeparatorTransformTable":[",\t."," \t,"],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy","wgMonthNames":["","январь","февраль","март","апрель","май","июнь","июль","август","сентябрь","октябрь","ноябрь","декабрь"],"wgMonthNamesShort":["","янв","фев","мар","апр","май","июн","июл","авг","сен","окт","ноя","дек"],"wgRelevantPageName":"Заглавная_страница","wgRelevantArticleId":1,"wgRequestId":"dfc9594aa741e7ad292fdee8","wgUserId":2,"wgUserEditCount":1249,"wgUserRegistration":1347855570000,"wgUserNewMsgRevisionId":null,"wgIsProbablyEditable":true,"wgRestrictionEdit":["sysop"],"wgRestrictionMove":["sysop"],"wgIsMainPage":true,"wgWikiEditorEnabledModules":{"toolbar":true,"dialogs":true,"preview":false,"publish":false},"wgCategoryTreePageCategoryOptions":"{\"mode\":0,\"hideprefix\":20,\"showcount\":true,\"namespaces\":false}"});mw.loader.state({"site.styles":"ready","noscript":"ready","user.styles":"ready","user.cssprefs":"ready","user":"ready","user.options":"loading","user.tokens":"loading","mediawiki.legacy.shared":"ready","mediawiki.legacy.commonPrint":"ready","mediawiki.sectionAnchor":"ready","mediawiki.skinning.interface":"ready","skins.vector.styles":"ready"});mw.loader.implement("user.options#0edrpvk",function($,jQuery,require,module){mw.user.options.set({"gender":"male","timecorrection":"ZoneInfo|420|Asia/Barnaul","gadget-DotsSyntaxHighlighter":"1","gadget-HotCat":"1","gadget-UTCLiveClock":"1","gadget-Wikilinker":"1","gadget-addThisArticles":"1","gadget-popups":"1","gadget-preview":"1","usebetatoolbar":"1","usebetatoolbar-cgd":"1","watchlisttoken":"SOME_TOKEN_1"});});mw.loader.implement("user.tokens#USER_TOKENS",function ( $, jQuery, require, module ) {mw.user.tokens.set({"editToken":"SOME_TOKEN_2","patrolToken":"SOME_TOKEN_3","watchToken":"SOME_TOKEN_4","csrfToken":"SOME_TOKEN_5"});/*#nomin*/;});mw.loader.load(["mediawiki.page.startup","skins.vector.js"]);});</script>
<script>(window.RLQ=window.RLQ||[]).push(function(){mw.loader.load(["mediawiki.action.view.postEdit","site","mediawiki.user","mediawiki.hidpi","mediawiki.page.ready","mediawiki.searchSuggest","mediawiki.page.watch.ajax","ext.gadget.referenceTooltips","ext.gadget.directLinkToCommons","ext.gadget.preview","ext.gadget.popups","ext.gadget.addThisArticles","ext.gadget.HotCat","ext.gadget.Wikilinker","ext.gadget.DotsSyntaxHighlighter","ext.gadget.UTCLiveClock"]);});</script><script>(window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgBackendResponseTime":385});});</script>
In mirror version (Debian Squeee, MediaWiki 1.25) all work.
enter image description here
<script>if(window.mw {mw.config.set({"wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"Заглавная_страница","wgTitle":"Заглавная страница","wgCurRevisionId":774,"wgRevisionId":774,"wgArticleId":1,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":"Ярослав","wgUserGroups":["bureaucrat","svnadmins","sysop","*","user","autoconfirmed"],"wgCategories":[],"wgBreakFrames":false,"wgPageContentLanguage":"ru","wgPageContentModel":"wikitext","wgSeparatorTransformTable":[",\t."," \t,"],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy","wgMonthNames":["","январь","февраль","март","апрель","май","июнь","июль","август","сентябрь","октябрь","ноябрь","декабрь"],"wgMonthNamesShort":["","янв","фев","мар","апр","май","июн","июл","авг","сен","окт","ноя","дек"],"wgRelevantPageName":"Заглавная_страница","wgUserId":2,"wgUserEditCount":885,"wgUserRegistration":1347855570000,"wgUserNewMsgRevisionId":null,"wgIsProbablyEditable":true,"wgRestrictionEdit":["sysop"],"wgRestrictionMove":["sysop"],"wgIsMainPage":true,"wgWikiEditorEnabledModules":{"toolbar":true,"dialogs":true,"hidesig":true,"preview":false,"previewDialog":false,"publish":false},"wgCategoryTreePageCategoryOptions":"{\"mode\":0,\"hideprefix\":20,\"showcount\":true,\"namespaces\":false}"});}</script><script>if(window.mw){mw.loader.implement("user.options",function($,jQuery){mw.user.options.set({"ccmeonemails":0,"cols":80,"date":"default","diffonly":0,"disablemail":0,"editfont":"default","editondblclick":0,"editsectiononrightclick":0,"enotifminoredits":0,"enotifrevealaddr":0,"enotifusertalkpages":1,"enotifwatchlistpages":1,"extendwatchlist":0,"fancysig":0,"forceeditsummary":0,"gender":"unknown","hideminor":0,"hidepatrolled":0,"imagesize":2,"math":0,"minordefault":0,"newpageshidepatrolled":0,"nickname":"","norollbackdiff":0,"numberheadings":0,"previewonfirst":0,"previewontop":1,"rcdays":7,"rclimit":50,"rows":25,"showhiddencats":0,"shownumberswatching":1,"showtoolbar":1,"skin":"vector","stubthreshold":0,"thumbsize":5,"underline":2,"uselivepreview":0,"usenewrc":0,"watchcreations":1,"watchdefault":1,"watchdeletion":0,"watchlistdays":3,"watchlisthideanons":0,"watchlisthidebots":0,"watchlisthideliu":0,"watchlisthideminor":0,"watchlisthideown":0,"watchlisthidepatrolled":0,"watchmoves":0,"watchrollback":0,"wllimit":250,"useeditwarning":1,"prefershttps":1,"mathJax":false,"language":"ru","variant-gan":"gan","variant-iu":"iu","variant-kk":"kk","variant-ku":"ku","variant-shi":"shi","variant-sr":"sr","variant-tg":"tg","variant-uz":"uz","variant-zh":"zh","searchNs0":true,"searchNs1":false,"searchNs2":false,"searchNs3":false,"searchNs4":false,"searchNs5":false,"searchNs6":false,"searchNs7":false,"searchNs8":false,"searchNs9":false,"searchNs10":false,"searchNs11":false,"searchNs12":false,"searchNs13":false,"searchNs14":false,"searchNs15":false,"gadget-referenceTooltips":1,"gadget-HotCat":"1","gadget-UTCLiveClock":"1","gadget-addThisArticles":"1","gadget-popups":"1","gadget-preview":"1","timecorrection":"ZoneInfo|360|Asia/Novosibirsk","usebetatoolbar":"1","usebetatoolbar-cgd":"1","watchlisttoken":"SOME_TOKEN_1"});},{},{});mw.loader.implement("user.tokens",function($,jQuery){mw.user.tokens.set({"editToken":"SOME_TOKEN_2","patrolToken":"SOME_TOKEN_3","watchToken":"SOME_TOKEN_4"});},{},{});/* cache key: sitedb-mediawiki_:resourceloader:filter:minify-js:7:SOME_ROKEN */}</script>
<script>if(window.mw){mw.config.set({"wgBackendResponseTime":320});}</script>
I installed MediaWiki 1.28 from the official site from the tar archive to a new directory and a new schema, without additional extensions. I set up Gadget-UTCLiveClock, but it still does not work on the article page.
There are no errors in the logs.
What could be the problem?
MediaWiki 1.28.0
PHP 5.6.30-0+deb8u1 (apache2handler)
MySQL 5.5.54-0+deb8u1
Debian Jessie 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux

What does this Cordova registry warning mean in the github facebook login plugin documentation?

After navigating to the github documentation for facebook from intel xdk plugin management section the second most prominent thing you see on the page is this.
<< --- Cordova Registry Warning [iOS]
Installing this plugin directly from Cordova Registry results in Xcode using a broken FacebookSDK.framework, this is because the current publish procedure to NPM breaks symlinks CB-6092. Please install the plugin through a locally cloned copy or re-add the FacebookSDK.framework to Xcode after installation.
------------------------------------------ >>
The link the the github page is here
https://github.com/Wizcorp/phonegap-facebook-plugin.
Can someone explain what this really means? It's already terribly confusing to get the basic fb login up and running on my mobile app, this warning is confusing the process for me even more as it assumes I know more than I do.
Can someone break this down in beginner terms? Thank you.
Problem
The FacebookSDK.framework will be delivered broken if you fetch it from NPM, because the publish procedure to NPM breaks symlinks. I can't tell you more then that.
Workaround
The workaround is cloning the repository of the plugin 'phonegap-facebook-plugin' with GIT and adding the plugin to your PhoneGap/Cordova project.
Enter the following command in your CMD or Terminal to clone the repository:
git clone https://github.com/Wizcorp/phonegap-facebook-plugin
Enter the following command in your CMD or Terminal to add the plugin to your PhoneGap/Cordova project:
cordova -d plugin add /path/to/cloned/phonegap-facebook-plugin --variable APP_ID="123456789" --variable APP_NAME="myApplication"
Solution
The developers of the plugin 'phonegap-facebook-plugin' have a solution for cordova > 4.0.0 in the develop branche of the plugin's repository.
More info for installing the plugin:
Android
iOS

How to test google chrome workspaces on linux?

I saw this two videos
http://www.youtube.com/watch?v=kVSo4buDAEE
http://www.youtube.com/watch?v=x6qe_kVaBpg
and I wanted to try google workspaces on my linux desktop
I followed these instructions: https://plus.google.com/+GoogleChromeDevelopers/posts/644qQuBKZeL
And this detailed tutorial: http://devcoma.blogspot.it/2013/01/how-to-enable-workspace-experiment-on.html
But the "File system folders in Sources Panel" won't show up
I tried with "Chromium Version 25.0.1364.160 Ubuntu 13.04 (25.0.1364.160-0ubuntu3)"
and also with "Chrome Version 29.0.1530.2 dev"
(I installed this dev version from http://www.chromium.org/getting-involved/dev-channel)
Anybody had any luck whith this?
I found the way to test it.
These are the steps I had to follow
Install a ppa with a more recent chromium version, from here:
http://www.webupd8.org/2012/09/new-chromium-stable-and-development.html
sudo add-apt-repository ppa:a-v-shkop/chromium-dev
sudo apt-get update
sudo apt-get install chromium-browser
as of today it install Version 27.0.1453.6 Ubuntu 13.04 (191032)
Open the browser and in the url bar enter chrome://flags/
enabled "Enable Developer Tools experiments."
restart the browser
open the web page you want to debug using workspaces
press F12 to open the dev tool
press F1 to open the settings panel
go to Experiments and check "File system folders in Sources Panel"
restart browser
in your file system, add a file named .allow-devtools-edit
cd
touch .allow-devtools-edit
once again, press F12, F1, and select Workspace, add folder, and add the root of your project
to map your web site to your file system, right click on any js file and select 'Map to network resource', then choose the corresponding file
and that's it, in the Workspace section of your Settings, you will see that a mapping has been added, with something like
'http://localhost:9000' -> '/home/opensas/dev/apps/my_js_project'
The good news is that it seems that with the latest Google Chrome development version everything works out of the box, no need to mess around with development or experimental features.
This question is a duplicate for this one
In the Dev-channel version things were changed a bit.
So you don't need to enable devtools experiments
and don't need to manually create .allow-devtools-edit

Mercurial Setup for Lotus Domino Designer 8.5.3

Working on getting the Mercurial Source Control installed and working with Lotus Domino Designer 8.5.3.
Been using Declan's powerpoint from Lotusphere 2012 "AD102: Source Control For The IBM Lotus Domino Developer" as a guide.
What I've done so far is:
Install 8.5.3 Client and Designer via the CI1LPEN.exe install file
Enabled Eclipse plug-in install from designer preferences
Did a File, Application, Install of 1.6.0 MercurialEclipse and 1.4.3 Mercurial Binaries from http://cbes.javaforge.com/update
Verfied they are installed by going to File, Application, Application Management and seeing them listed
Closed Domino designer and client. Restarted.
When I open an application in Designer and alternate click on it's title, the "Team Development" option is not listed. So not able to "Set Up Source Control for this Application.."
Are there any other prerequesites that need to be installed for this to work, or should I should be selecting different install packages?
If you're in 8.5.3 there is nothing that needs to be installed. HOWEVER, the Team Development menu option only appears if you're in the XPages perspective. It doesn't appear in the Domino Development perspective.
Found the problem and it is working for me.
First thing I needed to do was to install the "Source Code Enablement" from: http://www.openntf.org/internal/home.nsf/project.xsp?action=openDocument&name=Source%20Control%20Enablement%20for%20Designer .
The next thing was that I was right clicking on the application name in the Application pane, when I should have been right clicking on the application name in the Navigation pane.
Now see the "Team Development" option.
Have been able to run Mercurial through it paces - commit, branch, merge and etc.

How do I uninstall a plugin from Jenkins (Hudson)?

I have a few plugins in my Jenkins installation which I no longer need. I've already disabled the plugins (and my build still work), and I'd like to remove the plugins completely. What is the right process for completely removing a Jenkins (Hudson) plugin?
As mentioned by Jesse Glick in his answer, if you are using Jenkins 1.487 or higher, then there is a native way to uninstall plugins in the Jenkins UI. See JENKINS-3070 for details.
If you are using a version of Jenkins earlier than 1.487, then you can try manually uninstalling the plugin. As some people point out in the comments, this may not work on some platforms (in those cases, upgrade to at least 1.487 so that you can use the official uninstall feature).
To manually uninstall a plugin, stop Hudson/Jenkins, go to your HUDSON_HOME/plugins directory and remove both the .hpi file and the folder with the same name. So, if you were going to remove the CVS plugin, you would remove both the cvs.hpi file and the cvs directory.
After that, restart Hudson/Jenkins and the plugin won't be there anymore.
Jenkins 1.487 adds a UI for uninstalling plugins: JENKINS-3070
Deleting the <plugin>.hpi file and corresponding <plugin>-plugin directory will effectively remove the plugin.
However, if you have configured parameters that belong to the plugin within your jobs your Hudson or tomcat logs may contain *CannotResolveClassException: hudson.plugins ... * exceptions because it attempts to load the plugin. This can result in build failures even if build is successful.
To fix that,
go to the job configuration and save it again. This should get rid of the plugin reference
if not, go into the hudson home jobs directory and open the config.xml found under the folder named after the job and remove the reference to the plugin
restart hudson
Hudson Plugins explains that some core plugins ("Tier 1" plugins, as they are called) are shipped with Hudson itself, and I assume cannot be deleted therefore.
You can disable it using the Jenkins » Plugin Manager. Go to Installed tab and untick the plugins you want to uninstall and restart Jenkins. Though it does not unintall, at least keeps it away from appearing from configuration pages..