Jump to content

Skizzerz

Administrators
  • Content Count

    74
  • Joined

  • Last visited

Community Reputation

18 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. The "wiki ID" is a fancy term for "the name of the database where the wiki lives." So, something in your configuration is not setting the database name and/or database prefix correctly for this wiki. My guess has to do with the fact that it's a double subdomain "en.en" and your mapping of subdomain to database name is not changing that period to something else -- periods are not valid in database names or table prefixes.
  2. Skizzerz

    mw-config blank while trying to upgrade

    Did you get the new MediaWiki files via Git or by downloading the tarball? If you got it via Git, you will need to install and update all of the dependencies yourself. See here for more information. If you used the tarball, it appears that some of the files didn't get extracted properly or were possibly missed. Re-download the tarball and re-extract it to a new, empty folder. Then copy over your LocalSettings, updated versions of extensions, and images to the new folder. It's always recommended when upgrading with a tarball release to extract to a new folder as there may be issues caused by leaving around files from an old release that were removed in a future release. Unless you are already familiar with using Git and feel comfortable with your systems administration skills, I recommend using the tarballs.
  3. Skizzerz

    mw-config blank while trying to upgrade

    A blank page indicates PHP errors. See the how to debug manual for information on displaying the error messages so you can get more information. You may want to insert those error reporting lines at the top of mw-config/index.php instead of in LocalSettings.php.
  4. 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.
  5. Skizzerz

    Image Resize is not working!

    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.
  6. Skizzerz

    Image Resize is not working!

    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 pages that has a thumbnail error and save. This will generate a lot of output to that log file, including the error message for what is going on with the thumbnail. Once you get that log file after the page edit, you can remove that line from LocalSettings.php so that it does not fill up your disk with debug logs. The debug log will also contain some sensitive data which could allow someone to hijack your session, so I recommend taking the following security precautions: Do not log into any accounts while debug logging is active. Make sure you're already logged in beforehand. After turning debug logging back off, log out of your account in order to delete your session data from the wiki.
  7. Skizzerz

    Image Resize is not working!

    Thanks! Can you link to the particular page where the thumbnail is not appearing?
  8. Skizzerz

    Image Resize is not working!

    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.
  9. 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 bots that patrol for bad actors and send out notifications for humans to look at before things get too out of hand. The exact solution is not a one-size-fits-all sort of thing and depends largely on your community and what you want the wiki to achieve. Increase monitoring of RecentChanges so that similar events can be caught more quickly in the future and the offending user blocked before they cause massive damage. Ensure you have scheduled backups of the wiki database, so that in a worst-case scenario type of thing you can roll back to a known-good backup. A large benefit of MediaWiki is that pretty much every action a user can take can be reverted. It's a time-consuming process to revert hundreds of edits manually (bots, extensions, and maintenance scripts can help with this), but it's doable. The amount of attention this requires may be beyond the capabilities of some small wikis, however. Those wikis may find it easier or better to implement measures that block or restrict bad behavior up front (even if it has a chance of affecting legitimate users as well) simply due to the resources needed to quickly patrol everything shortly after it happens are nonexistent. The end solution is largely up to you, however. See the link I gave for some tips on tools you can use that may help.
  10. Skizzerz

    Getting logged out after submitting a page Change

    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.
  11. Skizzerz

    Getting logged out after submitting a page Change

    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-related or cache-related settings in your LocalSettings.php (do not upload your entire LocalSettings.php as it contains private info such as database passwords and secret keys)
  12. 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.
  13. Skizzerz

    Media Wiki connect speed

    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)
  14. 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.
  15. 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; }
×

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.