Extension talk:Regex Fun/Flow

Previous page history was archived for backup purposes at Extension talk:Regex Fun/LQT Archive 1 on 2015-07-10.

I updated my installation today from 1.35 to 1.37.4 and am now seeing this error message related to Regex Fun:

Notice: Indirect modification of overloaded property Parser::$mExtRegexFun has no effect in /var/www/my.wiki/public_html/mediawiki-1.37.4/extensions/RegexFun/RegexFun.php on line 727

Also seeing this:

Notice: Undefined property: Parser::$mExtRegexFun in /var/www/my.wiki/public_html/mediawiki-1.37.4/includes/debug/DeprecationHelper.php on line 209

I'm not sure why this started popping up; has anyone encountered this before? I grabbed the extension for 1.37 and have run all the normal updates, and this seems to be the only extension having issues. Any assistance greatly appreciated!

Never mind: I continued my system upgrade to the latest (1.38.2) and now the Regex Fun error has disappeared, so hey-ho! Huwmanbeing (talk) 09:53, 5 September 2022 (UTC)

Hello

I updated to 1.39.1 and i have the same error Parser::$mExtRegexFun.

I think it was fixed 5 months ago but I think that this change was not backported for MediaWiki 1.39

https://github.com/wikimedia/mediawiki-extensions-RegexFun/commit/756d152249af292c4ebe0d700033e23eaffb2440

So I suggest to do not use RegexFun at version 1.39

I have the same problem that Notice: Undefined property: Parser::$mExtRegexFun in /www/wwwroot/my.wiki/includes/debug/DeprecationHelper.php on line 211

I have too many teamplate used the function.I can't remove it so esaily.

On MW 1.31 I see the following warning: "Use of ParserLimitReport hook (used in ExtRegexFun::onParserLimitReport) was deprecated in MediaWiki 1.22."

I am trying to get the video ID from a youtube link using this extension but have failed. If anyone has done this please share.

Have a look at this StackOverflow question. As you can see there are various answers and comments so I just picked one (not necessarily the best or most suitable for you) of the described solutions there. Keep in mind that there is a chance that this might not work with all future youtube IDs if Google changes the format.

This should give you an empty string if no valid youtube url is given and the video ID if a valid url is given (not tested):

{{#regex: URL HERE | /^.*(?:youtu.be\/{{!}v\/{{!}e\/{{!}u\/\w+\/{{!}embed\/{{!}v=)([^#\&\?]*).*/ir | $1 }}

Please show some example code, snippet.. with regex_var function because there is misunderstood how to manipulate with regex_var ..

How can you specify alternation (|) in the pattern for #regex? e.g. if you want to match {{ #regex: abcdef | /abc|def/ }} ? Alternatives such as calling #regex twice won't work for me.

Two possible ways:

• Define a Template:! in your wiki which contains nothing move than a |. Then use {{ #regex: abcdef | /abc{{!}}def/ }}.
• Use the regex ascii escaping syntax. Without looking it up, \x7C should work if I am not misstaken. {{ #regex: abcdef | /abc\x7Cdef/ }}.

How can I get this to parse the content of a variable?

Using the Variables Extension.

{{#vardefine:cur|Current user rating: 4 (1 rating)}}

The variable cur contains variable text that can look like "Current user rating: 4 (1 rating)".

Why doesn't this work?

{{#regex: {{#var:cur}} |/^.*rating: ([0-9]+\.?[0-9]*).*$/|$1}}

that returns something like "1461dee31c1648-item-1--QINU" which changes every refresh.

Thanks for the awesome extension.

I can not confirm this.

{{#vardefine:cur|Current user rating: 4 (1 rating)}}
{{#regex: {{#var:cur}} |/^.*rating: ([0-9]+\.?[0-9]*).*$/ | $1}}

produces 4 using the current (trunk) version of Variables and Regex Fun. The "1461dee31c1648-item-1--QINU" thing you are writing about looks like a internal strip marker, something went utterly wrong there. But I can't believe this is due to simple variables/regex usage, perhaps you are using some strange version or something is interfering? Which version do you use?

I have seen this QINU problem before. Perhaps it is related, though I basically have no clue. Cheers

Accidently I saw another edit todoy which said: "The parser hook must return a value in MW 1.18+, so return the empty string" with return htmlspecialchars(""); Still I do not know if this is the cause of this problem.