I am currently writing an extension similar to CategoryTree that will
display a JavaScript drop-down tree and populate its children on the fly
using ajax. The drop down tree is based on the Gene
Ontology<http://www.geneontology.org/>,
a set of hierarchal terms to describe biological processes, functions and
locations. My questions are two:
(1.) What is the correct syntax for querying an external (mysql)
database? I have looked into the Database.php and
DatabaseFunctions.phpfiles, but don't quite understand how to do this.
My mysql database can
easily be queried to give the children of a particular term, if I could only
select that database. I currently have a voodoo-like approach using
functions I wrote myself, but I'm sure there is a better way to do this.
(2.) How do I correctly make an Ajax call? I have figured out how to
send my JavaScript along with the page, and I already have a
listener-function written, but I cannot figure out how to call a function in
a class on the server using ajax.
Daniel Renfro
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-458-3376
Hi,
I want to display the output of some extension/function to the right
side of the article title (under the tabs, aboe the article text).
how can I do that? where to edit-skintemplate?
Regards,
Jack
------------------------------------------------------------------------
------------
"When your work speaks for itself, don't interrupt"
This electronic mail (including any attachment thereto) may be confidential and privileged and is intended only for the individual or entity named above. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. Accordingly, if you are not the intended recipient, please notify the sender by replying to this email immediately and delete this email (and any attachment thereto) from your computer system...Thank You
Hi,
Anyone using the AjaxShowEditors extension with MW 1.11?
I have a problem with this extension. When 2 people Jack and John are
editing a page, it's showing only Jack's name as currently editing to
Jack. And to John it's showing "John is editing". Though the DB table
has 2 rows for jack and john. Any clues?
Regards,
Jack
----------------------------------------------------------------
"People forget how fast you did a job - but they remember how well you
did it"
-----Original Message-----
From: mediawiki-l-bounces(a)lists.wikimedia.org
[mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Rob Church
Sent: Tuesday, July 24, 2007 6:54 PM
To: MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] Only one edit at a time?
On 24/07/07, Platonides <Platonides(a)gmail.com> wrote:
> No. Take into account that there's no way to know if someone is
> currently editing a page (i could press edit and not save, or keep the
> edit window open for hours).
I seem to recall Ashar developed something to do that; an extension,
using some AJAX magic, which I believe is an idea that was developed
from a previous discussion on wikitech-l which Tim Starling started.
I don't know what state the code's in, but I imagine it's functional -
have a look at AjaxShowEditors.
Rob Church
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
This electronic mail (including any attachment thereto) may be confidential and privileged and is intended only for the individual or entity named above. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. Accordingly, if you are not the intended recipient, please notify the sender by replying to this email immediately and delete this email (and any attachment thereto) from your computer system...Thank You
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Could someone tell me how to enable tags with CSS class="stylename"? I
understand support was enabled after 1.5, but I can't get it to work on my
1.11.0 system. I suspect it has something to do with that it was upgraded
from 1.4 originally and something isn't set right.
this works:
text here
but this does not:
text here
any ideas?
-Jeff
--
View this message in context: http://www.nabble.com/Enable-%3Cspan-class%3E-tags--tf4525478.html#a12911759
Sent from the WikiMedia General mailing list archive at Nabble.com.
[Re: How to change defaults for preferences for all users?]
Well, that' SEARCH - and that's FANTASTIC, Dan - thanks:
> ... Set up default preferences
> for all NEW users (who have
> never logged in yet)...in
> LocalSettings.php by setting
$wgNamespacesToBeSearchedDefault
> For example:
# Choose default SEARCH namespaces:
$myAdditionalNamespacesSearchDefault = array(
NS_MAIN,
NS_TALK,
NS_USER,
NS_USER_TALK,
NS_PROJECT,
NS_PROJECT_TALK,
NS_IMAGE,
NS_IMAGE_TALK,
NS_MEDIAWIKI,
NS_MEDIAWIKI_TALK,
NS_TEMPLATE,
NS_TEMPLATE_TALK,
NS_HELP,
NS_HELP_TALK,
NS_CATEGORY,
NS_CATEGORY_TALK
);
foreach ($myAdditionalNamespacesSearchDefault as $value) {
$wgNamespacesToBeSearchedDefault[$value] = true;
}
That really should go on
http://www.mediawiki.org/wiki/Manual:%24wgNamespacesToBeSearchedDefault
==
Now for the other user preferences defaults - here are the ones
I care about - I wish there was a sysop special page to configure these:
[User profile]
[x] E-mail me when a page I'm watching is changed
[x] E-mail me when my user talk page is changed
[x] E-mail me also for minor edits of pages
[x] Enable e-mail from other users
[x] Send me copies of emails I send to other users
[Editing]
[x] Enable section editing via [edit] links
[x] Enable section editing by right clicking on section titles
(JavaScript)
[x] Edit pages on double click (JavaScript)
[x] Show edit toolbar (JavaScript)
[x] Show preview on first edit
[x] Show preview before edit box
[x] Mark all edits minor by default
[x] Prompt me when entering a blank edit summary
[Recent changes]
[x] Enhanced recent changes (JavaScript)Watchlist
[Search]
Hits per page: 40
Lines per hit: 10
Context per line: 100
[x] all namespaces - see above in LocalSettings.php for new users, see
http://lists.wikimedia.org/pipermail/mediawiki-l/2007-September/023696.h
tml for SQL for existing users!
[Misc]
Underline links: [always]
... other wiki sysops may want to set and or lock other defaults
to pre-configure their wikis to best server their audience, such as
eliminating Skins other than Monobook.
==
I'm reading
http://www.mediawiki.org/wiki/Manual:%24wgDefaultUserOptions ... it seem
like THIS below would be an appropriate cut and paste to add to
LocalSettings.php and change the "defaults" to my preferences:
// ## user preference defaults:
// ## User Profile
// $wgDefaultUserOptions['fancysig'] = 0 ;
// $wgDefaultUserOptions['rememberpassword'] = 0 ; // Remember my login
on this computer.
// $wgDefaultUserOptions['enotifwatchlistpages'] = 0 ; // Only used if
$wgEnotifWatchlist is set.
// $wgDefaultUserOptions['enotifusertalkpages'] = 1 ; // Only used if
$wgEnotifUserTalk is set.
// $wgDefaultUserOptions['enotifminoredits'] = 0 ; // Only used if
$wgEnotifWatchlist and $wgEnotifUserTalk are set.
// $wgDefaultUserOptions['enotifminoredits'] = 1 ; // Only used if
$wgEnotifWatchlist and $wgEnotifUserTalk are set.
// $wgDefaultUserOptions['enotifrevealaddr'] = 0 ; // Only used if
$wgEnotifRevealEditorAddress and either $wgEnotifWatchlist or
$wgEnotifUserTalk are set.
// ## Quickbar
// $wgDefaultUserOptions['quickbar'] = 1 ; // Quickbar location (only
applies if using Cologne Blue or Classic skins). Options are: 0 - None,
1 - Fixed left, 2 - Fixed right, 3 - Floating left, 4 - Floating right.
// ## Skin
// $wgDefaultUserOptions['skin'] = $wgDefaultSkin ;
// ## Math
// $wgDefaultUserOptions['math'] = 1 ; // How to render in-line maths
(contents of <math></math> tags). Only applies if $wgUseTeX is set.
Options are: 0 - Always render PNG, 1 - HTML if very simple or else PNG,
2 - HTML if possible or else PNG, 3 - Leave it as TeX (for text
browsers), 4 - Recommended for modern browsers, 5 - MathML if possible
(experimental)
// ## Files
// $wgDefaultUserOptions['imagesize'] = 2 ; // Size to limit images on
description pages to. Values correspond to the entries in
$wgImageLimits. By default, 2 is 800*600.
// $wgDefaultUserOptions['thumbsize'] = 2 ; // Thumbnail size - Values
Correspond to the entries in $wgThumbLimits. By default, 2 is 180px.
// ## Date and Time
// $wgDefaultUserOptions['date'] = 0 ; // Date format. 0 = No
preference.
// $wgDefaultUserOptions['timecorrection'] = NULL ; // Timezone offset
// ## Editing
// $wgDefaultUserOptions['rows'] = 25 ; // Edit box size (rows)
// $wgDefaultUserOptions['cols'] = 80 ; // Edit box size (columns)
// $wgDefaultUserOptions['editsection'] = 0 ; // Enable section editing
via [edit] links
// $wgDefaultUserOptions['editsectiononrightclick'] = 0 ; // Enable
section editing by right clicking on section titles (JavaScript)
// $wgDefaultUserOptions['editondblclick'] = 0 ; // Edit pages on double
click (JavaScript)
// $wgDefaultUserOptions['editwidth'] = 0 ; // Edit box has full width
// $wgDefaultUserOptions['showtoolbar'] = 1 ; // Show edit toolbar
(requires javascript)
// $wgDefaultUserOptions['previewonfirst'] = 0 ; // Show preview on
first edit
// $wgDefaultUserOptions['previewontop'] = 1 ; // Show preview before
edit box
// $wgDefaultUserOptions['minordefault'] = 0 ; // Mark all edits minor
by default
// $wgDefaultUserOptions['externaleditor'] = 0 ; // Use external editor
by default
// $wgDefaultUserOptions['externaldiff'] = 0 ; // Use external diff by
default
// $wgDefaultUserOptions['uselivepreview'] = 0 ; // Only used if
$wgLivePreview is true.
// $wgDefaultUserOptions['forceeditsummary'] = 0 ; // Prompt user when
entering a blank edit summary
// ## Recent changes
// $wgDefaultUserOptions['rclimit'] = 50 ; // Titles in recent changes
// $wgDefaultUserOptions['hideminor'] = FALSE ; // Hide minor edits in
recent changes
// $wgDefaultUserOptions['shownumberswatching'] = ? ; // Show the number
users, who are watching this page (on recent changes, watch list and
artice pages). Only used if $wgRCShowWatchingUsers is set.
// $wgDefaultUserOptions['usenewrc'] = FALSE ; // Enhanced recent
changes - javascript collapsable tree
// ## Watchlist
// $wgDefaultUserOptions['watchlistdays'] = 3 ; // Number of days to
show in watchlist
// $wgDefaultUserOptions['extendwatchlist'] = 0 ; // Expand watchlist to
show all applicable changes
// $wgDefaultUserOptions['wllimit'] = 250 ; // Number of edits to show
in expanded watchlist (if'extendwatchlist'== 1)
// $wgDefaultUserOptions['watchlisthideown'] = 0 ; // Hide the user's
own edits from the watchlist
// $wgDefaultUserOptions['watchlisthidebots'] = 0 ; // Hide bot edits
from the watchlist
// $wgDefaultUserOptions['watchlisthideminor'] = 0 ; // Hide minor edits
from the watchlist
// $wgDefaultUserOptions['watchcreations'] = 0 ; // Add pages the user
creates to their watchlist
// $wgDefaultUserOptions['watchdefault'] = 0 ; // Add pages the user
edits to their watchlist
// $wgDefaultUserOptions['watchmoves'] = 0 ; // Add pages the user moves
to their watchlist
// $wgDefaultUserOptions['watchdeletion'] = 0 ; // Add pages the user
deletes to their watchlist
// ## Search
// $wgDefaultUserOptions['searchlimit'] = 20 ; // Hits per page
// $wgDefaultUserOptions['contextlines'] = 5 ; // Lines per hit
// $wgDefaultUserOptions['contextchars'] = 50 ; // Context per line
// ## Misc
// $wgDefaultUserOptions['stubthreshold'] = 0 ; // Threshold for stub
display
// $wgDefaultUserOptions['underline'] = 2 ; // Whether to underline
links. Options are: 0 - never, 1 - always, 2 - browser default
// $wgDefaultUserOptions['highlightbroken'] = 1 ; // Format broken links
as red-underlined links (alternative: with a questionmark as the link,
like this?).
// $wgDefaultUserOptions['justify'] = 0 ; // Justify paragraphs
// $wgDefaultUserOptions['numberheadings'] = 0 ; // Option
"Auto-numbering Headings", 1 turns on the numbering of all headings
within articles
// $wgDefaultUserOptions['showtoc'] = 1 ; // Boolean. 1 is show the TOC,
0 is hide it.
// $wgDefaultUserOptions['nocache'] = 0 ; // Disable page caching
// $wgDefaultUserOptions['showjumplinks'] = 1 ; // Enable "jump to"
accessibility links
// $wgDefaultUserOptions['diffonly'] = 0 ; // Don't show page content
below diffs
... and just change the "= number" and remove the leading "//"
to engage the option, then register as a new user and see if it sticks!
It does.
I'll cut and paste these two sections into all my MediaWiki
LocalSettings.php files from here on to help custom configure them on
demand!
Thanks, Dan - you provided the missing link with the search
default settings.
Does someone want to cut and paste this info into
http://www.MediaWiki.org/ - even on the talk discussion page as "here's
how we use these settings" information (and fix the wrapped text lines
to unwrap so that ALL lines start with "//")?
Hello fellow MediaWiki sysops,
Does anyone know where in http://www.MediaWiki.org/ - failing that,
please share your experience here - we can find where and how to change
defaults for user preferences so that subsequent users get the new
defaults?
Is there a way to change defaults for preferences for even all users,
including existing users? There are endless references to users
changing their own preferences, but how to setup initial preferences?
For instance, in the user preferences under [Search] I want to engage
ALL namespaces. I see the first is checked: [ x ] (main) ... but a
search for "(main)" in the contents of all files in the mediawiki
directory tree returns nothing! So where do we look to control these
choices globally?
Thanks!
Hi fellow MediaWiki sysops,
Does anyone have any clever (easy? automatic?) ways to build large
quantities of page redirects?
For instance, to sort pages and sub pages we'll probably name
them "0700", "0800" and so on - chapters. Then we'll have individual
page in each chapter - "0700/0701" and "0700/0702.1(a)" and so on. But,
if someone types "700" into the [Go][Search] I want them to go to
"0700". And if they type "702.1a" (or "702.1(a)"), I'd like them to go
immediately to page "0700/0702.1(a)".
Sure, http://meta.wikimedia.org/wiki/Redirection says to build a
page for each synonym and put on it:
#redirect [[pagename]]
I note: "... to avoid problems with infinite recursion, if the
redirect target is another redirect page, the second redirect is not
applied..." so I have to build a separate page for each redirect, right?
For example, I now have page "700", so I "move" it ( see
http://meta.wikimedia.org/wiki/Help:Moving_a_page ) to "0700" and that
works, giving 2 pages, with old page "700" seamlessly redirecting to new
page "0700".
Has anyone seen or developed any other ways than building a
redirect page for each synonym? What do you all do to give your users
easy access to look up information and go directly to the answer page?
A look-up substitution index might work (smells like a
hard-coded php array hooked extension?). I think I'm after having the
user type their familiar name of the page they want to see (the name
that they are using for ancient DOS, HTML, or PDF resources) and see the
formally-named wiki page come up immediately - and there may be more
than one informal name by which they may try to get there, by the way.
Thanks!
PS - Again, a link to an http://www.MediaWiki.org answer would be
great - I couldn't find any but the links mentioned above!
Hi,
I' wondering by looking at the function attemptSave which parts are
needed, if I only want to store a new article. No parts of comments and
/or edit are in use
regards mic
Rob Church wrote:
> Run maintenance/rebuildImages.php (set up AdminSettings.php
> first, seeAdminSettings.sample), which should do a quick sweep
> and update MIME types for all your files.
Rob,
I ran rebuildImages. It said it updated 1 of 40 records. I looked at the images table, and the MIME types are still text/plain for all images uploaded prior to the recent changes. Specifically,:
img_media_type = TEXT
img_major_mime = text
img_minor_mime = plain
Fixing those entries isn't a priority for me. I can re-upload them. The problem with permissions--where the files are uploaded as 644 but Apache apparently needs 755 to get at them--is the major issue. The thing that changed was the installation of phpsuexec. Is it valid to run MW with phpsuexec? I assume so, but something isn't right, at least as configured on my server.
An admin at my hosting company wants to hack the script that uploads file to change the permissions, but I don't want to change MW if I can help it.
Any ideas?
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!