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 scripting
language.
The second and final RC of 5.1.2 was packaged today and is now available
for download. This has been a purely bug fix RC that addresses a number
of crash bugs and does a bit of further tweaking on the date
functionality. Please test it as much as you can, since pending any
major problems this becomes the final release on January 12th.
The release can be downloaded from here:
http://downloads.php.net/ilia/php-5.1.2RC2.tar.bz2
If you find any issues, please contact the PHP 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.
regards,
Ilia Alshanetsky
5.1 Release Master
As a quick hack on http://test.leuksman.com/ I've added a little notice that
displays at the top of the page if it's been recently modified, reminding the
user to check the edit history to see what's changed.
The color of the box and the approximate age gradually gets duller after about
10 minutes, 30 minutes, and 60 minutes, then finally disappears.
I believe this idea has been bounced around previously but I hadn't seen it
implemented yet. Not sure if we want it, but something like this might be good:
it can remind new visitors that things can change quickly, and not to worry
quite so much about vandalism they may see.
The actual text is ugly and poorly formatted, but hey, it's a demo hack. ;)
There are two parts: SkinTemplate.php is modified to export a JavaScript
variable containing the last modified date as a machine-readable Unix timestamp.
Then a function in MediaWiki:Monobook.js can check the age and poke a message
into the web page.
The advantage of using JavaScript for this is that the HTML output doesn't
change as it ages, so it wouldn't require fancy cache expiration footwork. The
disadvantage is that client-side clocks may be off, so there's a bit of a fudge
factor. Also a small percentage of visitors will have JS off and won't see it,
but it would be nonessential so that's not a big deal.
-- brion vibber (brion @ pobox.com)
Hi all,
I am trying to import the full english wikipedia in mediawiki 1.4. As
its 1.4 it does not have importdump.php. I am trying to use mwdumper.
But it gives a strange error.
I used the following command :
java -server -jar mwdumper.jar --format=sql:1.4 pages_full.xml.bz2 |
mysql -u root -p wikidb
where "wikidb" was the database i created while installing mediawiki1.4
It asks for password ..which i put in ..then it gives the following error:
Error 1146(42SO2) at line 31 : Table 'wikidb.old' does not exist
And then continues running adding pages and their revisions.So it runs
but will it work ? Given i get that error at first ?
... any clues ??
Previously , I have imported into mediawiki1.5 using importdump.php ...
but because of some reasons I have to move to 1.4 now..
You help will be highly appreciated
Candy
I guess this means we can have
+-----+
| C++ | ?
+-----+
:+)
-- Zigger
On 05/01/06, Tim Starling <timstarling(a)users.sourceforge.net> wrote:
> Update of /cvsroot/wikipedia/phase3/includes
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16755/includes
>
> Modified Files:
> Title.php
> Log Message:
> Allow + in titles
>...
Hello!
You are receiving this email because your project has been selected 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 4.4.2 can be found at
http://downloads.php.net/derick/ . If everything goes well, we hope to
release PHP 4.4.2 at the end of next week.
If you find any issues, please contact the PHP 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.
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
We'd like to modify our version of MediaWiki (currently running
1.4.x, but soon to upgrade to 1.5) so that the skin will display
differently depending on the content of the page. For example, if the
source code of page "Foo" contains the text "{{template:bar}}", page
"Foo" would show a different site logo than other pages on the site,
or it would use a different CSS stylesheet.
Is there an existing way to do this? If not, can someone point me to
the spot in the codebase where we should look if we need to hack this
ourselves?
--Sheldon
Hi,
I cannot understand why Special:Unwatchedpages is not listed in
Special:Specialpages.
is there any special reason?
Thanks,
Frieda
___________________________________________
http://it.wikipedia.org/wiki/Utente:Frieda
Good Wikitech-l Folk,
I write in the hopes of getting some input or ideas about an extension
I've written that attempted to solve a particular maintenance and
navigation problem I think I have. I most interested in whether it's
anything like The MediaWiki Way of doing things.
My problem: I have a lot of documents with a fairly straight-forward a
priori order (these are digitized notebooks and papers of family
memorabilia), where lots is hundreds of individual page-sides. I wanted
a couple of things:
To put them in a wiki to allow for them to be viewed, commented on,
linked, &c.
To lay down the original order the page-sides occured.
Sure, my audience is going to come along and add other connections, but
this is the first path they can start with.
One way I could have done this was to have each page contain a link to
the next and previous pages explicitly. Straihghtforward, and fairly
easy to have a bot go through and programmatically add the links. But
this approach also struck me as a maintenance problem: suppose I got
something wrong the first automation, and wrong in a tedious way to fix?
Suppose new information comes along later than makes us want to
re-arrange this order? Suppose I don't want to just write a bot to do
this for me?
If, on the other hand, instead of explicit links, something like
MediaWiki's Categories were added to each page, something that placed
the specific page in a broader context through code, then that would be
preferable. Categories, though, didn't quite answer, they are really
for grouping things that have some trait in common together, not for
sequencing many things.
Suppose one page in the wiki contained a map of some other pages? If I
included a tag in a page that refered to some map page, then my
extension could look up the map, find the context of the referring page,
and print out suitable navigation links.
Some crufting around later, Nav.php was born: at a little sandbox
mediawiki 1.5.4 at
http://www.nigelk.org/wiksand/index.php?title=Nav_Map_Demonstration,
find a couple of demonstrations of this Nav.php extension I've written.
Is there a built-in or better way of trying to solve this problem I
think I have? Would it be thought of differently by the mediawiki
developers here? Is this kind of lashup of interest to anyone? Is my
php completely horrible? Any thoughts or inputs, either here on the
list or in discussion at that sandbox above, is appreciated.
Respectfully submitted,
Nigel Kerr
nigelk(a)nigelk.org