in my wiki site google ocr buttton do not show , how can I solve this problem ? please help . thanks-~~~~
I'm not sure why a Google OCR button would show up. I don't even know what one is. The closest relevant thing that I found was a Google Drive feature but it doesn't look like you're talking about that.
Please see : https://www.mediawiki.org/wiki/Manual:Custom_edit_buttons But I don't konw how Can I add this. Please help
The page that you link to explains how you can add this. If some specific parts are unclear, please explain why so someone else could provide an explanation.
example: Google OCR button . please tell me this code for ocr button . thanks
I'm still confused about what you would want such a button to do. Adding an OCR button seems meaningless.
I want to proofing pdf book
It sounds like you want to hire a developer to implement this for you. I cannot help you to accomplish what you want here on the support desk.
In my site , When I put on OCR button Then show me this error
"<error> undefined Image URL must begin with 'https://upload.wikimedia.org/ " .
Can you tell me how can I solve this error ?
I'm sorry, but it looks like you need more help than I can give you here.
but where I can submit my help request / complain ? I need this help emergency .
The Google OCR button is not part of MediaWiki, so this is the wrong place to complain and ask for help.
I suggest you find someone who knows about the button. If they can't put it into MediaWiki for you, they might be able to help you ask the right questions.
but you know that there have an extension name ProofreadPage . THis is the error of ProofreadPage extension . So , I submit this in here .
Are you sure this is an error in ProofreadPage? Maybe you don't understand it.
Yes , I am Sure .. <error> undefined Image URL must begin with 'https://upload.wikimedia.org/ " .
As long as you do not explain why that is related to ProofreadPage and as long as you just re-post what you have already written without providing any requested information, nobody can help here, sorry. I doubt that ProofreadPage is related at all.
the first case(Extension:PdfExport) gives me the link print as formate PDF, but when i click on, gives me an error that export as format pdf- error, means doesnt find any convertion pdf and explain that i need to install PrinceXML, DomPdf o HTMLDoc. but i install DomPDF and Html doc and PrinceXML and doesnt work
and the second case with Extension:ElectronPdfService
gives me the link print PDF but when i click on , told me that the service doesnt find the page
ElectronPdfService is probably the best way to go forward, but many of these extensions are quite burdensome to set up indeed. You need to also install Electron service and a restbase endpoint..
This is badly documented I admit. The talk page of the extension has a few more people who have attempted to do the same and ran into similar problems. I encourage you to document your experiences.
How to authenticate a user by my own Authentication server?
If your own authentication server is LDAP-based, you might be able to use Extension:LdapAuthentication. There might be extensions for other types of authentication servers too.
I think the most important question is: What do you mean with "own authentication server". What technology is it based on, what API does it provide? Like @Anomie already mentioned, there're already a lot of extensions, which provide authentication methods for MediaWiki, so your server may already be supported :)
Warning and Fatal Error after uploading version 1.28
I've upgraded recently to 1.26 without problems.
Now I felt forced to upgrade again to 1.28.
When I start my wiki I get this message:
Warning: require(/kunden/vexilli.net/webseiten/Hombruch/wiki/includes/services/ServiceContainer.php): failed to open stream: No such file or directory in /kunden/vexilli.net/webseiten/Hombruch/wiki/includes/AutoLoader.php on line 81 Fatal error: require(): Failed opening required '/kunden/vexilli.net/webseiten/Hombruch/wiki/includes/services/ServiceContainer.php' (include_path='/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/pear_exception:/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/console_getopt:/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/pear-core-minimal/src:/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/mail_mime:/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/mail_mime-decode:/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/net_socket:/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/net_smtp:/kunden/vexilli.net/webseiten/Hombruch/wiki/vendor/pear/mail:.:/usr/local/lib/php') in /kunden/vexilli.net/webseiten/Hombruch/wiki/includes/AutoLoader.php on line 81
What should I do now?
Please make sure that you have updated all files of the installation. Also it is important that you extract the new files into a new folder. Any remaining files of the old MediaWiki version may cause errors. More details are at upgrading!
I did it all again and now I see: I'm getting an error message while depackaging mediawiki-1.28.0.tar. It comes while depackaging the file mediawiki-1.28.0\wiki.phtml which says "Can not create symbolic link : Access denied : C:\...my local path...\mediawiki-1.28.0\vendor\pear\net_smtp\README.rst"
And pear is the place where the start-up-time error message refers to.
So what to do about this depackaging?
I don't think this should be a problem.
From what I understand, the MediaWiki package includes a symbolic link "file" which are for Linux operating systems and as such are unsupported on Windows systems. These are like shortcuts and shouldn't be causing any breaking of the software.
"Can not create symbolic link" is what you'll see unless you run the extraction (depackaging) as an adminstrator. It won't cause problems because symlinking a README isn't going to affect the functionality.
Are you still getting the "Failed opening required..." error message?
I tried to go back to 1.26 but I damaged the backup.
Then I tried to go back to 1.23 but there were too many differences.
So I'm still most interested in getting 1.28 working.
Would it be possible to try using a different software package to extract the TAR file? The actual unzipping (really un-tarring) seems to be where the problem is.
Thank you all!
All problems are solved now!
Could you tell us what worked for you so others will know if they run into a similar problem?
I have the same problem and I have used the mediawiki-1.28.0.tar.gz which I unpacked in windows first and then placed on my server. Which file to you Wschroedter get to have it to work?
I think this stupid symlink should be reported as a bug! See bugreport for how you can do that! It is a useless link and is only causing trouble!
I filed phab:T156491. Please comment there saying which TAR extraction software you used when you encountered this problem.
Does anyone have a solution for this? My MediaWiki is still down and I don't know how to solve this after upgrading to 1.28
Warning: require(/volume1/web/MediaWiki/includes/services/ServiceContainer.php): failed to open stream: No such file or directory in /volume1/web/MediaWiki/includes/AutoLoader.php on line 81 Fatal error: require(): Failed opening required '/volume1/web/MediaWiki/includes/services/ServiceContainer.php' (include_path='/volume1/web/MediaWiki/vendor/pear/pear_exception:/volume1/web/MediaWiki/vendor/pear/console_getopt:/volume1/web/MediaWiki/vendor/pear/pear-core-minimal/src:/volume1/web/MediaWiki/vendor/pear/mail_mime:/volume1/web/MediaWiki/vendor/pear/mail_mime-decode:/volume1/web/MediaWiki/vendor/pear/net_socket:/volume1/web/MediaWiki/vendor/pear/net_smtp:/volume1/web/MediaWiki/vendor/pear/mail:.') in /volume1/web/MediaWiki/includes/AutoLoader.php on line 81
Found the problem
Somebody had renamed /includes/services to /includes/Services (note the upper case S ) changing this to lower case made the trick!
How and why does this happen in a release´?
This issue is a serious problem. This breaks mediawiki on any system that is case-sensitive.
> This issue is a serious problem.
Do you mean the renaming of /includes/services to /includes/Services that HKOCH mentioned? Could you explain exactly what you did that caused this folder to be renamed? As far as I can see this folder has always been lowercase.
Re: Somebody had renamed /includes/services to /includes/Services (note the upper case S ) changing this to lower case made the trick!
Exactly the same thing happened to me after relocating files from Windows to a *nix server. Other files had been named, too, such as SpecialUserLogin > SpecialUserlogin (see also: http://stackoverflow.com/questions/38135184/mediawiki-1-27-warning-requiring-specialuserlogin-php). The problem did seem to occur in the process of either zipping/tarring or extracting the files. Not sure if there's a connection with symlinks or PEAR dependencies.
This is probably caused by Windows being case insensitive and people not following the instructions on Manual:Upgrading stating that you shouldn't unpack new files over the old ones!
On Windows, files SpecialUserLogin.php and SpecialUserlogin are the same. If you unzip a new version over the old one, it sees the file already exists and updates the contents without using the new name. It continues to work on windows, until you move those files on a case-sensitive filesystem.
Thanks. Mmm, after unsuccessful attempts to upgrade MW in the manner prescribed (I remember it was something specific to MW 1.28.0), I resorted to a third-party installer to upgrade MW, which somehow worked (locally), but that's precisely where things must have gone wrong. A veritable mess, but everything should be in order now.
Hosting MediaWiki on Google Cloud for use in College Courses
I am setting up MediaWiki to get more students familiarized/comfortable with the ability to edit and contribute to Wikipedia & MetaWiki projects. (This includes both coding, and general editing)
I just set up: <https://bitnami.com/stack/mediawiki> on Google Cloud Platform.
Has anybody here tried Bitnami's Mediawiki, or hosting on GCP? Any recommendations for setting up mediawiki for use in a college setting?
Here is what is included in the Bitnami stack (I think):
- Ghostscript 9.05
- Apache 2.4.25
- ImageMagick 6.7.5
- MediaWiki 1.28.1
- MySQL 5.6.35
- OpenSSL 1.0.2k
- PHP 5.6.30
- phpMyAdmin 4.7.0
- SQLite 126.96.36.199
Moving mediawiki from linux to windows using postgres
We are trying to move our wiki from an old linux box to a windows PC.
We have installed the same version of mediawiki on the windows PC (1.15) and have copied the localsettings.php file across and pointed it to the database on the linux box and we just get a http 500 error.
Also restored the database onto the windows pc and changed to use that but we get the same issue
Not sure where to go from here
You first need to get a descriptive error message instead of a plain 500 error.
See Manual:How to debug. Look at error logs of the webserver, and enable error_reporting in PHP
Does your PHP on Windows have PostGreSQL drivers enabled?
I'd recommend to set
$wgShowSQLErrors = true;
in your LocalSettings.php file to get an useful error message.
General hint when migrating from Linux to Windows: Linux has a case sensitive file system. Windows does not. Make sure you don't loose any files from your "images/" directory (e.g. "Some_Image.jpg" could be overwritten by "Some_image.jpg"). Also MediaWiki on Windows does not allow non-ascii-chars (Umlauts and other special characters) in file names.
i download Pdf Export and i did this instructions:
I tested the following commands :
- Download Dompdf 0.7 from GitHub
- Unzip it in the MediaWiki directory, next to LocalSettings.php, the subdirectory is named "dompdf"
require_once __DIR__ . '/dompdf/autoload.inc.php';in your LocalSettings.php
- Download the patched version of PdfExport from my website (when the change above will be merged, it will be available in the "official" version on )
- Unzip it as usual in extensions/ (if you had a previous extensions/PdfExport move it to another location or delete it)
. But when I click on Print as PDF link it gives me a fatal error:
Warning: require_once(C:\xampp\htdocs\media/extensions/PdfExport/prince.php): failed to open stream: No such file or directory in C:\xampp\htdocs\media\extensions\PdfExport\converters\PrincePdfConverter.php on line 22
Fatal error: require_once(): Failed opening required 'C:\xampp\htdocs\media/extensions/PdfExport/prince.php' (include_path='C:\xampp\htdocs\media\vendor/pear/pear_exception;C:\xampp\htdocs\media\vendor/pear/console_getopt;C:\xampp\htdocs\media\vendor/pear/pear-core-minimal/src;C:\xampp\htdocs\media\vendor/pear/mail_mime;C:\xampp\htdocs\media\vendor/pear/mail_mime-decode;C:\xampp\htdocs\media\vendor/pear/net_socket;C:\xampp\htdocs\media\vendor/pear/net_smtp;C:\xampp\htdocs\media\vendor/pear/mail;C:\xampp\php\PEAR') in C:\xampp\htdocs\media\extensions\PdfExport\converters\PrincePdfConverter.php on line 22
what can i do ?? , thanks
yes, i download both extension , and in the first case print as formate PDF, gives me error that export as format pdf- error, means doesnt find any convertion pdf and told that i need to install PrinceXML, DomPdf o HTMLDoc. but i install DomPDF and Html doc and PrinceXML doesnt work
and the second case with Extension:ElectronPdfService
gives me the link print PDF but when i click on , told me that the service doesnt find the page
Block the display of certain articles
Sorry for my bad english.
But, I create my wiki.
I gave read rights on pages, I would like that these pages do not appear when we make a search on it, is it possible?
It will be necessary that only the group that has the rights can see them.
This does exactly what you want to do. Just replace the second group (user) with whatever group you want to give rights to.
Page display 500 Internal Server Error after loading extension
Incompatibilities with PHP 7.1. Please use PHP 7.0 until the bug is fixed
When I load an extension, the page can not be displayed properly and displayed 500 Internal Server Error. However after loading Renameuser extension, WikiEditor extension and SpamBlacklist extension, page can work properly, these extensions can also be used normally. My wiki version is:
and url(Normal status). Can someone come to help me?
See Manual:How to debug - the error log of your webserver software might have more information why you get an HTTP 500 error.
I tested, my wiki displayed some error logs.
One of among the log showed:"PHP Deprecated: Function mcrypt_create_iv() is deprecated in D:\瀛﹀洯閮藉競\w\includes\libs\CryptRand.php on line 256".
I found "This function was DEPRECATED in PHP 7.1.0" in php manual. Is my php version(7.1.3) too high for the reason?
The deprecation warning shouldn't be a problem in itself, unless those errors are being output on the final page. They are warnings for developers, they should be ignored in production environments. This one is tracked in task T143788.
You may try silencing that warning in php.ini so it doesn't spam your logs, in case it's also the cause of the 500 error by changing the error_reporting line:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_NOTICE
Yes, the deprecation warning should't be worried. But, this warning is already here when the page is normal. More seriously is..When I load Cite extension, the page doesn't display properly, and displayed two kinds error logs:"
PHP Warning: Parameter 1 to Cite::clearState() expected to be a reference, value given in D:\瀛﹀洯閮藉競\w\includes\Hooks.php on line 195" and "
PHP Warning: Parameter 2 to Cite::checkRefsNoReferences() expected to be a reference, value given in D:\瀛﹀洯閮藉競\w\includes\Hooks.php on line 195".
The line 195 is "
$retval = call_user_func_array( $callback, $hook_args );".
Ok, that's probably the interesting error and not the deprecation notice :)
Extension:Cite is already bundled with 1.28.1 tarball, so it should be working properly. Did you modify the Extension:Cite afterwards? be sure you're using the extension that comes from the MediaWiki tarball.
No. I haven't modified any extensions. Mediawiki is also downloaded from the official website(this website).
In fact, there are many problems in mywiki. For example, when I load CiteThisPage extension, the page error and showed
PHP Warning: Parameter 1 to CiteThisPageHooks::onSkinTemplateBuildNavUrlsNav_urlsAfterPermalink() expected to be a reference, value given in D:\瀛﹀洯閮藉競\w\includes\Hooks.php on line 195.
It seems that there is a problem with Hooks.php on line 195.
What version of PHP are you using? I don't see anything wrong with those extensions on my test wiki
As mentioned above, the version of the PHP is 7.1.3 .
Ok, I've found it: task T153505
Those are issues with PHP 7.1. You should use PHP 7.0 for now until that's resolved, or manually fixing it in your installation meanwhile.
P.S. When I load SpamBlacklist extension, pages under "User" and "User talk" namespaces can't be created.
Extension:Babel is known to be incompatible with the web updated, as noted on the documentation page.
Adding classes to links in extensions
I'm trying to write an extension in php that adds certain CSS classes to certain links. I already figured it out how to do it for the mediawiki base, but I don't know how to do that for links that are added by extensions, such as the Flow extension and the Social Profile extension. How do I go about that?