Sebastien BARRE said:
> At 3/16/2005 11:54 AM, you wrote:
>
>>I don't want you seeing that I viewed [[double-sided dildo]] prior to
>>viewing [[GAU-17]].
>
> And how would you view that ? Of course it should not be implemented
> server-side, that would be dumb, but client-side, as a cookie/session
> (like I did in my extension). And you should have a choice to disable
> it.
Take your favorite browser and visit a few Wikipedia pages.
Done that? Okay, here's what to do next.
Now take your mouse up to the top left of your browser. There is usually
a button marked with a left-facing arrow. Beside it there is usually a
small downward arrow. Click on the downward arrow and a drop-down box
will appear, containing a list of all the places on Wikipedia that you
have visited. Select one of the items on the list and you will be taken
back to that item.
Why reinvent the wheel?
> What about diffs ? I hope they are protected too ?
I think so; at least I could not hack around that.
> What about medias ? Sounds a little more difficult to do.
Images are not used in my wiki, as my provider runs PHP in safe mode and
the whole upload does not work. I have not looked at that aspect. I
would have to check whether the db table has any restriction column at
all.
Brion has a very good point in Templates - this is an open hole that has
to be closed.
Thanks for the feedback!
MaPhi
Hi,
I want a table of contents to be displayed. My main page has more than seven
pieces of headline text, but my table of contents is not being created. A
past suggestion was to force it by using __FORCETOC__, or in a position
other than just before the first heading by using __TOC__. Unfortunately I
don't understand what this means because I am just an eager novice?!?
What piece of code should I be editing with these lines?
Thanks in advance,
Alison
Alison,
Add these as wiki-text into whichever page you want the table of contents to
appear in.
Ryan Lane
NAVOCEANO
> -----Original Message-----
> From: wikitech-l-bounces(a)wikimedia.org
> [SMTP:wikitech-l-bounces@wikimedia.org] On Behalf Of Alison Russell
> Sent: Wednesday, March 16, 2005 8:30 AM
> To: wikitech-l(a)wikipedia.org
> Subject: [Wikitech-l] Automatic creation of Table of Contents after
> three or more headers on a page??
>
> Hi,
>
> I want a table of contents to be displayed. My main page has more than
> seven
> pieces of headline text, but my table of contents is not being created. A
> past suggestion was to force it by using __FORCETOC__, or in a position
> other than just before the first heading by using __TOC__. Unfortunately I
>
> don't understand what this means because I am just an eager novice?!?
>
> What piece of code should I be editing with these lines?
>
> Thanks in advance,
> Alison
>
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Hi everyone,
as I needed some basic protection on some pages of my wiki, I
went ahead and implemented a simple ACL mechanism. This is
based on the 1.3.11 version of the code, I did not yet look
at the 1.4 stuff. I plan to adapt 1.4 when I'm upgrading my
site, which will not happen before the final release.
The changed files can be found at
http://www.maphi.net/SimpleACLs-1.3.11.zip if anyone is
interested.
Now, as I have no idea on how the submittal process works.
Is there a chance to include this into the wiki itself, or
does it have to be for 1.4 in order to be included?
Do I need to submit the changes in a specific format, like
a diff? If so, which would be the right tool to use? I'm
working on a Windows box, using WinDiff - I guess that's not
the right tool here :)
Some background on what I did:
The page SpecialMakesysop allows Developer-Sysops (the user
needs both rights) to give arbitrary rights to users. This
can be any string, comma-separated for multiples, with a total
length of 255 characters because of the DB limit. With the
exception of sysop, bureocrat, developer, bot, and hidden
(see below) there is no special meaning to any right.
I changed Skin.php, SkinCologneBlue, and SkinPhptal, so that
the protect button is available to any user that has any
right. As these rights need to be given by someone else,
vandalism should not be an issue.
Protecting a page sets its restrictions to the rights of the
protecting user. If the user has more than one right, he can
specify which of his rights should be applied by editing the
restriction string. This is rather error prone, but in my
wiki, people have only one right.
The protect page contains a checkbox to hide a page from
public view. If this checkbox is set, the "hidden" restriction
is added to the page as well.
People can only edit a page if they have all rights (minus
hidden) that the page requires. This is straight from the
existing code. They also need all rights to unprotect the page.
People can only read hidden pages if they have at least one
of the necessary rights.
Sysops can always read, edit, and unprotect all pages.
I did a small change to SearchEngine, so that the search does
not give previews if the feature is enabled. Users will see
if their search term appears in a hidden page, but that's it.
I left RecentChanges alone, so the page names and change
comments are still visible to everyone.
The whole feature can be enabled by setting $wgEnableSimpleACLs
to true in LocalSettings.php. You also need to create one
developer,sysop user using SQL as described in
http://meta.wikimedia.org/wiki/Setting_user_rights_in_MediaWiki.
This user then can give rights to other users.
Comments (and bug detections) are welcome.
Regards, MaPhi
I noticed this feature being used in pages like:
http://www.wikicities.com/wiki/User_talk:Jasonr
where each headline text addition is automatically added to a dynamic table
of contents.
Is this a feature of MediaWiki or does anyone know what code is required to
implement this? I think its a really neat function.
Thanks in advance,
Alison
Hi,
I have added a Google search box to my Wiki. I am using 1.4 beta-6. I have
added it to monobook.php which is fine, but the length of the Google section
extends right across the page. I want it to be the same width as the
navigation, search and toolbox section. I think I should be adding it to the
code that controls the left hand side panel of each page, the quickbar I
think its called?!?
Where do I find that code? And where should I add the Google link so that
the text box and Google image appear after the search section and before the
toolbox section along the left of the page?
I want it to look like this wiki
http://creatures.wikicities.com/wiki/Main_Page
Thanks in advance,
Alison
(Where to report this?)
Opening
http://de.wikipedia.org/wiki/Portal-Standard-Software
repeatedly produced the following output:
---------------------------------------------------
Warning: mysql_query(): Unable to save result set
in /usr/local/apache/common-local/php-1.4/includes/Database.php on line
324
Unable to free MySQL result
Backtrace:
Database.php line 469 calls wfdebugdiebacktrace()
User.php line 464 calls databasemysql::freeresult()
SkinTemplate.php line 254 calls user::getnewtalk()
OutputPage.php line 417 calls skinmonobook::outputpage()
OutputPage.php line 614 calls outputpage::output()
Database.php line 360 calls outputpage::databaseerror()
Database.php line 309 calls databasemysql::reportqueryerror()
Parser.php line 3005 calls databasemysql::query()
Parser.php line 195 calls parser::replacelinkholders()
OutputPage.php line 243 calls parser::parse()
Article.php line 795 calls outputpage::addprimarywikitext()
index.php line 127 calls article::view()
-----------------------------------------------------
Regards,
Nino
Matt Kingston wrote:
>Sounds to me like it would be a sort of "expert" system. Consider:
>
>The Wikipedia article Anne Frank could have tags at the bottom like
>
>{WasBorn:1929}
>(IsA:Woman}
>{Wrote:The_Diary_Of_A_Young_Girl}
>{BornIn:Germany}
>
>you get the idea. These facts or relationships tie together different articles in a more structured way. Presumably a user interface system could then be written that would take all the data and be able to do things like list off all the female german authors of the twentieth century.
>
>Since facts aren't tied to one language, the "relationship database" could span all languages (since there is already a system for linking articles on the same subject to different languages). A relationship would have a certain ID internally with "translations" to different languages. So after typing in: {BornIn:Germany} in the english version, the computer would find the french equivelent of the relationship -BornIn- and the french equiv of Germany and update the french Anne_Frank article accordingly.
>
>Anyway, I'm no specialist in the area, I do know that there are some internet projects of this sort trying to teach computers "common sense" {Lion IsA Animal} I don't know how much success they've had. It might be usefull, but I'm not so sure it fits into wikipedias mandate.
>
>Just my three cents.
>
>Matt
>
>
>
I'm working on something like this already; it's an experimental Wiki
with the ability to embed special links, in this case with the format
[[property = value]].
These are then used to maintain entries in a tuple table, which is in
turn used to generate an alternate RDF view of the page.. Yes, you can
do [[is a = thing]]. Bits of Web GUI are generated based on class
deifinitions, and you can also do things like import CSV tables, and I
hope export them as well. I'm currently working on [[same as = thing ]]
and logical inference, as well as extending this to trans-wiki inference.
Hopefully some of this experience will be useful, when it becomes time
to add this to Wikipedia. For now, it won't hurt at all to use templates
to encode this sort of information, so some data will be available
first, before the knowledge-mining software gets written.
-- Neil
I made a late checkin on the 1.4 branch today.
The problem was with Hooks.php, the event-handling mechanism for
optional functionality and third-party extensions. wfRunHooks(), the
interface for mainline code to raise events for hooks to handle, was
using PHP's variable-argument syntax so you could give different
parameter sets to different events:
wfRunHooks('Event1', $param1, $param2, $param3); # three params
wfRunHooks('Event2', $param4, $param5); # just two params
The problem with this is that the var args syntax silently changes
pass-by-reference semantics to pass-by-value semantics. So events that
should allow modifying parameters do not. For example:
$wgEventHooks['Event3'][] = 'MyEvent3Handler';
# ...
function MyEvent3Handler(&$str) {
$str .= " and so on.";
return true;
}
# ...
$somestring = "Eggs, bananas, bacon";
# NOTE: OLD CALLING FORMAT
if (wfRunHooks('Event3', &$somestring)) {
echo $somestring; # prints "Eggs, bananas, bacon"
}
After some consulting with PHP gurus, the best solution I could come up
with was to pack the params in an array when passing them to
wfRunHooks(). Now the last few lines are:
if (wfRunHooks('Event3', array(&$somestring))) {
echo $somestring; # prints "Eggs, bananas, bacon and so on."
}
Adding a reference to an array keeps its "reference-ness".
I wanted to make sure that the hooks technology was at least worth
experimenting with in the 1.4 branch, and that the interface (from both
sides) was relatively stable. Hooks need to be able to modify their
parameters to be useful, so I made these changes.
I've done pretty extensive testing of all the points in 1.4 where
wfRunHooks() is called, and it seems to be stable.
~Evan
--
Evan Prodromou
evan(a)bad.dynu.ca