Manual talk:FAQ
Instead,
- see Project:Support desk
- use the mailing list
Further options for contacting appropriate people can be found at Communication.
| Language: | English • Deutsch • español • français • 日本語 • 한국어 • Nederlands • polski • português • русский • ไทย |
|---|
 Archives |
|---|
| Archive of Meta, Archive 2006, Archive 2007, Archive 2008, Archive 2009, Archive 2010. |
Contents
 First page |
 Previous page |
 Next page |
 Last page |
In the FAQ, the methods indicated in How do I hide the main page title won't work with MediaWiki 1.22 per Manual:$wgRestrictDisplayTitle, "Additionally, some inline CSS rules like display: none; which can cause the text to be hidden or unselectable are disallowed." Is there another method? Peculiar Investor (talk) 18:15, 8 December 2013 (UTC)
Try this instead of display: none;:
<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">...</span>
It's the standard method of visually hiding text while leaving it readable by screen readers, etc...
Thank you for this hint. Works perfect! This is the "exended" version:
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}
Is there a specific reason to duplicate the clip: rect(1px 1px 1px 1px); part of the CSS? I found it equally working in ommitting the second lot.
So I've disabled editing on my wiki for anybody that's not a developer. I made a test account and tried everythign out, and I ran into a problem where anybody can move a page and/or rename it. How can I block users from being able to move/rename a page?
Wg stands for "Wikipedia global", before MediaWiki expanded beyond Wikipedia. That should always be asked in order to remember the name of a variable. It should be a FAQ.
That's more of a historical fact. Knowing that isn't really necessary. I could see people equally considering 'wg' as 'Wiki global' and not having any issues without knowing the historical fact.
Fine, lets see it in the FAQ with your answer, short and sweet "A. wg stands for a Global variable on the Wiki system."?
I believe mnemonics are an important learning tool, and that variable naming is necessarily a mnemonic except when it's an abbreviation or initialism like "wg". (The rest of the name of the variable, after the "wg" is already a mnemonic.)
When I click on log in/create account from a normal page I only get a log in option. I notice on this page that log in & create account are separate links, so I'll see if this works.
Section How do I delete an old version of a page? reads
- For newer MediaWikis (1.14+), you can enable the core RevisionDelete feature
(emphasis added). I seem to gather from other statements in the manual that it should probably read 1.16+. Could someone please check this and fix it or add a remark why it is correct?
Thanks, 87.175.36.218 22:44, 1 February 2013 (UTC)
Can you please add that, when adding a logo URL to the LocalSettings.php file, the URL should point to the image itself and not the image description page? That threw me for a few minutes, and I'd like to spare someone else the trouble, or is this obvious?
Please excuse my lapse in case this should be something obvious I'm missing, but for me it just doesn't add up.
Why should anyone want to, even temporarily, let everyone assign rights when the objective is precisely and only to promote one single user, whether he/she is to be rewarded for having earned the merit of being the initial user on a new installation or not?
(This refers to http://www.mediawiki.org/wiki/Manual:FAQ # 1.14.3 Temporarily let everyone assign rights to promote your initial user)
- Isn't it so that giving rights to a user simply involves one activity by someone with sufficient rights to do so?
- Why does the whole userbase have to become active to perform whatever the author of this question had in mind, in order to do something that will be complete as soon as one person has done it?
- provided the case meant were that there's only one user on a new installation and that user has insufficient rights -- which would be a handling error doing the installation in the first place -- to, say, promote him/herself to Admin/Bureaucrat, then, seeing as changing a local variable is just as deep an intervention as changing a database record, why does the question (and the answer) propose doing it this way round while even stating already that this way round is most dangerous to system integrity?
Could somebody please state for me what I'm missing?
If I am seeing it correctly, it might (also) help to more clearly state the real objective (and/or scenario) meant than just say "to promote your initial user".
TIA, --217.81.174.189 15:55, 14 September 2011 (UTC)
Because that's a simple config change which allows to change permissions on wiki, while a direct permission change on the wanted account would require direct database access and modification.
While I also would not recommend to do that on a daily basis, it definitely is helpful in certain edge-cases:
I have ones used this procedure to give myself admin rights again after I had removed all users from the wiki. (Removing all accounts happened on purpose; some were later re-added in some modified way.) However, after that step, I followed exactly this description to give myself admin rights again.
When you upload a file, the edit summary (if given) is automatically added to its page. Is there a way to automatically append a headline to the top of these summaries that says something like "Summary" or "File Summary" rather than doing it manually?
Edit interface message "filedesc" on your wiki to achieve this.
This can be found on MediaWiki:Filedesc on your local wiki, edit that page to modify this interface message.
I edited that page and put "== Summary ==", and then uploaded a test file to see if it worked, but nothing's changed.
Maybe I'm not explaining what I'm trying to do clearly enough.
Can I edit this text: "By editing this page, you agree to irrevocably release your contributions under the CC-BY-SA 3.0 License. If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here. You are also confirming that you wrote this yourself, or copied it from a public domain or similar free resource. See Project:Copyright for full details of the licenses used on this site. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!" ?
Hi there,
I have been experiencing a very strange user creation phenomenon on our wikirating.org website and I hope someone can help me to understand or solve this problem: Yesterday Feb. 1st, 2012, a visitor created an account (Deguest) on wikirating: (User creation log); 00:47 . . Deguest (Talk | contribs | block) New user account
Few minutes later, a new user Fernandosjp has been created by the very same account Deguest: (User creation log); 01:30 . . Deguest (Talk | contribs | block) created new account User:Fernandosjp (interested in the idea!)
I contacted the user Deguest and asked him why he created a second user, and he told me that he never did that. OK, he could be a liar but I am pretty sure that he told me the truth. Especially because the user Fernandosjp entered his real name (a spanish name) and the user Deguest is a french guy. I know this does not mean anything at this stage. Then I could find the user Deguest on the internet from his real name. There is no way that this guy would try to cheat. He has a very high and respected profile.
Would anyone have an explanation for that? Thank you very much in advance Erwan Wikirating
Updated to 1.18 in the browser is not working Ctrl + z. What's the problem?
How can I import a pdf-file to a mediawiki page (inclusive bookmarks)?
Special:Upload on your wiki and install Extension:PdfHandler ? ~ Seb35 09:41, 9 November 2011 (UTC)
PdfHandler only show me the documents. But I need the documents as wiki pages, because we want edit this pages directly in browser.
This is quite difficult, there is no such functionality as it. Perhaps you can look at Extension:Proofread Page (used on Wikisource), but it’s not exactly what you want. This extension can retrieve text layer of DjVu files (and there are tools to convert pdf to djvu), but this is quite complicated.
I would like to install Mediawiki with Extensions (BlueSpice fully feature, ect.). For this, I need a new server.
The number of users (accounts) will be about 300. In addition, we also want save files in our wiki.
Now my question: could you recommend me a server and what are the server-requirements (Hard disk storage capacity,....)?
The number of users is not sufficient to speak about the requirements, it’s mainly the mean number of active users which is important (1 active, 10 active, 100 active?), where "active" could mean "edit once a day". An out-of-the-box MW is not very demanding in ressources for a small wiki (tens of edits daily), typically on my unoptimized laptop pages are loaded in half a second (no other user but me), and you will have to optimize Apache, MySQL and PHP to get good response time. BlueSpice could be more demanding, but I didn’t installed it. If you have hundred or thousands edits daily, you need a more powerful server and look at caching systems (see documentation). For disk storage, you need some hundreds of MB for 10 users for 1 year (I think, experience from a small public wiki using only image files), and is mainly depending of the mean number of active users and your usage of the files (is it an archiving wiki with many files or just for some images/documents sometimes?).
i cant log into a certain page....
Changes made:
- Use example.com see RFC 2602.
- Improved code logic and efficiency.
- Added escaping.
- Changed from 302 to 301 redirect.
- Added L flag.
- Changed wording from "rewrite" to "redirect".
- Mass redirects to root are a 'signal of low technical quality' as far as searchengines are *concerned. Preserved page name in the redirect.
Replacement wording for section:
After hiding all the appropriate links (see above), if you are using the Apache web server, you can disable actions and special pages using the following rewrite rules:
# Lock down the site (disable MediaWiki commands)
RewriteEngine On
#RewriteLog /tmp/rewrite.log
#RewriteLogLevel 9
## See http://www.mediawiki.org/wiki/Manual:Parameters_to_index.php#Actions
RewriteCond %{QUERY_STRING} (^|&)action=(&|$)
RewriteRule (.*) http://www.example.com/$1? [R=301,L]
RewriteCond %{REQUEST_URI} Special:
RewriteCond %{REQUEST_URI} !^/index\.php/Special:Search
RewriteRule (.*) http://www.example.com/$1? [R=301,L]
## Catch a trick...
RewriteCond %{QUERY_STRING} Special:
RewriteRule (.*) http://www.example.com/? [R=301,L]
Above, a request for 'http://www.example.com/wiki/Page_name?action=edit', for example, will be simply redirected to 'http://www.example.com/wiki/Page_name'. Similarly any page in the Special namespace (with the exception of Special:Search) will be redirected to 'http://www.example.com/wiki/Special:Page_name'. Remember, this is only a hack, and isn't intended as a solution for a secure CMS.
First page |
Previous page |
Next page |
Last page |
