Jump to content

Skizzerz

Administrators
  • Content count

    56
  • Joined

  • Last visited

Community Reputation

16 Good

1 Follower

About Skizzerz

  • Rank
    Member
  • Birthday October 10

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This indicates a misconfiguration in your email settings in MediaWiki. Can you please post the relevant bits of your LocalSettings.php that relate to email?
  2. Skizzerz

    MediaWiki 1.31 LTS Now Available

    MediaWiki 1.31.0 has now been officially released. This is a Long Term Support (LTS) release, meaning it will receive bugfixes and security updates for a period of 3 years (until June 2021). Below is a highlight of some of the release notes. To view the full release notes, click here. New System Requirements MediaWiki 1.31 now requires PHP 7.0 or higher. HHVM 3.18.5+ is still supported, but any users still on HHVM should look into migrating into PHP 7, as HHVM will no longer be supported in the future as Facebook will be dropping PHP support from the product. More Bundled Extensions The following extensions are now bundled with the MediaWiki download: CodeEditor -- provides a more friendly editing UI when editing CSS and JS pages MultimediaViewer -- opens clicked images in a lightbox instead of leading directly to the image page OATHAuth -- provides 2-factor authentication (2FA) support using apps such as Google Authenticator Replace Text -- provides a special page for admins to perform replacements across multiple pages of the wiki, for both page content and page titles Upgrading When upgrading MediaWiki versions, it is always important to take a backup of both your files as well as your database, as upgrades cannot be "rolled back" once performed. It is recommended to unpack the new files into a new, empty directory and then move over needed files (LocalSettings.php, images, extensions, skins) rather than unpacking the new files directly over the old ones. Unpacking over the old ones could cause files that were removed in 1.31 to remain in your directory tree, which could cause PHP errors down the line or cause security issues as those files will no longer be updated. The database changes in this release could take a while to run on large wikis.
  3. Skizzerz

    HTTPS Help

    You'll possibly need to modify some settings in LocalSettings.php as well. If you have any things in .htaccess, they may also need changes. As a note, when doing custom ports the port goes after the server name and before the path, e.g. https://example.com:82/mediawiki The redirect in your conf is technically unnecessary so long as you hardcode https into $wgServer in MediaWiki itself -- in that case, the wiki will take care of redirecting the user. Once you have everything working, set up HSTS (HTTP Strict-Transport-Security) so that visitors' browsers will automatically use https in the future.
  4. Skizzerz

    Tables & Templates

    Take another read through https://www.mediawiki.org/wiki/Help:Tables For putting multiple columns in a single line, use !! to separate them for header rows and || to separate for normal rows. If you have formatting, match the ! or |. {| class="wikitable" |+ Caption ! scope="col" style="color:red" | Column 1 !! scope="col" style="color: blue" | Column 2 !! scope="col" style="color: green" | Column 3 |- | data-sort-value="R1C1" | [[R1C1]] || data-sort-value="R1C2" | [[R1C2]] || data-sort-value="R1C3" | [[R1C3]] |- | data-sort-value="R2C1" | [[R2C1]] || data-sort-value="R2C2" | [[R2C2]] || data-sort-value="R2C3" | [[R2C3]] |} Produces the following: If that is what you are doing, try doing each column on its own line, or make use of HTML table markup (<table>, <tr>, <th>, and <td>) instead of using wiki markup for tables.
  5. Skizzerz

    Tables & Templates

    In MediaWiki markup, {| indicates the beginning of a new table and |} the end of a table. Your table row template should therefore not include those lines. I'm not entirely sure why you want to turn this into a template (as it is, in my opinion, more complex than just putting the raw table syntax on the page). If you do want to go down this route, you'll need to split things into 3 templates instead of wrapping it all into a single call to {{Table}}: [[Template:Table header]] would contain the table header, along with the parameters to make it sortable, collapsible, etc. [[Template:Table row]] (or just [[Template:Row]] if you want to save typing) would contain the markup to create a single row [[Template:Table footer]] would contain the final closing markup |} for the table and any other footer data you want Perhaps something like the following: Template:Table header {| class="wikitable {{#if:{{{sortable|}}}|sortable}} {{#if:{{{collapsible|}}}|mw-collapsible}} {{#if:{{{collapsed|}}}|mw-collapsed}}" {{#if:{{{center|}}}|style="text-align: center"}} {{#if:{{{caption|}}}| {{!}}+ {{#if:{{{caption-style|}}}|style="{{{caption-style}}}" {{!}} }} {{{caption}}} }} ! scope="col" | {{{1}}} {{optheader|{{{2|}}}}} {{optheader|{{{3|}}}}} {{optheader|{{{4|}}}}} {{optheader|{{{5|}}}}} {{optheader|{{{6|}}}}} Template:Optheader {{#if:{{{1|}}}| !! scope="col" {{!}} {{{1}}} }} Template:Table row |- | data-sort-value="{{{1}}}" | [[{{{1}}}]] {{optrow|{{{2|}}}}} {{optrow|{{{3|}}}}} {{optrow|{{{4|}}}}} {{optrow|{{{5|}}}}} {{optrow|{{{6|}}}}} Template:Optrow {{#if:{{{1|}}}| {{!}}{{!}} data-sort-value="{{{1}}}" {{!}} [[{{{1}}}]] }} Template:Table footer |} Then, you would use it as follows: {{table header |sortable=1 (if you want it to be sortable, otherwise leave this line out) |collapsible=1 (if you want it to be collapsible, otherwise leave this line out) |collapsed=1 (if it's default collapsed, otherwise leave this line out) |caption-style=font-weight: bold; ... (optional, you can leave this line out if no style) |caption=Caption goes here (optional, you can leave this line out if no caption) |First column header (required) |Second column header (optional, you can leave this line out) |Third column header (optional, you can leave this line out) |Fourth column header (optional, you can leave this line out) |Fifth column header (optional, you can leave this line out) |Sixth column header (optional, you can leave this line out) }} {{table row|Row 1 Cell 1|Row 1 Cell 2|Row 1 Cell 3|Row 1 Cell 4|Row 1 Cell 5|Row 1 Cell 6}} {{table row|Row 2 Cell 1|Row 2 Cell 2|Row 2 Cell 3|Row 2 Cell 4|Row 2 Cell 5|Row 2 Cell 6}} ... {{table footer}} First header and first cell are required, 2-6 are optional and are left out if omitted. If you aren't familiar with template syntax, there are a lot of tricks being used here. The #if parser function tests if a value is blank or not. If not blank, it outputs the text. Requires that Extension:ParserFunctions is installed (it is bundled with every mediawiki download) Numbered parameters don't require you to specify the name of them when calling the template; they're taken as positional unnamed parameters. You can still explicitly specify the name though (as 1=Value or 2=Value) -- which is required if the Value contains an = sign. The syntax {{{1|}}} means "If the parameter 1 was passed in, use the value for that. Otherwise use the value after the pipe, which in this case is blank/empty. This plays nicely into trick #1 above. The {{!}} built-in template expands to the pipe character |. Since | has a special meaning inside of templates, {{!}} is used to "escape" the pipe so it doesn't get looked at as part of the template, but rather as part of the resulting table markup. Overall though, this is probably more complicated than just encoding the table markup directly on the pages where you care about it...
  6. Skizzerz

    AutoCategoriseUploads

    Version 1.0.0

    2 downloads

    This extension automatically adds categories to new file uploads based on keyword metadata found in the file. The following metadata types are supported: XMP (many file types, including JPG, PNG, PDF, etc.) ITCP (JPG) ID3 (MP3) Categories are added to new uploads only (that is, uploads where a file description page does not already exist). This lets editors modify the categories without needing to worry about new versions of the file overwriting their changes. Any form of uploading is supported, whether that is via Special:Upload, the UploadWizard extension, uploading files via the API, or maintenance scripts to bulk-upload files. For installation instructions, please see the documentation page on MediaWiki.org. It is recommended that you "Follow" this download so that you can be notified automatically whenever there are updates. For support, please post a new topic on the forums. Free support is provided on a best-effort basis. Commercial support for this extension is available by purchasing a MediaWiki Support Subscription.

    Free

  7. Skizzerz

    Cannot find MediaWiki 1.3.0 RPM

    MediaWiki is not officially distributed via RPM. A number of RPMs have been created as unofficial community efforts, but due to the nature of this they often lag behind official releases. It is not recommended that you install MediaWiki via RPM, and instead download the tarball from the MediaWiki website and install it that way. If you want to create your own RPM, you'll need a fair bit of knowledge both in how RPMs are packaged as well as knowledge of how to install MediaWiki from the command line (CLI) by using the install.php maintenance script. I cannot provide much in the way of guidance in this matter as I don't have any experience in packaging RPMs. A second side-note regarding version numbering: don't treat the dot as a decimal point, but rather as a separator. MediaWiki versioning follows the standard of major.minor.patch. The version 1.3.0 is therefore major version 1, minor version 3, and patch version 0. 1.3.0 is ancient and no longer developed (and would be difficult to obtain). The most recent stable version of MediaWiki is 1.30.0, or major version 1, minor version 30, and patch version 0. 1.30.0 is 27 versions newer than 1.3.0.
  8. Skizzerz

    Common.js problem -- script missing

    Your Common.js page has syntax errors, which is why nothing is running. The Common.js page is for js only, whereas you put HTML into that page.
  9. Skizzerz

    Editing the Index page

    Do not edit any of the .php files that MediaWiki ships with. If you want to edit the content of your wiki pages, make use of the "Edit" tab while logged into your wiki. If you want to implement custom code, write or install an extension. In any case, never edit the core .php files -- doing so will make future upgrades incredibly difficult as any custom modifications to core .php files are completely lost on upgrades and need to be reapplied (unlike extensions, which stick around). Furthermore, the core code changes in structure a lot between versions, and unless you're keeping up with MediaWiki development, your custom hack that works in one version may not work in the next one without significant rewrites.
  10. Skizzerz

    Allow user to Input a variable in an inputbox

    This is unfortunately not possible with just the Inputbox extension. You may be able to make use of the Page Forms extension for this purpose (it's part of Semantic MediaWiki but can be installed standalone if you don't want all of SMW installed). However, I've never actually tried it out myself so I cannot say for certain whether or not it will work. You can grab the extension at https://www.mediawiki.org/wiki/Extension:Page_Forms
  11. Skizzerz

    Sorting navigational templates

    The only use of sortkey I know of is to impact how pages are displayed when viewing a Category page directly. If you have some navigational templates with a "sortkey" parameter, you'll need to link to those templates so we can look at the source and give tips/suggestions. Otherwise, can you please clarify what you are intending to do?
  12. I have enabled uploading templates to share with other wiki users. To get there, click on "Downloads" in the top navigation bar and then "Submit a file" If you have any feedback or suggestions for the template repository, please let me know.
  13. Skizzerz

    DeleteUserPages

    Version 1.0.0

    10 downloads

    This extension lets users delete their own user pages and user talk pages. Two permissions are added (by default not granted to anyone) which control whether or not one can delete their own user page or their own subpages. This extension does not allow users to delete pages that are not their user page or subpages of their user page. The user does not need to be the author of the page to delete it, and can only delete if they would otherwise be allowed to edit that page. For installation instructions, please see the documentation page on MediaWiki.org. For support, please post a new topic on the forums. Free support is provided on a best-effort basis. Commercial support for this extension is available by purchasing a MediaWiki Support Subscription.

    Free

  14. Skizzerz

    enable only some users to translate

    You need to change the user rights assignment for the translate right. At the moment, it seems that either '*' or 'user' (all users or logged in users) are given the translate right, and you should change that to a specific user group, such as making a new Translators group. See here for a sample configuration which adds a new translate group (which you can then assign to users you want to be able to translate via Special:UserRights)
  15. A broken layout like that is usually caused by you either having extra open tags or extra closed tag (like you have a <div> but no corresponding </div>, or you have an extra </div> without the associated <div> earlier on). Doesn't have to be div, could be any block-level tag such as <table> too. If you're copying templates from Wikipedia, you're going to need a handful of settings and extensions installed in order to make them work correctly. Click the links in each point for more info. Ensure that Tidy is enabled: $wgTidyConfig. My recommendation is to use the first example on that page under the Examples heading; it will require that the tidy PHP extension (not MediaWiki extension) is installed on your server. If Tidy is not enabled, broken layouts like the above can happen due to how the wikitext parser operates differently when not using Tidy, even if there is no actual issue with your wikitext. Ensure that you have installed the following MediaWiki extensions: ParserFunctions and Scribunto
×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.