Insect room

The Insect room is intended to inform about bugs particular to the OmegaWiki software. It is not a place for feature requests (see Meta:Functionality wanted).

Solved bugs should be moved to the Insect room/Archive.

• See also OmegaWiki related bugs at bugzilla. Bugzilla should preferably not be used: you might receive less attention if you post your bug on bugzilla.

Start a new discussion

Discussion pages

Strategic discussions

International Beer Parlour - archives

List of Beer Parlours

International Linguists Beer Parlour - Inflexions

Questions about words

Articles needing attention

Insect room (report bugs) - archives

Meta:Functionality wanted - archives

Open issues

Wiki-Tags do not work

The <sub> tag appears to be broken in the Expression namespace. For example see Expression:water. --Tosca 18:33, 1 June 2006 (CEST)

We want definitions to be "self contained" this means that a definition should not link to other definitions. There are several good reasons why we do not want this. One is that we do not yet link to DefinedMeanings but to Expressions. As to markup, some markup particularly the sub sup italic and bold are things that may be usefull. They have to be (re)enabled for the definitions.. Thanks, GerardM 12:17, 3 June 2006 (CEST)

We're working on a whitelist for some parser functions (or rather, a mini-parser for OmegaWiki). But, for the most part, we're going the relational route as far as possible. We may have the ability to link to a disambiguated term using a special syntax in the future.--Erik 00:10, 14 June 2006 (CEST)

Any progress/new ideas on this, Erik? Siebrand 18:33, 18 October 2006 (CEST)

http://bugzilla.wikimedia.org/show_bug.cgi?id=8090 Siebrand 15:08, 30 November 2006 (CET)

New messages notification

But it' not true, just only one posted a month ago but the orange message does not disappear! I have a mac with safari. The Doc 10:18, 14 June 2006 (CEST)

Is this still an issue? Please provide feedback. Siebrand 18:34, 18 October 2006 (CEST)

Yes it is, people with spaces in their usernames have this problem. Needs Mediawiki updating. Kipcool 18:04, 22 November 2006 (CET)

Fixed GerardM 03:23, 9 August 2007 (EDT)

Over fixed: I never get any notification for the pages I want to follow. --Fiable.biz 00:34, 26 September 2009 (UTC)

Did you select "M’avertir par courriel lorsqu’une page de ma liste de suivi est modifiée" in your preferences? --Kipcool 21:33, 9 October 2009 (UTC)

No but, on Wikipedia, for instance, when I connect and a page I follow has been modified, I then get a notification on the form of a banner in the web site itself, than is at the right time. Isn't it supposed to work like that in Omegawiki? --Fiable.biz 12:08, 2 December 2009 (UTC)

I've seen such a banner only for modifications to my talk page (also in Wikipedia). --Kipcool 13:49, 5 December 2009 (UTC)

I suggest we test. You select a Wikipedia page you want to follow, you say me which one, I modify it and inform you, then you check if you get a banner. Fortunately I never receive mails from Wikipedia, so if this doesn't work, I wonder what is the "Follow this page" checkbox for. --Fiable.biz 06:35, 20 December 2009 (UTC)

First Definition/Expression NEEDS to be marked

There is currently no way to see which Expression and Definition that constitutes any given DefinedMeaning. IMO it is fundamental to have this information available since it is the only way to avoid semantic drift. Now with new DM:s being created in great quantities from all languages it is absolutely vital that this information is shown. --Sannab 20:06, 28 July 2006 (CEST)

This issue is not yet resolved. I think this should have a fairly high priority, to avoid future drift in definition translations. Siebrand 18:39, 18 October 2006 (CEST)

http://bugzilla.wikimedia.org/show_bug.cgi?id=8092 Siebrand 15:11, 30 November 2006 (CET)

Cannot link to a word

The word asilo pe bammine or Expression:asilo p''e bammine exists and it can be found as asilo_p%27%27e_bammine. It is one place where MediaWiki sucks. GerardM 22:49, 17 September 2006 (CEST)

It works this way: Expression:asilo p''e bammine. Zanatic 22:53, 17 September 2006 (CEST)

This means another workaround ... well: in some way I am gettin quite ... ehm ... better to shut up ... with workarounds for nap ;-) --Sabine 23:10, 17 September 2006 (CEST)

