Topic on Project:Support desk

I was using the Geshi extension o 1.9.3 with content like

<code xml>

...

    <customcerts

dir="certs"

    />

...

</code>

Now the Geshi extension is gone and I could use Extension:SyntaxHighlight. However, I have hundreds of pages using the <code ''lang''> tag instead of <syntaxhighlight lang="''lang''">. Is there a solution to that apart from manually editing all of them?

Thanks and Regards, Christoph

You can try making use of Extension:Replace Text.

Thanks for pointing me to Replace Text, @AhmadF.Cheema!

However, I do not get the extension to work on a Windows system:

syntaxhighlight uses Pygmentize directly (such as 'C:\...\SyntaxHighlight_GeSHi\includes/../pygments/pygmentize" "-l" "xml" "-f" "html" "-O" "cssclass"').

pygmentize is a script starting with "#!/usr/bin/env python3" which is going to work on *nix'ish systems fine but won't work on Windows. So I get an expection "PHP Notice: Failed to invoke Pygments" when the extensions tries to render a page.

I installed python 3.8 on the box which seems to run fine (at least, I can get a python prompt with now errors).

So as far as I am concerned, this won't ever work on Windows, does it?

Some googling yields a page saying you need to install ez_install.py and run it. I did so (downloading it from pypi.org) and it bails out saying "SSL required". So I edited it and changed the download URL from http to https.

Now it bails out saying "in self.chown(tarinfo, dirpath) TypeError: chown() missing 1 required positional argument: 'numeric_owner'".

It is frustrating :-|

Am I on the right track with getting ez_install to run?

Or is there a way to tell mediawiki to just call upon python.exe directly?

This SO answer seems to have a hint.

@MarkAHershberger you made my day - almost!

here it is in a nutshell:

      [ install python 3.8 ]

python -m ensurepip --default-pip

      python -m pip install --upgrade pip setuptools wheel

      easy_install Pygments

now there is a Windows pygmentize.exe in .../python/Scripts

set "$wgPygmentizePath = "C:/.../python/Scripts/pygmentize.exe"; in LocalSettings.php

I can run pygmentize from the shell.

But: although $wgPygmentizePath is set correctly, I keep getting

PHP Notice: fwrite(): write of 1597 bytes failed with errno=22 Invalid argument in C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\shell\Command.php on line 475

Apparently, proc_open in Command.php cannot start the executable.

Has anyone got SyntaxHighlight_GeSHi to work on a Windows/IIS system? (IIS 8.5, latest PHP 7) ?

You seem to have stumbled upon a windows-only bug. Can you get a stacktrace of the error? Try the following:

• $wgShowExceptionDetails Enable more details (like a stack trace) to be shown on the "Fatal error" page.
• $wgShowDebug Adds the "log messages" part of wgDebugToolbar as a raw list to the page.

@MarkAHershberger

Here is the trace:

PHP Notice:  fwrite(): write of 53 bytes failed with errno=22 Invalid argument in C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\shell\Command.php on line 474

PHP Stack trace:

PHP  17. PPFrame_Hash->expand() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\parser\Parser.php:3330

PHP  18. Parser->extensionSubstitution() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\parser\PPFrame_Hash.php:328

PHP  19. SyntaxHighlight::parserHook() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\parser\Parser.php:4293

PHP  20. SyntaxHighlight::highlight() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php:117

PHP  21. WANObjectCache->getWithSetCallback() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php:348

PHP  22. WANObjectCache->fetchOrRegenerate() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\libs\objectcache\wancache\WANObjectCache.php:1278

PHP  23. SyntaxHighlight::{closure:C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php:306-348}() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\libs\objectcache\wancache\WANObjectCache.php:1424

PHP  24. MediaWiki\Shell\Command->execute() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php:320

PHP  25. fwrite() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\shell\Command.php:474

PHP Notice:  Failed to invoke Pygments: Der Befehl "C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\python38\Scripts\pygmentize.exe" "-l" "xml" "-f" "html" "-O" "cssclass" ist entweder falsch geschrieben oder

konnte nicht gefunden werden.

[Called from SyntaxHighlight::highlight in C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php at line 353] in C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\debug\MWDebug.php on line 333

PHP  19. SyntaxHighlight::parserHook() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\parser\Parser.php:4293

PHP  20. SyntaxHighlight::highlight() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php:117

PHP  21. wfWarn() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php:353

PHP  22. MWDebug::warning() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\GlobalFunctions.php:1066

PHP  23. MWDebug::sendMessage() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\debug\MWDebug.php:188

PHP  24. trigger_error() C:\inetpub\wwwroot\wiki\mediawiki-1.34.0\includes\debug\MWDebug.php:334

