I'm thinking about trying to implement sortable tables in mediawiki.
I'd probably try to make the table headers pass some parameter through
to the rendering engine by attaching some &T1=col1 or something similar
to the URL.
Any opinions? Great idea? Stupid idea? Someone else working on
something similar?
-Nick
Hi
I am curious to learn how the mediawiki community decides what features will
be implemented in the next release and what solutions you have found in
development collaboration. How much do you rely on sf.net and, according to
your experience, do you believe that it is beneficial to the wikipedia
community to allow non-developers view development-related discussions or
vote/feedback on them? is the MW development community-driven?
--
NSK
Admin of http://portal.wikinerds.org
Project Manager of http://www.nerdypc.org
Project Manager of http://www.adapedia.org
Hi, and thanks so much for the help in
getting MediaWiki running. I ended up
using the Linspire Laptop since it was
suggested I stick with Linux... and it
went very smoothly. It took me only
a few minutes to download the updates
and then ran the webscripted install from
the browser at the wiki´s directory...
Right away things were configured,
I moved the file over from the config
to the parent directory and refreshed
my browser... the Main_Page popped
up and the cute flower logo looked
great!
I have a question about the address to
the page... it seems to be
http://localhost/wiki/index.php/Main_Page
or
http://linspiron/wiki/index.php/Main_Page
(The laptop is a Dell Inspiron 1150)
somehow the ¨index.php¨ part doesn´t seem
right... is this right or did I goof somehow on
the setup of the software?
Again thanks for all the suggestions and the
excellent support pages I found on setting
up MediaWiki on Linux.
With regards,
Jay B.
Brion Vibber wrote:
> Update of /cvsroot/wikipedia/phase3/maintenance/archives
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5272
>
> Modified Files:
> patch-userlevels-defaultgroups.sql
> Log Message:
> Give sysops & bureaucrats the 'sysop' permission so they can edit protected pages!
>
>
> Index: patch-userlevels-defaultgroups.sql
> ===================================================================
> RCS file: /cvsroot/wikipedia/phase3/maintenance/archives/patch-userlevels-defaultgroups.sql,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -C2 -d -r1.2 -r1.3
> *** patch-userlevels-defaultgroups.sql 24 Oct 2004 22:28:21 -0000 1.2
> --- patch-userlevels-defaultgroups.sql 27 Oct 2004 07:20:47 -0000 1.3
> ***************
> *** 9,13 ****
> VALUES (2,'Loggedin','General logged in users','read,edit,move,upload');
> INSERT INTO `group` (group_id,group_name,group_description,group_rights)
> ! VALUES (3,'Sysops','Operators of this site','read,edit,move,delete,undelete,protect,block,upload,asksql,rollback,patrol,editinterface');
> INSERT INTO `group` (group_id,group_name,group_description,group_rights)
> ! VALUES (4,'Bureaucrat','The bureaucrat group is able to make sysops for example. They have no other rights.','read,edit,move,delete,undelete,protect,block,userrights,createaccount,upload,asksql,rollback,patrol,editinterface,siteadmin');
> --- 9,13 ----
> VALUES (2,'Loggedin','General logged in users','read,edit,move,upload');
> INSERT INTO `group` (group_id,group_name,group_description,group_rights)
> ! VALUES (3,'Sysops','Operators of this site','read,edit,move,delete,undelete,protect,block,upload,asksql,rollback,patrol,editinterface,sysop');
> INSERT INTO `group` (group_id,group_name,group_description,group_rights)
> ! VALUES (4,'Bureaucrat','The bureaucrat group is able to make sysops for example. They have no other rights.','read,edit,move,delete,undelete,protect,block,userrights,createaccount,upload,asksql,rollback,patrol,editinterface,siteadmin,sysop');
Hello,
This is more like a bug in editpage. User with "protect" right should be
able to edit a protected page.
The whole idea of the new user level rights system is to assign to
groups some actions that can be made, naming an action "sysop" is not
really intended :o)
I will try to fix it later, I am ill today ;(
cheers,
--
Ashar Voultoiz - WP++++
http://en.wikipedia.org/wiki/User:Hashar
Hello,
This email is intended to WikiMedia servers administrators.
I installed and configured Nagios ( http://www.nagios.org/ ) wich is a
website to monitor host and services as well as a tool to plan downtime
and comment about service shutdowns.
It can be accessed at:
http://zwinger.wikipedia.org/~hashar/nagios/
Login and password are in our zwinger:doc directory.
Nagios is split in 3 part:
1/ web engine (using cgi)
2/ a daemon
3/ plugins to check services (like check_http, check_ping)
web engine and daemon are currently installed in my home dir on zwinger.
Plugins should be spread on all machines to be able to check for local
services through ssh, wich is not really done right now. Actually it
just test ssh, http, ping, squid availability.
Server can be assigned to a hostgroup. Each group can be assigned a
contact-group (ex: database administrators) with several contacts (shai,
brion, jeronim ..). When a service / host goes down, a notification is
raised to the group, we can even have notification enabled only during
work-hour !
Let's have a tour at the interface:
'Tactical Overview' let you have a global report of what's actually down
through the network, be it disk usage > 90% , host down, ssh not answering.
'Host detail' let you know which servers are up/down while 'Host
service' give you a more detailed view (like http on alrazi is down). In
each view you will see when the host/service got last checked.
'Status overview' aggregate server view per hostgroups (mysql-servers,
apache-servers ...).
The most interesting feature is being able to add comment for every
outage and aknowledge a trouble (for example when you are working on
it). You can try it by having a look at Yang switch for which I briefly
explain why it's an outage. We can even stop monitoring this host.
Notification is available through plugins, actually email is somehow
available but we can have messages sent to pager or on irc :o)
Another feature is the ability to plan downtime window, during that
window, the host will no more be monitored and no notification sent.
Also have a look at the various reporting form availables. It's a good
way to find which host have recurrent troubles.
Basicly I would like, if possible, to have every one look at the
interface and play with it a bit then come back to me with their
impression. If we are interested in having this tool available I will
write a doc to install it cleanly on the foundation servers :o)
cheers,
--
Ashar Voultoiz - WP++++
http://en.wikipedia.org/wiki/User:Hashar
hi everybody
has anyone of you heard of or played around with touchgraphs wikibrowser
(http://www.touchgraph.com/TGWB_101_SS.html)? this is a great step
forward to intuitive wiki navigation!
i really wonder why this hasn't come up onto the agenda long ago. all it
takes for the current version of tgwikibrowser is a plaintext list of
immediate links from one page (or all the pages in sorted order). this
is accomplished by most wiki implementations by giving the url
http://wikiurl/mainpage?action=links&mimetype=text/plain or something
similar.
to start with, mediawiki doesn't seem to know such a feature. why?? if
we had that kind of "specialpage" and if we could adapt tgwikibrowser so
that it could only read out all the links for one page at a time and
retrieve the links of clicked pages on demand, this would produce no
more load than simple navigation through the textual interface.
what's more, one could even think of a semantic navigation, employing
the categories as "big bubbles" in the wikilink graph and their
corresponding articles as "small bubbles" - effectively giving the user
a kind of is-a ontology navigation tool with categories acting as
classes and articles as a kind of class instance similar to visulization
solutions in common ontology editors like protege. think of a wikipedia
that you can navigate in the same way as offered by such beautiful tools
like http://www.visualthesaurus.com/ etc.
anyone in favor of such a development? i could definitely contribute
some concrete ideas...
best
kai, better know as
user:kku
Probably can't really use drives which are 18GB or smaller, unless you know of some cheap box to put manyb them in. Otherwise it may cost more for the box than the drives are worth in performance. I think we have three 18GB drives from Suda sitting on a shelf somewhere. Abosolute minimum total box capacity for any database work is 250GB but 400GB is better. Ariel is 210GB usable and has at most 40GB free with all but one master/binary log file deleted. Once we can split out search duty it will be possible to use smaller slaves - they can contain only cur and searchindex.
The recently ordered slaves have 438GB in 6 disk RAID 0, one about 73GB 10K SCSI, the other 73GB 10K SATA. Given Bacon's 7200RPM performance in RAID 10 compared to Suda at 10K SCSI it seems likely that the SATA will at least match the SCSI. RAID 0 because we just don't care if we lose all data on a slave now we have a fair number of them. Might buy a cold spare drive for each though...:)
For read only we switch to a different server and run it read only.
It would be possible to start a new log on the temporary master and apply those updates to the real master but those would inevitably cause badly garbled article history (at least, probably more pain than that) as people try to redo their edits based on the outdated information on this slave serving as a temporary master.
For LVM are you thinking of having all writes go to all database servers at the same time, instead of via replication? Sounds as though that's what you have in mind...
>Installation isn't yet putting in all the right data for user groups.
>To make your user a sysop, do something like this:
>INSERT INTO user_groups (ug_user,ug_group) VALUES (1,3);Media
>where you would use the user_id and group_id values for the appropriate
>user and group. The default 'Sysops' group presently is id number 3.
>
>-- brion vibber (brion @ pobox.com)
I followed your advice, noticed some changes, but I still haven't the correct rights to edit MediaWiki:Pages .