http://bugzilla.wikimedia.org/show_bug.cgi?id=8097 Siebrand 15:17, 30 November 2006 (CET)

edit boxes overlapping other clickable items do not work

See last entry - if edit boxes overlap with other clickable content already on a page, selcting from a drop down list by clicking an item becomes impossible (with Opera 9.02 under WIN2K) - yet one may end up with the wanted item always at the wrong place. Opening and closing subdivisions on a page (- other languages / + other languages, etc.) may help to avoid the unwanted overlap. Unfortiunately, that may not always be possible. --Purodha Blissenbach 12:47, 25 December 2006 (EST)

I assume, the following description (stolen from User_talk:GerardM) describes the same problem.

Spaanse woordsoorten

Hola Gerard, Zalig Kerstfeest, met wat je vroeg hoop ik dat het is, waar ik nu met bezig ben, namelijk de woordsoorten in het Spaans te zetten. Spijtig maar ik kan de annotation mode niet gebruiken. Als ik naast de vertaling op annotation druk opent een vak met 3 keuzes. Ik kies dan de laatste en bij "attribute" kan ik "woordsoort" in brengen, tot hier alles ok maar bij de "option" waar zich een klein keuzevakje bevind loopt het mis. Druk ik daarop rolt er een piep klein vakje open 4 cm hoog of laag en 1 cm breed. Daar kan ook niet in geschreven worden. Doe ik wat verkeerd of is het iets anders maar ik heb vanalles geprobeerd en het lukt me niet. De groetjes MARCEL 12:16, 25 December 2006 (EST)

I have the same problem. HenkvD 13:47, 25 December 2006 (EST)

Translation please? Malafaya 15:27, 10 October 2009 (UTC)

Special:Select

At the top of Special:Specialpages, there's a funny-looking link to Special:Select. The latter page throws a database error. László 12:08, 12 February 2007 (EST)

OK, I've found SpecialSelect.php. Will fix later. László 03:08, 15 February 2007 (EST)

This has somewhen gone away :) László 09:07, 9 August 2007 (EDT)

I believe this page has some specific use and is expecting some parameters to be thrown in. An improvement would be input checking. Malafaya 01:46, 12 February 2009 (CET)

Unclean deletions

It would be good if a developer could have a look at the case of Expression:ちっそ and DefinedMeaning:ちっそ (456162) First, user MovGP0 deleted the DM and the Expression and made the links red. But if you opened the links the database entry was still visible. I had to delete the definition entry and the syntrans entry by hand to make the entry disappear. For a clean deletion, it would be great if deleting a DM would delete all of its entries and relations and not just make the link to the page red.--Mkill 11:49, 4 March 2007 (EST)

Indeed, Bugzilla GerardM 03:16, 9 August 2007 (EDT)

Red link to Meta:Policy

The deletion confirmation page (and probably several other pages) links to Project:Policy, which is redirected to Meta:Policy, but this page does not exists. Where is the policy? --Mkill 22:11, 14 February 2007 (EST)

Vocabulary trainer down

I have never been able to get the vocabulary trainer to work. After logging in it times out with the error message:

Fatal error: Call to a member function xpath() on a non-object in /var/www/ow/extensions/Wikidata/util/voctrain/collectionlist.php on line 19

McDutchie 05:30, 28 May 2009 (EDT)

Problem with Ugaritic script

Whenever I try to add a word in Ugaritic script, I got the following:

Une erreur de syntaxe de la requête dans la base de données est survenue. Ceci peut indiquer un bogue dans le logiciel. La dernière requête traitée par la base de données était :

    insert into page(page_namespace,page_title,page_is_new,page_touched) values(16, '𐎓𐎕', 1, 20100912221219)

depuis la fonction « ». MySQL a renvoyé l’erreur « 1062 : Duplicate entry '16' for key 2 (localhost) ».

--Kip 22:13, 12 September 2010 (UTC)

Note to myself, this is because of UTF-16 scripts not being supported by the current version of mySQL. There is a trick on the MediaWiki servers (binary instead of varchar), but I am not sure whether the change can be made without harming the data, or if it's just better to wait for a later version of MySQL that support utf-16. --Kip 23:37, 17 March 2012 (CET)

