Jim Hu | 1 Mar 17:31 2008
Picon

Re: Ajax Search Suggest (my first extension)

I made the changes on the code at mediawiki.org.

In general, I might wait to trigger the search until more characters  
have been entered.  1 seems like overkill; how useful will the  
suggestions be when you type 'e'?

In Firefox, the browser's autocomplete tries to run, and sits on top  
of what the extension is doing.  I wonder if that can be suppressed.

Jim

On Mar 1, 2008, at 10:22 AM, Jim Hu wrote:

> function wfAjaxSetSearchSuggestHeaders($outputPage) {
>>>       global $wgJsMimeType, $wgStylePath,$wgScriptPath;
>         $outputPage->addLink(
>                 array(
>                         'rel' => 'stylesheet',
>                         'type' => 'text/css',
>>>                       'href' => $wgScriptPath.'/extensions/
> searchsuggest/style.css'
>                 )
>         );
>>>       $outputPage->addScript( "<script type=\"{$wgJsMimeType}\"
> src=\"$wgScriptPath/extensions/searchsuggest/searchsuggest.js\">"."</
> script>\n");
>         $outputPage->addScript( "<script type=\"{$wgJsMimeType}
> \">hookEvent(\"load\", ss_ajax_onload);</script>\n" );
> }
>
(Continue reading)

B. Johannessen | 1 Mar 17:36 2008

Re: Redundancy, MySQL replication and $wgDBservers

Platonides wrote:
> Maybe you're using some extension which is directly accessing the master?
> Keep into mind that some few actions go directly to the master even when 
> they're only for reading, to avoid lag.

Plain install, no extensions. I've also added the following to 
LocalSettings.php, but the problem persists:

$wgEnableParserCache = false;
$wgMainCacheType = CACHE_NONE;
$wgMessageCacheType = CACHE_NONE;
$wgParserCacheType = CACHE_NONE;

	Bob
Jim Hu | 1 Mar 17:45 2008
Picon

Re: Ajax Search Suggest (my first extension)

Now that I have it sort of working... I'm testing in Safari and  
Firefox both on a mac.

I see the suggestions in the area under the search box, which I think  
is what the code is doing.  This would be nicer as a drop-down menu  
from the search box.

The suggestions that come up for me are weird.  For example I type x  
and get page titles that don't have x in them!

puzzling.  I think the sql query looks reasonable based on the  
extension code.

Jim

On Mar 1, 2008, at 10:31 AM, Jim Hu wrote:

> I made the changes on the code at mediawiki.org.
>
> In general, I might wait to trigger the search until more characters
> have been entered.  1 seems like overkill; how useful will the
> suggestions be when you type 'e'?
>
> In Firefox, the browser's autocomplete tries to run, and sits on top
> of what the extension is doing.  I wonder if that can be suppressed.
>
> Jim
>
> On Mar 1, 2008, at 10:22 AM, Jim Hu wrote:
>
(Continue reading)

Grietinus Koops | 1 Mar 18:01 2008
Picon

Re: Ajax Search Suggest (my first extension)

It seemed indeed to have to do with the path.
By the way on mediawiki there's still a "," in front of the path code.

And uhhh, hmmm, blush... I forgot to enable ajax :)

Now I put $wgUseAjax = true;
and it's working :)

Thx. Now we can test the real stuf :)

Grietinus

2008/3/1, Jim Hu <jimhu@...>:
>
> Now that I have it sort of working... I'm testing in Safari and
> Firefox both on a mac.
>
> I see the suggestions in the area under the search box, which I think
> is what the code is doing.  This would be nicer as a drop-down menu
> from the search box.
>
> The suggestions that come up for me are weird.  For example I type x
> and get page titles that don't have x in them!
>
> puzzling.  I think the sql query looks reasonable based on the
> extension code.
>
>
> Jim
>
(Continue reading)

jidanni | 1 Mar 21:54 2008

Re: Header errors: I need help please.

P> Putting a ?> at the endo of the file is optional. If there's an error
P> the extension was broken.

Sorry to break in to the conversation without even having checked the
parent articles for what computer language you are talking about, but
I would just like to note that like with the HTML language, some
closing items that were optional later became required, and for good
reasons. So one can predict the future here too. Hmmm, /bin/sh's <<EOF
optional closing EOF won't bite you until one day you concatenate or
nest or past/append what you thought was a comment... and there it
goes, executing this very message. OK, never mind.
Adam Meyer | 1 Mar 23:02 2008
Picon

Re: Ajax Search Suggest (my first extension)

Thank you for the changes!
I added some more functionality to it this morning. Im going to change  
the code around and upload it later today.

On Mar 1, 2008, at 11:31 AM, Jim Hu wrote:

> I made the changes on the code at mediawiki.org.
>
> In general, I might wait to trigger the search until more characters
> have been entered.  1 seems like overkill; how useful will the
> suggestions be when you type 'e'?
>
> In Firefox, the browser's autocomplete tries to run, and sits on top
> of what the extension is doing.  I wonder if that can be suppressed.
>
> Jim
>
> On Mar 1, 2008, at 10:22 AM, Jim Hu wrote:
>
>> function wfAjaxSetSearchSuggestHeaders($outputPage) {
>>>>      global $wgJsMimeType, $wgStylePath,$wgScriptPath;
>>        $outputPage->addLink(
>>                array(
>>                        'rel' => 'stylesheet',
>>                        'type' => 'text/css',
>>>>                      'href' => $wgScriptPath.'/extensions/
>> searchsuggest/style.css'
>>                )
>>        );
>>>>      $outputPage->addScript( "<script type=\"{$wgJsMimeType}\"
(Continue reading)

DanTMan | 1 Mar 23:20 2008
Picon

Re: (finish-and-release? '(Extension:MovePageEx Extension:WikiVid))

Hmmm... Do you think I should scratch plans to release it from the side 
of one of my other projects, and instead work on it in the Wikimedia SVN?

~Daniel Friesen(Dantman) of:
-The Gaiapedia (http://gaia.wikia.com)
-Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG)
-and Wiki-Tools.com (http://wiki-tools.com)

Platonides wrote:
> DanTMan wrote:
>   
>> Now secondly, there's another extension I've got, except it's in partial 
>> development (85% of it is complete, and it's got a fair amount of 
>> functional use already).
>> It's called WikiVid, and it's basically used for embedding videos from 
>> external video hosts into the page.
>>     
>
> (lots of lines skipped)
>
> It sounds great. So i encourage you to finish it if you can spend some 
> time on it.
>
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l@...
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>   
(Continue reading)

Adam Meyer | 2 Mar 01:51 2008
Picon

Re: Ajax Search Suggest (my first extension)

I just updated the code.
it should work out of the box now.

I added configuration to it in the php file.
You can select the number of results that come back.
You can select to search in the entire article name (default), or just  
in the beginning of the name.

The results are now links to the articles, so you can just click on  
them.

As for the Javascript. I trimmed it down, and:
Required 2 characters before search is done. (max 10 incase something  
leans on the keyboard)
Enables a memory system so it will not search if the last search was  
the same.

-Adam

On Mar 1, 2008, at 5:02 PM, Adam Meyer wrote:

> Thank you for the changes!
> I added some more functionality to it this morning. Im going to change
> the code around and upload it later today.
>
> On Mar 1, 2008, at 11:31 AM, Jim Hu wrote:
>
>> I made the changes on the code at mediawiki.org.
>>
>> In general, I might wait to trigger the search until more characters
(Continue reading)

Leon Kolchinsky | 2 Mar 15:52 2008
Picon
Picon

Re: link problems after upgrade

> > >  > Hello All,
> > >  >
> > >  > After wiki upgrade I witness very strange phenomenon.
> > >  > Please look at this page:
> > >  >
> > >  > http://wikiedtech.edu.haifa.ac.il/
> > >  >
> > >  > Now search for HiLearn. This word was a link. Now it seems like a
> > link but the actual link are words near it (go with your mouse to the
> > right from HiLearn and you'll see).
> > >  > It seems that the problem is on main page only with various links.
> > >  >
> > >  > Any help?
> > >
> > >
> > > Only HiLearn is a link for me with Firefox.
> >
> > Works for me, too. It's probably a browser issue, try it in a different
> > one.
> >
> 
> Indeed, I've checked with Opera and the link seems to be OK.
> The problem occurs in IE only, and this is a big problem for us, since the
> majority of users use this browser :(
> 
> Could anyone check it with IE and suggest some solution?
> 
> 
> Best Regards,
> Leon Kolchinsky
(Continue reading)

John W Foster | 2 Mar 16:00 2008
Picon
Picon

Re: Header errors: I need help please.

Well I did at any rate (being somewhat anal) go into the extensions code
and put the closing $> in place and eliminate any existing open lines
after that closing.....end of header problems, for now. 
Thanks guys!!
frosty

On Sun, 2008-03-02 at 04:54 +0800, jidanni@... wrote:
> P> Putting a ?> at the endo of the file is optional. If there's an error
> P> the extension was broken.
> 
> Sorry to break in to the conversation without even having checked the
> parent articles for what computer language you are talking about, but
> I would just like to note that like with the HTML language, some
> closing items that were optional later became required, and for good
> reasons. So one can predict the future here too. Hmmm, /bin/sh's <<EOF
> optional closing EOF won't bite you until one day you concatenate or
> nest or past/append what you thought was a comment... and there it
> goes, executing this very message. OK, never mind.
> 
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l@...
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Gmane