Somewhere around 17:20-17:30 UTC, Cogent readvertised routing to our primary IP
address block in Tampa, blocking access to the site for most people.
Partway through the period, wikis were placed into read-only lock so the few
people who could access it (mostly from AOL ;) were unable to edit without
review from the public.
The route was temporarily restored around 19:55, and read-write was restored to
the wikis at 19:59.
The old IP range will no longer be available to us as of Monday.
PowerMedium has assigned us a new IP space which is under their control (unlike
the old IPs which were leased from Cogent under an older contract), and we will
be transitioning to them over the weekend.
We have heard several conflicting things about exactly why and how our IP space
got dropped; more will be said when we have firmer knowledge.
-- brion vibber (brion @ pobox.com)
Ok this time I'm sure it's not me :)
I'm getting alternating this:
------------
ERROR
The requested URL could not be retrieved
While trying to retrieve the URL: http://en.wikipedia.org/wiki/
The following error was encountered:
* Valid document was not found in the cache and only-if-cached
directive was specified.
You have issued a request with a only-if-cached cache control
directive. The document was not found in the cache, or it required
revalidation prohibited by only-if-cached directive.
Your cache administrator is nobody.
Generated Fri, 18 Aug 2006 17:27:37 GMT by lily.knams.wikimedia.org
(squid/2.5.STABLE13)
----------
and the normal donation request page.
Steve
I am running a mediawiki 1.7.1 on a PC of my company, and the email server
is another pc on the intranet. I setted the mailserver address in php.ini,
and enabled the mail function in mediawiki. Once I test the mail function in
mediawiki I got the message like this:
"Error sending mail: mail()
[function.mail<http://192.168.21.25/ewiki/function.mail>]:
SMTP server response: 501 5.5.4 Invalid Address"
However, the following script in a soly php file has been tested working
well.
<?php
// The message
$message = "Line 1\nLine 2\nLine 3";
// In case any of our lines are larger than 70 characters, we should use
wordwrap()
$message = wordwrap($message, 70);
// Send
mail('caffinated(a)example.com', 'My Subject', $message);
?>
I wonder is it a bug of mediawiki?
BTW, I am running mediawiki on windows xp sp2 professional chinese edition,
apache 2.0.58, php 5.1.4 and mysql 5.0.22 .
Hi All,
If I go to http://en.wikipedia.org/Tokyo (note the missing "/wiki"), I get a 404 page that contains a 5 second-client side refresh
tag like so:
<meta http-equiv="Refresh" content="5; URL=http://en.wikipedia.org/wiki/Tokyo">
Is there any chance we could follow the great example of the PHP folks, and immediately give the user what they really want (e.g.
http://php.net/date , which instantly shows the user the content of the http://php.net/manual/en/function.date.php page) ?
In other words, use a server-side HTTP redirect/location header, rather than a client-side refresh?
This would be quicker for the user, friendlier, more forgiving, and just generally a nice touch.
All the best,
Nick.
I just found
http://en.wikipedia.org/wiki/User:Cacycle/wikEd
Quoting from said page:
"wikEd (alpha) is an editor extension that adds enhanced text processing
functions to Wikipedia edit pages. Currently it works only for Mozilla
Firefox, Mozilla, and Mozilla SeaMonkey browsers. wikEd is a complete
rich-text editor and comes with many MediaWiki features."
Might be interesting regarding WYSIWYG discussions.
Apologies if this is already well known (I did some quick searches but
found nothing here).
--Ligulem
An automated run of parserTests.php showed the following failures:
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test Template infinite loop... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: HTML Hex character encoding.... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Passed 412 of 429 tests (96.04%) FAILED!
On 8/17/06, Sabine Cretella <sabine_cretella(a)yahoo.it> wrote:
>
> > So if it substitutes letters which are not pronounced, what are those
> > unpronounced letters in 'o and 'a? My guess is that they are a special
> > exception which are always written 'o and 'a perhaps historically having
> > had an official letter. If this is the case we could say the rule is:
> >
> lo + la + le (plural form) d''e also exists
> > A double apostrophe occurs when contraction is made with the definite
> > articles, these being always written with an apostrophe.
> >
> > So my further questions:
> > a) Is there a "full spelling" for 'o and 'a?
> >
> it is not used - you only find it in veeeery old texts. nowadays they
> only use 'o, 'a and in plural form 'e
I just found 'a, 'e, and 'o on en.wiktionary. I am going to add la,
le, and lo as
alternative spellings and mark them as obsolete. Would you say this is
correct?
> > b) Are there any words besides 'o and 'a which take an apostrophe even
> > when not part of a contraction?
> >
> yes - 'nfrumma,
>
> 'mbruglià
English Wiktionary also includes 'a = from, 'e = of, 'llustrà = to illustrate,
'ntréllece = vivaciously, 'nzularchìa = jaundice
> also there it substitutes a letter - in all cases the substituted letter
> is a vowel (as much as I have in mind now
>
> and there's the article ll' used in front of a vowel
>
> sorry, but things come in mind while writing and imagining sentences -
> consider that I know some grammar rules, but I don't know all of them -
> my Neapolitan comes from everyday use when talking with people in this
> region. The few rules I know help me to write as correctly as possible
> and according to Carmine who proofreads my texts they are quite well and
> getting always better - during the last ones there were only some really
> minor changes. If we need further, more exact information I need to find
> out where I can get a grammar book - it is impossible to find it here
> where I live (that might seem strange, but it is like that).
No problem. Linguists create grammars by interviewing people who speak
them and it apparently works best if these informants can't analyse their
language grammatically. We're going very well so far! (-:
Andrew Dunbar (hippietrail)
> Best, Sabine
> Chiacchiera con i tuoi amici in tempo reale!
> http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/wikitech-l
>
--
http://linguaphile.sf.net
For your interest, it looks like Apple has come to the party with a
wiki of its own, without the need for people to learn markup language:
http://www.apple.com/server/macosx/leopard/wikiserver.html
We've been using MediaWiki as our office intranet over the years but
it's never been adopted to a level that we think it could be, because
of the requirement that users learn wiki markup. For this reason
we'll be ditching MediaWiki in our office next year for Apple's Wiki
Server.
The reason I'm posting this is simply put forward the view that I
hope WYSIWYG or some relevant variant will be developed for Wikimedia
projects in the near future, because I think the hurdles that stop
many people from participating on our office intranet apply equally
to Wikimedia projects. And the hurdle is not that wiki markup is
"difficult" or "hard to learn" but that it is intimidating and time-
consuming to learn.
I have little doubt that one day using wiki markup only to edit
websites like Wikipedia will be seen as an anachronism, even more so
as other alternatives to MediaWiki (such as Apple's Wiki Server) come
online, but there's a few hurdles to overcome yet and they're not all
technical ones as far as I can work out.
It's always surprised me that WYSIWYG editing has not been made a
high priority for Wikimedia, considering the fact that it was founded
on the idea of broad participation. Although technical difficulties
are often put forward as the reason, the biggest obstacle, it has
often seemed to me, is an installed base of Wikipedians who see wiki
markup as a way of protecting their territory and minimising
participation by others. I've even had people argue that wiki markup
is some kind of "intelligence" hurdle that people should have to
overcome before being allowed to edit Wikimedia projects. Somehow
this needs to be overcome if WYSIWYG is to gain traction and get a
higher priority it seems to me.
Thanks to those who have been working on WYSIWYG for MediaWiki,
particularly in trying to integrate FCKEditor, and I wish you well.
However, if integrating an editor into the current environment is so
difficult maybe there needs to be a new approach, such as developing
new software/syntax with some type of WYSIWYG editor built in from
the start? Worth a discussion at least, I should imagine.
Cheers,
Christiaan
P.S. I originally posted this to mediawiki-l(a)wikimedia.org but that
was probably the wrong list to post to.
Hello!
You are receiving this email because your project has been select to
take part in a new effort by the PHP QA Team to make sure that your
project still works with PHP versions to-be-released. With this we
hope to make sure that you are either aware of things that might
break, or to make sure we don't introduce any strange regressions.
With this effort we hope to build a better relation between the PHP
Team and the major projects.
If you do not want to receive these heads-up emails, please reply to
me personally and I will remove you from the list; but, we hope that
you want to actively help us making PHP a better and more stable tool.
The second release candidate of PHP 5.2.0 was released today, it can
be downloaded from http://downloads.php.net/ilia/. A great deal of
work was done since RC1 to stabilize the code, with over 50 bug fixes
since then. I'd like to ask everyone to try this release, in
particular paying attention to input processing, something that has
changed a fair bit with the introduction of the filter extension. If
you discover any (we hope not) please notify PHP's QA team at "php-
qa(a)lists.php.net".
In case you think that other projects should also receive this kinds
of emails, please let me know privately, and I will add them to the
list of projects to contact.
Best Regards,
Ilia Alshanetsky
5.2 Release Master
An automated run of parserTests.php showed the following failures:
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: HTML Hex character encoding.... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Passed 413 of 429 tests (96.27%) FAILED!