Long time to respond

Strange: The section before this one just took over 10 minutes to be saved. During that time, I had a trip to the bathroom, did various other things, and tried to load a number of pages from OmegaWiki in several browser windows, which all would not load during that time. --Purodha Blissenbach 02:07, 25 September 2010 (UTC)

And the server did not crash, so this is a good news.

I reduced the number of apache servers, to prevent swaping. When no more server can be created, you have to wait. --Kip 08:18, 25 September 2010 (UTC)

Aaah, I gotcha. I was doing several things in parallel, but the Lord himself may know what took more than tem minutes for all server copies to terminate. MediaWikis job queue, perhaps?

Yeah, really good, that it did not crash. I was happy! Greetings --Purodha Blissenbach 21:34, 25 September 2010 (UTC)

Duplicated definition and lost spellings of translations and synonymes

Yesterday, I created both definitions appearing on the page Expression:Dat sėn Jeschmakßaache, hät dä Buur jesaat, doh hätt e singe Koh der Aasch jebütz. at the moment, that is

• DefinedMeaning:Dat sėn Jeschmakßaache, hät dä Buur jesaat, doh hätt e singe Koh der Aasch jebütz. (1257670) and
• DefinedMeaning:Dat sėn Jeschmakßaache, hät dä Buur jesaat, doh hätt e singe Koh der Aasch jebütz. (1257675)

The respective URLs are:

• http://www.omegawiki.org/DefinedMeaning:Dat_s%C4%97n_Jeschmak%C3%9Faache,_h%C3%A4t_d%C3%A4_Buur_jesaat,_doh_h%C3%A4tt_e_singe_Koh_der_Aasch_jeb%C3%BCtz._(1257670) and
• http://www.omegawiki.org/DefinedMeaning:Dat_s%C4%97n_Jeschmak%C3%9Faache,_h%C3%A4t_d%C3%A4_Buur_jesaat,_doh_h%C3%A4tt_e_singe_Koh_der_Aasch_jeb%C3%BCtz._(1257675)

I see no difference between the two, thus imho, the 2nd on should not have been created, even though I knowingly made two tries. Experience with other pages showed up to now that saving the same data twice would not duplicate it, and that I could easily add different or even overlapping data from two browser windows to one page concurrently without duplcating something. No so this time.

Since I came from the page DefinedMeaning:Watt_dämm_Eijn_sing_Uhl_is_dämm_Andere_sing_Nachtijall._(1257659), where the above had been present already as an expression having "not identical meaning", I was wondering that its syntrans have "identical maning"s were not already automatically added to the new page with "not identical meaning", which I had expected, and which I had in mind having seen working this way before.

I believe, the problem is caused by the fact that software modified the original expression

from		Dat sėn Jeschmakßaache, hät_dä Buur jesaat, doh hätt_e singe Koh der Aasch jebütz.
to		Dat sėn Jeschmakßaache, hät dä Buur jesaat, doh hätt e singe Koh der Aasch jebütz

on its way from a data base entry, through a link, through an URL, to a character string being searched in the database. Each of "_", "%20", and a space character are mapped to a space character. This poses no problem since the underscore ("_") is rarely used in written language. Unfortunaltely, I copied the above string from the ksh Wikipedia, where we use underscores to denote liaison, and some syllable borders, so as to enhance readability, and to be a bit closer to spoken language, which often greatly reduces ambiguities, since word flow and intonation quite strongly determine meaning - often you negate a sentence by just shifting stress and choosing another melody for it (c.f. Ferdinand Münch: Grammatik der ripuarisch-fränkischen Mundart. Cohen, Bonn 1904, Saendig Reprint, Wiesbanden 1970, ISBN 3-500-21670-6 eg.), so the unmarked written form is highly ambiguous without context.

We do not have to use "_", and it usually does not appear inside words anyways, so it is nothing to really worry about for the relational data in OmegaWiki. I shall leave these things as they are for a while just in case someone want to investigate. I shall later, in a week or so, try to fix the whole thing, and only be back here if I do not succeed. However, I would also like to recommend to fix software so as to avoid such duplicates in the future. Ok, this may be low priority issue, and may be already on someones list, else I may dig deeper into how it exactly happened, and what could be done about it. --Purodha Blissenbach 10:46, 27 September 2010 (UTC)

