![]() To fix, find the $wgServer value in the LocalSettings. If you set the config setting wgHashedUploadDirectoryfalse then files will have a more straightforward location images/imagefilename.png so that could be worth a try. So you could try FTPing them there, but this seems a bit of a messy solution. Your LocalSettings.php file must be edited to reflect HTTPS for your domain. You can read about how this works in the mediawiki docs about wgHashedUploadDirectory. You may notice that MediaWiki loads incorrectly or shows 'insecure content' warnings in the browser bar after you add an SSL certificate to the domain where MediaWiki is installed. See the following articles for further instructions:įixing MediaWiki after adding an SSL certificate to a domain For example, you can change the following URL example: /w/index.php?title=Main_Page You can shorten the URLs to appear more user friendly. See the following article for further details:Īfter you finish troubleshooting your install, you should disable your debugging settings. By enabling this, you are provided detailed debugging information to help isolate the cause. You can enable debugging by adding lines at the bottom of your LocalSettings.php file. You can disable non-user edits with this feature. User rights You also have control over user rights. However, you can restrict who has the ability to create accounts. Restrict account creation By default, anyone can create an account on your wiki. CAPTCHA Enabling a Captcha on any form helps to reduce spam. The image handler at the URL referenced in the imagesuploadurl must store the image in the application. Images are sent to the Image Uploader via HTTP POST with each post containing a single image. Not all of which is obvious, so it's worthwhile for administrators to read through this too, as you might wish to refer your wiki users to this. Return a JSON object containing the imageâs upload location An example PHP upload handler implementation is available here. MediaWiki Wiki Spam Description of what wiki spam is, and instructions on how any user can help tackle the wiki-spam problem (not just administrators). Blocking MediaWiki spam Combating SPAM Provides steps you can take to combat SPAM on your website. If a page is 'watchlisted' by 100 users who have that user preference enabled, then a change to that page uses up your quota for an hour, if you are on Shared Hosting.Given the SMTP quota, you need to be careful if you enable $wgEnotifWatchlist. Otherwise, the email that users try to send each other through Special:EmailUser on your wiki cannot be delivered. This spoofs the domain so that the sending user's email is in a Reply-To header instead of the From header.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |