Un message de Nganguem Victor t'attend...
L'expéditeur et le contenu seront visibles seulement par toi et tu peux le supprimer à tout moment. Tu peux aussi y répondre directement au travers du messenger. Pour découvrir qui est à l'origine du message, suis simplement ce lien:
http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6
D'autres personnes sont aussi présentes:
Oded (Tel Aviv, Israël)
Priya (Udaipur, Inde)
Chika Reginald Onyia (Pnompen', Cambodge)
RajaYogi BK (Udaipur, Inde)
Karuna (Udaipur, Inde)
...Qui d'autre?
http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6
Les liens ne fonctionnent pas dans ce message? Copie les dans la barre d'adresse de ton navigateur.
Tu as reçu cet email suite à une requête de Nganguem Victor sur notre système. S'il s'agit d'une erreur, ignore simplement cet email. La requête sera alors effacée du système.
Merci,
L'équipe Badoo
Courrier automatique de Badoo suite à l'envoi d'un message à ton attention sur Badoo. Les réponses ne sont ni stockées, ni traitées. Si tu ne veux plus recevoir de message de Badoo, fais-le nous savoir:
http://eu1.badoo.com/impersonation.phtml?lang_id=6&mail_code=21&email=media…
Hi,
Is there a way to tag pages/titles NOT to be included in search result?
We want to exclude obsolete pages from search but just don't want to
delete them yet.
Thanks,
Toshi
On my intranet 1.16.2 wiki, with respect to email:
- Users can update their email addresses under preferences, save,
receive a confirmation email, and see that their address is
authenticated after clicking the link
- I (skew) receive notfications on all changes from everyone
(via $wgUsersNotifiedOnAllChanges)
- No users receive notifications for pages they're watching
- If I remove myself from $wgUsersNotifiedOnAllChanges, I don't
receive any notifications (after asking others to edit pages I
created that I'm watching)
I found plenty of messages on smtp setup, but nothing related to what I'm
seeing. Given how well it handles email, I'm not sure what else to look at
for why users can't get notifications. If anyone can offer any insights,
I'd appreciate it.
Here are my givens:
My LocalSettings.php file includes
----------------------------------------------------
# Default user options
$wgDefaultUserOptions['enotifminoredits'] = 1;
$wgDefaultUserOptions['enotifrevealaddr'] = 1;
$wgDefaultUserOptions['enotifusertalkpages'] = 1;
$wgDefaultUserOptions['enotifwatchlistpages'] = 1;
$wgDefaultUserOptions['watchcreations'] = 1;
$wgDefaultUserOptions['watchdefault'] = 1;
$wgDefaultUserOptions['watchdeletion'] = 1;
$wgDefaultUserOptions['watchmoves'] = 1;
# Email settings
$wgEmailAuthentication = true;
$wgEnableEmail = true;
$wgEnableUserEmail = true;
$wgSMTP = array(
'host' => xxxx.xxxx".com",
'IDHost' => xxxx.xxx".com",
'port' => 25,
'auth' => false,
'username' => "",
'password' => ""
);
$wgEnotifUseJobQ = true;
$wgEnotifUseRealName = true;
$wgEnotifUserTalk = true;
$wgEnotifWatchlist = true;
# These people receive emails on all changes
# Declare this twice so it works for all versions (comma to add more)
$wgUsersNotifiedOnAllChanges = array( 'skew' );
----------------------------------------------------
Under my preferences, I have these set:
----------------------------------------------------
E-mail confirmation: Your e-mail address was authenticated on May 4, 2011
at 23:42.
Enable e-mail from other users
E-mail me when a page on my watchlist is changed
E-mail me when my user talk page is changed
E-mail me also for minor edits of pages
Reveal my e-mail address in notification e-mails
E-mail me on replies to a thread I am watching
Along with
Add pages I edit to my watchlist
Add pages I move to my watchlist
Add pages I delete to my watchlist
Add pages I create to my watchlist
Watch threads that I create or reply to
(all of the Hide options are unset)
----------------------------------------------------
Thanks.
- skew
When a sysop needs to block a user using Special:BlockIP, there are boxes
that control optional behavior. One of these is "Automatically block the
last IP address used by this user ...". This always is set by default on
our wiki (we are using 1.16.2). We want to have this unset by default.
I have looked around for any configuration settings that would allow us
to deselect this option by default (e.g., http://www.mediawiki.org/wiki/
Help:Blocking_users) but have found nothing. Is there a global that
controls this or perhaps some other configuration setting?
--
-- Dan Nessett
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm happy to announce the availability of the first beta release of
the new MediaWiki 1.17 release series.
Please try it out and let us know what you think. Don't run it on
any wikis that you really care about, unless you are both very
brave and very confident in your MediaWiki administration skills.
MediaWiki 1.17 is a very large release that contains many new
features and bug fixes. This is a summary of the major changes of
interest to users. You can consult the RELEASE-NOTES file for the
full list of changes in this version.
*********************************************************************
What's new?
*********************************************************************
PHP 5.2.3
- ---------
We now require PHP version 5.2.3 or later. Why? Well, it brings with
it some tools for your beloved developers. It was released on June
1, 2007, so we believe this requirement will not be a hassle for
administrators. Be sure to check your PHP installation and contact
your host if it runs an outdated PHP version.
New installer
- -------------
MediaWiki 1.17 is shipping with a completely redesigned installer to
fix a lot of outstanding bugs, clean up the code quality, and make
it easier to use. Notably, you can now run upgrades from the web
without having to move LocalSettings.php. A couple of other notable
changes:
* The installer can now be fully localized like the rest of the
software and contains numerous help dialogs.
* The installer script directory has been renamed from config/
to mw-config/.
* You now download your generated LocalSettings.php at install
completion, rather than writing it straight to the
configuration directory. The previous behavior was a security
risk.
* IBM DB2 and MSSQL support were dropped from the installer.
ResourceLoader
- --------------
As web browsers have become more capable, the software that
MediaWiki runs on them has become more complex. This trend has
resulted in developers needing an efficient way to package and
deliver code to web browsers. To address this, MediaWiki 1.17
ships with ResourceLoader: a framework which combines and minifies
CSS and JavaScript before delivering them to the web browser.
ResourceLoader improves performance, while also making it easier to
write client-side features. ResourceLoader allows developers to
organize scripts, styles, and messages into named modules. Any
number of modules can be loaded through a single request, improving
page load times. Code is minified automatically and loaded when
needed, reducing unnecessary downloads. Other advanced features
include the ability embed images in style sheets using data URIs, or
automatically flipping horizontal information in style sheets for
right-to-left user interfaces.
Category sorting
- ----------------
Category sorting has been drastically improved.
* Sorting is now case insensitive.
* Sub-categories, pages and files can now be paged separately.
* When several pages are given the same sort key, they sort by
their names instead of randomly.
Language support
- ----------------
As with every release, MediaWiki 1.17 brings improved support for
languages in MediaWiki, with improved translation and features for
the many supported languages.
New languages:
* Moroccan Spoken Arabic (ary)
* Banjar (bjn)
* Kabardian (Cyrillic) (kbd-cyrl)
* Latgalian (ltg)
* Minangkabau (min)
* Dutch (informal) (nl-informal)
* Rusyn (rue)
API
- ---
API bug fixes and new features have been added to 1.17, providing
more options for input and output.
* API output can now be formatted by PHP's var_export() (format
type is dbg/dbgfm).
* An API module was added to list page properties.
* PARAM_REQUIRED can now be used on parameters, to have the API
enforce existence before code even reaches the module.
* The API now has a Really Simple Discovery module, useful for
publishing service information by the API.
The API contains 3 breaking changes against previous releases:
* action=patrol now requires POST.
* The patrol token is no longer the same as edit token.
* Session keys returned by ApiUpload are now strings instead of
integers.
Other
- -----
* Interwiki links in articles are now recorded in a separate
table.
* Users can now add CSS and JS to all skins by using
User:<name>/common.css and User:<name>/common.js.
Release notes
- -------------
Complete release notes are at
http://www.mediawiki.org/wiki/Release_notes/1.17
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.17/mediawiki-1.17.0beta1.tar.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.17/mediawiki-1.17.0beta1.tar.gz.s…
Public keys:
https://secure.wikimedia.org/keys.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3CmmwACgkQgkA+Wfn4zXl+EwCfZqqPPuFrSSF68hxzQfM6SXgr
gH0An2xr18+vNml2pv0D4XSPuLRDf/ie
=m5Rw
-----END PGP SIGNATURE-----
We had a great talk at recent SMWCon Spring 2011 on SEO, you check it out
at http://semantic-mediawiki.org/wiki/File:SMWCon_2011_SEO_Presentation.pdf.
it has more info than extensions and work for mediawiki in general.
Jesse
On May 4, 2011 11:02 PM, "Dorem - Jérémie Bouillon" <jeremie(a)dorem.info>
wrote:
Just added to MediaWiki.org:
http://www.mediawiki.org/wiki/Extension:WorkingWiki
WorkingWiki is a software extension for MediaWiki that makes a wiki into
a powerful environment for collaborating on publication-quality
manuscripts and software projects. It's designed for research labs'
wikis, but may have diverse other uses as well.
(I probably should have made it public long ago, but there was a big
refactor and it took a long time to settle out...)
Lee Worden
McMaster University
On 03/05/11 14:46, Daniel O'Connor wrote:
> Hey guys,
> I've just done a QA fix for http://pear.php.net/bugs/bug.php?id=16271 as
> it's been open for ~2 years - you might want to incorporate it upstream.
Thanks for that, I've done it.
> What's the future of File_Ogg - live in wikimedia, offered via PEAR channel;
> or live in pear; offered by pear channel + svn externals from wikimedia?
I'd like PEAR to be treated as the primary distribution channel, and
the OggHandler version to remain as a bundled copy.
-- Tim Starling