Entered syntrans lost during save

I've entered roughly two dozen syntrans of Expression:absolutief along with other data but got only 5 back on save, the pre-existing one included, two minutes ago. :-( I did not like that )-:   --Purodha Blissenbach 04:00, 5 November 2010 (UTC)

Never happened to me, and I often add about 20 translations at once. --Kip 13:18, 5 November 2010 (UTC)

Database Error.

Enne Fääler es opjefalle en dä Süntax vun ennem Befääl för de Datebank. Dat künnd_enne Fääler em Wikki-Projamm sin. De läzde Date_Bank_Befääl eß jewääse:

SELECT uw_expression.expression_id, spelling, language_id FROM uw_defined_meaning, uw_expression WHERE uw_defined_meaning.defined_meaning_id=kkudativ 126701 AND uw_expression.expression_id=uw_defined_meaning.expression_id AND uw_defined_meaning.remove_transaction_id IS NULL AND uw_expression.remove_transaction_id IS NULL

uß dä Funkzjohn: „“. MySQL mälldt dä Fääler: „1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '126701 AND uw_expression.expression_id=uw_defined_meaning.expression_id AND uw' at line 1 (localhost)“.

Greetings. --Purodha Blissenbach 10:57, 5 November 2010 (UTC)

There is an error here: "uw_defined_meaning.defined_meaning_id=kkudativ 126701"

but since you give no context at all, I can give no better answer. --Kip 13:19, 5 November 2010 (UTC)

Unfortunately, I do not have any. I was doing parallel works in a handful of browser tabs and windods, switching them all the time, and letting transmissions of data happen in the background. And I was getting tired and went to bed while my computer was still working collecting responses. When I came back after sleeping, I had that reply somewhere but was unable to reconstruct, what that window or tab had been doing. --Purodha Blissenbach 01:55, 6 November 2010 (UTC)

The link below has database error. http://www.omegawiki.org/index.php?title=DefinedMeaning:lexical_item_(402295)&action=history -Hiong3-eng5 (talk) 13:39, 19 April 2013 (CEST)

History tab does not work when I am logged in

Why does the history tab in the namespaces Help and Template lead to an empty page? Example: http://www.omegawiki.org/index.php?title=Help:Ultimate_Wiktionary&action=history; when I am logged out it works. --Ortografix 18:10, 10 January 2011 (UTC)

Works for me. It seems to be a problem with the German interface. Not sure what exactly. --Kip 22:43, 10 January 2011 (UTC)

It does not work with the English interface either. I tried de, en and fr; of these only fr works. --Ortografix 17:31, 11 January 2011 (UTC)

Still investigating. It works with

• http://www.omegawiki.org/index.php?title=Help:Ultimate_Wiktionary&action=history&limit=1

but not with

• http://www.omegawiki.org/index.php?title=Help:Ultimate_Wiktionary&action=history&limit=2 or above

No idea why. --Kip 09:37, 13 January 2011 (UTC)

Pop-up windows for Annotation don't close

The pop-up windows for Annotation links don't close, they prevent seeing or clicking on what is underneath. A close button is needed. --InfoCan 23:08, 8 March 2012 (CET)

