Jump to content

Skizzerz

Administrators
  • Posts

    174
  • Joined

  • Last visited

Everything posted by Skizzerz

  1. Not in any one particular location, it will involve a fair amount of searching most likely depending on the specific nature of the things you wish to do. The apache site at least is a good start insofar as it documentions how to do things. For TLS, there is a thing on the mozilla website that can generate solid and secure configurations for you for "modern" or "intermediate" browser compatibility. As far as MediaWiki is concerned, the only thing it needs is for the server to run PHP for .php files, and maybe some rewrites for a prettier URL appearance. Everything else is up to you if you'd like to add enhancements.
  2. It would likely be best to start over with a fresh apache configuration file for your wiki and then re-apply configuration changes according to current best practice, rather than taking the existing file and attempting to tweak everything to upgrade it.
  3. Unfortunately the only way to do this is to rename the page to be the desired title (you can leave Rule001, etc. as redirects to the final page to maintain existing links)
  4. Use the {{formatnum}} parser function, for example in your template code ${{formatnum:{{{numvariable}}}}}
  5. No on-wiki content is part of any repositories or docker images. You'll need to export them from the source wiki in question and import them into your wiki.
  6. You are likely missing the text of those templates (and all nested dependencies) from your input file/wiki. You may be missing some extensions as well, but that's something you'll just need to find out as you go along.
  7. Try adding $wgSessionCacheType = CACHE_DB; to your LocalSettings.php and see if that helps.
  8. There are no security issues here, and this is not an attack. Special:ListFiles is a special page on the wiki that lists all uploaded images, and from there you can obtain the full path to the image thumbnail. This could either be some sort of crawler bot, or a person interested in the images on your site. They could be on a dynamic IP, which explains the lack of previous hits, or they could have known somehow that your site is a MediaWiki instance and therefore that Special:ListFiles exists (as it exists on every MediaWiki installation). Regardless, nothing to worry about.
  9. You'll likely need to rebuild all of the elasticsearch indexes, so following the install/upgrade guide from the beginning should be helpful with that. That error indicates that communication can't be established between the wiki and the ES server, so I'd check firewall, etc. for that
  10. Blank page indicates a PHP error. See Manual:How to debug - MediaWiki for more information on how to either log or display PHP errors (displaying errors isn't recommended for production environments) so you can obtain more details.
  11. Correct, you will need to use the command line (accessible via SSH on linux servers) in order to run maintenance scripts. Any good host has the ability to connect via SSH, so look into how to do that wherever you are having your wiki hosted.
  12. Version 1.0.0

    1 download

    Embed interactive visualizations from OurWorldInData into your wiki pages. Requirements MediaWiki 1.37 or later Installation Download the file (a free account is required) and extract the file to your extensions directory. We recommend that you "follow" the download so that you are notified of new updates via email when they are released. To install the extension, add the following to your LocalSettings.php file: wfLoadExtension( 'OurWorldInData' ); Configuration This extension does not require any configuration. See Usage below for usage instructions. Usage This extension adds a new parser tag, <ourworldindata>. Place the chart name or OurWorldInData URL inside of the tag. Additional parameters can be used to adjust how the chart is displayed. == Simple Usage == Copy/paste the share link into the page <ourworldindata>https://ourworldindata.org/grapher/historic-and-un-pop-projections-by-age</ourworldindata> The share link may include parameters to filter the chart <ourworldindata>https://ourworldindata.org/grapher/historic-and-un-pop-projections-by-age?time=1950..2020</ourworldindata> == Advanced Usage == Specify a chart name directly <ourworldindata>historic-and-un-pop-projections-by-age</ourworldindata> Filter parameters can be added to the tag <ourworldindata time="1950..2020">historic-and-un-pop-projections-by-age</ourworldindata> Support Free community support is available on the mwusers.org forums. Paid support plans are available as well.
    Free
  13. Manually creating a user via SQL is not recommend. If you need to create a user in the backend, use the createAndPromote.php maintenance script.
  14. Can you provide the full error message? It should tell you why it's unable to delete that directory. If it's a permissions issue, you'll need to ensure that composer is running under the correct account name. Your host should be able to assist you with determining that.
  15. This can be achieved via the preloading feature, see https://www.mediawiki.org/wiki/Manual:Creating_pages_with_preloaded_text That link also has some extensions that can automatically insert the preload text when trying to create a new page.
  16. It should be safe to ignore those errors. If you are not planning on developing MediaWiki, it would be best to suppress those by turning error_reporting off in your php.ini
  17. Yes, you need a valid working email setup for most email providers to not outright reject emails from you. This is largely outside the scope of wiki management and in the scope of general server management. Set up SPF records in your DNS to let providers know which servers are authorized to send email from your domain Ensure your IP address is not listed in any DNS blacklists, and if it is, go through the processes of those lists to get it delisted Set up MX records in your DNS so that you can receive bounce emails which contain further details of rejections In MediaWiki, configure the outgoing email address appropriately With all of those set up, check system logs to ensure that the mails are being accepted and sent onwards. If they are, checking for bounce replies is helpful to see why something is rejected. Otherwise check firewalls and other things that may block connectivity. If you are attempting to send email from a home server, it is possible your ISP is implementing blocking of their own and you may need a completely different setup (such as connecting to a remote SMTP server to send email).
  18. This is a browser security feature; most browsers do not allow clicking on file links from an http/https website. There is no solution to make it work, upload the relevant file locally to your wiki and link to it using regular wikilinks.
  19. This forum is not for Wikipedia support, so we can't provide much help to you here. The easiest thing to do would be to try resetting your password while on a different IP (for example, if you got that message on your home wifi, try a cellular connection). Failing that, your best bet is to reach out to the Wikipedia admins for assistance; the block message should contain some instructions on how to do that.
  20. By default the extension will omit the tracking code if your browser sends a "Do Not Track" signal to the website. I am guessing this is what is happening for you, as some more privacy-focused browsers send this signal by default, and most other browsers can be configured to send that signal in their privacy settings. The extension page on mediawiki.org goes into more detail on how to configure this behavior, as well as a means of exempting user groups from being tracked.
  21. If you still have access to your old database server (the server itself, not just backup files): Export it as a .sql file using the mysqldump program via the command line Copy the .sql file generated to the new computer Import the .sql file using the mysql program via the command line If you no longer have access to the old database server, you are potentially out of luck if your existing .sql file did not import successfully.
  22. The location of your real files should not match the virtual directory you set up for short URLs. Good: Files in /w, e.g. https://example.com/w/index.php Article path in /wiki, e.g. https://example.com/wiki/Main_Page Bad: Files and article path in the same location (e.g. both in /wiki) Files and/or article path in website root You are in one of the "bad" cases which is why those rewrite rules are not working for you. Extra care is required when doing one of the configurations listed above as "bad", and even with a correct configuration certain article names matching file or directory names will become impossible to create on your wiki.
  23. If it's big and may cause timeouts on the web, use the importDump.php maintenance script from the command line. This involves first uploading the xml file onto the server somewhere, and then running the script on the file. It will still take a long time, but will not time out because maintenance scripts do not have time limits on execution.
×
×
  • 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.