Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Aaushi is a medical application of 30 years development that I use in my clinical practice as an internist and geriatrician. For the past 8 years, Aaushi has been published weekly on the web at www.anvita.info/wiki developed as a MediaWiki application. This site is no longer functional. Colleagues have been asking me when I will get the website back up. Four tab delimited text files (compressed) were uploaded weekly to a server that hosted a MediWiki application. I have since left the company that hosted the server, but have retained the copyright for the underlying software as a condition of my employment. I do not have the code that generates the MediaWiki site, nor do I have any experience setting up a server or website. What I do have are four tab delimited text files with pseudo html markup wrapping items for highlight/hyperlink. The files are generated weekly and contain all necessary information to generate ~92,000 pages. The website will be free without registration or log on. Editing of pages will not be permitted since new files are uploaded weekly, and there is no need for back up other than the core generic code needed to receive the files and execute the application. This offer is for an initial contract of $10,000 with additional payments contingent upon the initial work.
  3. Thanks. EDIT : Problem solved ! I guess the culprit was the cache memory of mediawiki ! Now, I can see it on my iPad, but not on my iMac. It may be a problem of cache memory.
  4. Hello, The search box is not showing up in the sidebar for anonymous users. When I'm logged as admin, it appears. How strange ! Any clue to fix this issue ? My wiki is here : www.france-japon.net/wiki/
  5. Earlier
  6. You can always include a comment in the wiki markup. Comments are not shown on the page itself, but are visible when editing. Comments begin with <!-- and end with --> Example: <!-- This is a comment that will be displayed while editing, but not visible in the page itself. You can use this to leave notes for editors. --> If you see typos by a different user on a talk page, it's usually poor etiquette to modify someone else's comments. A talk page is used for discussion about a page, and are generally held to different standards compared to mainspace pages.
  7. I was just browsing the "Talk:Talk pages consultation 2019/Phase 1 report" page (https://www.mediawiki.org/wiki/Talk:Talk_pages_consultation_2019/Phase_1_report) and spotted more than a few spelling and/or grammatical errors in "Once upon a time…"'s first paragraph. More than you'd expect a reasonably literate American user to commit. I thought that either this was an unusually careless typist or maybe a non-American who was not well practiced in the language yet. I was going to fix the errors but it then occurred to me that maybe this was meant to serve as an example of poor language skills and any errors found in this paragraph should NOT be fixed. I then got momentarily sidetracked by something else, returning to my computer a couple of hours later. Much to my surprise I found most of the errors already corrected, with only four still existing. I checked the version history and verified that the article was edited by someone a couple of hours earlier. But then I thought, "Suppose the Wikipedia administrators want to include a piece of text in an article that should stand "as is" and not allow editing by users? How would they prevent editing of the error-filled paragraph? Is there already a function for this? If not, I really should try to contact them to let them know about this omission. But how? I see no contact info anywhere that would let me drop a note to an admin." So I'm trying to do that this way. BTW, my name is not listed in the 'Please find your name in this report' section, nor would I expect it to be. I'm not working for Wikipedia or any of its offshoots. My Wikipedia username is Moodie-1. If, by chance, you're not a Wikipedia admin then please redirect this note to one, if possible.
  8. You can assign users to be admins. See here: https://www.mediawiki.org/wiki/Help:User_rights_and_groups For more details about user rights, see here: https://www.mediawiki.org/wiki/Manual:User_rights
  9. Hello, I started using a new mediawiki. I want to create several admins. How can I do it ? Thanks for helping me.
  10. Dan

    Fatal error

    I have a password-protected site. During the upgrade-process to MW 1.32 I discovered problems. I did not get much help from my web hotel though. Any suggestions about how to proceed. The current error is: [0404447970557a9cb2742385] 2019-05-18 15:59:51: Fatal exception of type Wikimedia\Rdbms\DBQueryError Fatal error: Uncaught Wikimedia\Rdbms\DBTransactionError: Wikimedia\Rdbms\LBFactory::shutdown: Commit failed on server(s) 25.mysql.servage.net: Cannot execute query from Wikimedia\Rdbms\LBFactory::shutdown while transaction status is ERROR. in /storage/content/45/1007945/journalen.org/public_html/includes/libs/rdbms/loadbalancer/LoadBalancer.php:1426 Stack trace: #0 /storage/content/45/1007945/journalen.org/public_html/includes/libs/rdbms/lbfactory/LBFactory.php(219): Wikimedia\Rdbms\LoadBalancer->commitMasterChanges('Wikimedia\\Rdbms...') #1 /storage/content/45/1007945/journalen.org/public_html/includes/libs/rdbms/lbfactory/LBFactorySimple.php(152): Wikimedia\Rdbms\LBFactory->Wikimedia\Rdbms\{closure}(Object(Wikimedia\Rdbms\LoadBalancer), 'commitMasterCha...', Array) #2 /storage/content/45/1007945/journalen.org/public_html/includes/libs/rdbms/lbfactory/LBFactory.php(221): Wikimedia\Rdbms\LBFactorySimple->forEachLB(Object(Closure), Array) #3 /storage/content/45/1007945/journalen.org/public_html/includes/libs/rdbms/lbfacto in /storage/content/45/1007945/journalen.org/public_html/includes/libs/rdbms/loadbalancer/LoadBalancer.php on line 1426 Regards Dan
  11. This error's reason is apache2's config is wrong.
  12. Hello. MediaWiki, I have runs the Wikipedia work to revise a document. 'copyright : mediawiki' into an error, as follows. My wiki site's URL is https://www.gaonwiki.com/w/ If the word Copyright is in it, there is no doubt that there will be an error. Other words do not produce errors. My server specifications are as follows. Ubuntu 18.04 Apache2.4.29 PHP 7.2 Mysql 5.7.26 Thank you for listening my errors.
  13. A blank white page indicates a PHP error, see the How to debug page on mediawiki.org for more information on obtaining the actual error messages. Once you know the error message, if you are having troubles figuring out what it means, post back here and we can help you out. I notice that you are attempting to load the extension twice in your LocalSettings.php; you have both a require_once for the WikiEditor files as well as wfLoadExtension. You should use either wfLoadExtension or require_once, but never both. Moving forwards, extensions should be loaded via wfLoadExtension, as the require_once method is now deprecated in recent versions of MediaWiki and support for it is being removed. Finally, your MediaWiki version (1.27) is going to be end of life next month. You should begin plans to migrate to a more recent version if you wish to continue receiving security updates and improvements.
  14. But, that line is need added on from the guideline. https://www.mediawiki.org/wiki/Extension:WikiEditor
  15. Remove the line wfLoadExtension( 'WikiEditor' ); and see if that helps.
  16. Hi Robinson, 1. unpack : /mediawiki-1.27.2/extensions/ 2. I also delete some key . Thanks ! <?php # This file was automatically generated by the MediaWiki 1.24.2 # installer. If you make manual changes, please keep track in case you # need to recreate them later. # # See includes/DefaultSettings.php for all configurable settings # and their default values, but don't forget to make changes in _this_ # file, not there. # # Further documentation for configuration settings may be found at: # https://www.mediawiki.org/wiki/Manual:Configuration_settings # Protect against web entry if ( !defined( 'MEDIAWIKI' ) ) { exit; } ## Uncomment this to disable output compression # $wgDisableOutputCompression = true; $wgSitename = "HW-WiKi-I"; ## The URL base path to the directory containing the wiki; ## defaults for all runtime URL paths are based off of this. ## For more information on customizing the URLs ## (like /w/index.php/Page_title to /wiki/Page_title) please see: ## https://www.mediawiki.org/wiki/Manual:Short_URL $wgScriptPath = "/mediawiki"; $wgScriptExtension = ".php"; ## The protocol and server name to use in fully-qualified URLs $wgServer = "http://192.168.1.52"; ## The relative URL path to the skins directory $wgStylePath = "$wgScriptPath/skins"; ## The relative URL path to the logo. Make sure you change this from the default, ## or else you'll overwrite your logo when you upgrade! $wgLogo = "$wgScriptPath/resources/assets/wiki.png"; ## UPO means: this is also a user preference option $wgEnableEmail = true; $wgEnableUserEmail = true; # UPO $wgEmergencyContact = "apache@192.168.1.52"; $wgPasswordSender = "apache@192.168.1.52"; $wgEnotifUserTalk = false; # UPO $wgEnotifWatchlist = false; # UPO $wgEmailAuthentication = true; ## Database settings $wgDBtype = "mysql"; $wgDBserver = "localhost"; $wgDBname = "mediawikidb"; $wgDBuser = "root"; $wgDBpassword = "xxxxxxxxxxxxxxxxxxxx"; # MySQL specific settings $wgDBprefix = ""; # MySQL table options to use during installation or update $wgDBTableOptions = "ENGINE=InnoDB, DEFAULT CHARSET=binary"; # Experimental charset support for MySQL 5.0. $wgDBmysql5 = true; ## Shared memory settings $wgMainCacheType = CACHE_NONE; $wgMemCachedServers = array(); ## To enable image uploads, make sure the 'images' directory ## is writable, then set this to true: $wgEnableUploads = false; $wgUseImageMagick = true; $wgImageMagickConvertCommand = "/usr/bin/convert"; # InstantCommons allows wiki to use images from http://commons.wikimedia.org $wgUseInstantCommons = false; ## If you use ImageMagick (or any other shell command) on a ## Linux server, this will need to be set to the name of an ## available UTF-8 locale $wgShellLocale = "en_US.utf8"; ## If you want to use image uploads under safe mode, ## create the directories images/archive, images/thumb and ## images/temp, and make them all writable. Then uncomment ## this, if it's not already uncommented: #$wgHashedUploadDirectory = false; ## Set $wgCacheDirectory to a writable directory on the web server ## to make your wiki go slightly faster. The directory should not ## be publically accessible from the web. #$wgCacheDirectory = "$IP/cache"; # Site language code, should be one of the list in ./languages/Names.php $wgLanguageCode = "zh-tw"; $wgSecretKey = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"; # Site upgrade key. Must be set to a string (default provided) to turn on the # web installer while LocalSettings.php is in place $wgUpgradeKey = "xxxxxxxxxxxxxx"; ## For attaching licensing metadata to pages, and displaying an ## appropriate copyright notice / icon. GNU Free Documentation ## License and Creative Commons licenses are supported so far. $wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright $wgRightsUrl = ""; $wgRightsText = ""; $wgRightsIcon = ""; # Path to the GNU diff3 utility. Used for conflict resolution. $wgDiff3 = "/usr/bin/diff3"; ## Default skin: you can change the default skin. Use the internal symbolic ## names, ie 'vector', 'monobook': $wgDefaultSkin = "cologneblue"; # Enabled skins. # The following skins were automatically enabled: require_once "$IP/skins/CologneBlue/CologneBlue.php"; require_once "$IP/skins/Modern/Modern.php"; require_once "$IP/skins/MonoBook/MonoBook.php"; require_once "$IP/skins/Vector/Vector.php"; # Enabled Extensions. Most extensions are enabled by including the base extension file here # but check specific extension documentation for more details # The following extensions were automatically enabled: # The following extensions were automatically enabled: require_once "$IP/extensions/Cite/Cite.php"; require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php"; require_once "$IP/extensions/Gadgets/Gadgets.php"; require_once "$IP/extensions/ImageMap/ImageMap.php"; require_once "$IP/extensions/InputBox/InputBox.php"; require_once "$IP/extensions/Interwiki/Interwiki.php"; require_once "$IP/extensions/LocalisationUpdate/LocalisationUpdate.php"; require_once "$IP/extensions/Nuke/Nuke.php"; require_once "$IP/extensions/ParserFunctions/ParserFunctions.php"; require_once "$IP/extensions/PdfHandler/PdfHandler.php"; require_once "$IP/extensions/Poem/Poem.php"; require_once "$IP/extensions/Renameuser/Renameuser.php"; require_once "$IP/extensions/SpamBlacklist/SpamBlacklist.php"; require_once "$IP/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php"; require_once "$IP/extensions/TitleBlacklist/TitleBlacklist.php"; require_once "$IP/extensions/WikiEditor/WikiEditor.php"; wfLoadExtension( 'WikiEditor' ); # End of automatically generated settings. # Add more configuration options below.
  17. Where did you unpack the WikiEditor files to? Can you show us your full LocalSettings.php file? Just delete the password first.
  18. Hi Everyone, I am a new guy try to install mediawiki. and want to install - wysiwyg editor (Wiki Editor) but fail. I follow the commad as link - Add the following code at the bottom of your LocalSettings.php: wfLoadExtension( 'WikiEditor' ); But after that , I can't access the mediawiki. and show the page does not exist. If I delete the "wfLoadExtension...." , mediawiki works again. mediawiki verson:1.27 PHP 7.0.33 and I sure select the right version for WikiEditor. 2019/05/07 update the error screen as below Thanks!
  19. MediaWiki 1.32.1 has been officially released. Below are a highlight of changes made in this patch release. Changes Fixed an issue in the API list=users which mistakenly reported users as missing Removed hard-coded Google site search from database error screens In addition, other bugs related to backend databases were fixed. Upgrading To upgrade from 1.32.0 to 1.32.1, unpack the new files in-place over the old ones. You do not need to run the database upgrade script (update.php) to upgrade from 1.32.0 to 1.32.1. As always, we recommend making a backup of your files before upgrading.
  20. Version 1.2.0

    1 download

    This extension uses the MediaWiki API and AuthManager framework to direct login requests with no local account to a remote wiki. The account and its preferences are imported, so the remote login only has be done once. This extension is useful for moving a community from another wiki when you do not have access to the user account database. From a user perspective, it's like they already had an account on the local wiki. For more details, see the documentation page on mediawiki.org. We recommend that you "Follow" this file after downloading by clicking the Follow button above the Download button. This will allow you to be notified when new versions are published.

    Free

  21. I want to create a similar wiki page as -https://en.wikipedia.org/wiki/Portal:Geography with my own contents in my wiki site(vanipedia.org). Can someone please help, what templates, codes and portals I need to create a similar page. Please help
  22. Thank you for your answers. It needs a function of bulletin board (text + comments) rather than a format of a forum. Although we tried the format of the forum, the format of the bulletin board was more effective than the format of the forum.
  23. The WikiForum extension seems like it does most of what the extension you linked did.
  24. You can certainly try. It should work, but there is of course no guarantee, Just make sure that you have a full backup of all files and your database. If it fails, let us know and we can try to help.
  25. Hi folks, I had a media wiki set up for me a while back and have been merrily using it ever since. I'd like to load some extensions on it, but have never upgraded it since the initial install. It looks like I am on version 1.15.1; can I safely upgrade directly to the latest version, or do I need to go through some interim versions first? Thanks!
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • 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.