You have to click on the same Annotation link again to close it. If it does not work, please indicate the browser you are using. There are some problems with Google Chrome (I'm working on it), but not this one. --Kip 09:29, 9 March 2012 (CET)

Oh, indeed it does! The popup panels that appear when you click on a textbox have it ("clear previous next X"), I guess I was expecting the same behavior. --InfoCan 18:39, 9 March 2012 (CET)

This is confusing for newbies. I remember I had the same problem. Would it be difficult to change the colour of the link (to orange, for instance) and maybe its size once the annotation is open in order to draw attention to the link? --Fiable.biz 23:22, 11 March 2012 (CET)

I can add an X and change the colour. I am in the process of rewriting the code so that it works fine with Google Chrome (and optimized with jQuery). I can do the change in the process. --Kip 23:34, 17 March 2012 (CET)

Thank you in advance. --Fiable.biz 14:49, 26 November 2012 (CET)

Language selection

My default language is set to English. I search for word "hala" which is a word in Turkish but does not have a counterpart in English (it means "sister of father"). I get a page with "Language:Rohingya" where only the word "black" is defined. Only when I click on the down-arrow next to Rohingya and select Turkish do I get the English definition of "hala". There is not even an "English" selection under Rohingya to see the English definition of the word. --InfoCan 19:40, 17 March 2012 (CET)

Oh I see, a feature, not a bug. [1] --InfoCan 23:04, 17 March 2012 (CET)

...yes, a recent feature. It is much better in terms of server response time, and avoiding too much scrolling.

However, I am aware that it is maybe not so obvious or intuitive for new users. If you have an idea to improve it, that'd be nice. I guess that the main problem you had is that you added a word in Turkish, and it did not show up when you saved? So maybe the page should automatically switch to the new language when a language is added (not sure how to do that with regard to the current php code). --Kip 23:31, 17 March 2012 (CET)

Maybe you could use tabs for each language, displayed horizontally (something like the Monobook skin tabs), instead of a combo/dropdown box. At least, it would be more visible that you can select the desired language. Malafaya 01:46, 25 March 2012 (CET)

good idea, I'll see how that can be implemented. --Kip 10:06, 25 March 2012 (CEST)

If there are translations in many languages, it may not be practical either. It seems the best solution is to be able to set in your Preferences which languages you want displayed for 1) interface language choices, 2) translations for a DM, 3) SyntTranses. Presumably most people would choose less than 10 languages they will ever be interested in. These then can be displayed without encumbering the user, overloading the server and slowing the display of information. Malafaya's suggestion above would work as well. --InfoCan 16:44, 25 March 2012 (CEST)

On a related subject (again, not a bug but a feature request), I think when the DefinedMeanings in a particular language are displayed, the regional variations of it should be displayed on the same page as well. Most users would not think about changing the language from "English" to "English-USA" to find additional entries, for example. --InfoCan 16:56, 25 March 2012 (CEST)

The regional variations will be changed to annotations, i.e. "English-USA" and "English-UK" will be merged to "English", and an annotation will be used to indicate that the word in used in US or UK (or Australia, or southern-US, or anywhere else). But before doing that, I need to make the annotations more visible. --Kip 17:35, 25 March 2012 (CEST)

I think this might have serious implications, so we should think seriously before taking such a decision. The ISO 639-6 standard lists languages variants within a single code, while RFC 5646 use a composite approach using subtags: Primary Language Subtag, Extended Language Subtag, Script Subtag, Region Subtag, Variant Subtag, Extension Subtag and Private Use Subtag. The RFC 5646 approach seems intellectually more beautiful, more promising, easier to manage by a program, and more like Omegawiki, but is also more dangerous: one can easily "define" purely artificial combinations, like "Cuneiform polytonic English"; secondly, at the opposite, some really existing variants could be referenced several ways. For instance, there are variants inside the the Mongolian-Uighur script, and they have not been standardised by the IANA yet. Another example is that, also the same "Cyrl" (Cyrillic) is used for several languages (Bulgarian, Belarussian, Mongolian etc) their alphabet is not exactly the same (For instance, Mongolians added 2 letters to the Russian Cyrillic), while the composite code seems to imply the alphabet would be the same. At the opposite, ISO 639-6 lists only real languages, and tries to register all (though, for the moment, ancient languages are badly registered). The IETF language tags uses both the composite tag system of RFC 5646 and a registration by IANA. But I suspect the IANA to be even less interested by ancient languages than the ISO. Maybe a way to deal with this would be to put language variations in annotations as you propose, like IETF, creating as many annotations as RFC 5646 tags, but using the private tags when necessary for ancient languages. For instance, it is not reasonable to have a single "grc" language for "ancient Greek", as if Homer in the 8th century before Christ and Bizantine emperor Constantine XI Palaiologos in the 15th century used the same language. These extra annotations would solve several problems, like writing or not accents and breathes on Greek words (IANA has a "polytonic" tag for this). It's important that variants of a given expression be registered as such, not only as different expressions of one definedMeaning. For instance, it's not enough that "dishonour" (British English), "dishonor" (American English) and "disgrace" (English) be registered as expressions of the same definedMeaning: it should also be registered that "dishonour" and "dishonor" are variations of the same expression, which is, so far, not done. Another thing to think of is that a few words may have regional variations without requiring to register a language variant for that. Example: " chocolatine" in Southern France and "pain au chocolat" in Northern France, though there is no such a thing as "Southern France French". So I suggest only registered combinations of Primary Language Subtag (i.e. annotation), Extended Language Subtag, Script Subtag, variant Subtag, Extension Subtag and Private Use Subtag be allowed, but the use of the regional subtag be freeer. --Fiable.biz 15:01, 26 November 2012 (CET)

