Hello guys,
I used another authentification way : mod_auth_kerb on the Apache side + Mediawiki with SSO plugin (HttpAuthPlugin.php)
It makes an automatic authentification for all users.
If you need any other information, do not hesitate to contact me.
Best regards,
Johan
> -----Message d'origine-----
> De : mediawiki-l-bounces(a)lists.wikimedia.org
> [mailto:mediawiki-l-bounces@lists.wikimedia.org] De la part
> de David Gerard
> Envoyé : vendredi 7 septembre 2007 14:00
> À : MediaWiki announcements and site admin list
> Objet : [Mediawiki-l] Authenticating users by NT login?
>
> For an intranet MW installation, it may (or may not [*]) be a
> nice feature to authenticate by their NT login, which is how
> they're known to pretty much all other systems in this
> company and which would save them remembering another password.
>
> Is there anything for MediaWiki to either (a) pick up their
> NT logon automatically or (b) ask for it and then get it
> verified from whatever serves authentication? Has anyone
> gotten this working? I see various plans mentioned on
> mediawiki.org to use NTLM (which I'm not sure how to set up
> either). Though nothing about anyone getting NT logons for
> use as usernames.
>
>
> [*] "may not" in that tying our wiki infrastructure to our
> Windows desktops strikes me as not the best idea if the
> company ever gets the notion to free us from Windows; I'd
> rather not give anyone another reason not to. OTOH, using
> their existing NT username and password would save me quite
> some effort.
>
>
> - d.
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
"Les informations contenues dans ce message électronique peuvent être de nature confidentielles et soumises à une obligation de secret. Elles sont destinées à l'usage exclusif du réel destinataire. Si vous n'êtes pas le réel destinataire, ou si vous recevez ce message par erreur, merci de le détruire immédiatement et de le notifier à son émetteur."
"The information contained in this e-mail may be privileged and confidential. It is intended for the exclusive use of the designated recipients named above. If you are not the intended recipient or if you receive this e-mail in error, please delete it and immediately notify the sender."
Is there a way to create a class of users or class of pages that can
only be edited by a few people?
I want to insert a set of documents into my wiki that really needs to
be static, except for minor changes from time to time. The people
that will do this work will need access to the wiki as a whole. But
most wiki users should see these documents as protected. The people
editing the protected documents do not need to be general site admins.
How can I set this up?
thanks
Bill
Thanks for the answer, that helps. For the rest of the questions:
1. Is the site name used anywhere in the MySQL database?
2. Will changing the site name make it any more complex to upgrade
from 1.5.4 to 1.1.x?
Appreciate the help.
Frank Fulchiero
Digital Media Specialist
Connecticut College
> From: "Gary Kirk" <gary.kirk(a)gmail.com>
> Subject: Re: [Mediawiki-l] How to change site name
>
> The sitename that displays in the title bar, {{SITENAME}} et al is
> controlled by $wgSiteName, yes.
> Hope this helps.
>
> On 9/7/07, Frank Fulchiero <fful(a)conncoll.edu> wrote:
>> I wanted to change our site name from acorn, to wiki.
>> I know this is generic, but have reasons to do it...
>>
>> The root is already "wiki"
>>
>> http://nutmeg.conncoll.edu/wiki/
>>
>> Running MediaWiki 1.5.4
>>
>> How can this be done?
>> Is it enough to change $wgSitename in LocalSettings.php?
>> Do any changes need to be made to the MySQL database?
>> Will this mess anything up when I upgrade to 1.1x in a few months?
> You normally need to instruct mysqldump not to bother messing about
> > with the character set during export; see
> > http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki#Character_set.
The problem is I don't have the possibility to use mysqldump (with that
appropriate "--deafault-character-set" Option) from the command line. My
provider does not provide it.
> > You may also be able to run the dump file through iconv or similar if
> > it's been corrupted.
Tried iconv, but it also failed. After conversation I get an "Specified
key was too long; max key length is 1000 bytes" error during importing.
Is it really such a hard problem to backup the Wikipedia data? Cause the
problem I have, must also involve a normal backup.
No way to simply export and import the database back via phpmyadmin on
MySQL 5 databases. All foreign special chars get corrupt.
I wonder, why only so few people seem to have that problem.
Kai
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
hi,
is there a possibility to manipulate an articletext before it gets displayed
in the editor?
Is there a hook I can use?
I would need that for a MediaWiki extension I am writing.
http://www.mediawiki.org/wiki/Extension:TagCorrection
Otherwise the FCKeditor destroys tags (eg for syntax highlighting).
Thanks for any help.
--Johannes
hi,
is there a way to edit the text of an article, before it gets to the editor? Is
there a hook for that (MW 1.10.1)?
Would need that for this extension, in order to be able to make reediting with
<tags> and the FCKeditor possible.
http://www.mediawiki.org/wiki/Extension:TagCorrection
--Johannes
hi,
is there a way to edit the text of an article, before it gets to the
editor? Is there a hook for that (MW 1.10.1)?
Would need that for this extension, in order to be able to make
reediting with <tags> and the FCKeditor possible.
http://www.mediawiki.org/wiki/Extension:TagCorrection
Yes I also don't like the idea of using a WYSIWYG editor with
MediaWiki, but since I'm just doing an internship and not the boss I
have to do that.
--Johannes
Hi,
I would like to build an extension for MediaWiki (MW) to make citing
scientific publications easier / more 'natural'. This extension will
be used for my private 'literature wiki', and so requires features
that are not strictly generally useful for MW. However, I think that a
lot of general principles should apply to this project that could
carry over to MW in general.
Below I will outline my thinking. I would like to get feedback on
these ideas, because basically I am very new at MW. Additionally, I
want to organize a list of resources related to this project, and
hopefully this will help me do that.
== First, why not just use an existing extension? ==
* http://en.wikipedia.org/wiki/WP:Citing_Sources#How_to_cite_sources
* http://en.wikipedia.org/wiki/Wikipedia:Citation_templates
* http://en.wikipedia.org/wiki/Wikipedia:Footnotes
In short, I find these methods clunky. Although these tools go a long
way towards providing proper citation support to MW, I think they fall
short in several respects;
* They are somewhat tricky to learn and implement.
* The specific citation data for a given source cannot be
automatically generated (AFAIK).
* Sources are not reusable across pages (sources are not independent 'objects').
* The format of the citation is not user configurable (there no scope
for setting format preferences).
The above list of missing features comes from my perspective as a
scientific student. I write papers citing articles that are mostly
from PubMed using tools like BibTeX, TexMed and Endnote. Typically the
'citation process' has a simple 'pipeline'.
1. Click 'insert citation' or type a citation keyword.
2. A) Select an existing citation from a personal collection or B)
perform a database search to download the citation data into a
collection.
3. Later - configure the citation style and print.
Of course things can differ from the above pattern, such as
occasionally having to manually type the citation details, however, in
general this is the pattern used by most scientists (I think).
I would like to build a system to allow this kind of pattern to be
implemented in MediaWiki.
Some of these issues are addressed by the following extensions;
And;
* http://www.mediawiki.org/wiki/Extension:PagesOnDemand (and PMID_OnDemand)
* http://www.mediawiki.org/wiki/Extension:ProcessCite
* http://www.mediawiki.org/wiki/Extension:Biblio
== Second, describing the system I have in mind. ==
Right! I am getting quite bogged down with the following description,
so lets keep it simple to begin with.
Lets assume that you want to insert a citation from an article listed
in PubMed. This 'source' is found by searching PubMed and has PMID =
1234567. Associated with this PMID is the citation data; title, year,
journal and abstract.
Every cited source will have its own page in the Wiki, called a
'source page'. Each source page will be an instance of a standard
'source template'. Particular source pages can then be dropped into a
regular page as needed.
Making a separate page for each source already provides advantages.
However, two 'magic' steps are still missing and need to be described;
1. Automatically 'instantiating' the source template in the source
page with data from PubMed.
2. Formatting the references in pages using citations.
These steps are described (in outline) in more detail below.
== Third, detailed use case. ==
While writing a scientific article the user types "bla bla
bla{{cite:myKey}}", where myKey is a personal citation keyword that
can be anything at all but will probably be a mnemonic for the desired
source. Lets assume that 'myKey' refers to a new 'source' that has not
been cited before. After saving the page {{cite:myKey}} shows up in
the text as a red link ("Template:Cite:myKey").
Clicking the red link will trigger some 'magic' (using the
PagesOnDemand extension). The 'magic' presents a user with the
"Template:Cite:myKey" page preloaded with a special 'PubMed search'
template.
The PubMed search template allows the user to (surprisingly) search
PubMed. For example of the PHP code required see 'Librarian';
http://bioinformatics.org/project/?group_id=131
>From here it gets a bit tricky... The PubMed search template is
obviously special, and needs to do a lot of things;
1. Lets say after performing a search, a particular 'source' article
is selected from PubMed (lets say with PubMed Unique Identifier
PMID:1234567).
2) The citation data returned from PubMed is used to automatically
instantiate a "PubMed source" template, automatically passing data to
the various fields of the template.
3) This 'instance' is saved into a 'standard' source template page,
something like "Template:PubMed source:PMID:1234567".
4) Finally the 'standard' template is automatically embedded
(transcluded) into the "Template:Cite:myKey" page.
5) The user is left viewing the saved "Template:Cite:myKey" page,
which contains only "{{PubMed source:PMID:1234567}}".
So... (at least) two things have now happened. 1) A "PubMed source"
template has been automatically instantiated with data from PubMed and
saved as a 'standard source'. ii) A layer of abstraction has been put
between the standard source and the mnemonic via template
transclusion. Viewing "Template:Cite:myKey" or "Template:PubMed
source:PMID:1234567" presents all the citation details (including the
abstract).
Viewing a page which calls {{Cite:myKey}} requires more magic ...
The citation should appear as a number in the text and automatically
add itself to a reference listing with a fixed style at the bottom of
the page (like Categories do). This should not require the user to
call a specific <references/> tag, but should happen automatically.
The format of the citation needs to be controlled by CSS.
== Sooo... ==
I now see that almost all of the above is done by PagesOnDemand and
ProcessCite as demonstrated on EcoliWiki. What is missing is the AJAX
search box and the automatic formatting (via CSS). I think that using
the above as a starting point, I can code the AJAX search box, first
presenting the user with a search interface, allowing a selection to
be made, filling in the template and showing the resulting page.
However, I am not sure how to begin to make the references appear
automatically in the way categories do, and I don't know how to set up
the layout to work in conjunction with CSS ...
Any feedback on any of the above (polite or otherwise) is most welcome!
Cheers,
Dan.
P.S.
The following list of extensions look relevant for this project;
* Bibtex
* Cite
* ProcessCite
* DynamicPageList
* CreateArticle
* CreateBox
* PagesOnDemand
* PMID_OnDemand
* Biblio
Also;
http://www.mediawiki.org/wiki/Markup_spec/BNF/Magic_links
Don't let me get in the way of your discussions, but I thought I should clarify that I wasn't trying to make "Unreal" into a namespace proper, it was just a part of the page title. Using the information provided about the database, I was able to find the offending interwiki record and delete it.
If I were to make a suggestion, it would be to disallow default third-party interwikis. This way you can't get blindsided by popular topics or by mere English words for that matter, both of which are true in my case. Failing that, there could be stricter naming guidelines, such as requiring the word "wiki" to be appended (e.g. unrealwiki). In total, though, IMO it's just bad form to provide third-party links to unsuspecting hosts or visitors, especially when there is no visible disclosure that this kind of thing could happen. I'm not clear on why these default links were included in the first place, unless maybe they contributed to the MW code?
At least, I am assuming that these interwikis are provided by default, since no one has yet chided me over an insecure server configuration. Removing default interwikis won't change the issues involved with hosts mixing namespaces and user-defined interwikis, of course, and I'm staying out of that discussion.
---------------------------------
Pinpoint customers who are looking for what you sell.
