On Fri, Sep 28, 2012 at 1:11 AM, Daniel Friesen
<daniel(a)nadir-seen-fire.com> wrote:
>> - Extensions should probably have some sort of manifest file. What
>> format should it be in and what information should it contain?
>
> I think Chad (^demon) was the the one focusing on this area. We should ask
> him what his plans were.
>
I had some rough ideas, but they never got fleshed out. In my ideal
world, I was thinking something like an abstract Extension class
that each extension would implement. It would have methods for
returning things $wgExtensionCredits does now, as well as being
able to say "I depend on Foo" extension. Then we'd have some kind
of ExtensionRegistry, so enabling an extension would be something
like ExtensionRegistry::register( new MyExt );
But yeah, I never really got further than that.
-Chad
Hey Teammates,
I am getting the following upload error in MediaWiki 1.19.2.
Error creating thumbnail: convert.exe: unable to open image `C:\WINDOWS\TEMP/transform_32f7ebc-1.jpg': Permission denied @ error/blob.c/OpenBlob/2614.
Is that because the IUSR does not have permissions to c:\Windows\Temp ? I'm really not able to give it permissions there for
security reasons, is there a workaround ?
Where is error/bloc.c/OpenBlob coming from ?
thx,
Lori
Liebe MW-Spezialisten,
Wir haben tausende Benutzeracounts von Spammern:
http://wiki.openseamap.org/wiki/Spezial:Benutzer
Wie kann ich diese löschen?
Eine "White list" von "guten" Benutzern ist vorhanden.
Gibt es da einen Bot?
Danke, Markus
Hi,
I'm running Mediawiki 1.19.1 on Debian/stable server via
lighttpd/php5-cgi. Earlier today I decided I wanted to enable
wgDebugToolbar in my LocalSettings.php - done that, but now the wiki was
not responding any more.
I've immediately reverted that change (and it really was only that change,
I compared with the backups) but still the wiki was not responding.
top(1) showed that one of the php5-cgi process was using up a lot of CPU
time, so I decided to kill that process and restarted the webserver. But
still, accesssing the wiki was not possible: the page was "Loading...",
but nothing got delivered back to the browser. Deleted cookies, tried
another browser, still the wiki appeared to be unusable.
Looking at the MySQL database serving the wiki, I could see what was going
on:
------
307 Query REPLACE /* MessageBlobStore::updateModule 10.0.0.123 */
INTO `mw_msg_resource` (mr_resource,mr_lang,mr_blob,mr_timestamp) VALUES
('user.tokens','en','{}','20120926011737')
307 Query SELECT /* MessageBlobStore::updateModule 10.0.0.123 */
mr_blob FROM `mw_msg_resource` WHERE mr_resource = 'user.options' AND
mr_lang = 'en' LIMIT 1
------
These two queries where sent over and over again to the database by the
php5-cgi process, ~10 times per second or so. Restarting the database did
not help, as soon as I accessed the wiki again, these queries appeared
again.
I've had this issues before, with 1.19.0, IIRC. I did not dig deeper
though, somehow the next morning the wiki was "just" working again. But
the issue was the same: changed something in the config and then these
strange queries appeared.
I've put the LocalSettings.php and the database query log here:
https://trent.utfs.org/bits/mediawiki/
Some more notes:
* I've switched from lighttpd/php5-cgi to apache2/mod_php5, still the
same: when the wiki is accessed, those strange queries appear and the
wiki page "loads" until php's maximum execution time is exceeded..
* I'm using the APC cache. Disabling that (and wgMainCacheType) did no
help either.
* I'm not using any Mediawiki extensions.
Anyone got an idea what might be going on here?
Thanks,
Christian.
--
BOFH excuse #148:
Insert coin for new game
Hey,
> Is there a reason we don't just put this in the core?
One of the reasons is that from my experience the MediaWiki core dev
community is not very open to such things. I think Tim is illustrating the
point pretty well, by implying what I did is total nonsense. Having tried
to get this into core would have lead to more insults getting thrown at my
head. Of course this is nonsense, as I'm sure some core developer will
point out in a reply.
Another reason is that although this is a rather generic diff utility, the
number of extensions that could make use of this seems rather limited. And
I don't think we want to just put any generic component into core without
good reason.
> It has about 50 lines of useful code wrapped in 1600 lines of
> abstraction. I don't think it is the sort of style we want in the core.
Unsurprisingly I'm going to Agree with Denny that this is rather harsh.
This kind of attitude is not very welcoming to other developers, especially
if you make such comments where they are not applicable.
And yes, I'm going to maintain it's not applicable. Being the genius that
you are, I challenge you to put your money where your mount is to write a
50 line extension that offers the same functionality as this extension.
One might discuss the suitability of using a class hierarchy to
> represent different DiffOps. But then again, that is the same class
> design as in the DairikiDiff engine, included in core as well.
>
Although you find small things to nitpick over, I'm confident the overall
design is sound. The Diff and DiffOps are following the composite pattern,
which seems very much like the right choice to me. I would not mind being
proven wrong or having other constructive discussion though.
"This is crap" is not constructive.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
Wondering if anyone else has run into this. Clicking on the edit link in
a portal styled page which uses the magic word, {{fullurl}} like this,
[{{fullurl:{{{editpage|/}}}|... Seems as if some are DNS'ing back to
this wiki and the actual link when hovered over the word "edit" is
resolving back to parasite domain names. Even shows still logged in,
perfect mirror.
Question is what is {{fullurl}} pulling its information from, the ip
address? If so it would explain a DNS back to wrong domain if the look
up hits the wrong domain first.
What is the fix?
Thanks
Tom
Hey,
I'm happy to announce the first release of a new little extension I wrote
called Diff.
https://www.mediawiki.org/wiki/Extension:Diff
It's a small utility library which might be of use to anyone creating a new
extension :)
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
I would like to adjust large image sizes to the user's screen port by Javascript. Is it possible to address ImageMagick by JS, and if yes, how?
Bernhard
Hi,I have a link like
Von „http://mywebsite.tld/w/index.php?title=Hauptseite&oldid=438“
at the bottom of my wiki and i do not know how to remove it.
Does someone have an idea?
*here is my site: http://bit.ly/UpjF6P*
*
*
(please dont post original URL's in here, 1000 thanks!)