Duplications in class lists

Minor bug. Some terms can occur multiple time in class lists. for example here, the words "ak" and "beyaz" are listed twice, probably because each is a synonym of the other. --InfoCan 22:27, 17 March 2012 (CET)

It is because they have two meanings (the two "beyaz" don't link to the same DM, one is an adjective, the other is a noun). Anyway, the class lists and collection lists pages need to be rewritten as special pages. --Kip 23:21, 17 March 2012 (CET)

Cannot unselect incorrect selection

Syntrans Annotation -> Option values -> grammatical property. I you select a value by mistake, you cannot unselect. Need to save first, then delete. Same problem with usage, part of speech, etc. Need to have a blank choice. --InfoCan 18:08, 16 April 2012 (CEST)

No word class in several languages, no gender in several languages needing them

If I define a word in languages "English (United Kingdom)", "English (United States)", "Middle French" or "Breton", there is no "part of speech" in "Annotation". It's safe to consider that word classes in "English (United Kingdom)" and "English (United States)" are the same as in "English", and that, as far as our, very rough, level level of precision is concerned, that the word classes of "Middle French" are the same as for "French". As far as Breton is concerned, I don't know, but I'm sure there are at least nouns. Moreover, in middle French and Breton there should be genders: masculine and feminine. --Fiable.biz 15:03, 26 November 2012 (CET)

Many language selections in sidebar selector cause SQL errors

I'v tied every language from kongo to latina, and the vast majority causes an error like the one reported below when trying to access wikidata pages. --Purodha Blissenbach (talk) 14:19, 16 January 2013 (CET)

Cannot access Expression:Afghane

Here is the erronous SQL statement yielded, when I try to go to Expression:Afghane

 SELECT expression_id, language_id FROM uw_expression WHERE spelling=BINARY 'Afghane' AND uw_expression.remove_transaction_id IS NULL AND EXISTS (SELECT * FROM uw_syntrans WHERE uw_syntrans.expression_id=uw_expression.expression_id AND uw_syntrans.remove_transaction_id IS NULL ) AND language_id=

Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near  at line 1 

Whe I am not logged in, the error does not occur. --Purodha Blissenbach (talk) 20:16, 28 December 2012 (CET)

Will look into it. --Kip (talk) 16:48, 16 January 2013 (CET)

Fixed. --Kip (talk) 12:02, 19 January 2013 (CET)

Thank you! --Purodha Blissenbach (talk) 16:42, 23 January 2013 (CET)

https problems

When trying to access Omegawiki via https, I get:

1. a warning about an outdated, self signed certificate, issued to a site different from omegawiki.org
2. lots of "missing page" errors, since index.php?title= is not automatically inserted behind the / following the domain in the URLs of pages. Yet, with it inserted manually, everything seems to work fine.

--Purodha Blissenbach (talk) 20:16, 28 December 2012 (CET)

https does not work with OmegaWiki because you have to pay [2] to get a certificate for your website, and I don't see the need to pay for that. --Kip (talk) 16:47, 16 January 2013 (CET)

Of course, except for password security and script integrity, there's nothing justifying encryption anyways. Unless someone is willing to donate a payed certificate, we should be happy with a self issued and self signed one. --Purodha Blissenbach (talk) 16:41, 23 January 2013 (CET)

I did not know it was possible with a self-issued certificate. I did some setup on the server, and it seems to work now (though with a warning as you said). --Kip (talk) 22:44, 24 January 2013 (CET)

I don't know if the cache is used for Omegawiki, but, as far as I know, https prevents any cache to work. --Fiable.biz (talk) 13:51, 29 January 2013 (CET)

http://omegawiki.org is again an index folder. Hiong3-eng5 (talk) 05:48, 31 January 2013 (CET)

It got broken when I set up https. Now working again. --Kip (talk) 08:04, 31 January 2013 (CET)

Cannot edit - Error from database - Syntax error in SQL statement

The URL before server-side rewriting was: http://www.omegawiki.org/index.php?title=DefinedMeaning%3Adictionary_%20915%20&action=edit#24742566868732074895

If a translation is needed, I can supply one. Yet I think, the viable information is in English & SQL anyways.

Fähler en de Daatebank

Enne Fähler es opjefalle en dä Süntax vun ennem Befähl för de Daatebangk. Dat künnd_enne Fähler em Wikki-Projamm sin. De läzde Befähl för de Daatebangk eß jewääse:

SELECT defined_meaning_id, expression_id from uw_defined_meaning where defined_meaning_id=ictionary 91 AND uw_defined_meaning.remove_transaction_id IS NULL

uß dä Fongxjohn: „“. De Daatebangk mälldt dä Fähler: „1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '91 AND uw_defined_meaning.remove_transaction_id IS NULL' at line 1 (localhost)“.

Di Sigg heh stamp vun „http://www.omegawiki.org/DefinedMeaning:dictionary_915“.

--Purodha Blissenbach (talk) 16:27, 1 May 2013 (CEST)

I have no idea how you arrived to that url. The correct url http://www.omegawiki.org/DefinedMeaning:dictionary_(915) works fine by me.

I think the above sql error will not happen anymore when we switch to number-only definedmeaning page titles. --Kip (talk) 13:51, 2 May 2013 (CEST)

Javascript problems

I get quite some "script freezes browser" error messages now on expression pages. Letting scripts continue, one to five times in a row, most often works, but sometimes, you cannot click e.g. annotations or headlines to open sections. Browsers: mostly Konquerer and Iceweasel, both under debian GNU/Linux on a somewhat slow-ish box. --Purodha Blissenbach (talk) 16:27, 1 May 2013 (CEST)

Is a problem with the sorting algorithm. You can try this Help:Customizing Javascript.

I think the sorting is slow because the pages are heavy. I am working on having lighter pages, which I hope will make sorting faster. If it still doesn't work, I'll have to sort it server-side (which sounds easy, but is not given the current structure of the code, or maybe I just didn't find the correct way to do it easily). --Kip (talk) 13:54, 2 May 2013 (CEST)

Link errors

• On page Help:Collection#Browsing the collections, there is a link to a tool. The link is broken.
• On the same page, the link to GEMET is broken, likely for the same reason.

--Purodha Blissenbach (talk) 16:40, 1 May 2013 (CEST)

This is not really a software bug... Anyway, in the link, try replacing "Wikidata" with "WikiLexicalData". Thanks. --Kip (talk) 13:55, 2 May 2013 (CEST)

Interface translation

I am missing some interface texts such as "Semantic annotations" and "related to" (appearing on page http://www.omegawiki.org/index.php?title=DefinedMeaning:Wikidata_ID_%281434066%29&action=edit for instance) in translatewiki.net where I would eagerly like to translate them.

"Semantic annotations" is a name that I introduced recently. Before having it as a translatable messages, I wanted some feedback about if the label "semantic annotation" is ok, or if another label should be used (Meta:International_Beer_Parlour#More_visible_annotations). Since I got no feedback, I guess it's ok, so I'll add it as a translatable message.

"related to" - indeed! Never noticed this one before. Will add to i18n as well. --Kip (talk) 14:05, 2 May 2013 (CEST)

Some messages there are outdated, referring to the old "Wikidata", see http://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Ow_db_consistency_not_found/en
--Purodha Blissenbach (talk) 21:24, 1 May 2013 (CEST)

"Wikidata" should be changed to "WikiLexicalData" which is the new name of our extension. I renamed it to avoid confusion with the Wikidata project. Of course now it is more work for us... I am not sure how to change it in relation to translatewiki (only change English?). If you know, can you maybe submit a patch? --Kip (talk) 14:05, 2 May 2013 (CEST)