Login to your hosting Control panel and click on the “MySQL Databases” tool. Enter a name in the Database name box and click on the Create button. We recommend you use mediawiki. The database name will be automatically prefixed with your hosting username, so you don’t have to worry about this database name being already used. The database name can contain only regular letters, numbers and underscores. The master MySQL user is the same as your hosting account Control Panel username, and it’s password is the same as the Control Panel password and this user has all rights to all databases you create. You can either use that user, or… Read MoreContinue Reading
There are (at least) 4 ways to get the MediaWiki software onto your hosting account. They are: Upload via the hosting Control Panel File Manager Upload via FTP Use SSH and wget (this is for more advanced users) Use SSH and get (also for advanced users) Let’s go through each method in detail: Upload via the hosting Control Panel File Manager or FTP For each of these methods, the start and end are the same, just the middle step differs, and we will explain below. First download the package by visiting the MediaWiki Download page. Download via the first link there, which today is Download MediaWiki 1.31.1 The middle step… Read MoreContinue Reading
Once you have the software in place and the database details ready, you visit the URL of your wiki, in order to start the installation process. So if your wiki is going to be http://CoolWiki.com/ you would enter that URL into your browser. Then the first screen you will see is a welcome screen just telling you that you must setup the wiki and you just click on the blue link to continue: Next screen allows you to choose a language: Next screen is a environment check where MediaWiki checks that your server is capable of running MediaWiki. If all is well, you just click Continue. If there would be… Read MoreContinue Reading
To share the users list in a “farm” setup in DokuWiki, meaning when you have multiple wikis running off of one codebase, you must add this code: $config_cascade[‘plainauth.users’] = array( ‘default’ => ‘/your/path/to/conf/users.auth.php’, ); to inc/preload.php and it must come after this line: include(fullpath(dirname(__FILE__)).’/farm.php’);Continue Reading
MediaWiki by default uses Wikitext (also known as Wiki markup or Wikicode), but there are Alternative parsers available as well. Wikitext is, however, by far the most common and that’s what we are going to talk about today. The most common items you might need are Section headings, italics, bold and links to other pages. We’ll review those first and then discuss some less common items. Most Common Markup Elements Section headings Headers are the “title” of a section of your page. They should be on their own line and surrounded by a number of = signs. The one you shouldn’t use is this
= Main Title =
because that’s meant for the… Read MoreContinue Reading
The letters DNS stand for Domain Name System. This is a world-wide convention that works like the phonebook of the Internet. A phone book tells you where a person or business is located. Using DNS, your web browser can find where a website is located. Every computer on the internet has an IP address. They are “ugly” things like 192.368.21.12 (older style) or even uglier like 2001:0db8:85a3:0000:0000:8a2e:0370:7334 (newer style). Without domain names, we would have to visit websites using their IP address. Luckily, however, those people who run the Internet provide us with DNS so we can use domain names like google.com and civihosting.com instead of numbers. What this has… Read MoreContinue Reading
MediaWiki uses “Wikitext” which is a text-based markup language, not difficult for programmers, but for regular people it can be very confusing. There are thus 4 options for a WYSIWYG editor for MediaWiki: BlueSpice Extension:TinyMCE Extension:VisualEditor Extension:WYSIWYG By far the best is the VisualEditor extension. The main drawback of it is that it requires a third party “Parsoid” server and is quite difficult to setup. At CiviHosting, we take care of this for you however. The advantage of the others is that they do not require a special server nor a special installation procedure. The disadvantage is that they are not as powerful nor as reliable as VisualEditor.Continue Reading
The Lua interpreter is available on all of our servers, and the path to it is: /usr/bin/lua Or via PHP extension. Please note that this extension works with PHP 7 only (PHP 7.1 and PHP 7.2), To enable the Lua extension, you need to add the following line to the account’s php.ini file (or in a local php.ini file): extension=lua.soContinue Reading
If you set a MediaWiki install with VisualEditor installed to be private, it will die on the spot. What I mean is that if you set the wiki to require a logon to even view the content (a completely private wiki) and you have VisualEditor installed, then all pages will return a 500 Server Error. The fix that we found that works most easily is the “Forwarding Cookies to Parsoid” solution here: Linking with Parsoid in private wikis which means in reality to just one line to LocalSettings.php. The comments are also helpful, to clarify the issues involved: // Forward users’ Cookie: headers to Parsoid. Required for private wikis (login… Read MoreContinue Reading
Regarding these errors:
The "X-XSS-Protection" HTTP header is not set to "1; mode=block". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly.
The "X-Content-Type-Options" HTTP header is not set to "nosniff". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly.
The "X-Robots-Tag" HTTP header is not set to "none". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly.
The "X-Download-Options" HTTP header is not set to "noopen". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly.
The "X-Permitted-Cross-Domain-Policies" HTTP header is not set to "none". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly.
Accessing site insecurely via HTTP. You are strongly adviced to set up your server to require HTTPS instead, as described in the security tips.
You may see those on Nextcloud on our servers. Here will we explain why and then how we fix that. Nextcloud sets certain variables in .htaccess and then uses the getenv() PHP function to read those. However getenv() reads the value of a PHP environment variable (http://php.net/manual/en/function.getenv.php). These would be the variables, as listed when executing the phpinfo() function. There is no guarantee that a variable that you set by using SetEnv in an .htaccess file will be available for getenv() as well. Generally those are available, however. We use suEXEC on our servers, and for security reasons it passes only a portion of all environment… Read MoreContinue Reading