Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Skizzerz

  1. Very odd, is your wiki public? If so, please provide a link to it. If not, please provide the following info: What version of MediaWiki are you running? What extensions do you have installed? In either case, check your webserver configs (for example, the conf file as well as .htaccess files for apache) to see if there's any errant redirects or rewrites in there that is causing it to go elsewhere.
  2. Yes, you'll need to follow up with them. If changing skins doesn't fix the thumbnails, however, then that wasn't the issue that we're after.
  3. I see that MediaWiki is encountering some error when attempting to generate the thumbnails, however your server is not configured to report error details (this is usually considered a good thing from a security point of view). To get more information, you will need to enable debug logging and then attach the debug log here. To do that, set the following in LocalSettings.php: $wgDebugLogFile = '/path/to/debug.log'; You will need to modify this path to be a directory that your user account can write to, but is ideally not accessible via the web. Once you enable that, edit one of the
  4. Thanks! Can you link to the particular page where the thumbnail is not appearing?
  5. There are a few possible reasons for this, but without more information (such as a link to your wiki, if it is public), it is difficult to determine what exactly is going on here. This page has some possible issues and resolutions, but it is not comprehensive and also not very comprehensible in some cases. Perhaps the first thing to check is to see if you have $wgUseImageMagick = true; in your LocalSettings.php. If not, add it in.
  6. Block the offending user(s). If your wiki is open for anyone on the internet to register accounts, keep in mind that many vandals are quite persistent and will come back ("evading the block") to bother you again. Look into the guide on combating vandalism. It contains a number of extensions and configuration parameters that can be used to detect and outright prevent some behaviors. Determine a solution suitable for your community. Perhaps you rate-limit new accounts to 1 edit per 5 minutes until they've reached a certain time and/or edit threshold ("autoconfirmed"). Perhaps you run
  7. I'm not sure if this will actually help or not, but try adding the following into your LocalSettings.php: $wgTmpDirectory = '/is/htdocs/user_tmp/wp10565584_JYRT1G91HG'; If that doesn't help, the next step is to enable debug logging for sessions to get greater insight into what's going on behind-the-scenes. See this article for information on how to set that up. To avoid tons of noise in the file, you may want to only enable logging for the session debug log group.
  8. Can you provide some more info? The output you gave makes it seem like MediaWiki thinks the session being sent to it is not valid/expired and therefore spins up a new one. There are a wide variety of causes for this, none of which are particularly obvious or easy to spot. The following information would be very helpful in diagnosing this further: 1. Your phpinfo() for the server. Easiest way to get this is to run php -i > phpinfo.txt from the command line; the information will be stored in a new file named "phpinfo.txt" which you can then upload as an attachment. 2. Any session-re
  9. The page Special:AllPages lists every page on your wiki. You can link to it on your main page via [[Special:AllPages]] or you can include it as a list with {{Special:AllPages}}. If you're looking for anything more complicated than that, you'll likely want to install and use the DynamicPageList extension.
  10. The easiest way to speed up the site is to configure caching. Install the apcu PHP extension (this will require root-level access to your server; if you don't have that then ask your host to do it for you), and then set $wgMainCacheType = CACHE_ACCEL; in your LocalSettings.php. See here for more details on performance tuning, including other methods like opcode caching (this might already be set up, but make sure it's turned on) and database query caching (I recommend using the excellent "mysqltuner" script for this)
  11. That is being created by the CharInsert extension combined with the MediaWiki:Edittools page on your wiki. The link to the extension contains more documentation and examples of how to set it up. More advanced uses (such as what you see on Wikipedia with the "Insert" drop-down) also require the Gadgets extension.
  12. Method 1: Create or edit the page on your wiki MediaWiki:Retrievedfrom while logged into an Administrator account and delete the contents (so it is a completely blank page). That should suppress the message from appearing at all. Method 2: Create or edit the page on your wiki MediaWiki:Common.css while logged into an Administrator account and add the following code to the bottom: /* hide the "Retrieved from" message */ .printfooter { display: none; }
  13. These are called "Page status indicators." You can read more about them here.
  14. Could be a number of things; do you have a link to your wiki that you can share? This would let me poke around with my browser devtools and see if I can uncover anything (perhaps there are permissions issues accessing the files, or its looking in the wrong place, or there's a version mismatch between your MobileFrontend/MinervaNeue version and MediaWiki version, or it could be working just fine now but a bad cache is making it appear to not be the case)
  15. Try putting the wfLoadSkin underneath the wfLoadExtension call; I believe the order is important here and loading the skin first will cause issues.
  16. 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?
  17. 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 Extensi
  18. 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 i
  19. 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]]
  20. 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. [[Templat
  21. Version 2.0.1


    AutoCategoriseUploads Extension for MediaWiki The AutoCategoriseUploads extension allows you to add categories to 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) And more! Requirements MediaWiki 1.31 or later The SimpleXML PHP extension (optional, used to decode XMP metadata if it exists) The zlib PHP extension (optional, used to decode compressed metadata if it exists) Installation Download the file (a f
  22. 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
  23. 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.
  24. 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 Med
  25. 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
  • Create New...

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.