Wikimedia Bugzilla is closed!

Those strict errors are PEAR's fault, not MediaWiki's, as can be clearly seen from the paths to the files.

(In reply to comment #1)
> Those strict errors are PEAR's fault, not MediaWiki's, as can be clearly seen
> from the paths to the files.

Right, which is why I added +upstream :) Although at a quick glance, I couldn't figure where you were using PEAR modules in this extension.

Probably because that was what is was using when I rewrote it for 1.16.

So I guess this is INVALID/FIXED by virtue of your rewrite.

Wait Wait
The point is, that the erros are displayed although error_reporting is set to 0 and the OpenID Extension is also using PEAR and gives no errors

And it's not just about the PEAR errors but that this extension is to correctly working with 1.19

(In reply to comment #5)
> The point is, that the erros are displayed although error_reporting is set to 0
> and the OpenID Extension is also using PEAR and gives no errors
> 
> And it's not just about the PEAR errors but that this extension is to correctly
> working with 1.19

It looks like error_reporting is being set in supressStrictWarnings() and restoreStrictWarnings() and the code is doing it wrongly.

Is anybody going to fix this great Extension?
There are a lot of errors because of the changes made in the upload section of mediawiki
Hope somebody can do this

I don't see a bug here. As Bryan pointed out, the extension was fixed in trunk to not use PEAR anymore. The bug listed was relating to PEAR's HTTP Request package (which would be an upstream bug anyway).

OpenID doesn't use this package, so that's why it works.

so should I open a new bug for the issue
"when trying to upload the name is not filled into the form and then it say's
that the URL is missing."??

By the way the strict errors still apear in the last SVN Version

(In reply to comment #9)
> so should I open a new bug for the issue
> "when trying to upload the name is not filled into the form and then it say's
> that the URL is missing."??

Yes.

If you're still getting strict errors please past what you're getting into a comment here.

Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /usr/share/psa-pear/HTTP/Request.php on line 692

Strict Standards: Non-static method PEAR::getStaticProperty() should not be called statically, assuming $this from incompatible context in /usr/share/psa-pear/HTTP/Request.php on line 724

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/share/psa-pear/HTTP/Request.php on line 739

Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /usr/share/php/PEAR.php on line 281

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/share/psa-pear/HTTP/Request.php on line 741

Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /usr/share/php/PEAR.php on line 281

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/share/psa-pear/HTTP/Request.php on line 1284

it's too long. I hope the next ist only repeating

As I said before, any errors in PEAR packages should be reported upstream.

I've the impression you focuse to much on the PEAR Errors.

The problem ist that they are displayed although displaying errors is disabled and when trying to import a picture there is this "when trying to upload the name is not filled into the form and then it say's
that the URL is missing." Error witch makes the Extension totalty useless

(In reply to comment #13)
> I've the impression you focuse to much on the PEAR Errors.
> 

Those have been the only errors you've pasted.

> The problem ist that they are displayed although displaying errors is disabled
>

That's not a MediaWiki bug either.

> and when trying to import a picture there is this "when trying to upload the
> name is not filled into the form and then it say's
> that the URL is missing." Error witch makes the Extension totalty useless

*That* is perhaps an actual bug, but I'll let Bryan decide.

(In reply to comment #14)
> (In reply to comment #13)
> > I've the impression you focuse to much on the PEAR Errors.
> > 
> 
> Those have been the only errors you've pasted.
> 
> > The problem ist that they are displayed although displaying errors is disabled
> >
> 
> That's not a MediaWiki bug either.
That's a problem with the extension! I've disabled error reporting in LocalSettings and the ImportFreeImages Extension is the only place where errors are displayed
> 
> > and when trying to import a picture there is this "when trying to upload the
> > name is not filled into the form and then it say's
> > that the URL is missing." Error witch makes the Extension totalty useless
> 
> *That* is perhaps an actual bug, but I'll let Bryan decide.

(In reply to comment #15)
> (In reply to comment #14)
> > (In reply to comment #13)
> > > I've the impression you focuse to much on the PEAR Errors.
> > > 
> > 
> > Those have been the only errors you've pasted.
> > 
> > > The problem ist that they are displayed although displaying errors is disabled
> > >
> > 
> > That's not a MediaWiki bug either.
> That's a problem with the extension! I've disabled error reporting in
> LocalSettings and the ImportFreeImages Extension is the only place where errors
> are displayed
> > 

That is not a bug in the extension, it sounds like PEAR is doing something wrong.

The extension is no longer using PEAR so closing as fixed.
Update your extension to the latest version.