[ I needed to shorten the trace cause mediwaiki was complaining about "Flow spam filter: large amount of consonant/vowel clusters" ]

I saw a note in PHP's doc for popen:

Example #2 proc_open() quirk on Windows

While one may expect the following program to search the file filename.txt for the text search and to print the results, it behaves rather differently.

<?php
$descriptorspec = [STDIN, STDOUT, STDOUT];
$cmd = '"findstr" "search" "filename.txt"';
$proc = proc_open($cmd, $descriptorspec, $pipes);
proc_close($proc);
?>

The above example will output:

'findstr" "search" "filename.txt' is not recognized as an internal or external command,
operable program or batch file.

To work around that behavior, it is usually sufficient to enclose the cmd in additional quotes:

$cmd = '""findstr" "search" "filename.txt""';

But I don't think its true. The symptom is exactly what I saw, however the solution doesn't work.

I finally got tired of this and sort of "fixed" it by changing the code in mediawiki-1.34.0\extensions\SyntaxHighlight_GeSHi\includes\SyntaxHighlight.php from

311 				$result = Shell::command(
312 					self::getPygmentizePath(),
313 					'-l', $lexer,
314 					'-f', 'html',
315 					'-O', implode( ',', $optionPairs )
316 				)
317 					->input( $code )
318 					->restrict( Shell::RESTRICT_DEFAULT | Shell::NO_NETWORK )
319 					->execute();
320 
321 				if ( $result->getExitCode() != 0 ) {
322 					$ttl = WANObjectCache::TTL_UNCACHEABLE;
323 					$error = $result->getStderr();
324 					return null;
325 				}
326                                 
327 				return $result->getStdout();

to:

                                $cmd = '"' . self::getPygmentizePath() . '" ' . 
				                    	'-l ' . '"' . $lexer . '" ' .
			                       		'-f ' . 'html ' . 
		                    			'-O ' . implode( ',', $optionPairs );
                                $filebase = @tempnam(wfTempDir(), "geshi");
                                $ioi = "$filebase-i.txt";
                                file_put_contents($ioi, $code);
                                $pyg = shell_exec("$cmd < \"$ioi\"");
                                if (false) {
                                    // debug, keep in/out put
                                    $ioo = "$filebase-o.txt";
                                    file_put_contents($ioo, $pyg);
                                } else {
                                    unlink($ioi);
                                }
                                return $pyg;

This is of course ugly to say the least but it works somehow and should be fine until a fix is there.

Let me add that I felt the Shell:: code to be overly complicated. However, I was perhaps just not fair cause it refused to work for me for so long ;-)

Many thanks! that worked for me. Greetings

This fix also worked for me on Windows. Thank you!

How can we get this issue logged and fixed in the production code?

I was just working on something similar, but now just made a copy&paste of your code and it works fine for me too, thanks.

PS: I too was overwhelmed by the complexity of Shell::code

It looks like this might be task T193613. Four months later, I don't know why I wrote this. It must be a typo.

I have the same problem too... So what you are saying is that this error should disappear with mw 1.35?

I'm not sure why I thought a stable interface policy would help. That must be a typo.

I have exactly the same problem.

So this bug is still present in version 1.35. I had to include the hack here (https://www.mediawiki.org/w/index.php?title=Topic:Vibz8ak3wnpu9mv8&topic_showPostId=viery0f4ta9jp35e#flow-post-viery0f4ta9jp35e) to get the extension to work in version 1.35.

This is still broken in 1.37.1; and in that version the relevant code has been rewritten so the "patch" above no longer works. I could find no bypass, so ended up using Highlightjs_Integration (i.e. wfLoadExtension( 'Highlightjs_Integration' );   )

This uses the identical syntax (i.e. syntaxhighlight).

To enable this functionality, Download the extension and add these lines to LocalSettings.php (ensure that you comment out #wfLoadExtension( 'SyntaxHighlight_GeSHi' ); and #$wgPygmentizePath = "j:/Python3/Scripts/pygmentize.exe";):

wfLoadExtension( 'Highlightjs_Integration' );

(I got the spam warning so had to divide this in 2 parts)

As of Jan 2022, the default version is 9.12. To upgrade to version 10:

• Go to the download page (https://highlightjs.org/download/) and build a "custom" package with the additional languages you want.
• Remove or rename the extensions/Highlightjs_Integration/highlight folder.
• Uncompress the custom package in extensions/Highlightjs_Integration. You should have a fresh new extensions/Highlightjs_Integration/highlight folder.

• Modify extension.json with the following:
  • Change "highlight.pack.js" to "highlight.min.js", and
  • Change "vs2015.css" to "vs2015.min.css".

any new with 1.38.1?