issue 28
(PageFunctions: #pagetitle does not work on newer MediaWiki l...) reported by bogdan.ristea
- What steps will reproduce the problem?
Install latest MW and latest PageFunctions extension including dependencies.
What is the expected output? What do you see instead?
No effect
What version of the product are you using? On what operating system?
What steps will reproduce the problem?
Install latest MW and latest PageFunctions extension including dependencies.
What is the expected output? What do you see instead?
No effect
What version of the product are you using? On what operating system?
Oct 06, 2009
issue 27
(Incompadibility with PHP 5.3.0) commented on by JeanLou....@gmail.com
- Thanks for your interest - for the time being, I have no plans to support PHP > 5.2.
I am not closing this ticket but I am not assigning any time on this either.
Thanks for your interest - for the time being, I have no plans to support PHP > 5.2.
I am not closing this ticket but I am not assigning any time on this either.
Sep 25, 2009
issue 27
(Incompadibility with PHP 5.3.0) reported by omega13a
- What steps will reproduce the problem?
1. Install the extensions (this problem effects several of your MediaWiki
extensions (Possibly some I haven't even tested. There's too many for me to
test)) on a server that runs PHP 5.3.0
What is the expected output?
The extensions to work as they did under PHP 5.2.x
What do you see instead?
Numerous PHP errors and warnings about passing by references and something
relating to using the MediaWiki's deprated Namespace class (It was
deprecated because Namespace in PHP 5.3.0 has a special meaning. The class
has been renamed to MWNamespace .)
What version of the product are you using? On what operating system?
Like I said, this issue effects several of your extensions when run under
PHP 5.3.0
Additional Information:
I know you said you are done with MediaWiki for now but it would be nice if
you can get your MediaWiki extensions compatible with PHP 5.3.0. I got the
effected ones I use to work but not everyone out there is a PHP wiz like
you and I and wont know how to fix these things on their own.
What steps will reproduce the problem?
1. Install the extensions (this problem effects several of your MediaWiki
extensions (Possibly some I haven't even tested. There's too many for me to
test)) on a server that runs PHP 5.3.0
What is the expected output?
The extensions to work as they did under PHP 5.2.x
What do you see instead?
Numerous PHP errors and warnings about passing by references and something
relating to using the MediaWiki's deprated Namespace class (It was
deprecated because Namespace in PHP 5.3.0 has a special meaning. The class
has been renamed to MWNamespace .)
What version of the product are you using? On what operating system?
Like I said, this issue effects several of your extensions when run under
PHP 5.3.0
Additional Information:
I know you said you are done with MediaWiki for now but it would be nice if
you can get your MediaWiki extensions compatible with PHP 5.3.0. I got the
effected ones I use to work but not everyone out there is a PHP wiz like
you and I and wont know how to fix these things on their own.
issue 26
(Linking for SecureHTML) reported by DaSch.Tour
- I think it would be usefull to create a link when using a template with the
#html or #sthml tag. By now the used templates are displayed as unused and
you can not see where they are used. --77.182.140.72 11:18, 14 December
2008 (UTC)
Ditto. --Subfader 17:21, 14 December 2008 (UTC)
I think it would be usefull to create a link when using a template with the
#html or #sthml tag. By now the used templates are displayed as unused and
you can not see where they are used. --77.182.140.72 11:18, 14 December
2008 (UTC)
Ditto. --Subfader 17:21, 14 December 2008 (UTC)
Nov 05, 2008
issue 20
(New extension: Related News) commented on by subfader
- I like it just that I'd like to see it a level below.
On B an C I add <relatedto>A<relatedto/>. On A I see 2 links to B+C without touching
it. On B and C I only see a link to A.
C doesn't care much that B also links to A.
I'd use it for a kinf of repeats. You have an original and repeates.
In your level you can get many and dirty relations pretty fast.
I like it just that I'd like to see it a level below.
On B an C I add <relatedto>A<relatedto/>. On A I see 2 links to B+C without touching
it. On B and C I only see a link to A.
C doesn't care much that B also links to A.
I'd use it for a kinf of repeats. You have an original and repeates.
In your level you can get many and dirty relations pretty fast.
Oct 13, 2008
issue 22
(Imagelink ignores anything after a # character in links) Status changed by JeanLou.Dupont
-
Status: Fixed
Status: Fixed
Oct 13, 2008
issue 25
(StubManager-1.3.0 Error: Too many arguments in Stub->__call) Status changed by JeanLou.Dupont
-
issue 25
(StubManager-1.3.0 Error: Too many arguments in Stub->__call) changed by JeanLou.Dupont
-
Status: Accepted
Labels: Type-Enhancement−Type-Defect
Status: Accepted
Labels: Type-Enhancement−Type-Defect
Sep 28, 2008
issue 25
(StubManager-1.3.0 Error: Too many arguments in Stub->__call) reported by evgeny.fadeev
- Error: Too many arguments in Stub->__call
Apparently there is a limit on number of arguments in the __call function.
I've found this when I tried to create a parser function with many arguments.
return call_user_func_array(array($obj,$method),$args);
replaces the switch statement that calls function with different number of
arguments and fixes the problem.
Error: Too many arguments in Stub->__call
Apparently there is a limit on number of arguments in the __call function.
I've found this when I tried to create a parser function with many arguments.
return call_user_func_array(array($obj,$method),$args);
replaces the switch statement that calls function with different number of
arguments and fixes the problem.
Aug 28, 2008
issue 24
(SidebarEx Broken) commented on by wendallc
- All of your documentation lacks the detail that ONLY StubManager is required as an
include. I actually found the solution on another site. None of the provided
documentation for any of your extensions will give a working setup as they are
currently written. The bug is specific to the documentation at this point.
All of your documentation lacks the detail that ONLY StubManager is required as an
include. I actually found the solution on another site. None of the provided
documentation for any of your extensions will give a working setup as they are
currently written. The bug is specific to the documentation at this point.
Aug 28, 2008
issue 24
(SidebarEx Broken) commented on by JeanLou.Dupont
- Does the 'require statement' for "StubManager" appear *before* the one for SidebarEx
in LocalSettings.php? If not, you would experience the situation you are describing.
Does the 'require statement' for "StubManager" appear *before* the one for SidebarEx
in LocalSettings.php? If not, you would experience the situation you are describing.
Aug 27, 2008
issue 24
(SidebarEx Broken) reported by wendallc
- What steps will reproduce the problem?
1. Install SidebarEx
2. Browse to Main Page or any other wiki page
What is the expected output? What do you see instead?
Produces the error:
[[Extension:SidebarEx]] <b>requires</b> [[Extension:StubManager]]
Error is produced because it doesn't properly pull in the StubManager
Class. And, yes, StubManager is installed.
What version of the product are you using? On what operating system?
Current svn version/Linux
What steps will reproduce the problem?
1. Install SidebarEx
2. Browse to Main Page or any other wiki page
What is the expected output? What do you see instead?
Produces the error:
[[Extension:SidebarEx]] <b>requires</b> [[Extension:StubManager]]
Error is produced because it doesn't properly pull in the StubManager
Class. And, yes, StubManager is installed.
What version of the product are you using? On what operating system?
Current svn version/Linux
