Hi folks,
today is sysadmin appreciation day! ( http://www.sysadminday.com/ )
Many thanks to the Wikimedia operations team for being there at all
times of day and night to keep our sites up and our users happy -- and
for always working hard to make things faster, more stable, and more
secure.
For the Wikimedia Foundation, that goes for the office IT team as well --
thanks for all your help with networks, printers, laptops, monitors, projectors,
smartphones, dumb phones, and the myriad pieces of open and not-open
software that we run. Special thanks to all the volunteers who
participate in Wikimedia operations, help with outages, close shell
bugs, document things, and do so much more.
Please join me in thanking our ops and IT teams. You all rock - thanks
for being here. :-)
Erik
--
Erik Möller
Deputy Director, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
(CC'd inez @ wikia)
In the process of getting a better feel for the current state of Wikia,
Wikihow, & a few others' rich text editor tools, I'm going through Wikia's
CKEditor-based RTE extension and seeing if I can get it working on MediaWiki
trunk.
I've got a fork from Wikia's SVN in this gitorious project:
http://www.gitorious.org/mediawiki-wikia-rte
The 'master' branch is a straight git-svn clone of the subtree; 'tweaks'
branch has some extra doc comments and some initial tweaks to get it loading
(if not actually working right yet ;) on stock MediaWiki 1.18-SVN.
Current state:
* most stuff won't work yet!
* the editor can be loaded if forced with &useeditor=wysiwyg
* load/save results in some corruption, probably mostly due to the parser
annotations not all being present (need to customize a few bits)
* the editor is loaded through ResourceLoader, using a quick stub to work
around the lack of removal of certain lines
* it's almost certain that the CSS and some JS is broken :D
* there are various Wikia-specific PHP-side and JS-side extensions, many of
which still need to be switched to the stock MW equivalent or copied over.
Note that definitions for such things can usually be found in the modified
MediaWiki core in Wikia's SVN tree --
https://svn.wikia-code.com/wikia/trunk/
At a minimum I'd like to end up with something that works on stock MediaWiki
1.18 (and if it can be made to work on stock or lightly-patched 1.17, even
better!). It should be a more stable option for 1.17 users than the old
FCKEditor extension.
I'm still a bit leery of the internal annotations & edge-case checks for the
round-tripping and whether this structure would work for us in the long
term, but there's some good stuff in here that's going to be useful to learn
from whatever we do, and it's a useful tool for many cases in the short
term.
If anybody feels like trying it out / pitching in on the fixes, do feel free
to give a shout. I can set a few folks up with commit access on the git repo
or take some pulls for now, and will merge it into our SVN extensions when
it's a bit more stable.
-- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
Hi Roan,
thanks for the quick reply. This is (one of) the statement(s) we've got a problem with.
------------------
DROP PROCEDURE IF EXISTS `insertfile_getFilePosition`;
DELIMITER $$
CREATE PROCEDURE `insertfile_getFilePosition`(filename VARCHAR(255))
BEGIN
SELECT tmp.rank FROM
(SELECT @row:=@row+1 rank, i.img_name
FROM /*$wgDBprefix*/image i, (SELECT @row:=0) r
WHERE (i.img_major_mime != 'image' AND i.img_minor_mime != 'tiff')
ORDER BY i.img_name ASC) tmp
WHERE tmp.img_name = filename;
END
$$
DELIMITER ;
------------------
If provided to the SQL Database directly, it works. But the update.php throws a syntax error.
In general, is it possible to provide stored procedures this way?
Could there be a problem with the way the sql-file is read?
Greetings,
Robert Vogel
Social Web Technologien
Softwareentwicklung
Hallo Welt! - Medienwerkstatt GmbH
__________________________________
Untere Bachgasse 15
93047 Regensburg
Tel. +49 (0) 941 - 56 95 94 98
Fax +49 (0) 941 - 50 27 58 13
www.hallowelt.biz
vogel(a)hallowelt.biz
Sitz: Regensburg
Amtsgericht: Regensburg
Handelsregister: HRB 10467
E.USt.Nr.: DE 253050833
Geschäftsführer: Anja Ebersbach, Markus Glaser, Dr. Richard Heigl, Radovan Kubani
On Wed, 27 Jul 2011 at 22:16 PM, Roan Kattouw <roan.kattouw(a)gmail.com> wrote:
>On Wed, Jul 27, 2011 at 12:47 PM, Robert Vogel <vogel(a)hallowelt.biz> wrote:
>> Hello everybody!
>>
>> At my company we develop extensions for MediaWiki. We use the "LoadExtensionSchemaUpdates" hook to create tables with the "maintenance/update.php" script.
>> Recently we faced the question whether it is possible to have stored procedures/functions in an extensions SQL-File, or not. We tried it out and it didn't work for us. The update.php says we've got an error in the SQL syntax, but there isn't one.
>>
>> Can anybody help us? Is it possible to provide stored procedures to the database using the update.php? Is there an example anywhere? Thx.
>>
>The SQL syntax error message comes from the database engine, not from MediaWiki. So if it tells you there's an SQL syntax error, there's a syntax error for sure. What you should look at:
>1. does the DB backend you connect to support the syntax you're using?
>Infamously, MySQL 4.0 will reject anything containing subqueries as a syntax error, because subquery support wasn't introduced until 4.1 if memory serves 2. is MediaWiki connecting to the DB that you think it's connecting to? There might be a version-triggered error like #1 above, but you might not notice if you're connecting to a different version than MediaWiki is 3. are you using magic phrases like /*_*/, /*$wgDBTablePrefix*/, /*i*/ or /*$wgDBTableOptions*/ ? MediaWiki substitutes these before sending the SQL to the DB backend, so make sure you test your queries with these substitutions applied
>
>Roan Kattouw (Catrope)
The boxes that are on a wikipedia-page on the top right hand corner
generally, as I have seen are created by using templates Infobox or
Navbox. Are there any other templates which can result in such a box?
Thanks
Priyank
Hello everybody!
At my company we develop extensions for MediaWiki. We use the "LoadExtensionSchemaUpdates" hook to create tables with the "maintenance/update.php" script.
Recently we faced the question whether it is possible to have stored procedures/functions in an extensions SQL-File, or not. We tried it out and it didn't work for us. The update.php says we've got an error in the SQL syntax, but there isn't one.
Can anybody help us? Is it possible to provide stored procedures to the database using the update.php? Is there an example anywhere? Thx.
Greetings,
Robert Vogel
Social Web Technologien
Softwareentwicklung
Hallo Welt! - Medienwerkstatt GmbH
___________________________________
Untere Bachgasse 15
93047 Regensburg
Tel. +49 (0) 941 - 56 95 94 98
Fax +49 (0) 941 - 50 27 58 13
www.hallowelt.biz
vogel(a)hallowelt.biz
Sitz: Regensburg
Amtsgericht: Regensburg
Handelsregister: HRB 10467
E.USt.Nr.: DE 253050833
Geschäftsführer: Anja Ebersbach, Markus Glaser, Dr. Richard Heigl, Radovan Kubani
In order to be able to have time to clean up the default assignments in
Bugzilla, I've put my weekly triage on hold this week and last week.
The rationale behind this cleanup is to avoid Cookie Licking
(http://communitymgt.wikia.com/wiki/Cookie_Licking) and make it easier for
people to find work that has been requested but isn't being worked on.
(Many thanks to Sumana for introducing me to the term.)
At the end of this process, my hope is that the assignments in Bugzilla
will actually reflect work that people intend to complete. I'm
restricting the changes to components that relate to Wikimedia sites
(Wikipedia, Wiktionary, Wikinews, Wikisource, etc.)
As part of these changes, I'm asking people who've been assigned bugs
because of the default assignments to review the list of bugs that they
are currently assigned. If you've been assigned any bugs by default, I
will email you a list of bugs and ask you to respond by telling me which
assignments you would like to keep because you intend to work on them
in the not-to-distant future.
If I do not receive a response by August 15th, I’ll assume that you
don't intend to work on any of the bugs and remove you from those in the
list I send you.
Again, note that I'm only doing this on components used on Wikimedia and
for bugs where the current assignee was the default assignee. If you
found a bug and “took” it by assigning yourself, I should not be
contacting you about it.
Your help in this is much appreciated.
Thanks,
Mark.
[If this ends up on the list twice, it is because I'm sending it again
through my own mail server since Google's Gmail shows it as sent two
hours ago, but it hasn't shown up in the list archives yet.]
Yesterday I came across this feature request, which I promptly
mis-understood:
https://bugzilla.wikimedia.org/30018
Option to make access to specific user rights or user groups
dependent on having a verified email address
The requester clarified the request today:
There's relatively little benefit to making people provide a
verified email address at one point time. On long-lasting wikis,
verification might have been 5-10 years ago. The aim of this bug is
to make user rights dependent on a verified email address *on an
ongoing basis*.
So for example if the user removes the email address, or replaces it
with another but doesn't verify it, the user rights associated with
their user group are automatically suspended, until a verified email
address is provided, when they're automatically re-enabled.
This would be more useful if there are situations where the
"verified" status of an existing email address can be automatically
revoked (eg if emails to the user bounce); I'm not sure if that's
the case but if it isn't that's a separate issue.
I'm fascinated by the idea and can see arguments both ways. I thought
I'd bring it up here to see if anyone could help me think through it.
Thanks,
Mark.