Re: [Semediawiki-user] [SF] - Autocomplete field location problem - SF 2.5.2 with SMW 1.8.0.4 on MW 1.20.3.3

[Alex M. H. (public) <amh...@on...>]

Yaron,

Thanks for the tip! I had very slightly modified the skins/Vector.php
file to add a custom footer icon that would not work properly when
trying to set it in LocalSettings. Once I removed that modification it
worked fine. Better to have working autocomplete than the footer,
though; I'll have to find some other way to do that.

Best,
Alex

--
Alex M. Hendler
ontolawgy™ LLC: connect . . . the . . . dots
http://ontolawgy.com

On Tue, Apr 2, 2013 at 6:05 PM, Yaron Koren <ya...@wi...> wrote:
> Hi Alex,
>
> I can't duplicate this problem, on a wiki that runs MediaWiki 1.21-alpha.
> Unless it's an issue that's specific to MW 1.20, my guess is that the
> problem is actually due to an interplay of MediaWiki, the skin (if you're
> not using Vector), any custom Javascript or CSS (if you have any of that),
> and possibly other extensions that are installed or used in that form - like
> Header Tabs or Semantic Forms Inputs. Is this on a public wiki? If not,
> could you send me the contents of the entire form-definition page? (I'd ask
> you to replicate the problem on scratchpad.referata.com, but Referata
> doesn't use MW 1.20 yet.)
>
> -Yaron
>
>
> On Tue, Apr 2, 2013 at 8:50 AM, Alex M. Hendler (public)
> <amh...@on...> wrote:
>>
>> Using Semantic Forms 2.5.2 with Semantic MediaWiki 1.8.0.4 (and all
>> related extensions from the current SemanticBundle release of
>> 2013-02-26) on MediaWiki 1.20.3 seems to cause text auto complete
>> drop-downs in forms to show up in the upper left corner of the screen,
>> at least when accessing them through Special:RunQuery. I would like to
>> start migrating some templates to Lua in the near future, so I would
>> like to use MW 1.20.3, if possible.
>>
>> Here's the relevant form:
>>
>> {{{field|Document title|input type=text with
>> autocomplete|size=70|values from property=Document title|remote
>> autocompletion}}}
>>
>> I access the form from Special:RunQuery, which passes the input to a
>> template that uses an inline query.
>>
>> I have the following set in LocalSettings.php:
>>
>> $sfgAutocompleteOnAllChars = true;
>> $sfgMaxAutocompleteValues = 10000;
>>
>> I'm not sure if either of those are relevant to the issue, but I do
>> need them both for this application (well, I certainly need the first
>> parameter; I could probably reduce the number in the second, but I
>> found that it was missing things with lower values).
>>
>> I do not see this problem in MediaWiki 1.19.4 (drop-downs appear below
>> the text field), so I've reverted. I'm using the default SQLStore3.
>>
>> Is this a problem that anyone else is seeing? If so, is anyone aware
>> of a fix/workaround?
>>
>> Thanks,
>> Alex
>>
>> --
>> Alex M. Hendler
>> ontolawgy™ LLC: connect . . . the . . . dots
>> http://ontolawgy.com
>>
>>
>> ------------------------------------------------------------------------------
>> Own the Future-Intel(R) Level Up Game Demo Contest 2013
>> Rise to greatness in Intel's independent game demo contest. Compete
>> for recognition, cash, and the chance to get your game on Steam.
>> $5K grand prize plus 10 genre and skill prizes. Submit your demo
>> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
>> _______________________________________________
>> Semediawiki-user mailing list
>> Sem...@li...
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>
>
>
>
> --
> WikiWorks · MediaWiki Consulting · http://wikiworks.com