Jump to content

Skizzerz

Administrators
  • Content count

    51
  • Joined

  • Last visited

Community Reputation

16 Good

About Skizzerz

  • Rank
    Member
  • Birthday October 10
  1. AutoCategoriseUploads

    Version 1.0.0

    0 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

  2. 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.
  3. 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.
  4. 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.
  5. 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
  6. 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?
  7. 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.
  8. DeleteUserPages

    Version 1.0.0

    9 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

  9. 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)
  10. 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
  11. Null edit

    You can disable the parser cache sitewide with the following in your LocalSettings.php. I do not recommend this except on small wikis: $wgParserCacheType = CACHE_NONE; There is an extension which supposedly let you disable the cache on a per-page basis. I have not used or tested it, and make no guarantees that they are compatible with modern versions of mediawiki: https://www.mediawiki.org/wiki/Extension:MagicNoCache In addition, other extensions may disable the cache on pages they are used, such as DynamicPageList.
  12. Null edit

    Pages in MediaWiki are cached, meaning that the page is not processed on each page view, but rather only once and then the process page served to users. If you want a truly dynamic page, you can install an extension that disables the parser cache (preferably on a per-page basis), but keep in mind that doing so will slow down page views for such pages and increase server resources.
  13. How can I use Visual Editor Extention?

    Once Parsoid is installed, edit /etc/mediawiki/parsoid/config.yaml and modify the uri string to point to your wiki's api.php endpoint. For example, https://example.com/w/api.php Then, install and configure VisualEditor as a mediawiki extension by following the 2nd link in my above post.
  14. How can I use Visual Editor Extention?

    Installing Visual Editor is a two part process: Installing Parsoid service Installing Visual Editor For some linux distributions, Parsoid is present in package repositories and can be installed from them. See here for details on installing and configuring Parsoid. Once Parsoid is installed, follow the Visual Editor setup instructions for info on how to configure VE to work with Parsoid.
  15. Restored MediaWiki, Not Gone Perfect

    1.16 is ancient. You'll probably want to restore it to a suitably ancient version of Ubuntu as well. My first guess is that the PHP version you have installed is too new; you'll probably want PHP 5.2, as I believe 5.3+ broke compatibility with super old versions of mediawiki. You will be able to verify this for sure by checking your server error logs. A 500 error should hopefully be logged somewhere in /var/log. Perhaps syslog, perhaps an apache error log.
×

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.