Hot answers tagged

12

Unless there's going to be a lot of content switching tiers, I'd recommend separate wikis, as MW was never built for solid access control. Read http://www.mediawiki.org/wiki/Security_issues_with_authorization_extensions first and decide whether it's worth the effort. There's a lot of warnings and exploits that can circumvent the protection methods. If you ...


9

The protocols (http, ftp, gopher, etc) which turn into links when surrounded by square brackets ([]) are defined in the $wgUrlProtocols array in your LocalSettings.php file. Here are the default protocols allowed. $wgUrlProtocols = array( 'http://', 'https://', 'ftp://', 'irc://', 'gopher://', 'telnet://', // Well if we're going to ...


9

One obvious point, or so it seems to me, is if you want something that's very tightly locked down then are you sure you actually want a Wiki. Isn't a large part of the ethos of a wiki that it's as open as possible? Once you've moved far enough away from the original purpose then doesn't it sooner or later become a better idea to try a different tool that has ...


6

Use separate source code and separate databases. That way you can install extensions or custom themes in one of them without impacting others. If you really know that you will never ever have custom extensions/themes in one but not in the other wikis, then 3. seems to be a better choice than 2, but keep in mind the upload folder (there is a setting in ...


6

Why don't you double check the size of the POST request. For example, you can use netcat to listen on 8080. netcat -l -p 8080 Then, redirect your browser to use a proxy on port 8080 just before submitting the form. You should get something like this: POST http://example.com/path/to/my/wiki/index.php HTTP/1.1 Host: example.com Proxy-Connection: ...


6

Probably the easiest way would be to first create a mysqldump of the database while it's pristine: mysqldump -u <username> -p <password|credentials file> mediawiki > media-wiki-pristine.sql ...then script a MySQL database drop: mysql -u <username> -p <password|credentials file> -e "drop database mediawiki;" ...followed by a ...


5

Mediawiki upgrades are a doddle anyway, so I run 2 totally separate instances, including a copy of the plugins directory and a copy (not a symlink) of the LocalSettings.php file. I found years ago that trying to save a few minutes on running 2 upgrades would cost me days of getting it set up right, so I just don't bother anymore :) 2 DBs, 2 code instances. ...


5

You can use the template in any page. Note this excludes the search boxes. {{Special:AllPages}} There is more documentation about namespaces on the MediaWiki site.


5

My first suggestion would be to ensure you are fixing the right problem. Track your memory usage over a reasonable time frame and see how high it goes (and if you can correlate this to something such as increased traffic). If you already have some monitoring in place (e.g. Munin) you should be able to see memory trends Otherwise, use sar (e.g. if you ...


4

Do you care at which layer in the stack the encryption happens? Short of massively modifying the source code to decrypt all DB queries (and that's ignoring the key management aspect), the best bet might be to encrypt the partition that the database lives on. What is the reasoning behind it? There may be a better way.


4

You have to generate the list of tables you want to dump then act upon it. mysql -u USER -p -D test -Bse "show tables like 'wiki_%'" >tables.out mysqldump -u USER -p test <tables.out >wiki_tables.dump or as a one liner mysqldump -u USER -p test $(mysql -u USER -p -D test -Bse "show tables like 'wiki_%'") but you still get to enter the password ...


4

check upload_max_filesize in /etc/php.ini


4

A MediaWiki installation is nothing more than a directory tree and associated database. You can run as many parallel installations as you like. Any part of the file base that needs to be shared can be done so using symlinks. It only gets tricky if you want to share parts of the database and because that tends to be a one way road to disaster you would be ...


4

Hey, We use company-wide wiki. This is how we do it: We use LDAP for storage for username and kerberos for authentication. MediaWiki has extension for using LDAP. We locked down that IP address such that our offices in Canada and US has access to wiki, done on our firewall. Even though the wiki is on external IP address, the firewall only allows access ...


4

You could start by reducing Google and Bing requests... Have you set up a robots.txt? Exclude the ScriptPath from crawling, so that only the canonical page URLs are indexed, but not any URL with parameters to api.php or index.php. Also set a crawl-delay if needed. Many MediaWiki sites are slowed down by search engines due to small configuration errors.


3

It looks like you have the libraries installed in a non standard location. If this is the case, it could be that php simply doesn't know where to look for the libraries it needs. Try setting the LD_LIBRARY_PATH environment variable to that path before launching php, if you're running it from command line. For example in bash: export ...


3

You need to change the collation of the database/tables, by selecting one that equates é with e that is most suitable for your needs, such as utf8_general_ci. You should carefully select one based on your requirements, unfortunately there are a lot to choose from; http://dev.mysql.com/doc/refman//5.5/en/charset-unicode-sets.html MySQL also offers some nice ...


3

The problem lies with the browser not the installation. It appears that the Google Chrome browser has some sort of caching problem. I found that when I cleared the browser cache, the problem went away.


3

Maybe /usr/share/webapps/mediawiki/images/lock_yBgMBwiR is symlink folder, check with ls -l.


3

It turns out that the SQL Server driver only supports PHP 5.4 (there's also a preview for 5.5) and I was using PHP 5.6. Rolling back to PHP 5.4 and enabling the php_pdo_sqlsrv_54_nts.dll and php_sqlsrv_54_nts.dll extensions worked.


3

http://www.makehumancommunity.org/w/api.php?action=query&meta=siteinfo&siprop=namespaces By default, namespace 2N is a subject namespace and namespace 2N+1 is the talk namespace belonging to it.


3

Take a look at your request headers. Cache-Control:no-cache and Cache-Control:max-age=0 Edit: These were not the cause of trouble and can be safely ignored. Varnish documentation stating: Note By default, Varnish does not care about the Cache-Control request header. If you want to let users update the cache via a force refresh you need to do ...


3

Yes, it will work fine. Be sure to keep them in separate paths and use separate databases for them, but otherwise you should see no trouble. Whether there is any reason to do this or why you might want to do it on Windows is another question entirely, but there is no reason it shouldn't work.


3

You need to make it clear what is appropriate and what isn't appropriate for posting if you're going to use something like MediaWiki. That's about all of the security that you're going to get. If your business requirements mean that you need complex ACLs, you need to look at a solution designed for it. SharePoint, Traction, Alfresco and SocialText are all ...


3

I find the extensions BreadCrumbs, FCKeditor and InputBox quite useful.


3

mysqldump and show create table are usually pretty reliable workhorses and shouldn't change encodings on their own. If they use a "binary" character set, chances are that is actually the character set given to the table (not necessarily the columns, though). Can you re-check the current table character set in a database browser? I would try a plain, simple ...


3

Unless that "copy" contains the database files in the mysql-data (.myd) then it probably does not have the data you are looking for. If you do have the .MYD file, then you have the actual MySQL database that the Wiki was run against and you should be able to attach that to another MySQL instance and query the data there.


3

I see AdminSettings.php so this is almost certainly a MediaWiki installation. What you are going to want to do is emulate the old system that this was hosted on, most likely a LAMP setup (Linux, Apache, MySQL, PHP). Essentially, you are going to want to do the following steps (very much simplified): Build new LAMP server Copy data to public_html or ...


3

This should be as simple as just adding a second database to your MySQL (or chosen SQL system) and then resetting your config file to allow you to start the installation from scratch. cd /var/www/mediawiki cp LocalSettings.php LocalSettings.php.old nano LocalSettings.php Place in the new details and then kickstart your install.


3

We're using the SphinxSearch extension and it is much better than the default Mediawiki search. The extension installs directly in the Mediawiki server. SphinxSearch is only "supported" on Mediawiki 1.9+, but you may be able to shoe-horn it for testing purposes. Aside: I would recommend you look into upgrading your Mediawiki install as well as Apache, PHP ...



Only top voted, non community-wiki answers of a minimum length are eligible